OSI/AS Management Programming Manual

Running the OSI/AS Subsystem Processes
Communicating with the OSI/AS Processes
056785 Tandem Computers Incorporated 2–3
You can use an implicit RUN command (that is, omit the word RUN) if your OSIMGR
file resides on the subvolume $SYSTEM.SYSTEM or $SYSTEM.SYSnn.
Examples:
OSIMGR /NAME $OSIM, NOWAIT, HIGHPIN ON, CPU 4/5
(D-series systems only)
RUN OSIMGR /NAME $OSI2, NOWAIT, PRI 125, SWAP $SPARE, CPU 7/8
Running OSIMGR
Programmatically With a
NEWPROCESS or
PROCESS_CREATE_ Call
An application can create the OSI manager process by calling the NEWPROCESS or
NEWPROCESSNOWAIT procedure provided by the Guardian 90 C-series system
operating system; for D-series systems the equivalent procedure is the
PROCESS_CREATE_ procedure. The complete syntax of these procedures is provided
in the System Procedure Calls Reference Manual, and further information about how to
use them is given in the Guardian 90 Operating System Programmer’s Guide.
Special considerations for using NEWPROCESS and NEWPROCESSNOWAIT or
PROCESS_CREATE_ to run OSIMGR are discussed in the following paragraphs.
In the first 12 words of the filenames parameter, specify the OSIMGR object file.
The swap-file or swap-volume option, which you specify in the last 12 words of the
filenames parameter, can be useful. This option allows you to move the swap file to
a disk volume other than the volume on which the program file resides.
You must include the name parameter; the Guardian 90 operating system will not start
an OSI manager process unless a name is specified.
After your application creates the OSI manager process, it must send it a startup
message including any additional desired startup parameters, as described in the
Guardian 90 Operating System Programmer’s Guide.
In the parameter string of the startup message, you should always specify the backup
CPU number parameter, so that the OSI manager will run as a NonStop process pair.
Otherwise, if the CPU in which the process is running fails, communications
applications calling the APS procedures will be unable to establish new connections.
Defining and Starting the
Other OSI/AS Processes
Once the OSI manager process is running, your management application must send
certain OSI/AS programmatic commands, specified in Section 5, to set up the MIB and
the other OSI/AS processes. First, if the MIB database file name is other than ZOSIDB,
or if the MIB file is not located in the same subvolume as the OSI manager process,
your application must send an OSI/AS ALTER SUBSYS programmatic command to
specify this file. Then it must send an OSI/AS START PROCESS command to place
the OSI manager process in the STARTED summary state. This command causes the
OSI manager process to do the following for each TAPS, TSP, and NSP PROCESS
defined in the MIB:
If the process is already running, the OSI manager opens it, requests its status, and
sets that status for that process within the MIB.
If the process is not running, the OSI manager sets its status to STOPPED.