3.1.1.1 Circuit Level Traces
The Gateway Management software provides an SDLC circuit level trace.
Run an SDLC circuit level trace if any of the following symptoms occur:
•
You suspect that a line is not being polled.
•
The line to IBM does not initialize properly.
•
You receive duplicate messages.
•
You suspect that messages are being lost.
•
You suspect data corruption.
3.1.1.2 Physical Unit Level Traces
Run a physical unit level trace if any of the following symptoms occur:
•
You cannot establish a connection between the Gateway-ST and IBM.
•
You establish a connection between the Gateway-ST and IBM, but it fails
repeatedly.
•
You receive a message indicating a protocol problem on the physical unit
level.
•
You are unsure of the specific LU on which you want to run a PU trace.
3.1.1.3 Session Level Traces
Run a session level trace if you perceive a protocol problem with a particular
session. Any of the symptoms listed in previous sections can indicate the need
for a session level trace.
3.2 IBM Traces
Gateway-ST users might need data from IBM traces to isolate problems in the
Gateway-ST environment. You use trace data to show protocol sequences on
the line level, on the channel level, on the physical level, and on the logical
level. Obtain IBM traces from your IBM systems programmer.
You can also request a VTAM internal trace and use the results to determine
which control blocks VTAM used when it established a session. Do not ask
your IBM system programmer to do a VTAM internal trace except as a last
resort.
For detailed information about IBM traces, see the following manuals:
•
VTAM Version 3 Release 1 and 1.1 Diagnosis Guide
•
MVS/Extended Architecture System Programming Library: Service Aids
3–2 Traces
