TMSUPDTE Messages

- BYPASSED -
ca1tms14-14-0
- BYPASSED -
Reason:
Due to other errors, the flagged control statement has been bypassed.
Action:
Correct the control statement(s) and resubmit the job.
* TRYING TO VER/REP xxxxxx *
Reason:
A field that can be propagated in a multivolume data set is attempting to be VERed or REPed throughout the volume chain.
Action:
None. This is an informational message.
* WARNING, VOLUME HAS EXPIRED *
Reason:
An update was performed to a Volume record and the EXPDT field in the record is less than or equal to the system date.
Action:
A volume that is expired and not marked out-of-area is eligible for scratch with the next execution of the TMSCLEAN program. If the volume needs to be protected, update the EXPDT with an appropriate value using TMSUPDTE or
CA 1
online facilities.
*** MAX ERROR RECORDING CAPACITY EXCEEDED
Reason:
The page counts exceed 10,000 pages.  If errors exist, the summary of page numbers that contain the errors is not produced when the total page-count exceeds 10,000.  All control statements are processed and are shown in the detail pages of the report.
Action:
If errors exist, they are denoted by *** (3 asterisks). Correct the control statement(s) and resubmit the job otherwise no action is needed.
COMMENTS CONTAIN ILLEGAL CHARACTER
Reason:
An invalid character was found in a comment statement.
Action:
Correct the control statement(s) and resubmit the job.
FIRST VOLSER MUST BE LOWER THAN SECOND
Reason:
When processing a range of VOLSERs, the first volume specified must express the low value of the range.
Action:
Correct the control statement(s) and resubmit the job.
High DSNB EXPDT date used = yyyy/ddd
Reason:
The VEXPDT= keyword was used on a REP statement, and a DSNB with a higher expiration date was found on the volume. That higher expiration date was used in place of the VEXPDT= value specified.
Action:
The update has taken place (unless PARM=TEST was specified), but a higher expiration date value was used in place of what was specified.
INVALID KEYWORD, NEAR COLUMN xx
Reason:
An invalid keyword was detected near the specified column.
Action:
Correct the control statement(s) and resubmit the job.
INVALID MULTI-VOLUME CHAIN
Reason:
An attempt to update a multivolume data set revealed an invalid chaining structure.
Action:
Execute TMSPTRS and correct any reported errors.
INVALID SYNTAX, NEAR COLUMN xx
Reason:
An attempt to parse the control statement failed at or near the specified position.
Action:
Correct the control statement(s) and resubmit the job.
INVALID TMC KEYWORD TABLE
Reason:
The
CA 1
keyword table, module TMSKEYAB, is invalid. This may be due to link list or STEPLIB contamination.
Action:
Contact the systems programmer responsible for maintaining
CA 1
INVALID VOLUME SERIAL NUMBER
Reason:
The VOLSER specified is not assigned to the TMC.
Action:
Correct the control statement(s) and resubmit the job.
KEYWORD MUST BEGIN BY COL 72
Reason:
Control statement keywords must begin before column 72.
Action:
Correct the control statement(s) and resubmit the job. RECORDS EXCEEDED
Reason:
More than 30 VER or REP statements were processed for a single update request.
Action:
Correct the control statement(s) and resubmit the job.
NOCHAIN REQUIRED FOR RANGE REQUEST
Reason:
When processing a range of VOLSERs, TMSUPDTE requires the use of the NOCHAIN option on the VOL statement.
Action:
Correct the control statement(s) and resubmit the job.
TEST FOR 'FLAGx ' FAILED, TMC CONTAINS - 00 USE VER FLAGx=HEXZEROS
Reason:
A value of zero in a FLAG value cannot be tested.
Action:
Use VER FLAGx=HEXZEROS
TMC VSN INVALID ADDR
Reason:
The next VOLSER in the multivolume chain to be updated is not in the TMC.
Action:
Execute TMSPTRS, correct the VOLSER field and resubmit the job.
UPDATE OF xxxxxxx VALID ONLY FOR WORM TAPE
Reason:
The specified TMC field pertains to 3592 WORM tapes, but the volume being updated is not a WORM.
Action:
Remove the invalid keyword from the control statement. If the TMC record does not reflect the correct media type, update DEN / TRTCH / FLAG5 accordingly.
UPDATE OF xxxxxxx NOT VALID FOR WORM TAPE
Reason:
The specified TMC field is not applicable to 3592WORM tapes, but the volume being updated is a WORM.
Action:
Remove the invalid keyword from the control statement. If the TMC record does not reflect the correct media type, update DEN / TRTCH / FLAG5 accordingly.
UNKNOWN RECORD TYPE
Reason:
A control statement was encountered that did not begin with VOL,VER or REP.
Action:
Correct the control statement(s) and resubmit the job.
VERIFY FOR 'DSN' IS MISSING
Reason:
The NODSN option was not invoked, and an attempt was made to update a record without data set name verification.
Action:
Correct the control statement(s) and resubmit the job.
VERIFY FOR 'xxxxxxx' FAILED, TMC CONTAINS - yyyyyyyy
Reason:
The verify operation for the keyword xxxxxxxx failed. The current contents of the TMC are displayed.
Action:
If the VOLSER was correctly specified and no attempt to update the field was involved, this can be considered an informative message. If you were attempting to update the record, verify that the VOLSER is correct.
VOLUME SERIAL NUMBER IS INVALID
Reason:
The volume serial number stored in the accessed TMC record is incorrect.
Action:
Update the record with the correct VOLSER using TMSUPDTE and resubmit the job.
xxxxxx IS A MULTI-VOLUME DATA SET, UPDATES SHOULD BE FOR yyyyyy
Reason:
A request to update a multivolume field was performed on VOLSER xxxxxx, which is not the first volume of the set. The correct Volume record for the update request is yyyyyy.
Action:
Correct the control statement(s) and resubmit the job.
xxxxxx IS NOT SCRATCH AND SCRATCH KEYWORD IS SPECIFIED
Reason:
The SCRATCH keyword was specified on the VOL statement, and the volume was not in scratch status in the TMC.
Action:
If the VOLSER is correct, remove the SCRATCH operand. Otherwise, determine the correct VOLSER, correct the VOL statement and resubmit the job.
xxxxxx NOT UPDATED - TEST MODE
Reason:
Volume xxxxxx was not updated due to the use of the TEST parameter on the JCL EXEC statement.
Action:
None. This is an informative message.
xxxxxx UPDATED.
Reason:
Volume xxxxxx was successfully updated.
Action:
None. This is an informational message.
xxxxxxx INVALID FOR BOOLEAN KEYWORD
Reason:
Only FLAG1, FLAG2, FLAG3 or FLAG4 can be specified for the boolean control statements TM, N1, and OI.
Action:
Correct the control statement(s) and resubmit the job.
xxxxxxx IS NOT A HEX KEYWORD
Reason:
The specified keyword for VER or REP is not a hexadecimal format keyword.
Action:
Correct the control statement(s) and resubmit the job.
xxxxxxxx CHANGED FROM - yyyyyyyy TO - zzzzzzzz
Reason:
The value of field xxxxxxxx has been changed from yyyyyyyy to zzzzzzzz due to the presence of PARM=AUDIT on the JCL EXEC statement.
Action:
None. This is an informational message.
xxxxxxxx IS NOT A KEYWORD
Reason:
A TM, OI or NI operation has been requested against a field that is not a hexadecimal field. A FLAGx field must be specified.
Action:
Correct the control statement(s) and resubmit the job.
'xxxxxx' INVALID STATUS CHANGE, MUST BE ADDED USINGTMSDELET/ISPF/TIQ 'xxxxxx' INVALID STATUS CHANGE, MUST BE DELETED USING TMSDELET/ISPF/TIQ
Reason:
The TMC record status cannot be changed using this utility.
Action:
Change the status of the TMC record using one of the methods listed. Correct the control statement(s) and resubmit the job.
'xxxxxxx' CONTAINS ILLEGAL CHARACTER
Reason:
The value for the specified keyword contains an illegal character oris not properly delimited.
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' 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 specified keyword contains invalid hexadecimal characters.
Action:
Correct the control statement(s) and resubmit the job.
'xxxxxxx' IS NOT A VALID TMC KEYWORD
Reason:
The keyword specified is not a valid TMC Volume record keyword.
Action:
Correct the control statement(s) and resubmit the job.
'xxxxxxx' MUST BE NUMERIC
Reason:
The value for the specified keyword must be numeric.
Action:
Correct the control statement(s) and resubmit the job.
'xxxxxxx' MUST BE yy CHARACTERS
Reason:
The value for the specified keyword must be a fixed number of characters in size.
Action:
Correct the control statement(s) and resubmit the job.
1ST CTL CARD MUST BE 'VOL' RECORD
Reason:
The first control statement was not a VOL control statement.
Action:
Correct the control statement(s) and resubmit the job.
'1STDSNB' EXCEEDS MAXIMUM OF xxxxxxx:XPL. The 1STDSNB exceeds the maximum number of DSNBs allocated. :URESP. Update the 1STDSNB field with a valid unused DSNB number. :MSG.'LSTDSNB' EXCEEDS MAXIMUM OF xxxxxxx
Reason:
The LSTDSNB exceeds the maximum number of DSNBs allocated.
Action:
Update the LSTDSNB field with a valid unused DSNB number.