OSI/FTAM Configuration and Management Manual

FTAM Troubleshooting
OSI/FTAM Configuration and Management Manual—421944-001
6-18
Configuration Errors
To obtain still more detailed information about what is happening on the association,
you can trace the initiator and underlying TAPS, TSP, and NSP processes, then use the
PTrace utility to examine the trace records. Each message sent from or to one of these
processes is represented by a trace record. The trace records allow you to follow the
primitives from the FTAM API down through the initiator and the underlying OSI
layers, showing you the information being carried at each step. In the initiator traces, the
USER and PROV records are labeled with the names of the primitives being sent or
received, and the ASN1 records show the data before and after encoding or decoding.
Check especially for provider or user abort indications; these often indicate a problem,
and the status, error, and ACSE reason codes can help you determine the source of the
problem.
For more information on error-handling in Tandem FTAM applications, see the Tandem
OSI/FTAM Programming Guide. For detailed descriptions of the trace records, refer to
the manuals listed in FTAM Manuals
on page xviii and Related Manuals on page xx.
Applications Using the Tandem Responder
For applications on a remote system, from a vendor other than Tandem, that access the
services of the Tandem responder, you’ll need to use whatever debugging tools are
available on the remote system. Your applications should follow good error-handling
strategy, as outlined in the Tandem OSI/FTAM Responder Manual.
Ensure that your application follows the FTAM protocol as described in the Tandem
OSI/FTAM Responder Manual and the ISO 8571 standard. Check for parameter errors.
Also ensure that the filenames, initiator IDs, and passwords used in your applications
match the corresponding Tandem filenames, user IDs, and passwords.
There are also troubleshooting tools available to you on the Tandem responder side that
can provide additional information about a problem.
The Tandem FTAM responder returns a set of diagnostic messages that provide
information beyond what is required in the ISO standard. These are described in the
Tandem OSI/FTAM Responder Manual. You can retrieve these diagnostic messages
using whatever interfaces are available on your remote system. Also check additional
error codes and diagnostic messages provided by the remote FTAM interface.
For some application errors detected by the Tandem responder, the responder also
generates an event message on your Tandem system. The following FTAM event
messages can indicate either a problem in the remote application or a breach of security
by the remote system:
•
Event message #20 (invalid initiator ID/password)
•
Event message #21 (file security error)
When troubleshooting a remote application, you should write your EMS filter to pass
FTAM event message #23, enabling you to obtain a record of all successful and
unsuccessful file-transfer completions.