Why the Job Did Not Run

The screen identifies several scheduling problems:

• There is a TIME LIMIT problem—the job must be submitted between 11:00 p.m. and 4:00 a.m. This problem does not appear in the Why screen if you happen to be working on this guide during those hours.

  Note: Your site-defined start of workday, that is, the time of New Day Processing, can impact how the TIME FROM and UNTIL range determines when the job should be submitted. For more information, see the discussion of date definition concepts in Introduction to Control-M, and the description of the TIME parameter in the Control-M for z/OS User Guide.

• The two missing RESOURCES (IDTAPE-DRIVE and IDCPOWER) and their required quantities are listed. These quantities are not listed if by chance you actually have resources with these names in use and allotted at your site.
• Finally, the missing IN CONDITION (IDJOB3-ENDED-OK) is listed, unless you have an actual job that added this condition.

The problems listed above are the runtime scheduling requirements that prevent your job from running.

Runtime scheduling requirements are defined for a purpose, and it is generally not desirable to nullify them or work around them. However, sometimes it does become desirable to manually intervene to enable job submission, and Control-M allows for such intervention. The following sections illustrate how you can correct the problems and enable the job run.