|
|
|
|
|
EnterpriseSCHEDULE can submit jobs that were created in the UNIX/Linux versions of the software as part of your EnterpriseSCHEDULE layouts. The settings for submission of UNIX/Linux jobs are detailed below:
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 the central database.
Process Name
This is the name of the process which the job should use.
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.
Versions
Number of versions of the log file that should be kept.
Print command
This defines what print command that the log file, if it is to be printed, will use.
Output flags (checkboxes)
Keep log file - Keep the log file on line after the job finishes.
Print log file - Print the log file after the job finishes.
Delete script file - Delete the job temporary script file on completion.
CPU time limit
This specifies the maximum CPU time that the job will execute. If 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.
Command shell
This specifies which Shell will be enabled for the job. The default value is ksh.
Resident size
The resident file size is the amount of memory to be used by the job.