Job log

Each job has an associated job log.

The job log can contain the following for the job:

• The commands in the job.
• The commands in a CL program if the CL program was created with the LOG(*YES) option or with the LOG(*JOB) option and a Change Job (CHGJOB) command was run with the LOGCLPGM(*YES) option
• All messages and message help sent to the requester and not removed from the call message queues.

• Write job log to a file
  After the job ends, the job log can be written to either the output file QPJOBLOG or a database file.
• Control information written in a job log
  You can control what information the system writes in the job log.
• Job log message filtering
  Message filtering is the process of removing messages from the job log based on the message logging level set for the job.
• Example: Control information written in a job log
  This example shows how the logging level affects the information that is stored in the job message queue and, therefore, written to the job log, if one is requested.
• Job log sender or receiver information
  The job log contains information about the sending or receiving program or procedure.
• Display the job log
  The way to display a job log depends on the status of the job.
• Prevent the production of job logs
  You can prevent a job log from being produced at the completion of a batch job using *NOLIST.
• Job log considerations
  The following information gives suggestions to apply to using job logs.
• Interactive job log considerations
  The following information gives suggestions to apply to using interactive job logs.
• Batch job log considerations
  The following information gives suggestions to apply to using batch job logs.
• Filter the job log to a database file
  If the job log is directed to a database file through use of the QMHCTLJL API, additional message filtering can be specified.
• Use job log output files