OSI/MHS Configuration and Management Manual

Management Environment for OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
2-15
SCF Command Format
•
The ALTER command omits the GROUP keyword because the preceding
ASSUME command specified that keyword.
•
The object name has three parts:
•
$ZMHS is the OSI/MHS subsystem name.
•
#RS is the RS CLASS name.
•
RSGROUP1 is the RS GROUP name.
•
This ALTER command is valid only if the GROUP object to which it applies has
already been added.
The following ASSUME command saves even more keystrokes:
ASSUME GROUP $ZMHS.#RS
This command could be followed by:
ALTER.RSGROUP1, attribute ...
ALTER.RSGROUP2, attribute ...
and so on.
SCF assumes that the names in the ASSUME command completely qualify the names
in the ALTER command. The periods before RSGROUP1 and RSGROUP2 indicate
that these are extensions of the object name and not object types. Therefore, SCF
constructs complete GROUP names that include the required periods:
$ZMHS.#RS.RSGROUP1 and $ZMHS.#RS.RSGROUP2.
The ASSUME command is most helpful when you use SCF interactively. It can also
be used in command files but should be used sparingly in the interest of readability.
For example, the subsystem $ZMHS could have a route named ROUTE7 through MTA
#BOSTON1 and a route named ROUTE7 through MTA #DENVER1. In this case, to
look up the attributes of ROUTE7 through #BOSTON1 is easy if the ADD command in
the configuration file identifies the route as follows:
ADD ROUTE $ZMHS.#BOSTON1.ROUTE7, attribute, ...
If instead the ADD command had the form
ADD .ROUTE7, attribute, ...
you would have to scan backward in the file for the applicable ASSUME command.
Nonsensitive Commands
A nonsensitive command is informational. This type of command cannot add or delete
an object or change its state or configuration. A nonsensitive command can be issued
by any user or program allowed to access the subsystem. The subsystem imposes no