Teleprocessing for output problems
Analyze the path the data should take.
Determine how the data flows through the programs and components
that process it and through the systems and hardware. Use this knowledge
to recreate the problem, using traces to checkpoint the data at certain
spots along the path.
Track the data from a point where it was correct to a point where
the data stopped or became incorrect.
Related information: For formatting of logrec records, see Recording logrec
error records in z/OS MVS Diagnosis: Tools and Service Aids .
See z/OS MVS Diagnosis: Tools and Service Aids for
the logrec records.
For explanations of the messages, see: z/OS MVS System Messages, Vol 1 (ABA-AOM)
z/OS MVS System Messages, Vol 2 (ARC-ASA)
z/OS MVS System Messages, Vol 3 (ASB-BPX)
z/OS MVS System Messages, Vol 4 (CBD-DMO)
z/OS MVS System Messages, Vol 5 (EDG-GFS)
z/OS MVS System Messages, Vol 6 (GOS-IEA)
z/OS MVS System Messages, Vol 7 (IEB-IEE)
z/OS MVS System Messages, Vol 8 (IEF-IGD)
z/OS MVS System Messages, Vol 9 (IGF-IWM)
z/OS MVS System Messages, Vol 10 (IXC-IZP)
z/OS MVS Dump Output Messages
The message book for a subsystem or program
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 to
diagnose VTAM® problems.
See the SLIP chapter in z/OS MVS System Commands for
information on setting a SLIP trap.
See z/OS MVS Diagnosis: Tools and Service Aids for
requesting dumps and traces.
See z/OS MVS Installation Exits for
exit routines.