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

General OSI/AS and OSI/TS Manual Changes and Corrections
107751 Tandem Computers Incorporated 8–15
ZNSP-TYPE specifies the type of connection. The named value ZAPS-VAL-NSP- xxx
designates the connection type, as follows:
ZAPS-VAL-NSP-X25 (value 1): X25AM connection
ZAPS-VAL-NSP-LAN (value 2): TLAM connection
ZAPS-VAL-NSP-TCPIP (value 3): TCP/IP connection
S 930923 1534 9718
Summary
There is garbled text in the last paragraph on page 2-11 in the Tandem OSI/AS
Configuration and Management Manual.
Manuals Affected
Tandem OSI/AS Configuration and Management Manual
SCF Reference Manual for Tandem OSI/AS
Tandem OSI/AS Management Programming Manual
Detailed Description
The text under the “null ENTRY Names” heading should read as follows:
Applications that don’t use TSELs, NSAPs, or SNPAs must specify the corresponding
entry in the MIB with a “dummy” or null value. If you specify the server processes
and profiles (the TSELs, NSAPs, and the SNPAs) in the APPL ENTRY, you eliminate
the need for null ENTRY names. However, if you don’t specify the server processes
and profiles in the APPL ENTRY, you must use a null ENTRY name for the ENTRY
objects your application doesn’t use. The way to specify a null entry is:
#NSAP.
#SNPA.
#TSEL.
For example, if your application does not require TSELs, you can use a null TSEL
ENTRY name to specify a server (TAPS process) without specifying a TSEL name.
Because the OSI manager process interprets a null ENTRY object as having a name
(which is null), you may use only one TSEL ENTRY null name, one SNAP null name,
and one NSAP ENTRY null name in your configuration.
S 921209 1534 9101
Summary
The OSI/AS Management Information Base (MIB) cannot be backed up while it is
open because it is opened in exclusive mode.
Manuals Affected
Tandem OSI/AS Configuration and Management Manual