Suggestions for Development of Remote | Troubleshooting |
Applications |
|
The Compaq FTAM responder returns diagnostic messages to your application as specified by the ISO 8571 standard. In many cases, more information is returned than is required by the standard. Appendix A, “Compaq FTAM Responder Diagnostic Messages,” provides cause, effect, and recovery information about all diagnostic messages returned by the responder.
Some responder diagnostic messages also contain text of up to 256 characters in the Further Details field, providing additional information on the nature of the problem. For example, if you attempt to create a file and receive diagnostic message 3006 (file cannot be created), the Further Details text provides the
As another example, if you attempt to open a file and receive diagnostic message 5036 (contents type inconsistent), the Further Details text “illegal MSL value” indicates that you attempted to open a file with a
It is recommended that you check Further Details whenever you receive a diagnostic message. The Further Details text for many messages is
Troubleshooting
To detect and eliminate problems in your remote application, you need to use whatever debugging tools are available on the remote system. However, there are also troubleshooting tools available on the Compaq system where the responder runs that can provide additional information about a problem. If you encounter interoperability problems or other problems that appear to originate on the Compaq system, you should work with a Compaq problem solver who has access to these tools.
The Compaq troubleshooting tools include the following:
•
•
•
The Event Management Service (EMS) log Subystem Control Facility (SCF) interactive interface The PTrace utility
The Event Management Service (EMS) on Compaq systems enables the Compaq problem solver to monitor problems and other significant events that occur during the operation of Compaq FTAM and other Compaq software. The FTAM responder and the APLMGR process that manages it generate event messages when they detect significant events, as do the processes in the underlying OSI/AS, OSI/TS, X25AM, and TLAM (or PAM for G06 and above releases) and TCP/IP subsystems. Event messages are logged to the console or displayed on a terminal as operator messages, which are described in the Operator Messages Manual.
