Reason:
The Audit data set was not allocated with a DSORG of PSU.
Action:
This is an informational message. Allocation with PSU ensures that the Audit cannot be moved with a DASD management package while CA 1 is active.
Reason:
The TMC was not allocated with a DSORG of PSU.
Action:
This is an informative message. Allocation with PSU ensures that the TMC cannot be moved with a DASD management package while CA 1 is active.
Reason:
The Audit control statement must be numeric.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
CA 1 must be in a batch active state.
Action:
Start TMSINIT, reply to the initialization prompt with system password, BATCH and resubmit the job.
Reason:
More than 300 deletion ranges were specified.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
No SYSIN was found.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
The DSNB control statement is not numeric.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
Control statement does not contain a FORMAT or EXTEND statement.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
The TMC to be formatted is allocated with BLKSIZE=680, which is not allowed. When blocking the TMC, the smallest valid block size is 1020.
Action:
Allocate the TMC with correct DCB attributes and resubmit the job.
Reason:
The audit data set to be formatted has a block size of less than the minimum of 4440 bytes.
Action:
Allocate the audit data set with a block size of 4440 or greater. Alternatively, you can remove the BLOCKSET parameter for the FORMAT AUDIT=nnnnn statement.
Reason:
The audit data set to be formatted has specified a number of records which is less than 100 blocks. The control statement specifies a BLOCKSET audit which is intended for large and active audit data sets.
Action:
No action is required. TMSFORMT will format the minimum of 100 blocks.
Reason:
The number of Audit records requested exceeds eight digits.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
TMSXITU did not convert to numerics the same volume TMSXITE converted.
Action:
Correct the logic in the exits, and resubmit the job.
Reason:
A VOLSER presented to the user exit TMSXITU could not be correctly translated to an internal numeric value.
Action:
Correct the logic in TMSXITU and reinstall the user exit. Resubmit the job.
Reason:
A FORMAT statement was found with an EXTEND statement for the same range.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
TMSXITE converted a VOLSER to numeric or alphanumeric, and TMSXITU did not return the same converted VOLSER.
Action:
Correct logic within the exit(s), and resubmit the job.
Reason:
The information in TMSCTL#2 from the restore tape does not match the number of DSNBs read from the backup tape.
Action:
Execute TMSPTRS and correct any chaining errors. Execute TMSCOPY to obtain a current backup tape, and rerun TMSFORMT.
Reason:
A VOLSER range specified for DELETE was not formatted or extended in this run of TMSFORMT.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
Volume ranges specified must be numeric. Exits TMSXITE and TMSXITU perform numeric to alphanumeric translations.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
The control statement has no delimiters.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
The range specified a volume range, but the range was not previously defined in the FORMAT or EXTEND control statement(s).
Action:
Correct the control statement(s) and resubmit the job.
Reason:
The volume range specified overlaps another range.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
Invalid input to TMSFORMT.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
The total number of volume ranges that can be defined to the TMC is 52.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
The volume mounted is either bad or not a TMC backup tape.
Action:
If the volume is bad, rerun TMSCOPY to obtain another backup.
Reason:
The FORMAT control statement was specified but the RESTORE DD statement is referencing a file. The RESTORE DD statement should not be used except in EXTEND processing.
Action:
Correct the DD or control statement and resubmit.
Reason:
The volume used by the RESTORE DD is not a backup of the TMC, which is required for an EXTEND operation.
Action:
Correct the JCL and resubmit the job.
Reason:
TMSFORMT cannot be used to extend the TMC if it has already been processed with the TMSXTEND or TMSBLDVR utilities.
Action:
Use the TMSXTEND utility to add volumes or DSNBs to the TMC. Refer to the Utilities and Report Reference Guide for details.
Reason:
EXTEND was requested and the RESTORE DD is DUMMY. The RESTORE DD must reference a current TMC backup tape.
Action:
Correct the JCL and resubmit the job.
Reason:
FORMAT was requested and the RESTORE DD is not DUMMY.
Action:
Correct the JCL and resubmit the job.
Reason:
Processing completed without any errors.
Action:
None. This is an informational message.
Reason:
The volume being processed is not defined to the TMC.
Action:
Execute TMSFORMT with an EXTEND to add the desired volume or range of volumes, and resubmit the job. If the VOLSER from TMDATA is not a valid VOLSER, correct input and resubmit TMSFORMT.
Reason:
There is a VOLSER in the TMDATA input file that is not higher in number than the previous VOLSER (after translation by TMSXITU).
Action:
Correct the sequence of the records in the TMDATA input file and resubmit the job.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|