What to do when the job log won't display

In iSeries™ Navigator, to find and display a job log, whether a batch job or an interactive job, right-click the job and then click Job log from the menu. However, depending upon the status of your job or how the job log values were set in the job description, your job log may be in the output queue, or it may be in a job log pending status or it may not be available.

The following are some steps to take if the Job log menu option is unavailable for your job.
Tip: Set the column display for Active jobs (or Server jobs) to include the Status. This will make it easier to quickly determine where to look for your job log.

To access a job log: My Connections > server > Work Management > Active Jobs or Server Jobs > Right-click the job and select Job log.

If the Job log menu option is not available or if you get an error message stating that the system is unable to retrieve the job log, consider the following:
  1. Check the status of the job.
    Option Description
    Running Check the Job Properties - Job Log window and make sure the Produce a job log box is checked. If it is not checked, then no job log was produced.
    Ended This job did not end in a normal manner. It might be due to an error or user intervention. Right click on the job and then clickPrinter Output. If you do not see your job log there, check the Job Properties - Job Log window and make sure the check box, Produce printer output for job log is selected.
    Completed - Printer output is available This job ended normally. Right click on the job and then click Printer Output. If you do not see your job log there, check the Job Properties - Job Log window and make sure that the field Create printer output for job log if job ends normally was checked.
    Completed - Job log pending The job log will not be produced. The job log remains in pending until removed. You will need to use the Display Job Log (DSPJOBLOG) command to view the pending job log.
  2. The job log may have been spooled to an output queue and has printed, in which case the log has been removed from the system.
  3. Another possibility is that the job log was deleted by another user.