THIS LINE TO TOP OF SCREEN .
PREVIOUS SECTION .
NEXT SECTION .
JOB SCHEDULE SCREEN .
BACK
------------------ CA-7 CPU JOB SCHEDULING PARAMETER EDIT --------------
FUNCTION: LIST (ADD,DELETE,EXIT,FORMAT,LIST,REPL,SAVE,SR,SS)
JOB: JOBNAME SCHID: 3 SCAL: WD ROLL: D INDEX: 000
DOTM LDTM SBTM
0100 0200 2300
__ __ DAILY
__ __ WEEKLY SUN: MON: TUE: WED: THR: FRI: SAT:
__ __ MONTHLY JAN: FEB: MAR: APR: MAY: JUN:
JLY: AUG: SEP: OCT: NOV: DEC:
WEEK: 1,-0,/2 DAY-OF-WEEK: THU
RDAY: 3,/5,/-2,-0
__ __ ANNUAL DAY: 100,/231
__ __ SYMETRIC START 21 SPAN: 28
PROGRAM SM20 MSG-INDX: 00 -- DB.2.1-E -- 99.365 / 23:59:59
MESSAGE: LIST SUCCESSFUL
THIS LINE TO TOP OF SCREEN .
PREVIOUS SECTION .
NEXT SECTION .
JOB SCHEDULE SCREEN .
BACK
The DOTM field.
The job's Due-out (DOTM) time is when it should complete.
Note that the submit time is back calculated from the DOTM so
here if the job was scheduled with these times it would be submitted
23:00 Sunday night. Batch keyword: TIME=(due-out,lead,submit)
THIS LINE TO TOP OF SCREEN .
PREVIOUS SECTION .
NEXT SECTION .
JOB SCHEDULE SCREEN .
BACK
The LDTM field.
Ensure that the LDTM is not more than the difference between
the DOTM and the SBTM - this ensures the job is requested by the
right schedule scan. If the CLOCK time is 2359 the DEADLINE
time is the DOTM minus the LDTM.
THIS LINE TO TOP OF SCREEN .
PREVIOUS SECTION .
NEXT SECTION .
JOB SCHEDULE SCREEN .
BACK
The SBTM field.
This is the time at which the job will be released.
If this is more than the DOTM, the submit date will be for the
previous day. If omitted the job will be requested and released
when Schedule Scan executes.
THIS LINE TO TOP OF SCREEN .
PREVIOUS SECTION .
NEXT SECTION .
JOB SCHEDULE SCREEN .
BACK
The SCHID field.
The schedule ID that the job will be requested for.
If the job is demanded with- out specifying a schedule ID
it will select the FIRST SCHID defined in the job schedule.
Keyword: SCHID=2
THIS LINE TO TOP OF SCREEN .
PREVIOUS SECTION .
NEXT SECTION .
JOB SCHEDULE SCREEN .
BACK
The SCAL Field.
The calendar to be used.
The default is set on the previous
screen but now under 3.2 it can be over-written here.
LISTDIR,DSN=*SCAL* will list all available calendars.
PRINT,SCAL= shows the details of one calendar.
Batch keyword: SCAL=WD
THIS LINE TO TOP OF SCREEN .
PREVIOUS SECTION .
NEXT SECTION .
JOB SCHEDULE SCREEN .
BACK
The ROLL Field.
This option determines what occurs when a non-working date is selected.
These dates are defined in the calendar - see the PRINT command.
If the default of D is used the job will not be run on this day.
If F is coded the next working day will be used.
B means the date will be the previous working date.
N means the job will not be rolled and the job will be run on
that date. (Note it doesn't work with DAILY) ROLL=D
THIS LINE TO TOP OF SCREEN .
PREVIOUS SECTION .
NEXT SECTION .
JOB SCHEDULE SCREEN .
BACK
The INDEX Field.
Once the ROLL has been calculated the INDEX is applied.
This is the number of days added to or subtracted from all
selected dates. Non-working days are not counted. INDEX=-2.
THIS LINE TO TOP OF SCREEN .
PREVIOUS SECTION .
NEXT SECTION .
JOB SCHEDULE SCREEN .
BACK
The DAILY Field.
Requests the job for every working day.
You cannot use ROLL=N to request jobs on non-working days
(Use ROLL=N, WEEKLY & an X next to each day) Batch keyword: DAILY=Y
THIS LINE TO TOP OF SCREEN .
PREVIOUS SECTION .
NEXT SECTION .
JOB SCHEDULE SCREEN .
BACK
The WEEKLY Fields.
Schedule on a weekly cycle.
Put X next to the day or days. Keywords:
WEEKLY=Y,DAYS=( , X , , , , , )
THIS LINE TO TOP OF SCREEN .
PREVIOUS SECTION .
NEXT SECTION .
JOB SCHEDULE SCREEN .
BACK
The MONTHLY Fields.
Run monthly.
Must be used with RDAY or both WEEK and DAY-OF-WEEK.
Leave all months blank if all are required.
Keywords MONTHLY =Y, MONTHS=( X , , , X , , , X , , , X , , )
THIS LINE TO TOP OF SCREEN .
PREVIOUS SECTION .
NEXT SECTION .
JOB SCHEDULE SCREEN .
BACK
The WEEK & DAY-OF-WEEK Fields.
Used to select or exclude particular days of the week within a month.
A / (slash) means dates are excluded and a - (minus) works
from the back of the month. Here the job will be requested
on the first and last THU & FRI of the month.
The /2 means the 2nd THU & FRI will be excluded if
selected by other criteria. These fields will select
and count non-working days. Kewords: WEEKS=1 -0 /2, DOW=THU FRI
THIS LINE TO TOP OF SCREEN .
PREVIOUS SECTION .
NEXT SECTION .
JOB SCHEDULE SCREEN .
BACK
The RDAY Field.
With SCHDDAYONLY=N it will select or exclude days of the month.
Here the 3rd and last days would be selected but the 5th day of
the month and the 3rd-to-last day would be excluded.
With SCHDDAYONLY=Y it selects or excludes relative working days
of the month. So here the job would run on the 3rd and last working
day and exclude the 5th and 3rd-to-last working day.
Batch keyword: RDAYS =3 -0 /5 /-2
THIS LINE TO TOP OF SCREEN .
PREVIOUS SECTION .
NEXT SECTION .
JOB SCHEDULE SCREEN .
BACK
The ANNUAL Field.
Selects or excludes Julian dates.
Note if resolving after JUNE, JAN-JUN dates are used
for the following year. This facitliy should be used
with care as the dates will need changing every year.
Consider using #ED and #BD statements so a year can be defined.
ANNDAYS=100 /231
THIS LINE TO TOP OF SCREEN .
PREVIOUS SECTION .
NEXT SECTION .
JOB SCHEDULE SCREEN .
BACK
The SYMETRIC START Field.
This defines the first day to be used on a SYMETRIC schedule.
If used on a SCHDDAYONLY=Y calendar this value will need to
be altered every year to maintain the cycle.
If the date specified is a non-working day, the next working day
is used. For SCHDDAYONLY=N calendars there should be no
need to update the field every year. However you may break
the cycle if resolved manually. Keywords: SYMETRIC=Y,START=21
The SYMETRIC SPAN Field.
With SCHDDAYONLY=Y this example means run every 28 working days.
For SCHDDAYONLY=N the job is requested every 28 days whether
working days or not. See START box for problems.
Keyword: SPAN=28