SNAX/XF and SNAX/APN Configuration and Management Manual
Introduction to SCF for SNAX/XF and SNAX/APN
SNAX/XF and SNAX/APN Configuration and Management Manual—425836-006
11-9
How SCF Works
SNAX/XF and SNAX/APN Object States
Each object has an operational state, such as STOPPED or STARTED. The set of
states an object can assume varies depending on the object type. Some subsystem
objects are always in the same state: for example, a SNAX/XF SESSION object is
always in the STARTED state.
The operational state of an object can affect the use of SCF commands to operate on
the object. For example, you can use the ALTER SUBSYS command only when the
SUBSYS object is either in the STOPPED state, or in the STARTED state with no
subordinate objects configured.
Some SCF commands include an optional SEL parameter that selects only objects that
are (or are not) in a particular object state. The SEL parameter has the following
syntax:
SEL [NOT] state
When the SEL option is used without the NOT keyword, the command affects only
those objects that are in the specified state. When the SEL option is used with the NOT
keyword, the command affects only those objects that are not in the specified state.
For example, the following command deletes the LINE object named $SNAP2 only if it
is in the STOPPED state:
DELETE LINE $SNAP2, SEL STOPPED
Object Attributes
Attributes are the named, configurable characteristics of objects. Attributes are
specified as parameters to the ADD, ALTER, and INFO commands. The attributes of
an object depend on its type; for example, TIMEOUT is an attribute of a SNAX/XF
LINE object. The attributes for SNAX/XF and SNAX/APN objects are described in
Section 4,“Attributes for SNAX/XF and SNAX/APN.”
How SCF Works
For commands that relate to a subsystem or its objects, SCF translates the command
into a formatted message for SCP, which then communicates with the appropriate
subsystem to perform the specified task.
SCF accepts commands from a workstation, a disk file, or an application process. It
sends display output to a workstation, a file, a process, or a printer.
If you start SCF interactively, the TACL RUN command specifies the input source
and output destination.
If you start SCF by using a process creation system procedure, the startup
message specifies the input source and output destination. Subsequent SCF
commands can change the input source and output destination.