Reason:
Due to other errors, the flagged control statement has been bypassed.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
A DSN= statement was found as the last control statement in the VPD.A V= statement should follow the DSN= statement. The total number of DSN= statements ignored are indicated in the value xxx.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
An expiration date less than or equal to the execution date was found on the flagged statement.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
The control statement contains VAULTS= which is invalid. All VAULTS= statements must precede DSN and V= statements.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
The keyword listed is a duplicate.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
The MAX= keyword was coded for LIB or LIBR which is invalid.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
The qualifier listed is missing a required value.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
The data set name contains an invalid pattern masking specification.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
An error was found while processing the vault movement statements.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
SEPDSN was specified on the DSN= statement with a JOB= keyword.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
The flagged control statement has invalid syntax, such as a missing or bad delimiter.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
After the last V= statement, a control statement was read that did not begin with DSN=.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
The control statement does not begin with DSN=, V=, VOL=, or CDSN=.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
No VAULTS= statement was found in the VPD.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
The vault name shown is too long. The maximum length for a vault name is 4 characters. If the vault name on the control statement is greater than 7 characters long, only the first 7 characters are shown in the message.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
The specified number of VPD entries are invalid.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
CA 1 was inactive. TMSVMEDT requires CA 1 to be active or batch active.
Action:
Initialize CA 1 using TMSINIT and resubmit the job.
Reason:
These combinations are not valid on the same V= statement.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
Duplicate V= statements were found in a pattern; xxx shows the retention value, such as C=.
Action:
Correct the control statement(s) resubmit the job.
Reason:
The same data set name was specified twice in the VPD.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
During a sequential read of the TMC, the first record did not contain the correct Control Record. The TMC dynamically allocated by TMSVMSRT is invalid.
Action:
See the Programming Guide and for assistance, contact Technical Support at http://ca.com/support.
Reason:
The DATEFMT= value coded on the JCL parameter is invalid.
Action:
Correct the JCL and resubmit the job.
Reason:
Incorrect keyword specification has been detected at the indicated position.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
The parameter listed is not a valid JCL parameter for TMSVMEDT.
Action:
Correct the JCL and resubmit the job.
Reason:
Invalid control statement syntax has been detected at the indicated position.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
A retention value was found to be invalid (such as, more than 255cycles).
Action:
Correct the control statement(s) and resubmit the job.
Reason:
These combinations are not valid on the same V= statement.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
A pattern specifies more than 28 consecutive V= statements. A maximum of 28 consecutive V= statements is allowed for a given group of DSN control statements.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
A pattern does not reflect the retention for a given location.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
No more storage was available for the data set name entry.
Action:
Increase region in JCL and resubmit the job.
Reason:
No more storage was available for the data set name entry.
Action:
Increase region in JCL and resubmit the job.
Reason:
No more storage was available for the data set name entry.
Action:
Increase region in JCL and resubmit the job.
Reason:
The load for module CTSPM failed.
Action:
CTSPM should reside in CAI.CTAPLINK. Check the link list concatenation or add the appropriate load library to the TMC STEPLIB ddname and resubmit the job.
Reason:
No V= statement was found after a DSN= statement.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
A request for storage failed during CTSPM initialization.
Action:
Correct the JCL and resubmit the job.
Reason:
A request for storage failed during TMSDATE initialization.
Action:
Correct the JCL and resubmit the job.
Reason:
A request for storage failed during TMSPRINT initialization.
Action:
Correct the JCL and resubmit the job.
Reason:
A request for storage failed during TMSVMSRT initialization.
Action:
Correct the JCL and resubmit the job.
Reason:
The number of Volume records read does not equal the number of Volume records on the TMC.
Action:
Execute TMSPTRS and correct any reported errors before resubmitting the job.
Reason:
An error occurred while trying to initialize the TMSDATE interface.
Action:
See the reason feedback codes listed for the TMMDATE macro in the Programming Guide.
Reason:
The TMSRPT report ddname could not be found or opened.
Action:
Correct the JCL and resubmit the job.
Reason:
Invalid EXEC parameter field in the JCL.
Action:
Correct the parameter in the EXEC statement and resubmit the job.
Reason:
An error occurred during TMSVMEDT processing. The FDBK value and message printed describe the problem.
Action:
See the message text to correct the error and resubmit the job.
Reason:
A record did not begin with *, VAULTS=, DSN= or V=, or the VAULTS= definition was not the first control statement.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
A V= statement reflects a name not on the VAULTS= statement.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
These combinations are not valid on the same V= statement.
Action:
Correct the control statement(s) and resubmit the job.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|