OSI/AS Management Programming Manual

Running the OSI/AS Subsystem Processes
Communicating with the OSI/AS Processes
2–2 056785 Tandem Computers Incorporated
Running the OSI/AS
Subsystem Processes
Before your management application can send commands to OSI/AS through SCP,
you must first install your NSP processes using the Tandem system generation
program SYSGEN. For instructions, refer to the sections on configuration of X25AM
and TLAM in the System Generation Manual. The Tandem OSI/AS Configuration and
Management Manual also provides information on installing NSP processes.
After the NSP processes are installed, you must create the Management Information
Base (MIB) and then run the OSI manager process. (The TSP processes will be
installed via the OSI manager process.) You can run the OSI manager process either
interactively through the Tandem Advanced Command Language (TACL) or SCF, or
program C-series systems) or PROCESS_CREATE_ (D-series systems) procedure.
Creating the MIB Database The OSI/AS software includes an input file called DBFUP that creates the MIB
database. DBFUP creates two files, with the default names ZOSIDB and ZOSIDB0.
To create the MIB, enter the following TACL commands:
VOLUME $ mibvol . mibsubvol
PURGE ZOSIDB, ZOSIDB0
FUP / IN $ osivol . osisubvol .DBFUP/
$ mibvol.mibsubvol
is the volume and subvolume where you want to create the MIB.
$ osivol.osisubvol
is the volume and subvolume where your OSI/AS software is installed.
Running OSIMGR
Interactively With a RUN
Command
The OSI manager process code is contained in an object file called OSIMGR. To run
this process interactively, enter the RUN command from either TACL or SCF. For the
syntax of the RUN command, refer to the TACL Reference Manual.
The following paragraphs describe special considerations for using some of the TACL
run options and other parameters when running OSIMGR.
First, you must specify the NAME option; the Guardian 90 operating system will not
start an OSI manager process unless a name is specified.
The SWAP option 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.
For D-series systems, by default the process will be run at a low PIN. If you want the
process to run at a high PIN, you must specify HIGHPIN ON in the command line.
You should always specify a primary and a backup CPU, 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.