CA ADS Batch Print Log Utility › How to Use the Print Log Utility

How to Use the Print Log Utility

In a single execution of the print log utility, you can print any or all of the following types of information contained in the log file:

• User—Informational messages issued by WRITE TO LOG and CONTINUE commands, and by WRITE TRANSACTION commands that perform a mapout to the dialog's output file. The message is specified in the MESSAGE TEXT parameter of the command.
• Debug—Debugging information issued by SNAP commands and by the CA ADS Batch trace facility.
• Edit error—Error messages issued when an input record is written to the suspense file. The runtime system writes one record consisting of the associated suspense file record number and the first 32 bytes of the input record, followed by one record for each applicable error message.

  In addition, if the input record was written to the suspense file by a WRITE TRANSACTION command, any message specified in the MESSAGE TEXT parameter of the command is also written to the log file as an edit error message.

• Operator—Operator informational messages issued by WRITE TO OPERATOR commands. All messages sent to the operator are also sent to the log.
• Abend—Abnormal termination messages issued by ABORT commands and by the runtime system when an application abends. Abend messages include snap dumps.

  Note: If an abend occurs during a mapping operation, the snap dump goes instead to the z/OS data set associated with the ddname (linkname) IDMSSNAP or, in VSE, to SYSLST (as described under JCL). An example of a mapping abend is when an input record that contains errors cannot be written to a suspense file because the MAXIMUM ERRORS for the dialog, which is specified at system generation or at runtime, has been exceeded.

• Statistics—Statistics records written by the runtime system when dialog statistics are being collected for the application.

Selecting Log File Records

The print log utility enables you to select log file records by:

• Dialog—You can specify that only log file records created by one or more specified dialogs are included in the report.
• User id—You can specify that only log file records created by specific users are included in the report. The user is determined at runtime by the current value of the $USER ($REQUESTOR) system-supplied data field; $USER ($REQUESTOR) can be initialized at runtime through an assignment command.
• Beginning time and date—You can specify that only log file records created on or after a certain time and date are included in the report.
• Ending time and date—You can specify that only log file records created on or before a certain time and date are included in the report.

You can specify any or all of the above selection criteria. Log file records must meet all criteria you specify in order to be included in the report.