OSI/FTAM Configuration and Management Manual

FTAM Troubleshooting
OSI/FTAM Configuration and Management Manual—421944-001
6-19
Interoperability Problems
If your remote application accesses FTAM-2 files as SQL tables, your filter should also
pass FTAM event message #10. You must recompile the FTAMROBJ file using NonStop
SQL before starting your responder processes; otherwise, the responder will generate
this event message, reporting an SQL error of -8025, on the first attempt to access an
FTAM-2 file as an SQL table. The responder also reports this event if any other NonStop
SQL error occurs.
As in troubleshooting configuration problems, you can use the NAMES SU and
STATUS SU commands to determine the status of associations with remote applications.
Check the Opens field of STATUS SU to determine whether each subdevice is being
used for an association; for those that are, check the functional units and addresses for
problems.
You can obtain additional information by tracing the responder and the underlying
TAPS, TSP, and NSP processes and by then using PTrace. The trace records allow you
to follow the primitives from the underlying layers up through the responder. In the
responder traces, the 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. Again, check for provider or user abort indications, and examine the status,
error, and ACSE reason codes in the trace records for these.
For more information on troubleshooting problems in remote applications using the
Tandem FTAM responder, see the manuals describing the interface used by the remote
application. For cause, effect, and recovery information about diagnostic messages
returned by the Tandem responder, see the Tandem OSI/FTAM Responder Manual.
Interoperability Problems
Interoperability problems arise from protocol incompatibilities between
implementations. These are often signaled by event message #22, indicating that the
Tandem initiator or responder’s threshold for FTAM protocol errors has been exceeded.
If you see this event message, you should trace the initiator or responder process and
examine the trace records using PTrace.
Other possible areas of incompatibility, which you can check using PTrace, are FTAM
functional units, service class, and attributes; presentation and session functional units;
and unsupported FTAM primitives. Check also for abort indications.
In addition, the functional units and addressing information displayed by the SCF
STATUS SU command with the DETAIL option can be useful in detecting
interoperability problems.