SETDEBUG
Use the SETDEBUG command to provide additional information in the DEBUG file.
This information is helpful when diagnosing a problem in the processing of your data by the UIE batch job.
Syntax
SETDEBUG debugKeyword
Syntax explanations
debugKeyword can be specified as one of the following:
- JOBS—Causes a JOBS REPORT to be written in the DEBUG file. For each job, the following values are printed:
- JOB NAME
- SID
- JESID
- JOB CLASS
- PG number
- SRV.Class
- REP.Class
- Workload Category to which Job belongs
- WORKLOAD to which Job belongs
- SUITE to which Job belongs
- RDR Start date
- RDR Start time
- Date and Time of last SMF record available for the JOB, that is, Job end if it ended, or the end time of last SMF interval record.
- Length of first Account parameter
- 1-ST ACCNT Field
- 110DICT1, 110DICT2, and 110DICT3—Specify that UIE should provide additional information in the DEBUG file about the processing of the 110 dictionary records.
- DCDS—Specify that UIE should print a Data Set Grouping Report in the DEBUG file.
Rules
Each keyword should be specified on a separate SETDEBUG command.
Examples
You want to generate a JOBS REPORTS to determine which JOBS were found in the SMF type 30 records. The syntax of the SETDEBUG command is:
SETDEBUG JOBS
Related topic
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*