OSI/AS Configuration and Management Manual

Installing and Configuring the Subsystem
OSI/AS Configuration and Management Manual—424119-001
4-14
Starting TSP and TAPS Processes
•
With TSP and TAPS processes, you can specify a code file that contains the object
code from which these processes are started. For example:
ADD PROCESS $OSIM.#TAPS.TAPS1, NAME $TAPS1 &
, CODEFILE $DATA.OSICODE.TAPS
If you do not specify a CODEFILE parameter, the OSI manager looks for object
code in the default locations. Default locations for TSP and TAPS process object
code, respectively, are:
$volume.subvolume.TSPOBJ
$volume.subvolume.TAPSOBJ
$volume.subvolume is the location of the OSI manager process code file.
•
The following TSP process attributes cannot be controlled by OSI/AS:
°
LANDFC
°
LANDFT
°
LANEXPANDIOSIZE
°
LANIOSIZE
°
LANREADS
°
LANWRITES
°
RECEIVEDEPTH
°
RECEIVESIZE
•
When you use the BACKUPCPU attribute to specify a backup CPU when you add
the TSP and TAPS processes, the OSI manager process runs your TSP and TAPS
processes as NonStop process pairs. If a TAPS or TSP primary process fails, the
TAPS or TSP process continues to exist, but you must restart all connections. If the
OSI manager primary process fails, connections are not affected.
Starting TSP and TAPS Processes
Use the SCF START command to put TSP and TAPS processes in the STARTED state.
Examples
The following examples start TSP and TAPS processes:
START PROCESS $OSIM.#TSP.TSP1
START PROCESS $OSIM.#TSP.TSP2
START PROCESS $OSIM.#TAPS.TAPS1
START PROCESS $OSIM.#TAPS.TAPS2
Note. When altering these specific TSP attributes, use process-name. However, you must
still use indirect-process-name when suspending or restarting TSP processes. For
example, to alter one of these TSP process attributes, use the following sequence of
commands:
SUSPEND indirect-process-name
ALTER process-name, attribute-name-value
START indirect-process-name