OSI/AS Configuration and Management Manual

Installing and Configuring the Subsystem
OSI/AS Configuration and Management Manual—424119-001
4-13
Adding NSP, TSP, and TAPS Processes
Notice that you use indirect-process-name to perform this task.
•
The first attribute-spec names the process, using process-name (the
direct process name)
NAME $NETA
NAME $LANB
NAME \B.$L4B
NAME $TSP2
NAME $L5A
NAME $TAPS2
Notice that the name of the NSP process must correspond to the device name (an
I/O name) under which the NSP process was installed. The names for the TSP and
TAPS processes are the Guardian process names under which these processes run
when they are started.
•
The remaining attribute-spec names the CPU where the primary process is to
run, the CPU where the backup process is to run, the location of the code file (the
code file should be on the same system in which the process is started), and the
volume to be used for swapping data:
CPU 2, BACKUPCPU 3, \B.$SYSTEM.OSIFILES.TSPCODE
CPU 3, SWAP $DISKA
Considerations
•
Note that NSP processes are X25AM or TLAM (or PAM, for G06 and above
releases) processes that you have already installed. The ADD command merely
registers these processes with the OSI manager process.
•
The NAME attribute is required. It identifies the Guardian external filename for the
process.
°
Local TAPS and TSP process names can be up to six characters ($ followed by
five characters).
°
Remote TAPS and TSP process names can be up to five characters ($ followed
by four characters).
°
Local NSP process names can be up to seven characters ($ followed by six
characters).
°
Remote NSP process names can be up to six characters ($ followed by five
characters).
°
In the case of NSP processes, you must specify the same name as the device
name entered for the process in the SYSGEN configuration file (DEVICE
NAME parameter). You can only specify a device name once in a configuration.
For example, the two NSP processes added in this example could not use the
same name.