OSI/AS and OSI/TS Supplement (Includes RFC-1006 Support)

OSI/AS SCF Commands Changed to Support RFC-1006
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems
107751 Tandem Computers Incorporated 3–17
The following
attribute-spec
for the ADD ENTRY #SNPA command has a new
meaning when using RFC-1006:
[ L3SERVER
indirect-process-name
]
L3SERVER (ZL3-SERVR)
defines the name of the local TCP/IP process that services the local SNPA.
This is a required attribute for local SNPAs only.
Value: A TCP/IP process name in the following format:
$
osi-mgr-name
.#NSP.
internal-name
Default: No default value is provided.
ADD PROCESS The following
attribute-spec
for the ADD PROCESS command has a new meaning
when using RFC-1006:
{ NAME
guardian-process-name
}
NAME (ZNAME)
specifies the TCP/IP process name. It is used to register an existing TCP/IP
process with the OSI manager. NAME is the only attribute that is used for NSP
processes; all other attributes are ignored.
This is a required attribute; a value must be supplied.
Value: A TCP/IP process name in the following format:
[\
system
].$
process-name
The name of a TCP/IP process located on the same system as the OSI
manager process can be up to six characters (the $ sign followed by
five characters). For example:
$TCP10
$TCPB1
The name of a TCP/IP process not located on the same system as the
OSI manager process can be up to five characters (the $ sign followed
by four characters). For example:
\GOOFY.$TCP1
\GOOFY.$TCPA
Default: No default value is provided.