| Previous | TContents | YIndex |
H When you wish to invoke SCHEDULE enter the command SCHEDULE at G the DCL prompt, followed by the requested function. The general syntax 4 of the command is indicated by the following format.
|
" 5 $ SCHEDULE COMMAND [/SECTION] job_name [/qualifiers] |
D All qualifiers can appear anywhere to the right of the section name.
@ Data inside the SCHEDULE System is broken up into five @ sections. A section name must be specified after the command to H indicate which section is to be affected. The various section names are listed below.
| Name | "Section |
|---|---|
| /JOB | job control attributes |
| /CALENDAR | calendar definitions |
| /HISTORY | job history data |
| /QUEUE | scheduling queues |
| /DIRECTORY | directory information |
= Some of the SCHEDULE line commands are listed below.
| Field | &Description |
|---|---|
| COPY/JOB | $ copy an entire job definition |
| CREATE/CALENDAR | ' create a new calender definition |
| CREATE/JOB | " create a new job definition |
| CREATE/DIRECTORY | create a new directory |
| DELETE/JOB | ' delete a job definition from the SCHEDULE database |
| DIRECTORY/CALENDAR | 6 display information about the calendars defined |
| DIRECTORY/JOB | 1 display information about the jobs defined |
| DIRECTORY/DIRECTORY | 2 display information about known directories |
| EDIT/JOB | B allows any one of the three lists (commands, initiates, or $ prerequisites) to be modified |
| MODIFY/JOB | = change any of the fields that make up a job definition |
| MONITOR/QUEUE | * monitor the activity on a job queue |
| SUBMIT/JOB | I submit a job for immediate execution, regardless of any parameter settings |
| TYPE/JOB | N type out the list sections that can be associated with a job definition |
| TYPE/HISTORY | + type out historical data about a job |
| Previous | VNext | TContents | YIndex |