NetBatch Manual

Attributes
NetBatch Manual—522460-004
7-56
EVERY Job Attribute
Each crontab-entry field can contain:
•
A number in the specified range
•
Two numbers separated by a dash to indicate an inclusive range
•
A list of numbers separated by commas, which selects all numbers in the list
•
An asterisk (*), meaning all legal values
The specification of days can be made by two fields ( day-of-month and day-
of-week). If you specify both as a list of elements, both are adhered to. For
example, this entry specifies midnight on the first and fifteenth days of each month,
as well as every Monday:
0 0 1,15 * 1
If you use only one of the two fields to specify days, you must put an asterisk in the
other field.
Considerations
•
A job with the EVERY attribute can run immediately on submission unless
delayed by another attribute. When execution finishes, the scheduler reschedules
the job to run when the EVERY interval expires. The scheduler calculates the next
run time by adding the interval to the original submission time. The rescheduled job
retains all its original attributes, including the job number.
•
To remove the EVERY attribute from a job, use the ALTER JOB command to
specify EVERY without any qualifiers; for example, ALTER JOB 19, EVERY.
•
The NetBatch expression for a job with the CALENDAR or EVERY attribute
is
“recurrent job.” These attributes cause the job to run repeatedly (that is, recur) at
a specified interval. Conversely, a nonrecurrent job is a job whose attributes do not
include CALENDAR or EVERY.
•
A job with the EVERY attribute accumulates a run backlog if it is held (HOLD
ON)
or suspended for longer than the EVERY interval and the scheduler has the
attribute CATCHUP ON. When you take the job off hold or reactivate it, it runs
repeatedly until the backlog clears. The job also accumulates a run backlog if it
runs for longer than the EVERY interval. The scheduler treats a job with a HOLD
ON set as a failed job. When a job is HOLD OFF, the scheduler correctly
reschedules the job. If it is an EVERY JOB, it immediately runs once. For more
information about run backlogs (including how to prevent them from running), see
ACTIVATE JOB Command on page 6-32.
•
The CALENDAR and EVERY job attributes are mutually exclusive. This
restriction means a job can have one of the attributes, but not both. It also means
that CALENDAR overrides EVERY when assigned to a job whose attributes
include EVERY, and EVERY overrides CALENDAR when assigned to a job whose
attributes include CALENDAR.