OSI/AS Configuration and Management Manual

Management Environment
OSI/AS Configuration and Management Manual—424119-001
2-34
SCF Commands for the SUBSYS Object
SCF Commands for the SUBSYS Object
You can use the following SCF commands with the SUBSYS object:
Names for SUBSYS Objects
A SUBSYS object has the same name as the OSI manager process that controls the
subsystem. For example, if your OSI manager process is called $OSIM, then $OSIM is
the name you use in SCF commands to control the SUBSYS object.
Examples
The following commands show various uses of the SUBSYS object:
•
The following examples show nonsensitive commands you can use to collect
general information on your OSI/AS subsystem:
INFO SUBSYS $OSIM
INFO SUBSYS $OSIM, DETAIL
NAMES SUBSYS $OSIM
NAMES SUBSYS $OSIM, SUB
STATUS SUBSYS $OSIM
VERSION SUBSYS $OSIM
By using the SCF ALTER command, you can specify where the subsystem should
look for TAPS and TSP code files, set limits on the number of protocol processes
that can be added to an OSI/AS subsystem, or identify the name of the MIB to the
subsystem.
•
The following example illustrates how to set the maximum number of protocol
processes that can be added to your OSI/AS subsystem:
ALTER SUBSYS $OSIM, MAXNSP 2, MAXTSP 5, MAXTAPS 5
This example sets a maximum of two NSP processes, five TSP processes, and five
TAPS processes that can be added to your subsystem.
•
The following example specifies where the subsystem should look for code files
when starting new TAPS and TSP processes:
ALTER SUBSYS $OSIM, TAPSFILE $DATA.OSICODE.TAPSOBJ
, TSPFILE $DATA.OSICODE.TSPOBJ
ALTER Modifies one or more attributes of the subsystem.
INFO Lists the attribute values for the subsystem.
NAMES Lists the names and object types of all objects configured within
the subsystem.
STATS Displays statistics information for the subsystem.
STATUS Displays the current status of the subsystem.
VERSION Displays the current software version of the subsystem.