z/OS JES2 Diagnosis
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Using the JES2 DEBUG facility

z/OS JES2 Diagnosis
GA32-0993-00

You can use the DEBUG facility to trap unauthorized alterations of checkpoint-resident data, a job queue element (JQE), or a job output element (JOE) by specifying the $T DEBUG=Y|N command. It can also be used (if additional parameters are included with the command) to record certain JES2 events and activities. For example, you can specify whether to count certain events, provide certain $HASP095 error information to the operator, verify the integrity of a newly created checkpoint version, or, start or stop monitoring updates made to the checkpoint data set.

Because the DEBUG facility checks all checkpoint records before processing them, DEBUG causes performance degradation. Use the $T DEBUG=Y|N command only when you experience problems that you suspect are checkpoint I/O problems. Also, because of performance degradation, IBM® suggests that you do not use the DEBUG command with the CKPT or VERSION parameters specified in a production environment.

DEBUG can detect:
  • A failure to issue a $QSUSE or a $CKPT macro by another member in the multi-access spool (MAS) configuration.
  • Random overlays of the 4-kilobyte pages, the job queue, and job output table (JOT). However, the facility cannot detect all unauthorized alterations. DEBUG will not detect the error if a routine changes a checkpointed element either without:
    • Issuing a $QSUSE macro. It is possible that the routine already has exclusive control of the checkpoint data set.
    • First issuing a $CKPT macro, and another a checkpoint element in the same block was altered validly during the same checkpoint cycle.
  • Unauthorized updates to the checkpoint in a multi-access spool environment.
  • Problems with the application copy of the checkpoint subtask.
  • Access logging including warnings for JES2 output work selection for:
    • JES2 devices (such as local and remote printers and punches, and NJE and offload SYSOUT transmitters).
    • External writer (XWTR) requests.
    • SYSOUT application program interface (SAPI) requests (SSI function code 79).
    • With SECURITY=YES specified, you will receive RACF® messages, but no $HASP186 message for profiles in warn mode.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014