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

Configuring OSI/AS
RFC-1006 Subsystem Configuration
107751 Tandem Computers Incorporated 2–17
If you want to check the status of the NSP process, use STATUS PROCESS
command with the DETAIL option.
2. Use the ADD PROCESS command to register a TSP process name with the OSI
manager process. The command syntax is:
ADD [ PROCESS indirect-process-name ] ,
{ NAME guardian-process-name }
guardian-process-name is the name of the TSP process.
Example:
ADD PROCESS $OSIM.#TSP.TSP0, NAME $TS0
Use the ALTER PROCESS command to change the value of the NAME attribute
of an existing process.
Verify the TSP process name by using the INFO PROCESS command.
If you want to check the status of the TSP process, use the STATUS PROCESS
command with the DETAIL option.
3. Use the ADD PROCESS command to register a TAPS process name with the
OSI manager process like you normally would.
Define profiles as you normally would.
Define the entries:
Note The SNPA entry name only represents a Tandem internal number, not the real local SNPA address. It is
used internally to eventually associate an NSP process with an NSAP address (IP address); the NSP
process handles all connections that use the specified NSAP address. For more details on SNPA, refer
to the SCF Reference Manual for Tandem OSI/AS.
1. Use the ADD ENTRY #SNPA command to register the local SNPA entry with
the OSI manager and to associate the NSP process (from Step 1) with this
SNPA entry. The command syntax is:
ADD [ ENTRY entry-name ] ,
L3SERVER indirect-process-name ]
indirect-process-name defines the name of the NSP process that services
the local SNPA. The L3SERVER attribute is used only for local entry names.
Example:
ADD ENTRY $OSIM.#SNPA.80, L3SERVER $OSIMGR.#NSP.TCP0
Use the ALTER ENTRY command to change the value of the L3SERVER
attribute of an existing entry.
Verify the SNPA entry by using the INFO ENTRY command with the DETAIL
option.