Why screen

The Why screen (Screen 3.?) is displayed when the ? (Why) option is entered on the Active Environment screen. The Why screen shows the reasons why a job is in WAIT SCHEDULE status.

Figure 47 Active Environment Why Screen

------------------------ PRUPDT02 SCHEDULING ANALYSIS --------------------(3.?)

COMMAND ===>                                                    SCROLL===> CRSR

OPT DESCRIPTION                                                              

    TIME LIMIT       FROM   1730             UNTIL    0200                   

    RESOURCE         DB2-POWER               QUANTITY 0030                   

                               HELD BY   PRDKPL01 (U)  QUANTITY 0022         

                               HELD BY   GPLIR17A (U)  QUANTITY 0020         

                               HELD BY   INTR0002 (U)  QUANTITY 0015         

                               HELD BY   PRUPDOLV (U)  QUANTITY 0010         

                               HELD BY   MTPRQV   (U)  QUANTITY 0025         

    RESOURCE         CARTRIDGE               QUANTITY 0002                   

                               HELD BY   PRDKPL01 (U)  QUANTITY 0001         

                               HELD BY   GPLIR17A (U)  QUANTITY 0002         

    IN HOLD STATE                                                            

    CONDITION  PRUPDT01-ENDED-OK                        ODATE  0606          

    NOT-COND   PRPLD03-ENDED-NOTOK                      ODATE  0606          

    SCHEDULING ANALYSIS FOR SMART TABLE  ACCOUNT (ACCOUNT-GROUP)             

    SMART TABLE’S RUNTIME CRITERIA SATISFIED                                       

 ====== >>>>>>>>>>>>>>>>>>>>>   END OF "WHY" LIST   <<<<<<<<<<<<<<<<<<<<< =====

OPTION:  A ADD CONDITION  D DELETE NOT-COND                            10.32.27

To return to the Active Environment screen, press the END key (PF03/PF15).

Possible WHY reasons are:

• ALL RUNTIME CRITERIA SATISFIED. JOB WILL BE SUBMITTED SOON
• CONTROL-M MONITOR IS NOT ACTIVE
• IN HOLD STATE
• WAIT CONFIRMATION
• TIME LIMIT FROM hhmm UNTIL hhmm
• NEXT RUN FROM mmddyy hhmm
• CONDITION condition-name ODATE mmdd

  Prerequisite condition required by the job, along with its original scheduling date.

• RESOURCE resource-name [R] QUANTITY quantity BY priority memname

  Name and quantity of a Quantitative resource not currently available for the job. For critical path jobs, a job with a higher path priority than the current job is also identified.

• CONTROL OVER resource TYPE type BY priority memname [ownership type]

  Name and type of a Control resource currently being used by another job order, which is identified by name. For critical path jobs, path priority of the owner is also identified.

• CONTROL OVER resource TYPE type HELD BY priority ******** [ownership type] IOAID ioaid

  Name and type of a Control resource currently being used by another job order in a different instance of the Control-M monitor. The IOAID of the monitor holding this resource is also shown.

• [L|G]-WORKLOAD policy_name REACHED MAX JOBS POLICY LIMIT OF number

  Name of Workload Policy (either Local or Global) that did not allow the job to run, and the number of concurrent jobs set as the maximum limit in the JOB-type rule in the Workload Policy.

  If a description is defined in the Workload Policy rule, an additional line provides the description.

  If a Load-Index is defined in the Workload Policy rule (limiting the enforcement of the rule to a threshold load level), an additional line provides the name of the Load-Index and the current Load-Index level.

  Below is an example:

------------------------ M17WAIT3 SCHEDULING ANALYSIS --------------------(3.?)

 COMMAND ===>                                                    SCROLL===> CRSR

 OPT DESCRIPTION                                                                

     L-WORKLOAD SCHENV               REACHED MAX JOBS POLICY LIMIT OF 0001      

     DESCRIPTION: ONLY 1 SCHEDULE ENVIRONMENT SHOULD 1                          

     L-WORKLOAD GROUP SCHN           REACHED MAX JOBS POLICY LIMIT OF 0001      

     DESCRIPTION: ONLY SCH ENV                                                  

     DUE TO LOAD-INDEX LI123              AT LEVEL CRITICAL                   

  ====== >>>>>>>>>>>>>>>>>>>>>   END OF "WHY" LIST   <<<<<<<<<<<<<<<<<<<<< =====

• required_number RESOURCES resource_name NOT AVAILABLE FOR 
         [L|G]-WORKLOAD policy_name DUE TO MAX OF number

  Required number of a specific resource were not available for the job, due to a RESOURCE-type rule in the Workload Policy (either Local or Global). The rule set a maximum limit for the number of resources that the job is allowed to use.

  If a description is defined in the Workload Policy rule, an additional line provides the description.

  If a Load-Index is defined in the Workload Policy rule (limiting the enforcement of the rule to a threshold load level), an additional line provides the name of the Load-Index and the current Load-Index level.

• L-WORKLOAD policy_name  JOBS EXECUTION POSTPONED
  WHILE [L|G]-WORKLOAD blocking_policy_name JOBS ARE EXECUTING

  Name of Local Workload Policy that did not allow the job to run, due to a SEPARATE EXECUTION rule that blocks job execution at the same time as jobs from other Workload Policies (specifically listed in the rule). Each blocking Workload Policy that had running jobs is listed on a separate line.

  If a description is defined in the Workload Policy rule, an additional line provides the description.

  If a Load-Index is defined in the Workload Policy rule (limiting the enforcement of the rule to a threshold load level), an additional line provides the name of the Load-Index and the current Load-Index level.

• JOB WAIT FOR PIPES COLLECTION

  PIPE pipename

  The job was not run for one of the following reasons:

  • Control-M is waiting for the minimum number of participants in the indicated pipe.
  • At least one prerequisite (prerequisite condition, resource, confirmation, and so on) for a participant in the indicated pipe is not satisfied.

If the job belongs to a SMART Table, the Why screen displays messages related to both the selected job and the table to which the job belongs. In this case, the reasons indicated above may be applicable to the selected job and/or to the table.

To enable you to distinguish between "job" reasons and "table" reasons, the job reasons appear in the screen before the table reasons, and the two sets of reasons are separated by the following line:

In addition to the above line, the following reasons can appear only for a job in a SMART Table:

• JOB’S RUNTIME CRITERIA SATISFIED

  This reason applies to the job.

• TABLE’S RUNTIME CRITERIA SATISFIED

  This reason applies to the table.

• WAIT WORKLOAD

  The job was not run for one of the following reasons:

  • WORKLOAD <workload_name> - REACHED MAX JOBS POLICY LIMIT OF xxxx
  • nnnn RESOURCES <resource_name> NOT AVAILABLE FOR WORKLOAD <workload_name> DUE TO MAX OF mmmm

  Where:

  xxxx - maximum number of parallel executing jobs for WORKLOAD

  nnnn - required number of resources for this job

  mmmm - maximum number of resources defined for WORKLOAD