| Previous | TContents | YIndex |
G A series of SCHEDULE commands may be executed using a command A file. The command file can consist of multiple SCHEDULE 0 commands as well as several formatting commands.
> The command can be entered in any of the following three ways:
+ schedule @ command_file.schedule /
schedule . command_file.schedule 4
schedule source command_file.schedule
A All valid SCHEDULE commands in the command file will be H executed in order. In addition a number of other formatting conventions @ may also be used. These are described in the following sections. / 2.3.8.1 Comments
F A comment may be added to a command file using either of two symbols. H Sections of a command file delineated by this symbol will be ignored by B the command interpreter. The symbol may be either a ! or a #. The D following is an example of a comment in a SCHEDULE command file.
|
" J !======================================================================== J ! The following commands will create and set the protection on a SCHEDULE ! directory. J !======================================================================== mkdir /report chdir -prot=og+r /report |
A All or selected lines of a SCHEDULE command file may be E displayed to the screen by turning on the verify option. This causes G all lines to be echoed following the command. The verify option may be > turned off at any point by placing noverify at the end of the C designated section. An example of the verify option is shown below:
|
" verify mkdir /report chdir -prot=og+r /report noverify |
G SCHEDULE command files can process input from subsequent data F lines using a prefix and suffix before and after the input lines. For A instance, this can be used to insert report definitions into the SCHEDULE database.
? The data input lines must directly follow the command as shown:
|
" INSREP NEW_REP * $DECK G report title="System wide summary of events/selected by all settings/- (SCHH_SYS_ALLEVENT_ALL_80)",- out=**."Output",- = srcshr=scheduleshr,srcrtn=scheduleh_db_io,columns=80 & select directory, include="[*],[*.*]" " select job_name, include=**."Job" H select set_id, minimum=**."Minimum set id", maximum=**."Maximum set id" > select log_date, from=**."From log date", to=**."To log date" * select sch_event, include=**."Queue_list" B print log_date,sort,title="Log date",edit_string="NN-DD-YYBTTTTT" print sch_event,title="Event" 5 print full_name,title="Job name",edit_string="X(20)" print set_id,title="Set id" 9 print cpu_time,edit_string="ZZZ,ZZZ.ZZ",title="Cpu time" 8 print io_count,edit_string="Z,ZZZ,ZZZ",title="Io count" end $EOD |
C The keyword or symbol used to represent data input from within the ) command file can be any of the following:
command *
command sys$input
command stdin
command 0
% The list of data must be preceeded by
$DECK
or
*DATA*
and followed by
$EOD.
or
*EOD*.
| Previous | VNext | TContents | YIndex |