How the BACKLOG option works in Scheduler and when BACKLOG cannot be used.
Article ID: 53412
Updated On:
Products
Issue/Introduction
Schedules and jobs that do not complete on the day on which they were selected can be carried over to the next day. These are called backlogged schedules or jobs. This document describes how the BACKLOG option works at a job level, schedule level and when BACKLOG cannot be used.
Environment
Release: 11.0
Component: Scheduler Job Management MVS
Resolution
The BACKLOG option determines which action Scheduler will take if a job or a schedule has not completed when the current day's AUTOSCAN runs. The BACKLOG option can be set at the schedule or job level and this option is relevant only when the schedule has "Auto Selection" set to YES.
Example:
--------------- CA SCHEDULER R11 SP0 (SCHD-SYSA) SCHEDULE BASE ---------------- COMMAND ===> Name . . . SCHEDUL1 Scheduling: Auto Selection . . YES Skip . . . . . 000 Backlog . . . . . YES Date Table . . Execution: Execution Node . . . . Execution Sysid . . . . Job Defaults: Library Type . . . JCL DDname . . . . Insert CA-11 . . . JES Class . . . . A Stage JCL . . . . JES Priority . . . Ins Sched Enviro . Sched Enviro . . . Non-Executable . . NO Job Type . . . . . Hold . . . . . . . NO
When BACKLOG is set to YES and the job or schedule has not completed when AUTOSCAN runs, the job/schedule is allowed to complete. Once it is completed, a new job/schedule is brought into the active workload.
BACKLOG = YES does not work for the following types of job/schedule:
- Job/Schedule defined with criteria keyword "REQUESTED". When a job or schedule is selected because of the REQUESTED keyword, it is added to the active workload with a status of "NOT REQUESTED". The job/schedule is not eligible for execution unless the REQUEST command is issued for it. If the REQUEST command has not been issued when the current day's AUTOSCAN runs, the job/schedule is purged and is not backlogged.
- Job/Schedule defined with REPEAT=YES. If the repeated job or schedule has not completed when the current day's AUTOSCAN runs, the job/schedule is purged and is not backlogged.
- If the job or schedule is defined with option HOLD=YES, and is still on hold when the current day's AUTOSCAN runs, the job/schedule is canceled and is not backlogged. If the job or schedule is placed on hold via the HOLD JOB or HOLD SCHEDULE command, the job/schedule will be backlogged.
Note:
A job will never be canceled by Scheduler if it's still running at AUTOSCAN time, regardless of the BACKLOG option.
If the CANCEL command is done on the on a backlogged schedule, a new schedule is brought into the active workload.
When a schedule is BACKLOG=YES and a job is BACKLOG=YES: any job in the schedule that has not completed is backlogged and the job is allowed to run.
When a schedule is BACKLOG=NO and a job is BACKLOG=YES: the behavior is similar to BACKLOG=YES at both the schedule and job level.
When a schedule is BACKLOG=YES and a job his BACKLOG=NO: any job in the schedule that has not completed (status WAITING) is canceled with a status "NO BACKLOG CNCL". The schedule is also canceled because there's no point of backlogging a schedule with no job.
When a schedule has BACKLOG=NO and job has BACKLOG=NO: the behavior is similar to the BACKLOG=YES at the schedule level and BACKLOG=NO at the job level.
When a schedule has BACKLOG=YES and job has BACKLOG=blank: the BACKLOG value defined for the schedule is used.
Additional Information
CA Scheduler Job Management Online Reference Guide r11 - section 11.4 Backlogged Work
Feedback
