Parameter description DEBUG
- 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 that
are listed individually on this statement.
Modification: $T DEBUG operator command.
- 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 that are
listed individually on this statement except VERBOSE= and MEMBER_STATUS= (which are unaffected).
Specifying DEBUG=No requests JES2 to stop recording all events that are listed individually on this
statement except MEMBER_STATUS= (which is
unaffected).
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.
- EDS=Yes|No
- Specifies whether (YES) or not (NO) JES2 email sender task in JES2 EDS address space should
provide additional diagnostic information during communication with the z/OSMF
server.
Modification: $T DEBUG operator command.
- MEMBER_STATUS=No|Yes
- Specifies whether (YES) or not (NO) JES2 issues the $HASP1701 message when the status of a
member has changed.
Modification: $T DEBUG operator command.
- MISC=Yes|No
- Specifies whether (Yes) or not (No) JES2 provides occurrence counting
of certain JES2 events.
Modification: $T DEBUG operator command.
- QVERIFY=Yes|No
- Specifies whether (Yes) or not (No) JES2 is to perform a verification of the job, output, and
BERT data areas and queues every time the JES2 checkpoint is read. This is intended to detect
various types of errors in the checkpoint data read by the current system. If an error is detected,
JES2 issues a disastrous error with label KVRFYERR.
JES2 does not attempt to correct the error, report it and continue. This might result in the KVRFYERR disastrous error being issued every time that the checkpoint is read until the error is corrected (for example by a hot start).
Due to the significant additional overhead of this process, it is intended for use only in a test environment or to capture data for which all other diagnostic tools have failed.
Modification: $T DEBUG operator command.
- SECURITY=Yes|No
- Specifies whether (Yes) or not (No) JES2 provides more 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 that is specified by the 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 issues 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.
- TIMECLOCK=Yes|No
- Specifies whether (Yes) or not (No) JES2 takes a disastrous error (TIMERROR) when a job's hold
time and SCHENV-delay time added to arrival time exceeds current clock value.
Modification: $T DEBUG operator command.
- VERBOSE=Yes|No
- Specifies whether (Yes) or not (No) JES2 should use a more verbose form of messaging. For
example, messages associated with MEMBER_STATUS=YES is issued with additional text. Other messages
that normally are only placed in the hardcopy are directed to the console.
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.