Jobs in Joblog Pending Status; Joblogs Are Not Being Created

Several jobs are in joblog pending status. There are several joblog server jobs started; however, the joblogs are not being created.

When specified, a job can have its job log production handled by the job log server. A job can also opt to not have its job log written. This is the case when a job is in *JOBLOG PENDING status.

How a job log is produced is controlled by the Job log output (LOGOUTPUT) job attribute. This can be set manually from a JOBD or from SYSVAL. The system value related to this is QLOGOUTPUT. In this instance, it helps if the customer can send in the job attributes for a job that is in pending status. I would expect to see a *PND in there.

Example

Job:   QDFTJOBD       User:   JIM            Number:   001003    
                                                                 
Job description . . . . . . . . . . . . . . . . . :   QDFTJOBD    
  Library . . . . . . . . . . . . . . . . . . . . :     QGPL      
Job queue . . . . . . . . . . . . . . . . . . . . :   QBATCH      
  Library . . . . . . . . . . . . . . . . . . . . :     QGPL      
Job priority (on job queue) . . . . . . . . . . . :   5          
Output priority (on output queue) . . . . . . . . :   5          
End severity  . . . . . . . . . . . . . . . . . . :   30          
Message logging:                                                  
  Level . . . . . . . . . . . . . . . . . . . . . :   4          
  Severity  . . . . . . . . . . . . . . . . . . . :   0          
  Text  . . . . . . . . . . . . . . . . . . . . . :   *SECLVL    
Log CL program commands . . . . . . . . . . . . . :   *NO        
Job log output  . . . . . . . . . . . . . . . . . :   *PND        
Printer device  . . . . . . . . . . . . . . . . . :   PRT01

More information:

When a job is in PENDING status, the job log server will not automatically pick it up and handle it. Restarting the job log server does not help.

This is what can be done:

Find the jobs that are in *JOBLOG PENDING status. Then do a change job and change the LOGOUTPUT attribute to *JOBEND or *JOBLOGSVR. You can use the WRKJOBLOG command to help find the jobs. Using the defaults on the WRKJOBLOG command will not bring up all the pending joblog jobs. Change the settings to the following to find all the pending joblog jobs:

WRKJOBLOG PERIOD((*AVAIL *BEGIN) (*AVAIL *END))

To help manage in the future, there are some things that you can do. Changing the system value is a good start. There are some job descriptions shipped by IBM that are shipped as *PND. Therefore, you do not get them all. You can modify the OA Cleanup options to clean up pending job logs after 'X' amount of days. You could also use the Remove Pending Job Log (QWTRMVJL) API to clean up pending job logs.