Operator Guide › Operator Commands › SUBMIT Command

SUBMIT Command

Use the SUBMIT command to submit jobs defined in job template files to CA VM:Backup for processing.

The default values for all options except MDSKLIST are the values specified on corresponding JOBOPTIONS record parameters in the job template file. Specify SUBMIT command options only if you want to override the values in the job template file.

You can also use the Submit System Backups operator screen to submit job template-defined backup jobs.

Submit jobname [("Options"...] 

Options:

  [EXClusive [Yes | No]]
| [Hold [Yes | No]]
| [JOBend [NOTify | QUIet]]
| [ONEtime [Yes | No]]
| [PRIority [Yes | No]]
| [REDuce [REMounts |TAPeuse]]
| [Streams number]
| [TAPemount [Yes | No]]
| [MDSKlist [filename [filetype]]]

Definitions

jobname

Specifies the filename of the job template file for the job to submit.

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. Specifying EXCLUSIVE is the same as specifying EXCLUSIVE YES.

Jobs that back up CA VM:Backup are always exclusive and ignore this option.

Hold [Yes| No]

Specifies whether CA VM:Backup is to place the job in the job queue in on hold status. Specifying HOLD is the same as specifying HOLD YES.

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 the JOBEND command is issued 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. Specifying ONETIME is the same as specifying ONETIME YES.

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 if the jobs are reordered using the ORDER command. Specifying PRIORITY is the same as specifying PRIORITY YES.

REDuce [REMounts | TAPeuse]

For backup jobs, indicates whether CA VM:Backup is to remount tapes already written to.

REMOUNTS prevents the remounting of tapes in most situations, which can make backup jobs run more quickly. If your data center uses automatic cartridge loaders (ACLs), you might want to specify REMOUNTS. Depending on the control setting for your ACL, it might not be able to remount a tape that has already been mounted in the currently running job. This is true if the control setting on the ACL is set to AUTOMATIC. This might also be true if the control setting is set to SYSTEM and the software you use to mount tapes cannot handle this situation.

TAPEUSE allows CA VM:Backup to remount tapes that have already been written to in the currently running backup job, minimizing the number of tapes needed for the job.

For more information about tape remounts, see the chapter "Managing Tape and DASD Resources" in the Programming Guide.

Streams number

For backup jobs, specifies the number of output streams the job is to use. Specify an integer from 1 through 15.

TAPemount [Yes | No]

For REINIT jobs, specifies whether CA VM:Backup is to mount tapes during the job. YES tells CA VM:Backup to mount the tapes specified in the job and rewrite the tape labels. NO tells CA VM:Backup to not mount the tapes specified in the job; the tape labels are not rewritten. Whether YES or NO is specified, CA VM:Backup updates either the resource pool information or the CA VM:Tape TMC (if the tape is from a CA VM:Tape pool) to indicate that the tape is expired and available for use. Specifying TAPEMOUNT is the same as specifying TAPEMOUNT YES.

MDSKlist [filename [filetype]]

For restore jobs, specifies that CA VM:Backup is to ignore the input guidelines specified in the restore job template file and instead restore only those minidisks listed in the filename filetype file.

You can specify a file coded manually or a file generated by the MDSKLIST command. The file you specify must reside on the A-disk of the user ID submitting the restore job template. The default is VMBACKUP MDSKLIST, which is the default name of the file generated by the MDSKLIST command.

If you use this parameter, specify it last.

Examples

• To submit the job defined by job template file AUTOCAT to run by itself as soon as possible, regardless of other jobs waiting in the job queue, enter the following command:

  vmbackup submit autocat (exclusive priority
  

  To submit a system backup defined by a job template file named MONTHLY, enter the following command:

  vmbackup submit monthly
  

• To submit a system backup defined by a job template file named WEEKLY, place the job in the queue, and place the job on hold, enter the following command:

  vmbackup submit weekly (hold
  

• To submit a restore job defined by a job template file named WEEKLY, place the job on hold, and tell CA VM:Backup to restore only those minidisks listed in the VMBACKUP MDSKLIST file, enter the following command:

  vmbackup submit weekly (hold mdsklist
  

• To submit a system backup defined by a job template file named MONTHLY and specify that it should use two streams instead of one, enter the following command:

  vmbackup submit monthly (streams 2