Keep Active for

Determines the number of extra days (beyond the original scheduling date) that the job is allowed to remain in the Active Jobs database while awaiting execution. If the job still has not run after the specified number of days, the job is removed from the Active Jobs database.

The Keep Active for parameter of a job which belongs to a SMART folder or folder is overwritten by the Keep Active for value that belongs to the first Rule-Based Calendar that is fulfilled (the Rule-Based Calendar which is used by the job), if the relationship parameter of the job is defined as "or".

The Keep Active for parameter for a SMART Folder or sub-folder is taken from the first positive Rule-Based Calendar.

The Keep Active for parameter is used to handle the following types of occurrences:

For non-cyclic jobs

• A job that is scheduled for execution on a specific day is not always submitted that same day. This may be due to any number of reasons, such as a heavy production workload, a problem in one of the job’s predecessors causing a process to stop, or a hardware failure. When the Keep Active for is assigned a value greater than zero, the job is retained in the Active Jobs database up to the specified number of days, allowing the job additional opportunities to be submitted.
• A job that ends NOTOK during the night is deleted from the Active Jobs database on New Day plus one day. Using the Keep Active for parameter, the user can retain an overnight job that ends NOTOK in the Active Jobs database for a number of days, allowing the operator an opportunity to correct the problem and rerun the job without the need to re-order the job. A job that end NOTOK is retained in the Active Job's database by the scheduled ODATE+Keep Active number of days+ 1 additional day.

  Example:

  • Jobs A and B ordered on 02/09 with Keep Active for 3 days.
  • Job A ends NOT OK on 02/09.
  • Job B, having not yet been submitted, is removed on 02/13.
  • Job A is removed on New Day for 02/14.

  NOTE: If the time zone job is set with the Control-M/Server time zone, and the job ends NOTOK, it remains one additional day in the Active Jobs database.

For cyclic jobs

• If CYCLIC_MAXWAIT (Control‑M parameter) is set to KEEP (default), the Keep Active for parameter does not depend on whether the job ended OK or NOTOK. Cyclic jobs are only deleted from the Active Jobs database after the expiration of the Keep Active for parameter.
• If CYCLIC_MAXWAIT is NOT_KEEP, Cyclic jobs are removed from the Active Jobs database at the next run of the New Day procedure, unless they are executing when the New Day procedure begins. In this case, they are removed at the run of the following New Day procedure.

EXAMPLE 1: Retain job until resources available

Retain a scheduled job indefinitely, until the runtime resources required for the job are available:

Keep Active forever

EXAMPLE 2: Retain job beyond original scheduling date

Retain a job for an extra three days beyond its original scheduling date:

• Days 02,04,06
• Keep Active for 03

  Assume that the job does not run due to the absence of the required runtime resources. The job that is scheduled for day 2 of the month waits from the second through the fifth to be executed.

  On the sixth of the month, Control‑M "gives up," and the job that was originally scheduled for day 2 is deleted. The jobs scheduled for days 4 and 6 wait until as late as days 7 and 9 respectively to be executed.

EXAMPLE 3: Schedule a job for periods when the computer is inactive

Schedule the job for every working day, whether the computer is active. Allow each scheduled job three extra days to execute:

• Days Calendar WORKDAYS
• Retro Y
• Keep Active for 03

  Given the following circumstances:

• The WORKDAYS calendar, specified in the Days Calendar parameter, contains the values 15, 16, 17, and 19.
• The computer was off-line from day 15 up to and including day 18.

  When the computer is brought back online on day 19, the job is scheduled four times, with original scheduling dates (Odate) of the 15, 16, 17 and 19, respectively. Each scheduled job that does not execute successfully (, either not submitted or did not end OK) is handled as follows by Control‑M:

• The job with Odate 15 is retained on day 19 and deleted from the Active Jobs database on day 20 even though the Keep Active for period of three days has already passed since each job with Retro Y is given at least one day to run.
• The job with Odate 16 is deleted on day 20 since day 19 is the last day of the Keep Active for period of three days.
• The job with Odate 17 is deleted on day 21 since day 20 is the last day of the Keep Active for period of three days.
• The job with Odate 19 is deleted on day 23 since day 22 is the last day of the Keep Active for period of three days.