SNAX Creator-2 Configuration and Control Manual

Subsystem Control Facility
Introduction to SCF for SNAX Creator-2
117143 SNAX Creator-2 Configuration and Control Manual 1–5
screening are called sensitive commands. Sensitive commands are limited to the
following user IDs:
Members of the super group (group ID 255)
Members of the user group that owns the process to which the command is sent.
Other commands make no changes, but simply allow the SCF user to view
information. SNAX Creator-2 does not perform any security checking on these
commands, but allows any user to perform them. These commands are called
nonsensitive commands.
The command description for each sensitive command in Section 4, “SCF Commands
for SNAX Creator-2,” clearly states that the given command/object-type pair is a
sensitive command.
General Command Format
An SCF command always begins with a keyword identifying the command (such as
ADD, START, or STATS).
For SCF commands that pertain to an object, the keyword is always followed by an
object type and an object name. For example, the following command deletes the
ENTRY object called $CREA.MYENTRY:
DELETE ENTRY $CREA.MYENTRY
If additional information is required, the object name is followed by a comma and the
parameters required to further specify the action to be taken. For instance, the
following command changes the value of the TEXT attribute for the ENTRY object
named $CREA.MYENTRY:
ALTER ENTRY $CREA.MYENTRY, TEXT "a character string"
In some commands that provide displayed information, such as the INFO and
STATUS commands, you can specify the DETAIL keyword to obtain a more lengthy,
detailed information display.
The full syntax of each subsystem-specific SCF command for SNAX Creator-2 is given
in Section 4, “SCF Commands for SNAX Creator-2.” The syntax of SCF commands
that are not subsystem-specific is given in the Subsystem Control Facility (SCF) Reference
Manual.
Objects SCF controls a wide variety of subsystems, the individual components of which are
called objects. Each object has an object type and an object name. The object type
describes the kind of object, such as APPL (application) or SU. The object name
uniquely identifies an object within the system. Object names usually follow a
consistent set of naming conventions.
The SNAX Creator-2 subsystem is structured hierarchically, with objects of one type
logically subordinate to objects of another type. For example, in a SNAX Creator-2
subsystem, objects of type CONNECTION are subordinate to objects of type SU.