z/OS JES2 Initialization and Tuning Reference
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Parameter Description DEBUG

z/OS JES2 Initialization and Tuning Reference
SA32-0992-00

DEBUG=Yes|No
Specifies whether (Yes) or not (No) you require JES2 to record certain JES2 events and to monitor certain JES2 activities. Specifying DEBUG=Yes requests JES2 to record all events listed individually on this statement.

Modification: $T DEBUG operator command.

DEBUG
Use this form of the DEBUG initialization statement to selectively request JES2 to record certain JES2 events and to monitor certain JES2 activities.

Modification: $T DEBUG operator command.

BERT=Yes|No
Specifies whether (Yes) or not (No) JES2 provides error code $BR3 to inform the operator that a data error has been detected in a chain of BERTs.

Modification: $T DEBUG operator command.

CKPT=Yes|No
Specifies whether (Yes) or not (No) JES2 should verify the integrity of the checkpoint data set.

Modification: $T DEBUG operator command.

Start of changeMEMBER_STATUS=Yes|NoEnd of change
Start of changeSpecifies whether (YES) or not (NO) JES2 issues the $HASP1701 message when the status of a member has changed.

Modification: $T DEBUG operator command.

End of change
MISC=Yes|No
Specifies whether (Yes) or not (No) JES2 provides occurrence counting of certain JES2 events.

Modification: $T DEBUG operator command.

SECURITY=Yes|No
Specifies whether (Yes) or not (No) JES2 provides additional RACF® security logging related to the $HASP186 error message. YES specifies that JES2 requests RACF to log access violations, including warning mode violations, 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).

If an access violation occurs, and you have DEBUG SECURITY=YES, JES2 issues message $HASP186 after RACF issues message ICH408I. The LOGSTR that JES2 passes to RACF identifies the problem as one of the following:

  • JES2 Work Selection Screening
  • External Writer Work Selection Screening
  • SYSOUT Application Program Interface (SAPI) requests (SSI function code 79).

Modification: $T DEBUG operator command.

STORAGE=Yes|No
Specifies whether (Yes) or not (No) JES2 provides $HASP095 error code GW3 to inform the operator that $RETWORK macro processing detected that the storage being returned was modified beyond the length specified by it's associated $GETWORK macro invocation.

Modification: $T DEBUG operator command.

SYMREC=Yes|No
Specifies whether (Yes) or not (No) when JES2 requests that MVS™ write a symptom record to the logrec data set, JES2 will issue message $HASP805 jobname SYMREC ISSUED FROM module WITH A DESCRIPTION OF desc. Although the message is useful to inform you of errors, some symptom records are informational and you might not want to receive this message whenever JES2 requests a symptom record. Symptom records are written to the logrec data set regardless of this specification.
Note: You can use the DEBUGMSG=No specification on the $SYMTAB macro to suppress the $HASP805 message even when SYMREC=Yes is specified here.

Modification: $T DEBUG operator command.

VERSION=Yes|No
Specifies whether (Yes) or not (No) JES2 should verify the integrity of a newly created checkpoint version.

Modification: $T DEBUG operator command.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014