OSI/AS Configuration and Management Manual

Installing and Configuring the Subsystem
OSI/AS Configuration and Management Manual—424119-001
4-11
Installing the OSI Manager Process
The OSI/AS software includes an input file called DBFUP that creates a MIB file with
the correct attributes. Use the VOLUME command to move to the volume in which you
want the MIB file located, then issue the following FUP command:
$volume.subvolume
is the volume and subvolume in which your OSI/AS software is installed.
This FUP command creates a key-sequenced file called ZOSIDB and an alternate-key
file called ZOSIDB0 in the same subvolume. The MIB files should be secured so that
the OSI manager process has both read and write access to them.
After creating the MIB, you must next install the OSI manager process.
Installing the OSI Manager Process
To install the OSI manager process, you must be logged on with SUPER ID access. You
install the OSI manager process as follows:
1. Create the OSI Manager Process
Create the OSI manager process by running it from the object file called OSIMGR. This
object file is located on the volume and subvolume in which your OSI/AS software is
installed. You issue a RUN command from SCF or a TACL command interpreter. For a
description of the syntax of the RUN command, see the TACL Reference Manual.
Special considerations apply to some of the TACL run options and other parameters
when you run OSIMGR. First, you must specify the NAME option; the NonStop
Kernel operating system does 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.
You should always specify a primary and a backup CPU, so that the OSI manager
process runs as a NonStop process pair. Otherwise, if the CPU in which the OSI
manager process is running fails, you are unable to establish new connections.
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.
The following examples show first an implicit, then an explicit, RUN command:
OSIMGR /NAME $OSIM, NOWAIT, CPU 4/5, HIGHPIN OFF
RUN OSIMGR /NAME $OSI2, NOWAIT, PRI 125, SWAP $SPARE, &
CPU 7/8
FUP / in $volume.subvolume.DBFUP /
Note. The OSI manager process, by default, runs as a high PIN process. To run it as a low
PIN process, you must specify HIGHPIN OFF in the RUN command.