SCHEDULE
MOTIF Interface Guide

The access controls determine access rights to the new job, including ownership and protection.

Data	Description
Username	All automated submit operations are done on behalf of this user. Only a user with CMKRNL can change this field.
Owner	This field indicates the UIC that controls the job. This can be either an IDENTIFIER or a UIC code.
Protection	This field is a bitmap that grants access to the system, owner, group and world classes. The protection bits are used as follows: D - Delete access allowed to the job W - Write access allowed to the job R - Read access allowed to the job E - Submit, initiate or prerequisite access allowed The access modes are nested as follows: D -> W -> R -> E. In other words W access gives you W, R and E access but not D.

2.2.1.3 General...

Data	Description
Startup window	This time, when added to the scheduled start time, defines the window of time for which this job is allowed to start execution. If the job is unable to run within this window because of a hardware failure, the rescheduling algorithm is forwarded to the next available start time. This prevents jobs from immediate submits when the machine or server has been down.
Execute window	This time, when added to the actual start time, defines the window of time for which this job is allowed to execute. In the event of a hardware failure, if this window is exceeded, the completion status is always FAILED and no initiates will be performed.
Pre com file	This is a command procedure that is executed first before any other commands associated with a job.
Post com file	This is a command procedure that is executed last after all commands associated with the job.
Job tag	This is the initial value that is given to the SET TAG whenever this job is used to start a job set.
Submit count	This count is incremented each time a job is submitted for execution.
Down submit count	This count is decremented each time a job is submitted for execution. When a value of zero is reached, all automatic job submissions terminate. A value of INFINITE or -1 indicates an unlimited number of runs are allowed.
Restart limit	This number indicates how many times a job is allowed to be automatically restarted. A non-zero value indicates that the job can be restarted on failure (error and severe error conditions) and how many times it is allowed. Any initiate jobs that are specified are not activated until a job has failed this number of times. Job failure events include such things as a node going down, a job explicitly deleted out of the queue, or a program failure.
Save history	In order to save job history data, select this button.
Fixed set id	In order to use a fixed set id. select this button.