Reason:
Due to other errors, the update for the control statement has been bypassed.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
The DSNB listed contains a volume serial pointer that is invalid.
Action:
Update the invalid VOLSER field using TMSUDSNB and resubmit the job.
Reason:
During an attempt to access a TMC or Audit Control Record, the record read did not contain TMSCTL# as the first seven characters. During an attempt to access a DSNB record, the first byte of the record read did not contain X'FF'.
Action:
In the case of Control Records, this message can indicate that the TMC or Audit has been corrupted. For information on formatting a new Audit data set, see the TMC recovery procedures in the TMSCOPY discussion in this guide or refer to the TMSFORMT discussion. In the case of the DSNB record, TMSUDSNB can be used to update the first byte to X'FF'; this field is externally referenced as BID (for example, REP BID=FF).
Reason:
FLAG1 has been changed so that the RNAME capability has been changed. This state may cause errors with any system that has not reflected the changes.
Action:
Run TMSINIT on all systems that access this TMC or IPL these systems.
Reason:
An invalid character was detected in a comment statement. Valid characters are the alphanumeric characters and the special characters blank, hyphen and period.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
DSNB xxxxxx was not updated due to the presence of the TEST parameter on the JCL EXEC statement.
Action:
None. This is an informational message.
Reason:
DSNB xxxxxx has been successfully updated.
Action:
None. This is an informational message.
Reason:
DSNB xxxxxx has been successfully verified.
Action:
None. This is an informational message.
Reason:
An invalid keyword was detected in the control statement at or near column xx.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
An attempt to parse the control statement failed at or near column xx.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
More than the maximum 30 VER or REP statements were processed for a single update request.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
The NXAVAIL exceeds the maximum number of dsnbs allocated.
Action:
Update the NXAVAIL with a valid unused DSNB number.
Reason:
The DSNB number specified on the control statement does not exist in the TMC.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
A control statement was encountered that did not begin with CTLx, DSNB, VER, REP or PASSWORD.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
There is no VER control statement for the xxxxxx field of the DSNB record or for the RECID field of the Control Record, or it occurs before the first REP control statement.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
The verify operation for the keyword xxxxxxx failed. The TM contains yyyyyyyy for that keyword value.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
The VOLSER in the accessed DSNB record is not a VOLSER properly defined to the TMC or user exit TMSXITU is in error.
Action:
Update the invalid VOLSER field using TMSUDSNB or reinstall user exit TMSXITU and resubmit the job.
Reason:
The first control statement after the PASSWORD control statement must be a CTLx or DSNB control statement.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
An update to a record has been attempted and the CA 1 system password has not been supplied.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
An update to a record has been attempted and the CA 1 system password supplied is incorrect.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
This is displayed when PARM=AUDIT is coded on the JCL EXEC statement. The keyword xxxxxxxx has been changed from a value of yyyyyyyy to a value of zzzzzzzz.
Action:
None. This is an informational message.
Reason:
The specified keyword value cannot be changed due to specifications in the CA 1 keyword table TMSKEYAB that prevent the field from being manually updated.
Action:
None. This is an informational message.
Reason:
The value for the keyword xxxxxxx contains an illegal character oris not properly delimited. Valid characters are the alphanumeric characters and the special characters blank, hyphen and period. If special characters are used, the value must be delimited by any character less than the character A.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
The value for the keyword xxxxxxx exceeds yy, the maximum size for that keyword.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
The keyword listed contains a value greater than the number of CTL4audit records generated.
Action:
Correct the value of the keyword listed and resubmit the job.
Reason:
The date value specified for keyword xxxxxxx is invalid.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
The value for the keyword xxxxxxx contains invalid hexadecimal characters. Valid characters are A through F and digits 0 through 9 .
Action:
Correct the control statement(s) and resubmit the job.
Reason:
The time value specified for keyword xxxxxxx is invalid.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
On a VER or REP statement, the keyword xxxxxx does not reflect a valid DSNB or Control Record keyword field name.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
The value for the keyword xxxxxxx must be numeric. Valid characters are the digits 0 through 9.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
The value for the keyword xxxxxxx must be yy, a fixed number of characters in size.
Action:
Correct the control statement(s) and resubmit the job.
Reason:
The CURDSNB field exceeds the maximum number or DSNBs allocated.
Action:
Update the CURDSNB field with a valid DSNB number.
Reason:
The NEXT field exceeds the maximum number or DSNBs allocated.
Action:
Update the NEXT field with a valid DSNB number.
Reason:
The PREV field exceeds the maximum number or DSNBs allocated.
Action:
Update the PREV field with a valid DSNB number.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|