Template Programming Interface Guide › Restore Job Template Files › JOBOPTIONS Record

JOBOPTIONS Record

REQUIRED

Use the JOBOPTIONS record to specify job processing options for the job.

A file can include multiple JOBOPTIONS records. Each record can specify more than one parameter; however, a file can include only one of each parameter.

You can override parameter values specified on this record when you submit the job.

Note: Parameters on this record replace equivalent parameters on the OPTIONS record. However, CA VM:Backup will continue to accept already imported job template files that include the OPTIONS parameters.

These parameters are available only through TPI. Using any one of them will prevent you from managing the job template file through the CA VM:Backup screens.

JOBOPTIONS {"Parms"}...

Parms:

  EXCLUSIVE {YES | NO}
| HOLD {YES | NO}
| JOBEND {NOTIFY | QUIET}
| ONETIME {YES | NO}
| PRIORITY {YES | NO}

Definitions

EXCLUSIVE {YES | NO}

Specifies whether CA VM:Backup is to prevent other jobs from running while this job runs. CA VM:Backup will not start an exclusive job until all running jobs have completed and will not allow other jobs to start until the exclusive job has completed.

HOLD {YES | NO}

Specifies whether CA VM:Backup is to place the job in the job queue in hold status. To run a held job, the operator or system administrator must release it using the Manage System Activity operator screen or the RELEASE command.

JOBEND {NOTIFY | QUIET}

Specifies whether CA VM:Backup is to issue the JOBEND command to the submitting user ID to inform it that the job completed or was canceled. NOTIFY tells CA VM:Backup to notify the submitting user ID. QUIET tells CA VM:Backup not to notify the submitting user ID.

ONETIME {YES | NO}

Specifies whether CA VM:Backup is to erase the job template file and any associated exception and exclusion files from the CA VM:Backup 191 minidisk when the job either runs successfully or is canceled.

PRIORITY {YES | NO}

Specifies whether to submit the job at the top of the job queue, after any existing priority jobs. CA VM:Backup runs priority jobs before any other job in the queue. The only way another job can run ahead of a priority job is when the jobs are reordered using the ORDER command.