Global Pend Mach Interval

The Global Pend Mach Interval parameter defines the following:

The time interval (in seconds) that the scheduler waits before starting jobs in PEND_MACH status when an offline machine returns to service.
The burst value, that is, the number of jobs in PEND_MACH status that the scheduler starts after waiting for the specified interval.

The scheduler starts the specified number of jobs, waits for the specified interval, starts the specified number of jobs, waits for the specified interval, and so on. This process repeats until all jobs in PEND_MACH status for that machine are started.

When an offline machine returns to service, the scheduler updates the status of all jobs scheduled for that machine from PEND_MACH to ACTIVATED unless the jobs fail their starting condition checks. If a job fails its starting condition checks, the scheduler updates its status to INACTIVE, unless it is in a box. All jobs contained in boxes are placed in the ACTIVATED state, even if they fail their starting condition checks.

Note: You can configure CA Workload Automation AE to skip re-evaluation of starting conditions for queued jobs. If you use this configuration option, the scheduler immediately updates jobs in the PEND_MACH state to ACTIVATED when the required machine returns to service. For more information about this configuration option, see the Administration Guide or the Online Help.

If the ACTIVATED jobs meet their starting conditions or if CA Workload Automation AE is configured to skip starting condition evaluation for queued jobs, the scheduler verifies the following before starting the jobs:

Manual changes to the status of the job—If you send a manual CHANGE_STATUS event for a job and the status of the job is updated, the scheduler detects the status change and does not run the job on the machine. A message is written in the scheduler log and the scheduler proceeds with the next job start.
Issuing a FORCE_STARTJOB event—If you issue a FORCE_STARTJOB event for a job, the scheduler detects the status change and does not run the job on the machine. A message is written in the scheduler log and the scheduler proceeds with the next job start.
Reevaluation of the scheduled machine—The scheduler runs a job on a different machine (any machine other than the machine that was used to bring the job out of the PEND_MACH status) during the following situations:
- If a job is defined to run on a virtual machine and one or more component machines in the virtual machine return to service, the scheduler determines the best machine for the job from one of the component machines in the virtual machine. The same applies for jobs that are defined to run against a comma-separated list of machines. When one or more machines in the comma-separated list of machines return to service, the scheduler determines the best machine for the job from one of the machines in the list.
- If a job is initially defined against a single machine and you define a one-time override against the machine attribute while the job is in PEND_MACH status and the initial single machine returns to service, the scheduler starts the job on the machine specified by the override. If the scheduler cannot contact the machine specified by the override, it puts the job in PEND_MACH status until the machine specified by the override becomes available.
- If a job is initially defined against a virtual machine and you define a one-time override against the machine attribute while the job is in PEND_MACH status and one or more component machines in the initial virtual machine return to service, the scheduler starts the job on the machine specified by the override. If the scheduler cannot contact the machine specified by the override, it puts the job in PEND_MACH status until the machine specified by the override becomes available.
- If a job is initially defined against a comma-separated list of machines and you define a one-time override against the machine attribute while the job is in PEND_MACH status, the scheduler behaves as follows:
  - If you define a one-time override to a single machine while the job is in PEND_MACH status, the scheduler starts the job when the overridden single machine returns to service.
  - If you define a one-time override to a virtual machine while the job is in PEND_MACH status, the scheduler starts the job when one or more component machines in the overridden virtual machine return to service. The scheduler determines the best machine for the job from one of the component machines in the overridden virtual machine.
  - If you define a one-time override to a different list of machines while the job is in PEND_MACH status, the scheduler starts the job when one or more machines in the overridden list return to service. The scheduler determines the best machine for the job from one of the machines in the overridden list.
  If the scheduler cannot contact the machine specified by the override, it puts the job in PEND_MACH status until the machine specified by the override becomes available.
  
  Note: Overriding the machine attribute of a job in PEND_MACH status does not cause the scheduler to start the job. The job remains in PEND_MACH status regardless of the status of the machine specified by the override. The scheduler only evaluates jobs in PEND_MACH status when it processes the MACH_ONLINE events.
Online machine status—If the scheduler loses contact with the machine, the machine is put in offline state and all remaining jobs are put back in PEND_MACH status.

Notes:

The Global Pend Mach Interval parameter is applied at the global level and not at the machine level or job level. That is, this parameter value applies to all machines that return to service and have jobs in PEND_MACH status that are scheduled to start on them.
If you set the interval to 0 (the default value), the scheduler starts all jobs in PEND_MACH status with no delay between job starts and the burst value is ignored.
The order in which the jobs are started depends on the job priority and amount of time the job has been in PEND_MACH status. For example, if JOB1, JOB2, and JOB3 have the same priority and they enter the PEND_MACH status at 08:00:00 a.m., 08:00:01a.m., and 08:00:02 a.m. respectively, the order in which they are started is JOB1, JOB2, and JOB3. Once the scheduler determines the starting order of jobs that are coming out of the PEND_MACH status, you cannot modify the starting order by using the sendevent command to send the CHANGE_PRIORITY event. If you send the CHANGE_PRIORITY event, the job priority changes do not apply to the run of the job exiting in PEND_MACH status. The job priority changes apply to the next run of the job.
If jobs enter PEND_MACH status at the same time and have the same priority, their starting order is not guaranteed. If the job priority is set to 0, it overrides the duration the job has been in PEND_MACH status and starts immediately.
If the Global Pend Mach Interval parameter is set to a new value while the scheduler is starting jobs in PEND_MACH status, the scheduler applies the new interval only after it completes the current wait cycle.
For more information about controlling jobs in PEND_MACH status, see the User Guide.

Example: Start 100 Jobs in PEND_MACH Status with an Interval of 30 Seconds

Suppose that you want the scheduler to wait for 30 seconds before starting each of the 100 jobs in PEND_MACH status when an offline machine returns to service. Enter 30 in the Global Pend Mach Interval field on the Scheduler - CA Workload Automation AE Administrator window. The scheduler takes 50 minutes (100 jobs multiplied by 1/2 minute each) to start all of the jobs.

Example: Incrementally Start 600 Jobs in PEND_MACH Status

Suppose that you have 600 jobs in PEND_MACH status for a machine that is currently offline. When the machine returns to service, you want the scheduler to start 5 jobs at 5 second intervals. Enter 5,5 in the Global Pend Mach Interval field on the Scheduler - CA Workload Automation AE Administrator window. The scheduler takes 10 minutes to start all of the jobs.