c D SCHEDULE Automated Job Submission System Guide and Reference Manual D SCHEDULE
Automated Job Submission System
Guide and Reference Manual
E The "I" indicates that the contents of "myfile.com" will be included . into the temporary COM file that is submitted.
@ The $ indicates that the following DCL command will be executed.=
/GENERAL=PRE_COM_FILE:file_spec | "I myfile.com" | $ DCL command
/GENERAL=NOPRE_COM_FILE
C The PRE_COM_FILE field indicates that a COM file is to be executed H prior to running the scheduled job. The COM file and the job are run in the same batch job. E The "I" indicates that the contents of "myfile.com" will be included . into the temporary COM file that is submitted.
@ The $ indicates that the following DCL command will be executed.=
/GENERAL=PROTECTION:(S:RWED, O:RWED, G:RWED, W:RWED)
G The PROTECTION field specifies the UIC based access rights for the job. & /GENERAL=RESTART_COUNT:number
B A nonzero RESTART_COUNT allows the job to be restarted (up to the E specified number of times) if it is terminated with a failure status code. + /GENERAL=STARTUP_WINDOW:delta_time
H The STARTUP_WINDOW specifies the interval after which a job in schedule F queue B will not be initiated. This only occurs if the system is down E when a job would have had a time based start. If the system comes up E within this interval then the job will start immediately. After this 0 interval this immediate initial run is not done. C The interval time check is suppressed if this field is set to zero (i.e. the window is infinite).
/GENERAL=STATUS:number
E The STATUS field is a full 32 bit integer status code that indicates F the success (odd) or failure (even) of a job execution. This field is 0 automatically updated each time a job completes.! /GENERAL=UP_COUNT:number
E The UP_COUNT field indicates how many times a job has been submitted - for execution. This is automatically updated.
/LOG
/NOLOG
E The LOG qualifier causes each completed operation to issue a note to the user. ) /NOTIFY=AFTER_DELAYED:delta_time
H The AFTER_DELAYED datum specifies a time limit so that any job that has E waited longer than this interval for prerequisites, disk space, or a @ file is considered delayed. At this time a notification is sent.: /NOTIFY=ALL:([user(s)] [,MAIL(Def)] [,BROADCAST])
/NOTIFY=NOALL
F The ALL sets and the NOALL clears all other NOTIFY commands. Thus ALL A will cause the creator of the job to be notified when the job is H submitted, started, delayed, completed, or if and when a job failed. If E BROADCAST is set then a logged in user will get a broadcast message. F Use NOBROADCAST to disable this. If MAIL is set a VMS MAIL message is @ sent. Use NOMAIL to disable this. If more then one user name is G specified surround the names with parentheses and separate with commas. @ /NOTIFY=COMPLETED:([user(s)] [,MAIL(Def)] [,BROADCAST])
/NOTIFY=NOCOMPLETED
E The COMPLETED field will notify the creator of a job when the job is @ completed. If BROADCAST is set then a logged in user will get a E broadcast message. Use NOBROADCAST to disable this. If MAIL is set a G VMS MAIL message is sent. Use NOMAIL to disable this. If more then one H user name is specified surround the names with parentheses and separate with commas.> /NOTIFY=DELAYED:([user(s)] [,MAIL(Def)] [,BROADCAST])
/NOTIFY=NODELAYED
G The DELAYED field will notify the creator of a job if and when the job A is delayed. If BROADCAST is set then a logged in user will get a H broadcast message. Use NOBROADCAST to disable this function. If MAIL is H set a VMS MAIL message is sent. Use NOMAIL to disable this function. If = more then one user name is specified surround the names with % parentheses and separate with commas. = /NOTIFY=FAILED:([user(s)] [,MAIL(Def)] [,BROADCAST])
/NOTIFY=NOFAILED
F The FAILED field will notify the creator of a job if and when the job G failed. If BROADCAST is set then a logged in user will get a broadcast D message. Use NOBROADCAST to disable this. If MAIL is set a VMS MAIL H message is sent. Use NOMAIL to disable this. If more then one user name C is specified surround the names with parentheses and separate with commas. > /NOTIFY=STARTED:([user(s)] [,MAIL(Def)] [,BROADCAST])
/NOTIFY=NOSTARTED
C The STARTED field will notify the creator of a job when the job is H started. If BROADCAST is set then a logged in user will get a broadcast E message. If MAIL is set a VMS MAIL message is sent. If more then one H user name is specified surround the names with parentheses and separate with commas.? /NOTIFY=SUBMITTED:([user(s)][,MAIL(Def)] [,BROADCAST])
/NOTIFY=NOSUBMITTED
E The SUBMITTED field will notify the creator of a job when the job is @ submitted. If BROADCAST is set then a logged in user will get a H broadcast message. Use NOBROADCAST to disable this function. If MAIL is H set a VMS MAIL message is sent. Use NOMAIL to disable this function. If = more then one user name is specified surround the names with % parentheses and separate with commas. 6 /RESOURCES=DISK_SPACE:(disk,number_of_blocks)
/RESOURCES=NODISK_SPACE
D The DISK_SPACE resource specifies how many blocks must be available * before the job is submitted for execution.- /RESOURCES=ESTIMATED:(cpu,elapse,io)
C The ESTIMATED datum allows for establishing an initial estimate of D cpu_time, elapse_time, and io_count. These estimated values are not D used1 for any computation. Their purpose is to assist in * planning and initially setting up the job. | Field | & Description |
| cpu | ! estimated number of seconds |
| elapse | ! estimated number of seconds |
| io | 1 estimated number of buffered and direct I/O |
" /RESOURCES=FILE:file_spec
/RESOURCES=NOFILE
H The FILE datum indicates which file, if any, must be present prior to a " job being submitted for execution.2 /RESOURCES=MEASURED:(cpu,elapse,io,count)
E The MEASURED datum displays information about cpu_time, elapse_time, G io_count, and num_count. It is usually modified automatically as a job
completes. | Field | & Description |
| cpu | average number of seconds |
| elapse | average number of seconds |
| io | / average number of buffered and direct I/O |
| count | ) number of times average is based on |
- /RESCHEDULING=CALENDAR:calendar_name
E The CALENDAR datum specifies which calendar to use when evaluating a D rescheduling method. An example of a calendar is one that specifies which days are holidays.* /RESCHEDULING=INTERVAL:delta_time
C The INTERVAL datum allows the user to specify how often or at what E interval the job is run. The INTERVAL datum is mutually exclusive of ! the MARKED, NAMED, or NONE datum. ) /RESCHEDULING=MARKED:letter_mark
H The MARKED datum allows the user to run a job on days that are "marked" E with the indicated letter. The MARKED datum is mutually exclusive of E the NAMED, INTERVAL, or NONE datum. The TIME_OF_DAY datum is used to ; specify the time the job is to run on the specified day(s). L /RESCHEDULING=MONTHLY:january...december,ordinal_number,day_of_week
H The MONTHLY datum allows the user to specify a month, several months or F ALL for all months that the job will run in. The months are separated H by commas followed by a comma then by an ordinal number (FIRST, SECOND, = THIRD, FOURTH), followed by a comma then the day of the week. |
JANUARY | FEBRUARY | MARCH | APRIL |
| MAY |
JUNE |
JULY | AUGUST |
| SEPTEMBER |
OCTOBER | NOVEMBER | DECEMBER |
| ALL | FIRST | SECOND | THIRD |
| FOURTH | DAY_OF_WEEK | | |
! /RESCHEDULING=NAMED:date
@ The NAMED datum allows the user to specify a particular date or H sequence of dates on which a job is to run by its name. The NAMED datum B is mutually exclusive of the MARKED, INTERVAL, or NONE datum. The G TIME_OF_DAY datum is used to specify the time the job is to run on the specified day(s). | SUNDAY |
TUESDAY | THURSDAY | SATURDAY |
| MONDAY | WEDNESDAY | FRIDAY | MONTH_START |
| YEAR_START | 445 | 544 | MONTH_END |
| YEAR_END | 454 | | |
/RESCHEDULING=NONE
E The NONE datum indicates that the job is not to start based on time. B Such jobs will only start if initiated by another job or manually
submitted.2 /RESCHEDULING=TIME_OF_DAY:[+/-]delta_time
E The TIME_OF_DAY field allows the user to specify what time of day to G run a job. This command is used with the MARKED and NAMED qualifier s. G The interval specified here is added to the selected day. The interval F specified can be of any length, from seconds to days. The job must be 4 on either named day or marked calendar rescheduling. /RESOURCES
D Create a generalized resource and add to RESOURCE list. The list is H where the bulk of advanced job programming occurs. Here IF-THEN and SET @ statements are processed that can check or alter the value of a 5 variable, supress a job run or cause a wait to occur.
/ N Note
P 1 In a future release these values and O the measured values will be used in a chart displaying the progress of the job. |