How to get z/VSE debug data
Ingolf24 120000DRN3 Visits (162)
If you have problem with your z/VSE system (such as a system hang, soft- or hardwait) and contact the z/VSE Service (Level 2) Team, you are often asked to run a debug trace and try to reproduce the problem. The debug trace area is allocated in the Shared Virtual Getvis Area (31 bit). If the problem reoccurs, z/VSE Level 2 asks to send a standalone or system (AR) dump, which includes the debug trace area.
Debug traces system events and records registers and control data. With that information you or the Level 2 team may get closer to the cause of the problem. However, in most cases you need deep internal knowledge to interpret the debug traces.
The Attention Routine (console) command DEBUG ON allocates the debug area and starts the debug trace. With that command you may specify the size of the area (default is 16K). DEBUG OFF stops tracing and DEBUG END stops tracing and frees the debug arae.
You can limit the tracing to specific events and may stop the system, if a pre-defined condition occurs (DEBUG STOP). For more details please see the following books:
You can download those books from here.
Please let me know, if I should provide more detail about debug.