Note: Although this panel and command specifically mentions CPU jobs, these functions are also available with all cross-platform jobs (for example, XPJOBs or agent jobs).
The Job Scheduling Parameter Edit panel lets you define or review schedules for jobs that are run on a date and time basis.
To display the panel, enter EDIT as the function on the DB.2.1 panel.
To exit the panel:
------------------ CA-7 CPU JOB SCHEDULING PARAMETER EDIT ------------------ FUNCTION: xxxxxxxx (ADD,DELETE,EXIT,FORMAT,LIST,REPL,SAVE,SR,SS) JOB: xxxxxxxx SCHID: nnn SCAL: xx ROLL: x INDEX: nnnn DOTM LDTM SBTM ---------------------REPEAT---------------------- hhmm hhmm hhmm INTERVAL: hhmm TYPE: xxxxx COUNT: nnnn STOP: hhmm -- _ -- DAILY -- _ -- WEEKLY SUN: _ MON: _ TUE: _ WED: _ THU: _ FRI: _ SAT: _ -- _ -- MONTHLY JAN: _ FEB: _ MAR: _ APR: _ MAY: _ JUN: _ JUL: _ AUG: _ SEP: _ OCT: _ NOV: _ DEC: _ WEEK: ______________ DAY-OF-WEEK: ___________________________ RDAY: ____________________________________________________________ -- _ -- ANNUAL DAY: _______________________________________________________ DEFAULT SCAL: xx -- _ -- SYMETRIC START: ___ SPAN: ___ SCHID-COUNT: nnn PROGRAM: SM72 MSG-INDX: nn -- DB.2.1-E -- yy.ddd / hh:mm:ss MESSAGE:
This panel contains the following fields:
Specifies the function to perform. Value must be the name of some other panel or one of the following:
Adds a new SCHID to the work area.
Deletes a SCHID from the work area.
Returns the user to the DB.2.1 panel restoring the SCHID-COUNT and schedule data to that which existed when EDIT was initially entered and clears the work area. Any changes made are ignored.
Clears the panel of user input data.
Lists all existing SCHIDs, one per panel.
Replaces an existing SCHID in work area. (Before replacing, you must use the LIST command to display the existing record.)
Updates SCHID-COUNT and SCHID information, and returns the user to the DB.2.1 panel. Work area data (changes) are retained but the database is not updated.
Combination function that results in a SAVE, a return to the DB.2.1 panel, and a subsequent REPL to replace an existing schedule in the database. Saves all schedule IDs into the Active Area and replaces them in the CA WA CA 7 Edition database. If not specified, the scheduling changes are lost once leaving this panel. Entering the SR function automatically returns you to the prior scheduling panel.
Combination function that results in a SAVE, a return to the DB.2.1 panel, and a subsequent SAVE to add a newly defined schedule in the database.
Batch keyword: Positional parameter
Reflects the job name from the previous panel. This is informational only.
Specifies the numeric schedule ID on which the user wants to perform the specified action.
Limits: 1 to 3 numeric characters from 1 through 999
Batch keyword: SCHID
(Optional) Specifies the override of the default SCAL for this SCHID. If this SCHID is using the default, this field is blank.
Limits: 2 alphanumeric characters
Batch keyword: SCAL
(Optional) Specifies the action to take when a schedule day falls on a base calendar nonavailable processing day. This is not used if the DAILY option is used. If used, the value must be one of the following:
Roll the schedule back to the previous available processing day in the Base Calendar.
Roll the schedule forward to the next available processing day.
Do not roll. Schedule day must stand.
Do not roll and do not schedule.
Default: D
Batch keyword: ROLL
(Optional) Specifies an adjustment to schedule days. After exercising the ROLL option, the schedule is adjusted, forward for plus or backward for minus, by the number of working days entered.
Limits: 4 numeric characters specified as Innn where I can be plus (unsigned) or minus (-) and nnn can be 0 to 365 days
Batch keyword: INDEX
You can use this field together with the RDAY field to schedule a job to run 3 work days before the 15th of the month: specify -3 in the INDEX field, X in the MONTHLY field, and 15 in the RDAY field.
Specifies the due-out time of day for this schedule ID.
Limits: 4 numeric characters specified as hhmm where hh can be 00 through 24 and mm can be 00 through 59. Must be greater than 0000.
Required for ADD and REPL functions.
Optional for DELETE, EXIT, FORMAT, LIST, SAVE, SR, and SS functions.
Batch keyword: TIME
In batch format, this field and the next two fields must be provided as a list of hhmm values as follows:
TIME=(dueout,lead,submit)
Specifies the lead time (elapsed or clock time) for this schedule ID. Lead time specifies the amount of time necessary to ensure that the job completes before its due-out time plus any additional time required to perform setup functions. This value is used for deadline prompting and forecasting only if elapsed (clock) time on the DB.1 panel is set to 2359.
Limits: 4 numeric characters specified as hhmm where hh can be 00 through 24 and mm can be 00 through 59. Must be greater than 0000.
Required for ADD and REPL functions.
Optional for DELETE, EXIT, FORMAT, LIST, SAVE, SR, and SS functions.
Batch keyword: TIME
(Optional) Specifies the submit time of day for this schedule ID. If specified, the job is not submitted before this time. If the submit time is before deadline start time, the submit time requirement is automatically satisfied when the job enters the queue. A submit time of zeros is the same as not specifying it, and no submit time is set up.
Note: If the submit time is after the due-out time, the submit day value is set to the previous day.
Limits: 4 numeric characters specified as hhmm where hh can be 00 through 24 and mm can be 00 through 59
Batch keyword: TIME
(Optional) Specifies that the job should be repeated (executed more than once) and specifies the amount of time between each iteration.
If INTERVAL is specified, the SBTM (submit time requirement) and TYPE fields are required.
If both INTERVAL and COUNT are specified, the INTERVAL value times the COUNT value must total less than 24 hours.
If INTERVAL is not specified, the job is not repeated.
Note: For more information about how deadline, due-out, and submit time requirements are calculated for repeating jobs, see the Usage Notes.
Limits: 4 numeric characters in hhmm format where hh can be from 0 to 23 and mm can be from 00 to 59
Batch keyword: INTERVAL
(Optional) Determines how the submit time requirement is calculated for repeating jobs. A TYPE of CLOCK indicates that the INTERVAL is added to the previous iteration's submit time requirement to determine the new submit time requirement. A TYPE of START and END indicates that the INTERVAL is added to the previous iteration's last (most recent) start and end times, respectively, to determine the new submit time requirement. TYPE is required if INTERVAL is specified. TYPE is discarded if INTERVAL is not specified.
Limits: CLOCK, START, or END
Batch keyword: TYPE
(Optional) Specifies the maximum number of times to repeat the job. COUNT is discarded if INTERVAL is not specified. If both COUNT and STOP are specified, the job stops repeating when either the COUNT reaches zero or the STOP time is reached, whichever comes first. If COUNT is not specified, the job repeats until the STOP time is reached.
Limits: 1 to 4 numeric characters from 0 to 1439. Leading zeros can be discarded.
Batch keyword: COUNT
(Optional) Specifies the clock time on or after which the job should not be repeated. STOP is discarded if INTERVAL is not specified. If both COUNT and STOP are specified, the job stops repeating when either the COUNT reaches zero or the STOP time is reached, whichever comes first.
If the STOP time is less than the submit time requirement, the stop date is assumed to be the following day.
A stop time of zeros is the same as not specifying a value.
Default: 1439 minutes (24 hours minus 1 minute) after the submit time
Limits: 4 numeric characters specified as hhmm
where hh can be from 0 to 23 and mm can be from 00 to 59
Batch keyword: STOP
(Optional) Specifies that the user wants to define a daily schedule. Daily means every available processing day as defined by the Base Calendar. Enter an X or Y to select this. If DAILY is used, the ROLL function has no effect.
Batch keyword: DAILY
(Optional) Specifies that the user wants to define a weekly schedule. Enter an X or Y to select this. If WEEKLY is used, the run days of the week must be selected using the SUN through SAT fields.
Batch keyword: WEEKLY
Defines specific days of the week on which to run the job.
Online:
Place an X in panel field names SUN through SAT as necessary to indicate the weekly run days.
Limits: Required if WEEKLY is used.
Batch keyword: DAYS
Batch:
Place an X in any of the seven positions following the batch keyword DAYS to indicate weekly run days. A day is skipped by omitting an X for that day. For example, if a job is to run weekly on Sunday, Wednesday and Saturday, the user would specify:
DAYS=(X,,,X,,,X)
(Optional) Specifies that the user wants to define a monthly schedule. If this field is used, the user can optionally specify on which particular months the job is to run. If specific months are not specified in the JAN through DEC fields, all months are assumed. Enter an X or Y to select this.
Limits: At least WEEK(S) and DAY-OF-WEEK (DOW) or RDAY(S) must also be specified if MONTHLY is used.
Batch keyword: MONTHLY
(Optional) Online:
Place an X in panel field names JAN through DEC to indicate the run months during the year. Used with MONTHLY.
Default: Every month if MONTHLY is used and no months are chosen
Batch keyword: MONTHS
Batch:
Place an X in any of the 12 positions following the batch keyword MONTHS to indicate run months. A month is skipped by omitting an X for that month. For example, if a job is to run in January, June, July, and November, the user would specify:
MONTHS=(X,,,,,X,X,,,,X,)
Specifies which weeks of the month to run the job. The values specified can be positive (unsigned), negative (-) or slash (/).
Positive values 1, 2, 3, 4, or 5 are used to indicate days of week relative to the beginning of the month. Negative values -0, -1, and -2 are used to indicate occurrence of day of week relative to the end of the month. Slashes indicate not the following value. For example, a job that is to run on the first occurrence of day of week of every month and is also to run on the last occurrence of day of week of the month would be entered as:
Online:
WEEK:1,-0 (separated by blanks or commas)
Limits: 1 to 14 numeric characters and required if MONTHLY and DAY-OF-WEEK are used.
Batch keyword: WEEKS
Batch:
WEEKS=1 -0 (separated by blanks)
Specifies which days of the week to run the job. If used, each day must be the first three letters of the wanted run days just as it appears on the panel following the weekly field (for example, SUN, MON, and so on).
Online:
DAY-OF-WEEK:TUE,THU
(separated by blanks or commas)
Limits: 3 to 27 alphanumeric characters and required only if WEEK is used with MONTHLY.
Batch keyword: DOW
Batch:
DOW=TUE THU (separated by blanks)
(Optional) Specifies relative days of the month on which the job is to run. Used with MONTHLY. A day relative to the beginning or end of the month is specified. If a positive (unsigned) value is used, the job runs that day relative to the first of the month. Negative (-) values are used to indicate run days relative to the end of the month.
Additionally, if you have days of the month when this job is not to run, a slash (/) can be used with the unsigned or negative values. Valid positive values range from 1 to 31. Valid negative values range from -0 to -30.
Limits: 1 to 60 numeric characters
Batch keyword: RDAYS
To understand the meaning and use of RDAY, assume a job is to run daily, but not on the first and last day of each month. The user could select DAILY, MONTHLY and specify:
Online:
RDAY:/1,/-0 (separated by a blank or comma)
Batch:
RDAYS=/1 /-0 (separated by a blank)
Note: RDAY(S) represents calendar days, unless the base calendar was generated with OPTIONS=SCHDYONLY, in which case RDAY(S) represents processing days.
(Optional) Defines an annual schedule. To select this type of schedule, enter an X or Y in this optional field.
Limits: If ANNUAL is used, DAY is required.
Batch keyword: ANNUAL
(Optional) Specifies on which days of the annual schedule the user wants to run the job. Days are entered as 1 through 366 and are prefixed by positive (unsigned) or slash (/) values. Slash indicates not this day.
Limits: 1 to 55 numeric characters and required if ANNUAL is used.
Batch keyword: ANNDAYS
For example, if a job is to run on days 121, 132, 240, and 241, but is not to run on days 122, 242, and 1, the user would specify:
Online:
DAY:/1,121,/122,132,240,241,/242
(separated by blanks or commas)
Batch:
ANNDAYS=/1 121 /122 132 240 241 /242
(separated by blanks)
By default, days not specifically defined as processing days (with a number) are considered as unscheduled days unless another field, such as WEEKLY or MONTHLY schedules those days. The use of the slash (/) examples given above is only provided here to illustrate the format of the date specification.
The following illustrates a more practical example of using "not days" (/). Assume a job's schedule has been defined as every Friday by selecting WEEKLY and FRI. During the week containing Julian day 177 (a Friday), the job is to run on Thursday (176) instead of Friday. The user would select WEEKLY, FRI, ANNUAL, and specify:
Online:
DAY:/177,176
Batch:
ANNDAYS=/177 176
When specifying annual days in a schedule definition, keep in mind whether this schedule is to be resolved for a January through December schedule or a July through June schedule. For January through December resolutions, the Julian dates specified are simply for the year resolved.
For July through June resolutions, July through December dates are for the current year. January through June dates are for the next year.
Reflects the default SCAL value from the previous panel. This value applies to all SCHIDs unless the SCAL field is supplied on the current panel.
(Optional) Used with the START and SPAN fields, defines a symmetric schedule. With this option, schedules are defined as beginning on the date specified with the START field and recurring every nnn days as specified with the SPAN field. (This field is misspelled intentionally to provide compatibility with the batch keyword that cannot exceed eight characters.) The selection of this type of schedule is made by entering an X or Y.
Batch keyword: SYMETRIC
(Optional) Used with SPAN and SYMETRIC fields, defines a symmetric schedule. This field is required when the SYMETRIC option is taken. Value must be specified as the Julian day of the year on which the symmetric schedule is to begin. This value should be evaluated yearly before schedule resolution and may need to be changed each year.
If the schedule will be resolved on a July-June basis, the start date must be within the first of the two years in which the schedule overlaps. For January-December schedules, it is simply relative to January 1 of the year specified on a RESOLV command.
If the calendar against which this SCHID will be resolved does not have the OPTIONS=SCHDYONLY, the START day is adjusted each year to maintain the job's symmetric schedule from the job's original specified START day.
If the calendar against which the SCHID will be resolved was generated with overall available processing days only (OPTIONS=SCHDYONLY), the start date must specify the first day on which the job would actually run. This requires manually setting (verifying) the START value each year before the RESOLV.
If a nonprocessing day is specified, the start day is the next processing day found in the calendar. For example, if January 1 is a nonprocessing day and the calendar was generated with OPTIONS=SCHDYONLY, and 1 is specified as the START day, January 2 is the actual START day (provided it is an available processing day). SPAN is based from January 2 in this example rather than January 1.
For other types of calendars, the start date is determined at RESOLV time based on the ROLL and INDEX options taken.
Limits: 3 numeric characters specified as Julian day of the year from 1 to 365
Batch keyword: START
(Optional) Used with SYMETRIC and START, defines symmetric schedules. This field is required if the SYMETRIC option is taken. When used, specifies the number of days between scheduled processing cycles.
If the calendar against which the SCHID will be resolved was generated with processing days only (OPTIONS=SCHDYONLY), the SPAN value is specified as the number of available processing days between and including the next processing date as opposed to the actual number of days. With this type of calendar, the ROLL and INDEX options serve no practical purpose. For other calendar types, the SPAN value is specified as the number of calendar days between processing cycles and the ROLL and INDEX options can be used as necessary.
Limits: 1 to 3 numeric characters from 1 to 255
Batch keyword: SPAN
Identifies a system-generated field containing the current schedule ID count for this job.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|