Job logs

A job log contains information related to requests entered for a job. A job log has two forms, a pending form and a spooled form.

In its pending form, a job log for a completed job can change as other jobs (the subsystem, the system operator, and so on) interact with the completed job. In its spooled form, a job log is a snapshot (a moment in time) and does not change (such as spooled files that are created by the Display Job Log (DSPJOBLOG) command, or created after the job completes its activity).

Each job has an associated job log that can contain the following information 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 (the message and help text for the message) sent to the requester and not removed from the program message queues

At the end of the job, the job log can be written to the spooled file QPJOBLOG so that it can be printed. However, producing a job log doesn't necessarily mean printing it or creating a spooled file. (For example, the Control Job Log QMHCTLJL API can be used to specify that the job log is to be written to an outfile at the end of job.)

You can reduce the number of job logs produced and reduce the contention for resources (such as output queues). This reduces the resource consumption caused by producing job logs.