OSI/AS Configuration and Management Manual

Routine Management Tasks
OSI/AS Configuration and Management Manual—424119-001
5-5
Retrieving Configuration Information
The following sequence of SCF commands causes the OSI manager to invoke the
configuration contained in MIB1:
SUSPEND PROCESS $OSIM
ALTER SUBSYS $OSIM, MIB $SYSTEM.CONFIG.MIB1
ACTIVATE PROCESS $OSIM
The following sequence of SCF commands causes the OSI manager to invoke the
configuration contained in MIB2:
SUSPEND PROCESS $OSIM
ALTER SUBSYS $OSIM, MIB $SYSTEM.CONFIG.MIB2
ACTIVATE PROCESS $OSIM
In each case, when the OSI manager process changes from the SUSPENDED state to the
STARTED state, it reads the designated MIB. Changing the subsystem configuration or
altering the MIB file has no effect on active connections.
Retrieving Configuration Information
The SCF commands CHECK, INFO, NAMES, STATS, and VERSION provide
configuration information about an OSI/AS subsystem. The following subsections
describe commands you can use to answer the following common configuration
questions:
•
How Many Objects of Each Type Are Defined? on page 5-5
•
What Objects Are Defined Within Each Type? on page 5-6
•
What Are the Guardian Attributes of Processes? on page 5-9
•
How Are the SERVICE Objects Currently Defined? on page 5-10
•
How Are the PROFILE Objects Currently Defined? on page 5-10
•
How Are the ENTRY Objects Currently Defined? on page 5-10
•
Where Does the Subsystem Look for the Code Files? on page 5-10
•
What Versions Are the Processes? on page 5-11
How Many Objects of Each Type Are Defined?
Use the STATS SUBSYS command to find out how many objects of each type are
currently registered to a specific OSI manager process. You issue a command like the
following:
STATS SUBSYS $OSIM
The OSI manager process returns a screen that includes the following configuration
information: