When a job does not run at the scheduled time, find out what you can do.
To troubleshoot the Advanced Job Scheduler, first view the Job
Scheduler frequently asked questions 
Web page. Read about commonly asked questions that
identify how to do certain functions with Advanced Job Scheduler.
Also, here are a list of items that you can review when a job does not run at the scheduled time:
- Current® fix level
- The first thing you should verify is that your fixes are current. When you request fixes, be sure to request a list of all fixes. Not all fixes are included in the cumulative packages.
- Check job monitor
- Job QIJSSCD should be active in the QSYSWRK subsystem. If it is not, process the Start Job Scheduler (STRJS) command.
- The job monitor can be in a loop if the status of the job is RUN for over ten minutes. If it is in a loop, end the job with *IMMED, and start the job monitor again (STRJS).
- If there is a message to answer, reply with a C (Cancel). The job monitor will go into a 90-second delay and then start monitoring again. Print the job log for the monitor job. This will contain the error messages.
- Check the Advanced Job Scheduler log
- Process the Display Log for Job Scheduler (DSPLOGJS) command for the job. Press F18 to go to the end of the list. Entries exist to explain why the job did not run. Examples of the entries include a resource failure, active or job dependency situation, or submission error.
- Dependency on another job
- If the job is dependent on another job, take option 10 from the Work with Jobs display to display job dependencies. Press F8 to list all predecessor jobs. A dependent job cannot run unless all the predecessor jobs show *YES in the Complete column.
- Track a job's progress
- If a job is not functioning properly, you can use the Set Step using Job Scheduler (SETSTPJS) command before or after a step in your CL program to help determine what the problem is. Specify the command along with description text in your CL program. Use this command as many times as necessary. The text description that is associated with the current command is displayed in the Command step field on the Last Run page of the scheduled job properties. In addition, you can view the Command step field on the Status window of an active job. The Command step field is automatically updated every time the job encounters the SETSTPJS command. Use this command to help determine the progress of a job.
Collecting these data samples will help in your problem analysis:
- Error message conditions
- Print the job log for the interactive session, monitor job or scheduled job, depending where the error occurred.
- Job schedule date is not correct
- Process the DSPJOBJS command for the job with OUTPUT(*PRINT). Print a calendar report if a calendar is used within the job. Print a holiday calendar report if a holiday calendar is used within the job. Press the Print key to print the display of each fiscal calendar entry for the fiscal calendar used within the job.
- Advanced Job Scheduler log
- Always print the Advanced Job Scheduler log for the time period in question.
- Files QAIJSMST and QAIJSHST
- Files QAIJSMST and QAIJSHST in library QUSRIJS might need to be journaled before trying to reproduce the problem. Also, the QUSRIJS library may be needed by IBM® support.