SCHEDULE
Automated Job Submission System
Guide and Reference Manual

mkcal

Create a new calendar definition.
The mkcal command will add a new calendar definition to the database.

General Format

mkcal [-options] calendar_name

Alternate
create -calendar [-options] calendar_name

option summary

applicable to the calendar header entry:

-owner = uic
-protection = (ugo+/-rwx)
-comment = "any text string"
-[no]workdays [= noholiday (default), noweekend (default)]
-flags = noholiday_runs, noweekend_runs
-fiscal = starting month (default = january)

general qualifiers:

-node = node name
-[no]log
-[no]confirm

Examples

#1
Schedule> mkcal monthly_accounting -log created /mhattar/monthly_accounting

Options

-comment="any text string"
The COMMENT option is any useful description that you may want to add. This is an 80 character option.
-confirm

-noconfirm
CONFIRM requests that the user be prompted prior to any operation to verify that the selected job is the correct one.
-node=target_node
The hostname option specifies what hostname (either local or remote) you want the operation performed on. -hostname may be substituted for -node.
-fiscal=starting month
The FISCAL option specifies which month is to begin the fiscal year. The default setting is January. The month may be entered as a number (1-12) or as text (e.g. "June").
-flags=noholiday_runs, noweekend_runs, skip, slide
The FLAGS option allows the user to specify dates on which a job is to run. The various flags are:

Flag Description

NOHOLIDAY_RUNS No jobs will run on a holiday

NOWEEKEND_RUNS No jobs will run on a weekend

SKIP Skip runs on disallowed days

SLIDE Slide run forward on disallowed days

Whenever multiple flags are used, they must be enclosed in parentheses.
-log

-nolog
The LOG qualifier causes each completed operation to issue a note to the user.
-owner=[UID,GID]
The OWNER option specifies the owner user id and group id code for the calendar.
-protection:[who]+permission

-protection:[who]-permission
The PROTECTION qualifier modifies the read, write and execute permissions of specified calendars.
who specifies whether permissions are being defined for user(u), group(g) or all others(o).
permission specifies the permissions being defined. Read permission(r) allows reading. Write permission (w) allows the ability to write out a new version. Execute permission(x) allows execution of jobs and calendars, search of directories.

-workdays[=noholiday(d), noweekend(d)]

-noworkdays
The WORKDAYS option specifies which days a job will not run. The default settings are NOHOLIDAY and NOWEEKEND. To change a day on a WORKDAYS calendar that is not included in the defined workdays use the STANDARD_DATE option . Either noholiday, noweekend or both may be used.

Flag	Description
NOHOLIDAY_RUNS	No jobs will run on a holiday
NOWEEKEND_RUNS	No jobs will run on a weekend
SKIP	Skip runs on disallowed days
SLIDE	Slide run forward on disallowed days

morecal

Type out a calendar.
The morecal command will display the selected month or months from the specified calendar.

General Format

morecal [-options] calendar_file

Alternate
type -calendar [-options] calendar_file

option summary

field qualifiers:

-from = date
-to = date
-marks

general qualifiers:

-[no]log
-[no]confirm
-node = target node
-env[=prefix_string,format]

Examples

#1
Schedule> morecal workdays -from=jan-1996 1996 January Sun. Mon. Tue. Wed. Thu. Fri. Sat. .. .. 1 AB 2 3 .. .. .. .. 4 5 6 7 8 .. .. .. .. 9 10 XX 11 12 13 .. .. .. .. 14 15 16 17 18 .. .. .. .. 19 20 21 22 1996 February (default) Sun. Mon. Tue. Wed. Thu. Fri. Sat. 1 .. .. .. .. 2 3 4 5 6 .. .. .. .. 7 8 9 10 11 .. .. .. .. 12 13 14 15 16 .. .. .. .. 17 18 19 20 1996 March (default) Sun. Mon. Tue. Wed. Thu. Fri. Sat. 1 .. .. .. .. 2 3 4 5 6 .. .. .. .. 7 8 9 10 11 .. .. .. .. 12 13 14 15 16 .. .. .. .. 17 18 19 20 21 .. .. .. .. 1996 April (default) Sun. Mon. Tue. Wed. Thu. Fri. Sat. 1 2 3 4 5 .. .. .. .. 6 7 8 9 10 .. .. .. .. 11 12 13 14 15 .. .. .. .. 16 17 18 19 20 .. .. .. .. 21 22 1996 May (default) Sun. Mon. Tue. Wed. Thu. Fri. Sat. 1 2 3 .. .. .. .. 4 5 6 7 8 .. .. .. .. 9 10 11 12 13 .. .. .. .. 14 15 16 17 18 .. .. .. .. 19 20 21 22 23

 
 
 
 Schedule> morecal workdays -from=jan-1996 
 
 
 
 1996  January     
 
         Sun.   Mon.   Tue.   Wed.   Thu.   Fri.   Sat. 
                       .. ..   1 AB   2      3     .. ..  
         .. ..   4      5      6      7      8     .. ..  
         .. ..   9     10 XX  11     12     13     .. ..  
         .. ..  14     15     16     17     18     .. ..  
         .. ..  19     20     21     22                   
 
 1996  February        (default) 
 
         Sun.   Mon.   Tue.   Wed.   Thu.   Fri.   Sat. 
                                             1     .. ..  
         .. ..   2      3      4      5      6     .. ..  
         .. ..   7      8      9     10     11     .. ..  
         .. ..  12     13     14     15     16     .. ..  
         .. ..  17     18     19     20                   
 
 1996  March           (default) 
 
         Sun.   Mon.   Tue.   Wed.   Thu.   Fri.   Sat. 
                                             1     .. ..  
         .. ..   2      3      4      5      6     .. ..  
         .. ..   7      8      9     10     11     .. ..  
         .. ..  12     13     14     15     16     .. ..  
         .. ..  17     18     19     20     21     .. ..  
         .. ..                                            
 
 1996  April           (default) 
 
         Sun.   Mon.   Tue.   Wed.   Thu.   Fri.   Sat. 
                 1      2      3      4      5     .. ..  
         .. ..   6      7      8      9     10     .. ..  
         .. ..  11     12     13     14     15     .. ..  
         .. ..  16     17     18     19     20     .. ..  
         .. ..  21     22                                 
 
 1996  May             (default) 
 
         Sun.   Mon.   Tue.   Wed.   Thu.   Fri.   Sat. 
                               1      2      3     .. ..  
         .. ..   4      5      6      7      8     .. ..  
         .. ..   9     10     11     12     13     .. ..  
         .. ..  14     15     16     17     18     .. ..  
         .. ..  19     20     21     22     23

Options

-node=target_node
The hostname option specifies what hostname (either local or remote) you want the operation performed on. -hostname may be substituted for -node.
-confirm

-noconfirm
CONFIRM requests that the user be prompted prior to any operation to verify that the selected calendar is the correct one.
-from=date
The FROM option specifies that only those months that include or are after the specified date are to be displayed. The date specified can be either an absolute time or a combination time. The default month is the current month.
-log

-nolog
The LOG option causes each completed operation to issue a note to the user.
-marks
The MARKS option displays a list of the days in the calendar that are marked as well as the letter mark for that day in a two column list.
-output=output_file
The OUTPUT option sends all output to a text file. Output can be printed or displayed as needed.
-env[=prefix_string] or [=(prefix_string,format)]
The environmental variable option requests that all calendar information be output to a file containing a list of enviroment variables. Every field in the control record is listed in the file as an environment variable. The environment variable name is constructed by prefixing the field name with the provide string. If none is provided a default value of SM is used.
The format defines the way that environmental variables are output. The default output specification is: "$export %s=\" %s\" "" (ksh), "$setenv %s=\" %s\" "" (csh) which produces the following format style.
SM_FLAGS = "Slide_over_disallowed"
Alternate output styles may be created by changing the format field.
-to=date
The TO option specifies that only those months that are before or include the specified date are to be displayed. The date specified can be either an absolute time or a combination time. The default month is the current month.

mvcal

Rename a calendar definition.
The mvcal command will change the name of a calendar definition.

General Format

mvcal [-options] old_calendar_name new_calendar_name

Alternate
rename -calendar [-options] old_calendar_name new_calendar_name

option summary

-[no]log
-[no]confirm
-node = node_name

Examples

#1
Schedule> mvcal holidays special_days -log renamed /ktarnay/holidays to /ktarnay/special_days

Options

-confirm

-noconfirm
CONFIRM requests that the user be prompted prior to any operation to verify that the selected entry is the correct one.
-node=target_node
The hostname option specifies what hostname (either local or remote) you want the operation performed on. -hostname may be substituted for -node.
-log

-nolog
The LOG qualifier causes each completed operation to issue a note to the user.

rmcal

Delete a calendar definition.
The rmcal command permanently removes a calendar definition from the on-line database.

General Format

rmcal [-options] calendar_name

Alternate
delete -calendar [-options] calendar_name

option summary

-[no]log
-[no]confirm
-node = node_name

Examples

#1
Schedule> rmcal bir* -confirm delete /jryan/birthdays [y/n]: (y)?

Options

-confirm

-noconfirm
CONFIRM requests that the user be prompted prior to any operation to verify that the selected entry is the correct one.
-node=target_node
The hostname option specifies what hostname (either local or remote) you want the operation performed on. -hostname may be substituted for -node.
-log

-nolog
The LOG qualifier causes each completed operation to issue a note to the user.

Chapter 7
Job data operations

Job data in SCHEDULE is managed and manipulated using the commands listed below:

Command Description

chjob modify a job definition

complete complete a job run

cp or cpjob copy a job definition

edjob edit a list associated with a job

extjob extract a list from a job

incjob cycle the start time forward

insjob insert a list

ls or lsjob list out job definitions

mk or mkjob create a job definition

more type out a list associated with a job

mv or mvjob change the name of a job

rebjob rebuild the initiate/prerequisite linkages

rm or rmjob delete a job definition

sigjob signal completion

subjob submit a job for execution

Command	Description
chjob	modify a job definition
complete	complete a job run
cp or cpjob	copy a job definition
edjob	edit a list associated with a job
extjob	extract a list from a job
incjob	cycle the start time forward
insjob	insert a list
ls or lsjob	list out job definitions
mk or mkjob	create a job definition
more	type out a list associated with a job
mv or mvjob	change the name of a job
rebjob	rebuild the initiate/prerequisite linkages
rm or rmjob	delete a job definition
sigjob	signal completion
subjob	submit a job for execution

For a job to be known to the SCHEDULE system a CONTROL¹ entry must exist. This entry defines all of the attributes:

How to submit the job to an execution queue.
When to start up the job, time or event based starts.
Who to notify when an scheduling event occurs.
What resource requirements are needed to start the job.
How this job is related to other jobs on the same node, other nodes in the cluster or other nodes in the network.

Note

¹ All the CONTROL data is kept in the file SCH0_CONTROL.DAT.

chjob

Modify a SCHEDULE job definition.
The chjob command will change any of the fields that make up a job definition.

General Format

chjob [-options] job_name
-section = field
-section = field:value
-section = (field,field,...)
-section = (field:value,field:value,...)

Alternate
modify -job [-options] job_name
-section = field
-section = field:value
-section = (field,field,...)
-section = (field:value,field:value,...)

option summary

-resources=
[no]disk_space : (disk,number_of_blocks)
[no]file : file_spec
measured : (cpu_time,elapse_time,io_count, num_count)
estimated : (cpu_time,elapse_time,io_count)

-notify=

after_delay : delta_time
[no]submitted : ([username(s)][,mail (default)] [,broadcast])
[no]started
[no]delayed
[no]completed
[no]failed
[no]all : (modify all of the above together)

-process=

shell : text
node : node_name
cputime : delta_time
[no]hold
[no]keep
[no]restart
[no]delete
[no]log_file : file_spec
versions_of_log : number
name : text
parameter : (p1,p2,...p8)
user : username
variable : (var1=value, var2=value etc.)

-general=

comment : text
next_submit : date
last_start : date
last_submit : date
last_completed : date
restart_count : number
up_count : number
down_count : number
flags : [no]history,[no]fixed_set_id,[no]blocked, open_vms|unix|windowsnt
owner : uic
protection : (ugo+/-rwx)
status : number
[no]job_tag : text
startup_window : delta_time
execute_window : delta_time
[no]pre_com_file : file_spec|"I myfile.com"|$ command
[no]post_com_file : file_spec|"I myfile.com"|$ command

-rescheduling=

interval : delta_time
marked : letter_mark
monthly : (january...december,ordinal_number,day_of_week)
named : (monday...sunday,445...544,month_start...year_end)
none
calendar : calendar_name
time_of_day : [+/-]delta_time

general options:

-[no]log
-[no]confirm
-hostname = target_node

general options:

-from = prototype_name
-ignore_errors

Examples

#1
Schedule> chjob test1 -submit=restart -confirm Modify /dwilliams/test1 [Y/N] ? (Y):

#2
Schedule> chjob /demo/a/start- -submit=(delete,hold) - -rescheduling=(interval:1)

Options

-confirm

-noconfirm
CONFIRM requests that the user be prompted prior to any operation to verify that the selected entry is the correct one.
-node=node_name
The NODE option specifies what node (either local or remote) you want the operation performed on.
endactions
The ENDACTIONS listing is a list of resource adjustments that are to be run upon completion of the job.
-general=comment:"any text string"
The COMMENT field is any useful description that you may want to add. This is an 80 character option.
-general=down_count:number
The DOWN_COUNT field indicates the remaining number of times a job is to be executed. This is automatically updated. When zero is reached no further jobs will be submitted automatically.
-general=execute_window:delta_time
The EXECUTE_WINDOW specifies the interval in which a job is allowed to have all requirements met and execute. This is the time it takes a job to move from scheduling queue C or D to M. Any job that exceeds this interval will have none of its initiates activated. This interval is designed to prevent a run away catch up mode from happening if the system is down for a long period. The interval time check is suppressed if this field is set to zero (i.e. the window is infinite).
-general=flags:history|fixed_set_id

-general=flags:nohistory|fixed_set_id

-general=flags:open_vms|unix|nt

-general=flags:[no]blocked

-general=flags:[no]delete_upon_completion
The HISTORY flag indicates whether or not history data is to be recorded for this job. A job that runs very frequently generates a lot of history data. To reduce the growth of this history file specify the NOHISTORY flag.
The FIXED_SET_ID flag forces a job to always use a constant set id.
The operating system flags determine the operating system the job was created to run on: OPEN_VMS for an Open VMS job, UNIX for a UNIX job or NT for a Windows NT job.
The BLOCKED flag is used to block a job from running. The job will not run until this flag is set to the default noblocked.
The DELETE_UPON_COMPLETION flag is used to delete a job once it has completed and is removed from the P queue. The interval that it will remain in the P queue is normally 15 hours. When that time elapses, the job will be deleted from the database. The job will not be deleted if the retain_on_error submit flag is on.
-general=job_tag:text
The JOB_TAG field specifies the initial value for the SET_TAG value when the job is first entered into the scheduling queues.
-general=last_completed:date
The LAST_COMPLETED field indicates when a job was last completed. This is automatically updated.
-general=last_start:date
The LAST_START field indicates the last time a job was started. This is automatically updated.
-general=last_submit:date
The LAST_SUBMIT field indicates when a job was last submitted. This is automatically updated.
-general=next_submit:date
The NEXT_SUBMIT field allows the user to specify the next job start date. A job will start on its own only if this date and time are set.
-general=owner:uic
The OWNER field indicates the owner user id and group id code for the job.
-general=post_com_file:file_spec | "I myfile.com"| $ unix command

-general=nopost_com_file
The POST_COM_FILE field indicates that a COM file is to be executed after the scheduled job has run to completion. The COM file and the job are run in the same batch job.
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 unix command will be executed.
-general=pre_com_file:file_spec | "I myfile.com" | $ unix command

-general=nopre_com_file
The PRE_COM_FILE field indicates that a COM file is to be executed prior to running the scheduled job. The COM file and the job are run in the same batch job.

Previous Next Contents Index

SCHEDULE Automated Job Submission System Guide and Reference Manual

mkcal

General Format

mkcal [-options] calendar_name

option summary

Examples

Options

-comment="any text string"

-confirm

-noconfirm

-node=target_node

-fiscal=starting month

-flags=noholiday_runs, noweekend_runs, skip, slide

-log

-nolog

-owner=[UID,GID]

-protection:[who]+permission

-protection:[who]-permission

-workdays[=noholiday(d), noweekend(d)]

-noworkdays

morecal

General Format

morecal [-options] calendar_file

option summary

Examples

Options

-node=target_node

-confirm

-noconfirm

-from=date

-log

-nolog

-marks

-output=output_file

-env[=prefix_string] or [=(prefix_string,format)]

-to=date

mvcal

General Format

mvcal [-options] old_calendar_name new_calendar_name

option summary

Examples

Options

-confirm

-noconfirm

-node=target_node

-log

-nolog

rmcal

General Format

rmcal [-options] calendar_name

option summary

Examples

Options

-confirm

-noconfirm

-node=target_node

-log

-nolog

Chapter 7Job data operations

1 All the CONTROL data is kept in the file SCH0_CONTROL.DAT.

chjob

General Format

chjob [-options] job_name

option summary

Examples

Options

-confirm

-noconfirm

-node=node_name

endactions

-general=comment:"any text string"

-general=down_count:number

-general=execute_window:delta_time

-general=flags:history|fixed_set_id

-general=flags:nohistory|fixed_set_id

-general=flags:open_vms|unix|nt

-general=flags:[no]blocked

-general=flags:[no]delete_upon_completion

-general=job_tag:text

-general=last_completed:date

SCHEDULE
Automated Job Submission System
Guide and Reference Manual

Chapter 7
Job data operations

¹ All the CONTROL data is kept in the file SCH0_CONTROL.DAT.