OSI/FTAM Configuration and Management Manual

Monitoring FTAM Performance
OSI/FTAM Configuration and Management Manual—421944-001
5-6
Displaying Subdevice Status
This display provides the OSI addresses for various connections and associations across
an OSI network. The addressing fields in the display are interpreted according to the
type of activity.
When a local initiator makes an association with a remote responder and you issue the
STATUS SU command to the appropriate subdevice, for example
STATUS SU $FTI2.#Z000006
The addressing information on the screen is as follows: Calling Address displays the
OSI address of the local initiator; Called Address indicates the OSI address of the
remote responder that is requested by the initiator; and Responding Address displays the
OSI address of the remote responder that actually responds to the initiator’s request. The
values of Called Address and Responding Address are the same unless the responding
system has specified a different address.
When a local responder has posted attaches with the OSI/AS subsystem, but no
association has been made, and you issue STATUS SU to the appropriate subdevice, for
example
STATUS SU $FTR1.#ZF00004
the addressing information in the display is as follows: Called Address displays the OSI
address of the FTAM responder process; all other addressing fields will be blank.
When a local responder has posted attaches and an association with a remote initiator
process has been made, Calling Address displays the OSI address of the remote initiator
process, and Called Address displays the OSI address of the local responder process. In
this case, the LOCAL and REMOTE labels displayed on the screen are interchanged.
The STATUS SU command is most useful in problem detection rather than performance
tuning. Here are some ways in which you can use the information in the STATUS SU
display to pinpoint potential problems:
•
For connection problems, you can check the remote addressing information to
determine whether or not the FTAM association has been established with the
designated remote entity.
•
Once an association is established, you can check the functional units on the screen
to compare the functional units requested with those negotiated. If not all required
functional units have been negotiated, interoperability problems might exist.
•
Refer to the Tandem OSI/FTAM Programming Reference Manual for detailed
information on nonzero Error and Error Subcode values for an initiator subdevice.
Error and Error Subcode values for responder subdevices are generated by the TAPS
process; for detailed information on these values, see the Tandem OSI/FTAM
Programming Guide. For information on diagnosing problems with lower-layer
processes, see the OSI/AS Configuration and Management Manual.
Issuing the STATUS SU command without the DETAIL option returns the name of the
subdevice and its state, the number of opens, and the last error code and subcode
returned during operation of the subdevice.