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

PTrace Records Changed to Support RFC-1006
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems
107751 Tandem Computers Incorporated 3–47
ZFIL-TKN-FILENAME
for C-series systems, is the name of the file on which the error occurred.
ZFIL-TKN-XFILENAME
for D-series systems, is the name of the file on which the error occurred.
Probable Cause
OSI/TS reports this event for one of the following reasons:
The OSI/TS subdevice is configured incorrectly.
For a TSP process that is part of an OSI/AS subsystem, the OSIMGR database is
configured incorrectly.
An NSP device error has occurred.
An error has occurred on $ZNET.
Recommended Action
If the error was caused by a configuration error, reconfigure the subdevice or database.
If the error was caused by an NSP device or $ZNET, check to be sure the object is
running and is in the proper state. Otherwise, contact your Tandem representative.
PTrace Records
Changed to Support
RFC-1006
There is one change to the OSI/AS PTrace records and several changes to the OSI/TS
PTrace records.
OSI/AS PTrace Change The OSI/AS PTrace records will display the larger TPDU sizes and will display the
string “TCP/IP,” when TCP/IP is the NSP.
OSI/TS PTrace Changes The following changes have been made to the OSI/TS PTrace records:
In previous releases, PTrace would flag an error in trace records when class 0
CR- and CC-TPDUs included the Additional Option Selection parameter. For
RFC-1006, it is valid to include this parameter, so PTrace was changed to no longer
generate an error under this condition.
CR- and CC-TPDUs may only contain this parameter when using RFC-1006.
However, since the trace entry does not include an indication of the NSP type,
PTrace therefore cannot tell whether these trace entries are valid or not; it simply
displays them assuming they are valid.
For large TPDUs, PTrace may truncate the trace records.
When TCP/IP is the NSP, the TPDU size parameter in CR- and CC-TPDUs can
indicate larger values, up to 65531 bytes.
When TCP/IP is the NSP, the ED-TPDU is valid; its format is described in Section
5, “TPDUs Used by RFC-1006.”