OSI/FTAM Configuration and Management Manual

FTAM Troubleshooting
OSI/FTAM Configuration and Management Manual—421944-001
6-16
Configuration Errors
The STATUS SU display shows the calling address being used by the initiator (the
address specified by the application, if any, or the configured default address), the called
address, and the responding address. A missing responding address indicates that the
remote entity has not responded to the association request; this might indicate address
configuration problems.
The STATUS SU command with the DETAIL option also displays the name of the
associated TAPS subdevice. If you suspect a problem in an underlying subsystem, you
can issue an OSI/AS STATUS SU command to query the TAPS subdevice, as described
in the OSI/AS SCF Reference Manual.
When a Tandem responder is first started, problems with the OSI/AS address
configuration for the responder can cause event message #8 (subdevice access failed). If
you receive this event message, use OSI/AS SCF commands to make sure the TAPS
process is running and is allowing opens; if all is well with the TAPS process, recheck
the addresses configured in OSI/AS.
Once the responder is running, you can use the NAMES SU and STATUS SU
commands to determine the status of associations with remote applications. If the Opens
field of STATUS SU has a value of 1, the subdevice is being used for an association; if it
has a value of 0, the subdevice is waiting for an incoming associate indication. If an
association exists, you can determine the status of the underlying TAPS subdevice by
using an OSI/AS STATUS SU command.
Application Protocol Errors
The troubleshooting strategy you should use for protocol errors in your applications
depends on whether your applications run on a Tandem system using the Tandem
initiator and the FTAM API, or run on a remote system from another vendor and access
the services of the Tandem responder.
Because OSI addressing information is provided by both the configuration and the
application, addressing problems can originate in either place. For this reason, some of
the same tools (such as the STATUS SU command with the DETAIL option) are useful
in troubleshooting both configuration and application addressing errors.