Submit - Setting the job submission options
The Submit options determine how jobs are submitted in Schedule.
Schedule gives you the choice of which Operating System to submit the job on. The choices are: Windows, UNIX and VMS. Depending on which Operating System you choose the screen will change with the correct submitting options. The user can submit a single job or a job set. To learn more about job set, click here.
OpenVMS job submission
The fields for OpenVMS job submission are:
.png)
Process Controls
|
On Node |
This specifies on which node this job is to execute. Inside a cluster, any node that is a member of the same cluster is allowed to submit and execute the job. This parameter is very useful in a "Satellite/Central database" network configuration. In this network topology, the job will execute on the remote node. All the control data and commands will come from thecentral database. |
|
Process name |
This is the name of the process which the job should use. |
|
Username |
the owner of the job |
|
Default submission tag |
A text field that specifies information to be passed from one job to another inside a set of jobs. |
|
In batch queue |
This defines what batch queue the job is to be placed in for execution. This can be either a generic or node specific execution queue. The default if none has been defined either implicitly or explicitly is SYS$BATCH. |
|
Hold in queue (checkbox) |
Place the job in the PENDING state on entering into the batch queue. |
|
Retain on error (checkbox) |
Used in conjunction with the checkbox called "delete upon completion of job" in the General tab. If this is checked and the log file says that the job failed, the job will not be deleted. This is a special case for temporary jobs. |
|
Batch notify (checkbox) |
Notify via batch |
Output Controls
|
Log file name |
This specifies where to place the job log file that is created during job execution. Any file name that is provided is parsed and a default of' job_name.LOG'' is used to complete any missing elements. |
|
Print queue |
This defines what print queue that the log file, if it is to be printed, is to be inserted into. The default if none has been defined either implicitly or explicitly is SYS$PRINT. |
|
Keep log file (checkbox) |
Keep log file upon completion |
|
Print log file (checkbox) |
Print the com file - Delete the job temporary COM file on completion. |
Batch queue selection (Advanced)
|
CPU Time Limit |
This specifies the maximum CPU time that the job will execute. The batch queue also has a CPU time limit the smaller of the two is used. If none is specified this implies NO LIMIT. The field contains a standard delta date specification. This value places a hard limit on the jobs execute time limited |
|
Account name |
This specifies what account value to assign the job when it is submitted for execution. This parameter is only useful if you have an application that can use this value. |
|
Command interpreter |
This specifies which command language interpreter will be enabled for the batch job. The default value is DCL. |
|
Queue priority |
This specifies what queue priority to assign this job when it is inserted into the batch queue for execution. The priority is NOT the execution priority but strictly the priority used to order jobs in the batch execution queue while they are waiting to start. |
Working set controls (advanced)
|
Working set default |
This defines for a batch job a working set default and the default number of physical pages that the job can use. If the queue on which the job executes has a nonzero default working set, the smaller of the specified job and queue values is used. If the queue on which the job executes has a working set default of 0, the smaller of the specified job and UAF values (value established in the user authorization file) is used. If you specify the value 0 or NONE, the specified queue or UAF value is used. |
|
Working set quota |
This defines for the batch job a working set quota and the amount of physical memory that the job is guaranteed. If the queue on which the job executes has a nonzero working set quota, the smaller of the specified job and queue values is used. If the queue on which the job executes has a working set quota of 0, the smaller of the specified job or the value established in the user authorization file (UAF) is used. If you specify the value 0 or NONE, the specified queue or UAF value is used. |
|
Working set extent |
This defines for the batch job a working set extent and the maximum amount of physical memory that the job can use. The job uses the maximum amount of physical memory only when the system has excess free pages. If the queue on which the job executes has a nonzero working set extent, the smaller of the specified job and queue values is used. If the queue on which the job executes has a working set extent of 0, the smaller of the specified job and the value established in the user authorization file (UAF) is used. If you specify the value 0 or NONE, the specified queue or UAF value is used. |