TMSUDSNB Messages

ca1tms
CANNOT BE GT THAN 10
Reason:
The +/- variable statement was used in an attempt to update TMSCTL#2. However, the value specified cannot be greater than 10.
Action:
If the ERR41 message from TMSPTRS is a value greater than 10, then use the value from the ERR41 message.
'sysid' CPU NOT FOUND
Reason:
The specified CPU was not found in TMSCTL#5.
Action:
Verify that the CPU is correct. Run TMSBINQ with HEADERS to verify.
'sysid' CPU REMOVED FROM TMSCTL#5
Reason:
The specified CPU has been removed from TMSCTL#5.
Action:
None.
'sysid' CPU WOULD HAVE BEEN REMOVED FROM TMSCTL#5
Reason:
Because a Parm of TEST was used, no update was made to TMSCTL#5.
Action:
None.
AUDIT DATASET IS NOT A BLOCKSET AUDIT
Reason:
The Remove_CPU statement was used on a NON Blockset Audit data set.
Action:
This statement can be used only on a Blockset Audit data set.
CANNOT REMOVE ACTIVE CPU
Reason:
The Remove_CPU was specified on the Active system.
Action:
The Remove_CPU statement can be used only for another system in TMSCTL#5.
- BYPASSED -
Reason:
Due to other errors, the update for the control statement has been bypassed.
Action:
Correct the control statement(s) and resubmit the job.
*** ACTIVE DSNB xxxxxxxx CONTAINS INVALID VOLSER
Reason:
The DSNB listed contains a volume serial pointer that is invalid.
Action:
Update the invalid VOLSER field using TMSUDSNB and resubmit the job.
*** INVALID CONTROL OR DSNB RECORD WAS READ OR WRITE ATTEMPTED ***
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 TMC recovery procedures in the TMSCOPY discussion 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).
*** RNAME FUNCTIONALITY HAS BEEN MODIFIED - TMSINIT REQUIRED ON ALL SYSTEMS ***
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.
COMMENTS CONTAIN ILLEGAL CHARACTER
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.
DSNB xxxxxx NOT UPDATED - TEST MODE
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.
DSNB xxxxxx UPDATED.
Reason:
DSNB xxxxxx has been successfully updated.
Action:
None. This is an informational message.
DSNB xxxxxx VERIFIED.
Reason:
DSNB xxxxxx has been successfully verified.
Action:
None. This is an informational message.
INVALID KEYWORD, NEAR COLUMN xx
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.
INVALID SYNTAX, NEAR COLUMN xx
Reason:
An attempt to parse the control statement failed at or near column xx.
Action:
Correct the control statement(s) and resubmit the job.
MAX VER/REP RECORDS EXCEEDED
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.
'NXAVAIL' EXCEEDS MAXIMUM OF xxxxxxx
Reason:
The NXAVAIL exceeds the maximum number of dsnbs allocated.
Action:
Update the NXAVAIL with a valid unused DSNB number.
REQUESTED DSNB DOES NOT EXIST
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.
UNKNOWN RECORD TYPE
Reason:
A control statement was encountered that did not begin with CTLx, DSNB, VER, REP or SHUTDWN.
Action:
Correct the control statement(s) and resubmit the job.
VERIFY FOR 'xxxxxx' IS MISSING OR NOT PRIOR TO FIRST REP
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.
VERIFY FOR 'xxxxxxx' FAILED, TMC CONTAINS - yyyyyyyy
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.
VOLUME SERIAL NUMBER IS INVALID
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.
1ST CTL CARD MUST BE 'CTLX' OR 'DSNB'
Reason:
The first control statement after the SHUTDWN control statement must be a CTLx or DSNB control statement.
Action:
Correct the control statement(s) and resubmit the job.
xxxxxx DID NOT SPECIFY SHUTDWN VALUE WHICH IS REQUIRED
Reason:
An update to a record has been attempted and the
CA 1
shutdown value has not been supplied.
Action:
Correct the control statement(s) and resubmit the job.
SYSTEM SHUTDWN VALUE REQUIRED-INCORRECT SHUTDWN VALUE SPECIFIED
Reason:
An update to a record has been attempted and the
CA 1
system shutdown value supplied is incorrect.
Action:
Correct the control statement(s) and resubmit the job.
xxxxxxxx CHANGED FROM - yyyyyyyy TO zzzzzzzz
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.
'xxxxxxx' CANNOT BE CHANGED
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.
'xxxxxxx' CONTAINS ILLEGAL CHARACTER
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.
'xxxxxxx' EXCEEDS yy CHARACTERS
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.
'xxxxxxx' GREATER THAN CTL4 AUDIT RECORDS GENERATED
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.
'xxxxxxx' HAS INVALID DATE
Reason:
The date value specified for keyword xxxxxxx is invalid.
Action:
Correct the control statement(s) and resubmit the job.
'xxxxxxx' HAS INVALID HEX CHARACTERS
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.
'xxxxxxx' HAS INVALID TIME
Reason:
The time value specified for keyword xxxxxxx is invalid.
Action:
Correct the control statement(s) and resubmit the job.
'xxxxxxx' IS NOT A VALID TMC KEYWORD
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.
'xxxxxxx' MUST BE NUMERIC
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.
'xxxxxxx' MUST BE yy CHARACTERS
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.
'CURDSNB' EXCEEDS MAXIMUM OF xxxxxxx
Reason:
The CURDSNB field exceeds the maximum number or DSNBs allocated.
Action:
Update the CURDSNB field with a valid DSNB number.
'NEXT' EXCEEDS MAXIMUM OF xxxxxxx
Reason:
The NEXT field exceeds the maximum number or DSNBs allocated.
Action:
Update the NEXT field with a valid DSNB number.
'PREV' EXCEEDS MAXIMUM OF xxxxxxx
Reason:
The PREV field exceeds the maximum number or DSNBs allocated.
Action:
Update the PREV field with a valid DSNB number.