OSI/AS Configuration and Management Manual

Routine Management Tasks
OSI/AS Configuration and Management Manual—424119-001
5-11
What Versions Are the Processes?
and TSP processes to reside. This command also displays where the OSI manager
process expects the MIB file to be located.
The following example illustrates this command:
INFO SUBSYS $OSIM, DETAIL
This command produces a display like the following. Notice that you must use the
DETAIL option to display code file location information:
What Versions Are the Processes?
You can use the SCF VERSION command to retrieve the version banners for the OSI
manager process and any of the processes that belong to it. This information allows you
to verify that you are using compatible versions when starting subsystem processes from
files that may have been updated or modified.
To display the version banner for the OSI manager process, use the VERSION
command with either the SUBSYS object, the PROCESS object, or the null object:
VERSION SUBSYS $OSIM
VERSION PROCESS $OSIM
VERSION $OSIM
To display the version banner for a process, use the VERSION command with either the
PROCESS object or the null object. For NSP processes, use the null object:
VERSION $TAPS1
VERSION PROCESS $TAPS1
VERSION $TSP2
VERSION $TSP
VERSION $X25A
Managing Subsystem Processes
This subsection describes how to control the different types of processes that make up
an OSI/AS subsystem. Controlling processes can be divided into two types of tasks:
•
Adding and Deleting Processes on this page
•
Altering Process Attributes on page 5-14
OSIAS Detailed Info SUBSYS \MARS.$OSIM
*MaxNSP.......... 128 Current NSPs........ 12
*MaxTSP.......... 128 Current TSPs........ 20
*MaxTAPS......... 128 Current TAPSs....... 24
*MIB................ $MARS.OSI.MIB
*TSPCodeFile..... $MARS.OSI.TSPOBJ
*TAPSCodeFile.... $MARS.OSI.TAPSOBJ
OSIMGRCodeFile.. $MARS.OSI.OSIMGR