SIRMETH command: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
|||
| Line 15: | Line 15: | ||
SUBSYSTEMCONTEXT csubsys | ALL} - | SUBSYSTEMCONTEXT csubsys | ALL} - | ||
[SUBSYSTEM subsys [NONPRE] ] | [SUBSYSTEM subsys [NONPRE] ] | ||
For more information about the SIRMETH command, see | For more information about the <var>SIRMETH</var> command, see [[System and Subsystem classes#Using SIRMETH to specify security rules|"Using SIRMETH to specify security rules"]]. | ||
<!-- SPY - OWNED BY ITS --> | <!-- SPY - OWNED BY ITS --> | ||
<!-- SUSPEND - OWNED BY CCA --> | <!-- SUSPEND - OWNED BY CCA --> | ||
Revision as of 22:44, 15 November 2012
The SIRMETH command provides system managers with the ability to allow specific subsystems or even all users, whether or not they are system managers, to do certain things that previously only system managers and pre-compiled subsystem procedures could do. These things are:
- Set system globals and strings.
- Set subsystem globals and strings.
- Set a subsystem context.
SIRMETH command syntax
SIRMETH {ALLOW | DISALLOW} -
{SYSTEMSET | SUBSYSTEMSET | -
SUBSYSTEMCONTEXT csubsys | ALL} -
[SUBSYSTEM subsys [NONPRE] ]
For more information about the SIRMETH command, see "Using SIRMETH to specify security rules".