TMSAGGR Messages

AUDIT DATA SET FULL *****
ca1tms
AUDIT DATA SET FULL *****
Reason:
The number of Audit records written exceeds a site-defined level, and all batch processing terminates.
Action:
Execute TMSCOPY to copy all Audit records written since the previous backup to tape and to reset the logical pointers in the Audit Control record, and resubmit the job.
CA 1
DATE MODULE OPEN ERROR.
Reason:
CA 1
could not open the date processing routines.
Action:
Ensure that all
CA 1
libraries are correctly specified in the link list or STEPLIB and resubmit the job.
DATE CANNOT BE A
CA 1
KEYWORD
Reason:
Only the EXPDT keyword can contain
CA 1
expiration date keywords.
Action:
Correct the control statement(s) and resubmit the job.
DATE FORMAT IS INVALID
Reason:
The value for a date field on a control statement is in error based on the default date format or the specified date format.
Action:
Correct the control statement(s) or the JCL and resubmit the job.
DSNB DELETED
Reason:
This message indicates that the DSNB record has been successfully processed by the DEL control statement.
Action:
No action is required. This is an informative message.
DSNB IS ALREADY UNUSED
Reason:
An attempt to delete a DSNB failed because the DSNB was already in inactive (unused) status, ACTIND set to X'00'.
Action:
No action is required. This is an informative message.
DSNB IS PART OF A VALID CHAIN
Reason:
An attempt to delete a DSNB failed because the DSNB is part of a valid DSNB chain.
Action:
No action is required. This is an informative message.
F1STVSN NOT IN CHAIN OR NOT IN SEQUENCE
Reason:
The F1STVSN volume is either not part of the multivolume chain the DSNB is being added to, or has a volume sequence lower than the F1STVSN volume of the previous DSNB or the volume specified on the VOL control statement.
Action:
Correct the control statement(s) and resubmit the job.
IEBTMS10 - WARNING, A MIXED EXPIRATION WAS ISSUED FOR xxxxxx
Reason:
The mixed expiration date parameter (MIXEXP) in TMOOPTxx is set to WARNING, and a mixed expiration date was detected. A secondary file was written to a volume using a different expiration date than the first file, and one of these expiration dates is a
CA 1
expiration date keyword. If the second file's expiration date is numerically higher than that of the first file, it becomes the controlling date and the Volume record for the first file is updated accordingly.
Action:
No action is required. This is an informative message.
IEBTMS11 - A MIXED EXPIRATION WAS ISSUED BUT DISALLOWED FOR xxxxxx
Reason:
The mixed expiration date parameter (MIXEXP) in TMOOPTxx is set to DISALLOW, and a mixed expiration date was detected. No update has been performed.
Action:
Either (a) correct the control statement(s) and resubmit the job or (b) change the parameter option in TMOOPTxx, reinitialize
CA 1
using TMSINIT, and resubmit the job.
INVALID CONTINUATION CARD
Reason:
The previous control statement indicated a continuation control statement to follow this control statement contains data before column 16 which is the continuation column.
Action:
Correct the control statement(s) and resubmit the job.
INVALID OR MISSING VOLUME SERIAL NBR
Reason:
The volume serial number on the VOL control statement is not in the TMC ranges, is missing, or user exit TMSXITU is in error.
Action:
Correct the control statement(s) or reinstall user exit TMSXITU and resubmit the job.
INVALID RELATIVE BLOCK FOR DSNB
Reason:
A nonnumeric DSNB number was specified on a control statement.
Action:
Correct the control statement(s) and resubmit the job.
INVALID REQUEST ON VOL CARD
Reason:
The keyword on the VOL control statement is not PURGE. This is the only keyword supported on a VOL control statement.
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.
MISSING DSNB KEYWORD TABLE
Reason:
The DSNB section of the keyword table could not be located in module TMSKEYAB.
Action:
Ensure that the correct version of the TMSKEYAB module is being used and resubmit the job.
NEED MORE CORE TO PROCESS DSNB'S
Reason:
A GETMAIN instruction failed for lack of storage allocated for the job. The default storage taken or the value specified through the REGION parameter on the JCL JOB statement is insufficient.
Action:
Correct the JCL and resubmit the job.
NO MORE ROOM FOR DSNB'S
Reason:
The number of free DSNBs in the TMC has been exhausted, or less than50 DSNBs were free at the beginning of the job.
Action:
Either (a) execute TMSCLEAN to free more DSNBs or (b) extend the size of the TMC with TMSFORMT. Reinitialize
CA 1
using TMSINIT, and resubmit the job.
REQUIRED KEYWORD NOT SPECIFIED FOR DSNB
Reason:
Each DSNB data control statement must contain the data set name and expiration date keyword. Either the DSN keyword or the EXPDT keyword is missing.
Action:
Correct the control statement(s) and resubmit the job.
TMC HAS NO DSNB'S TO PURGE
Reason:
An attempt to delete all associated DSNBs for a volume failed because the volume has no associated DSNBs.
Action:
No action is required. This is an informative message.
TMC xxxxxx ALREADY HAS DSNB'S
Reason:
Volume xxxxxx already has DSNB records allocated. DSNB records cannot be added to a Volume record with an existing DSNB chain.
Action:
If DSNB records are to be added to this volume, the complete DSNB chain must be rebuilt by releasing all related DSNB records using a VOL control statement with the PURGE keyword first. Correct the control statement(s) and resubmit the job.
TMC xxxxxx HAS EXPIRED
Reason:
Volume xxxxxx has expired. DSNB records cannot be allocated to a volume whose expiration date is the current date or in the past.
Action:
No action is required. This is an informative message.
TMC xxxxxx HAS INVALID CHAIN POINTERS
Reason:
Volume xxxxxx contains invalid chain pointers.
Action:
Execute TMSPTRS, correct the chaining errors, and resubmit the job.
VALUE OF 'HEXZEROS' NOT SUPPORTED
Reason:
A DSNB data control statement was processed using the
CA 1
keyword value HEXZEROS to reset the value. HEXZEROS is not supported by TMSAGGR.
Action:
Correct the control statement(s) and resubmit the job.
vvvvvv IN DELETE STATUS, MUST BE ADDED
Reason:
Volume vvvvvv is in DELETE status. Adding DSNBs to the volume is disallowed.
Action:
Add (activate) the volume with TMSDELET or an online facility and resubmit the job.
xxxxxxx CANNOT BE UPDATED
Reason:
Keyword xxxxxxx is not allowed to be updated.
Action:
Remove this keyword from the input DSNB data control statement and resubmit the job.
1ST CTL CARD MUST BE 'VOL' OR 'DEL'
Reason:
The first control statement is not a VOL or DEL control statement. The first statement cannot be a comment statement.
Action:
Correct the control statement(s) and resubmit the job.
'VOL' CARD WITH NO DSNB CARDS
Reason:
A VOL control statement without the PURGE keyword should be followed by DSNB data control statements, but none were encountered.
Action:
Correct the control statement(s) and resubmit the job.
'VOL' OR 'DEL' CARD MUST FOLLOW PURGE
Reason:
A control statement other than VOL or DEL was found after the VOL control statement with the PURGE keyword. DSNB records cannot be released and added with the same VOL statement.
Action:
Correct the control statement(s) and resubmit the job.
'xxxxxxx' ALREADY SPECIFIED FOR DSNB
Reason:
The keyword xxxxxxx can be used only once per DSNB data control statement, but was found more than once.
Action:
Correct the control statement(s) and resubmit the job.
'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. The values for the keywords are documented in the DSNB data control statement section.
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 the digits 0 through 9. The values for the keywords are documented in the DSNB data control section.
Action:
Correct the control statement(s) and resubmit the job.
'xxxxxxx' IS NOT A VALID KEYWORD
Reason:
The keyword xxxxxxx is not a valid keyword. The supported keywords are documented in the DSNB data control statement section.
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. The values for the keywords are documented in the DSNB data control statement section.
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 characters in size. The values for the keywords are documented in the DSNB data control statement section.
Action:
Correct the control statement(s) and resubmit the job.
***** NOT PROCESSED *****
Reason:
This control statement was not processed due to a previous control statement error.
Action:
Correct the control statement(s) and resubmit the job.