OSI/AS Configuration and Management Manual

Troubleshooting Guide
OSI/AS Configuration and Management Manual—424119-001
8-4
Examples
•
When a connection configured for dynamic subdevices (in other words, the
DELETETIME attribute for the APPL ENTRY object is set to 0) terminates, all
subdevices created for that connection are terminated. In this case, CHECK SU
wont show anything useful unless the connection is established. In other words,
error information cannot be displayed on dynamic subdevices if you are having
trouble establishing a connection or the connection has failed.
•
When a connection configured for static subdevices (in other words, the
DELETETIME attribute for the APPL ENTRY object is set to -1) terminates, all
subdevices opened for that connection are set to inactive (not deleted). In this case,
CHECK SU can display useful information on failed connections. Since static
subdevices are not deleted, error information for these subdevices is retained by the
subsystem and can, therefore, be retrieved.
•
X25AM returns many different kinds of errors; TLAM or PAM returns very few
kinds of errors. Because TLAM (or PAM) is very different from X25AM in this
regard, do not assume that TLAM (or PAM) errors are not registered—they are,
indeed, registered and reported to you. In addition, frames lost on the LAN are
indirectly indicated in the OSI/TS STATUS SERVICE display in the Timeout and
Retransmission Count fields.
•
The ERRORONLY option cannot detect all possible subdevice errors. NSP
subdevice errors are usually reset by the next NSP operation, but are saved in the
Transport Layer and can be displayed by using the CHECK SU TSP command.
Similarly, TSP subdevice errors are usually reset by the next I/O operation to the
TSP process, but are saved in the upper layers and can be displayed by using the
CHECK SU TAPS command. TAPS subdevice errors, however, are reset by the next
TAPS operation and cannot always be saved. Therefore, not all TAPS errors can be
captured by CHECK SU.
The ERRORONLY option selects only subdevices that are in an error state and that
are being used by the server specified in the CHECK SU command. All other
subdevices associated with those selected error subdevices are also displayed,
depending upon the selection specifiers included in the command. For example, if
the ERRORONLY option is specified for a TAPS process, the CHECK SU
command looks only for TAPS subdevices in an error state. Any TSP and NSP
subdevices associated with those selected TAPS error subdevices are also displayed,
whether they are in an error state or not.
Examples
The following examples show some of the different options that can be used with the
CHECK SU command.
The following command displays information about all subdevices being used by the
application process $MYAPP and associated with the TAPS server $TAP1. Note that
this command displays information for all levels because the command defaults to ALL:
CHECK SU $TAP1.*, OPENER $MYAPP