OSI/AS Configuration and Management Manual

Management Environment
OSI/AS Configuration and Management Manual—424119-001
2-21
Naming PROCESS Objects
The OSI manager name is a valid Guardian process name.
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).
process-name has the following format:
Here are two examples that illustrate this syntax:
$OSIM
\B.$L4B
$TSP1
NSP Process Names
NSP processes are named when the TLAM (with D-series releases) or PAM (for G06
and above releases) or X25AM subsystem is generated. 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).
TSP and TAPS Process Names
TSP processes and TAPS processes are named when the OSI/AS subsystem is
configured. 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).
$process-name
Note. Always use indirect-process-name whenever there is a choice. An exception
to this rule is when you want to alter the following TSP process attributes: LANDFC,
LANDFT, LANEXPANDIOSIZE, LANIOSIZE, LANREADS, LANWRITES,
RECEIVEDEPTH, and RECEIVESIZE. In this case only, use process-name. 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