SCHEDULE
Automated Job Submission System
Guide and Reference Manual
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=protection:[who]+permission
-general=protection:[who]-permission
The PROTECTION field modifies the read, write and execute permissions
of specified jobs.
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.
-general=restart_count:number
A nonzero RESTART_COUNT allows the job to be restarted (up to the
specified number of times) if it is terminated with a failure status
code.
-general=startup_window:delta_time
The STARTUP_WINDOW specifies the interval after which a job in schedule
queue B will not be initiated. This only occurs if the system is down
when a job would have had a time based start. If the system comes up
within this interval then the job will start immediately. After this
interval this immediate initial run is not done.
The interval time check is suppressed if this field is set to zero
(i.e. the window is infinite).
-general=status:number
The STATUS field is a full 32 bit integer status code that indicates
the success (odd) or failure (even) of a job execution. This field is
automatically updated each time a job completes.
-general=up_count:number
The UP_COUNT field indicates how many times a job has been submitted
for execution. This is automatically updated.
-ignore_errors
All errors will be ignored when a set of jobs are modified using a
wildcard.
-log
-nolog
The LOG option causes each completed operation to issue a note to the
user.
-notify=after_delayed:delta_time
The AFTER_DELAYED datum specifies a time limit so that any job that has
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
The ALL sets and the NOALL clears all other NOTIFY commands. Thus ALL
will cause the creator of the job to be notified when the job is
submitted, started, delayed, completed, or if and when a job failed. If
BROADCAST is set then a logged in user will get a broadcast message.
Use NOBROADCAST to disable this. If MAIL is set a mail message is sent.
Use NOMAIL to disable this. If more then one user name is specified
surround the names with parentheses and separate with commas.
-notify=completed:([user(s)] [,mail(def)] [,broadcast])
-notify=nocompleted
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
broadcast message. Use NOBROADCAST to disable this. If MAIL is set a
mail message is sent. Use NOMAIL to disable this. If more then one user
name is specified surround the names with parentheses and separate with
commas.
-notify=delayed:([user(s)] [,mail(def)] [,broadcast])
-notify=nodelayed
The DELAYED field will notify the creator of a job if and when the job
is delayed. If BROADCAST is set then a logged in user will get a
broadcast message. Use NOBROADCAST to disable this function. If MAIL is
set a 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
The FAILED field will notify the creator of a job if and when the job
failed. If BROADCAST is set then a logged in user will get a broadcast
message. Use NOBROADCAST to disable this. If MAIL is set a mail message
is sent. Use NOMAIL to disable this. If more then one user name is
specified surround the names with parentheses and separate with commas.
-notify=started:([user(s)] [,mail(def)] [,broadcast])
-notify=nostarted
The STARTED field will notify the creator of a job when the job is
started. If BROADCAST is set then a logged in user will get a broadcast
message. If MAIL is set a mail message is sent. If more then one user
name is specified surround the names with parentheses and separate with
commas.
-notify=submitted:([user(s)][,mail(def)] [,broadcast])
-notify=nosubmitted
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
broadcast message. Use NOBROADCAST to disable this function. If MAIL is
set a 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.
-resources=disk_space:(disk,number_of_blocks)
-resources=nodisk_space
The DISK_SPACE resource specifies how many blocks must be available
before the job is submitted for execution.
-resources=estimated:(cpu,elapse,io)
The ESTIMATED datum allows for establishing an initial estimate of
cpu_time, elapse_time, and io_count. These estimated values are not
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
|
estimated number of buffered and direct I/O
|
-resources=file:file_spec
-resources=nofile
The FILE datum indicates which file, if any, must be present prior to a
job being submitted for execution.
-resources=measured:(cpu,elapse,io,count)
The MEASURED datum displays information about cpu_time, elapse_time,
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
The CALENDAR datum specifies which calendar to use when evaluating a
rescheduling method. An example of a calendar is one that specifies
which days are holidays.
-rescheduling=interval:delta_time
The INTERVAL datum allows the user to specify how often or at what
interval the job is run. The INTERVAL datum is mutually exclusive of
the MARKED, NAMED, or NONE datum.
-rescheduling=marked:letter_mark
The MARKED datum allows the user to run a job on days that are "marked"
with the indicated letter. The MARKED datum is mutually exclusive of
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).
-rescheduling=monthlyjanuary...december,ordinal_number,day_of_week
The MONTHLY datum allows the user to specify a month, several months or
ALL for all months that the job will run in. The months are separated
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
sequence of dates on which a job is to run by its name. The NAMED datum
is mutually exclusive of the MARKED, 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).
|
SUNDAY
|
TUESDAY
|
THURSDAY
|
SATURDAY
|
|
MONDAY
|
WEDNESDAY
|
FRIDAY
|
MONTH_START
|
|
YEAR_START
|
445
|
544
|
MONTH_END
|
|
YEAR_END
|
454
|
|
|
-rescheduling=none
The NONE datum indicates that the job is not to start based on time.
Such jobs will only start if initiated by another job or manually
submitted.
-rescheduling=time_of_day:[+/-]delta_time
The TIME_OF_DAY field allows the user to specify what time of day to
run a job. This command is used with the MARKED and NAMED option s. The
interval specified here is added to the selected day. The interval
specified can be of any length, from seconds to days. The job must be
on either named day or marked calendar rescheduling.
-resources
Create a generalized resource and add to RESOURCE list. The list is
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
variable, supress a job run or cause a wait to occur.
It is recommended that resources be listed in the RESOURCE list using
the editor as opposed to this method.
-process=cli:name
The SHELL field specifies the shell to be used to process the job.
Selections include C shell, Korn shell and Bourne shell. .
-process=cputime:delta_time
CPUTIME will define a CPU time limit for the batch job. Time can be
specified as delta time, or as 0 or NONE (no limit on the time). If the
queue on which the job will execute has a defined CPUMAXIMUM value, the
smaller of the PROCESS command and queue values is used.
-process=delete
-process=nodelete
The DELETE field will control whether or not command files are deleted
after processing. The default setting is NODELETE.
-process=hold
-process=nohold
The HOLD field will place the job into a queue in the HOLD state. The
default setting is NOHOLD.
-process=keep
-process=nokeep
The KEEP field will indicate that the log file produced by the
execution of the job is to be kept and not deleted. The default setting
is KEEP.
-process=log_file:file_spec
-process=nolog_file
The LOG_FILE field specifies the name of the job log file. By default
the file is placed in the user's login directory. The default name is
the job name and the default type is .LOG.
-process=name:text
The NAME field allows a different name (from that of the job itself) to
be used when the job is entered into an execution queue.
-process=node:node_name
The NODE field indicates which node is to process the job. In a
cluster, it is assumed that any node can process a job for execution on
behalf of any cluster member.
-process=parameter:(p1,p2,...p8)
The PARAMETER datum will provide the values of up to eight optional
parameters (p1,p2,...p8) for each command procedure in the job. The
symbols are local to the specified command procedure. Characters other
than alphanumeric characters must be included in quotation marks.
-process=restart
-process=norestart
The RESTART field will mark the created job as being restartable. Thus,
if the job is restarted during execution, the environment variable
$RESTART is set to true. Then the user provided command procedure will
check this value and continue execution as needed. The default setting
is NORESTART.
-process=user:username
The USER field indicates on who's behalf the job is to be processted
for execution. Normally this user name is the same as person who owns
the job. To change this field requires CMKRNL privilege.
-process=variable:(var1=value, var2=value etc.)
The VARIABLE qualifier creates or modifies one or more existing job
variables. If the job variable exists in the Notes cosection of the job
it will be modified, if not it will be created.
-submit=versions_of_log: number
The VERSIONS_OF_LOG field specifies the number of versions of the
SCHEDULE log file to retain.
Note
1 In a future release these values and
the measured values will be used in a chart displaying the progress of
the job.
|
complete
COMPLETE performs the final stage of a job run.
The complete command completes the final stage of a job run. The job's
command list is not processed, nor are any resource or end action list
commands. The job will appear as a successful completion in the P
(Holding previous completions) queue and initiates will be submitted if
the /INIT qualifier is used in combination. If the command is used to
recover from a previous job run, the set id of the previous run should
be designated to insure proper job flow.
General Format
subjob [-options] job_name
option summary
general options:
-[no]log
-[no]confirm
-hostname = target_node
submit conditions:
-initiates
-noinitiates (default)
-noprerequisites (default)
-after = date/time
restart step controls:
-step = number
job set controls:
-set_tag = "string"
-set_parameter = "string"
-set_id = number
Examples
| #1 |
Schedule> complete /jkrieg/backup_job
|
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.
-initiates
-noinitiates
This indicates whether or not on completion of the job the initiate
list should be carried out.
-set_id
The SET_ID option indicates to what set the job belongs. If a number is
not provided then the system automatically assigns the next available
set number.
-set_parameter="text"
The SET_PARAMETER option specifies information to be passed from one
job to another inside a set of jobs.
-set_tag="text"
The SET_TAG option also specifies information to be passed from one job
to another inside a set of jobs.
-step=number
The STEP option indicates at which step to start the job.
cp (or cpjob)
Copy a scheduled job definition.
The cp command will copy an entire job definition into another name.
All aspects of a job are copied including all lists. This includes all
the entries on the prerequisite list, initiate list, command list and
all other lists.
General Format
cp [-options] from_job_name to_job_name
Alternate
copy -job [-options] from_job_name to_job_name
option summary
-[no]log
-[no]confirm
-[no]node=target_node
-nocheck
Examples
| #1 |
Schedule> cp schedule_a schedule_b -confirm
Copy /skapur/schedule_a to /skapur/schedule_b [Y/N] ? (Y):
|
| #2 |
Schedule> cp boot:/test/schedule_a center:/test/schedule_a -confirm
Copy boot:/test/schedule_a to center:/test/schedule_a [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.
-nocheck
The NOCHECK option disables the CHECK whether or not a provided
prerequisite or initiate list makes references to any non-existent jobs.