Track request information with the job log of a distributed relational database

Every job on the iSeries™ server has a job log that contains information related to requests entered for a job.

The information in a job log includes:

Commands that were used by a job
Messages that were sent and not removed from the program message queues
Commands in a CL program if the program was created with LOGCLPGM(*JOB) and the job specifies LOGCLPGM(*YES) or the CL program was created with LOGCLPGM(*YES)

At the end of the job, the job log can be written to a spooled file named QPJOBLOG and the original job log is deleted. You can control what information is written in the job log by specifying the LOG parameter of a job description.

The way to display a job log depends on the status of the job. If the job has ended and the job log is not yet printed, find the job using the Work with User Jobs (WRKUSRJOB) command, then select option 8 (Display spooled file). Find the spooled file named QPJOBLOG and select option 5 (Display job log). You can also display a job log by using the Work with Job (WRKJOB) command and other options on the Work with Job display.

If the batch or interactive job is still active, or is on a job queue and has not yet started, use the WRKUSRJOB command to find the job. The Work with Active Jobs (WRKACTJOB) command is used to display the job log of active jobs and does not show jobs on job queues. Select option 5 (Work with job) and then select option 10 (Display job log).

To display the job log of your own interactive job, do one of the following things:

Enter the Display Job Log (DSPJOBLOG) command.
Enter the Work with Job (WRKJOB) command and select option 10 (Display job log) from the Work with Job display.
Press F10 (Display detailed messages) from the Command Entry display to display messages that are shown in the job log.

When you use the Display Job Log (DSPJOBLOG) command, you see the Job Log display. This display shows program names with special symbols, as follows:

>>: The running command or the next command to be run. For example, if a CL or high-level language program was called, the call to the program is shown.
>: The command has completed processing.
. .: The command has not yet been processed.
?: Reply message. This symbol marks both those messages needing a reply and those that have been answered.