OSI/AS Configuration and Management Manual

Installing and Configuring the Subsystem
OSI/AS Configuration and Management Manual—424119-001
4-12
Adding NSP, TSP, and TAPS Processes
2. Specify Location of MIB, If Necessary
If the MIB is not in the same subvolume from which OSIMGR was executed, then you
must alter the SUBSYS object to direct OSIMGR to the correct subvolume. Issue an
SCF command like the following:
ALTER SUBSYS $OSIM, MIB $SYSTEM.OSI.ZOSIDB
3. Start the OSI Manager Process
Start the OSI manager process by using the SCF START PROCESS command. For
example, to start the OSI manager process named above, issue the following command:
START PROCESS $OSIM
After you have started the OSI manager process, you can begin to install and configure
the processes in your subsystem.
Adding NSP, TSP, and TAPS Processes
Use the SCF ADD command to register processes with the OSI manager process. The
OSI manager process stores information on these processes in the MIB.
Examples
The following examples register NSP, TSP, and TAPS processes with the OSI manager
process $OSIM:
ADD PROCESS $OSIM.#NSP.X25A, NAME $NETA
ADD PROCESS $OSIM.#NSP.LANB, NAME $LANB
ADD PROCESS $OSIM.#TSP.TSP1, NAME \B.$L4B, CPU 2, &
BACKUPCPU 3, CODEFILE \B.$SYSTEM.OSIFILES.TSPCODE &
SWAP \B.$DATA
ADD PROCESS $OSIM.#TSP.OSI4B, NAME $TSP2
ADD PROCESS $OSIM.#TAPS.TAPS1, NAME $L5A, CPU 3, &
SWAP $DISKA
ADD PROCESS $OSIM.#TAPS.OSI5B, NAME $TAPS2
These commands consist of three distinct elements: the command name, object-spec,
and attribute-spec. For a description of the syntax of the SCF commands, see the
OSI/AS SCF Reference Manual. The elements of these commands are described, as
follows:
•
Each command and object-spec adds a process to the OSI manager
ADD PROCESS $OSIM.#NSP.X25A
ADD PROCESS $OSIM.#NSP.LANB
ADD PROCESS $OSIM.#TSP.TSP1
ADD PROCESS $OSIM.#TSP.OSI4B
ADD PROCESS $OSIM.#TAPS.TAPS1
ADD PROCESS $OSIM.#TAPS.OSI5B