Documentation
To determine the cause of an SNALINK LU0 session hung
terminal, the following might be needed:
- SNALINK LU0 log or MVS™ console log
- NETSTAT DEVLINKS display output
- VTAM® display application status output
- SNALINK LU0 DEBUG trace output
- VTAM buffer trace of the SNALINK LU0 applications
- VTAM internal trace
For information about VTAM traces, see z/OS Communications Server: SNA Diagnosis Vol 1, Techniques and Procedures and z/OS Communications Server: SNA Diagnosis Vol 2, FFST Dumps and the VIT.
This list of documentation includes documentation needed to resolve most types of hung terminals. All of the indicated data might not be needed for each occurrence of a hung terminal. The following section provides information about the types of data that might be needed for each diagnostic step.