This chapter describes the structure of tape reinitialization (REINIT) job template files created using TPI and shows example files. It then explains each record that REINIT job template files can include. The records are listed in alphabetical order.
Note: REINIT jobs are only available through TPI and can only be submitted by an authorized client.
This section contains the following topics:
REINIT Job Template File Structure
The following table outlines the structure of a REINIT job template file. The table lists the records in the order an authorized client might use them in a file.
|
Record |
Information Specified |
Quantity Allowed |
|
JOB |
Type of job set up in file |
1 |
|
COMMENT |
Comment |
1 |
|
* |
Additional comments |
Multiple |
|
JOBOPTIONS |
General job processing options |
Multiple |
|
REPORT |
Report options |
1 |
|
REINIT |
Input tape to reinitialize |
Multiple |
|
CHECKSUM |
Number that protects the file from manual modification |
1; last in file |
An authorized client can use the * record to add comments to job template files in addition to the comment specified on the COMMENT record.
A client can use * records with the COMMENT record or by themselves. The records can be placed anywhere in the file after the JOB record; however, when the file is exported, CA VM:Backup places all * records in order after the COMMENT record or, if no COMMENT record exists, after the JOB record.
* [text]
Can include up to 80 characters of comment text; any additional text is truncated. Column 1 of the record must contain an asterisk. Uppercase and lowercase letters are accepted; when the file is imported or exported, text case is preserved.
The CHECKSUM record contains a hexadecimal number calculated from the contents of the file.
This record protects the file from manual modification. When CA VM:Backup imports a file created by an authorized client, it computes its own checksum value for the file. If that value does not match the value in this record, CA VM:Backup does not import the file.
IMPORTANT! Do not modify CHECKSUM records.
CHECKSUM hexadecimal
An authorized client can use the COMMENT record to enter a comment in a file.
COMMENT [text]
Can include up to 50 characters of comment text; any additional text is truncated. Uppercase and lowercase letters are accepted; when the file is imported or exported, text case is preserved.
The JOB record identifies the job that is set up in the file as a REINIT job.
JOB REINIT
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: This record replaces the OPTIONS record. However, CA VM:Backup will continue to accept already imported job template files that include OPTIONS records
JOBOPTIONS {“Parms”}...
Parms:
EXCLUSIVE {YES | NO}
| HOLD {YES | NO}
| JOBEND {NOTIFY | QUIET}
| ONETIME {YES | NO}
| PRIORITY {YES | NO}
| TAPEMOUNT {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.
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.
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.
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.
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.
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.
The REINIT record specifies the volser of an input tape the job is to reinitialize.
REINIT {“Parms”}...
Parms:
STATUS {AVAILABLE | UNAVAILABLE}
| VOLSER volser
Indicates whether the tape is available for mounting.
Specifies the volser of the tape to reinitialize.
The REPORT record specifies:
REPORT {“Parms”}...
Parms:
KEYWORD { YES | NO }
| PULLUSER {userid | NONE | SYSTEM}
| REPCLASS class
| REPDEST userid
| REPNODE node
Specifies whether CA VM:Backup is to create a keyword data report for the job.
Specifies whether to create a pull list and where to send it:
CA VM:Backup sends the pull list to userid regardless of what is specified on the PULLUSER configuration file record.
CA VM:Backup does not create a pull list for the job even when a PULLUSER configuration record is specified in the CA VM:Backup configuration file
CA VM:Backup uses configuration information to determine whether to create a pull list and where to send it. If the PULLUSER configuration file record is specified, CA VM:Backup sends the pull list to the user ID defined on this record. If the PULLUSER configuration file record is not specified, CA VM:Backup does not create a pull list.
Specifies the spool class for the REINIT job detail report. The default is the class of the first virtual printer defined in the response that CA VM:Backup receives from the CP QUERY VIRTUAL UR command at system initialization.
Identifies the user ID to which the CA VM:Backup is to send the job detail report. The default is the user ID that submitted the job.
Specifies the node to which CA VM:Backup is to send the job detail report. The default is the local system.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|