TMSCOPY Messages

** DSNB xxxxxx IS AN INVALID DSNB RECORD** LOCATED AT PHYSICAL RECORD yyyyyy
ca1tms
** DSNB xxxxxx IS AN INVALID DSNB RECORD** LOCATED AT PHYSICAL RECORD yyyyyy
Reason:
The physical record count of physical record yyyyyy is greater than the number of Volume records defined in the volume ranges in TMC Control Records #1 and #3. The DSNB number xxxxxx is the number of DSNBs counted at the time the abend occurred. A DSNB has been overlaid, or more TMC records have been backed up than have been defined to
CA 1
Action:
Execute TMSPTRS and correct any chaining errors. For assistance, contact Technical Support at http://ca.com/support.
***** DSNBS GENERATED AND NUMBER BACKED UP NOT EQUAL *****
Reason:
The number of DSNBs backed up does not equal the number of DSNBs formatted as indicated in Control Record #2.
Action:
Execute TMSPTRS and correct any chaining errors. When TMSPTRS executes without any chaining errors, resubmit the job.
*** ERROR - xxxxxx IS AN INVALID VOLSER, PREV DSNB # = yyyyyy AT RELATIVE RECORD zzzzzz
Reason:
VOLSER xxxxxx was not defined in the volume ranges of TMC Control Records #1 and #3. The last good DSNB read was yyyyyy at relative record zzzzzz.
Action:
For assistance, contact Technical Support at http://ca.com/support.
*** ERROR - xxxxxx IS AN INVALID VOLSER, PREV VOLSER READ = yyyyyy AT RELATIVE RECORD zzzzzz
Reason:
VOLSER xxxxxx was not defined in the volume ranges of TMC Control Records #1 and #3. The last good volume read was yyyyyy at relative record zzzzzz.
Action:
For assistance, contact Technical Support at http://ca.com/support.
*** ERROR - xxxxxx IS OUT OF SEQUENCE, PREVIOUS DSNB # = yyyyyy AT RELATIVE RECORD zzzzzz
Reason:
DSNB xxxxxx is not greater than the relative record number zzzzzz. The last good DSNB backed up was DSNB number yyyyyy.
Action:
For assistance, contact Technical Support at http://ca.com/support.
*** ERROR - xxxxxx IS OUT OF SEQUENCE, PREVIOUS VOLSER READ = yyyyyy AT RELATIVE RECORD zzzzzz
Reason:
The internal volume number for VOLSER xxxxxx is not greater than the relative record number zzzzzz for VOLSER yyyyyy.
Action:
For assistance, contact Technical Support at http://ca.com/support.
***** FIRST DSNBS RELATIVE RECORD AND DSNB BASE IN HEADER2 NOTEQUAL *****
Reason:
The number of Volume records read is not equal to the DSNB base (TMDSNB03) from TMC Control Record #2 minus 3.
Action:
Execute TMSAUDIT and request Type 0 Audit records. Execute TMSPTRS and correct any chaining errors. For assistance, contact Technical Support at http://ca.com/support.
** I/O ERROR - error message
Reason:
An unrecoverable I/O error has been encountered during processing. The error message is from the SYNAD routine.
Action:
Determine the cause of the error, correct the error and resubmit the job.
***** NUMBER OF TMC RECORDS GENED AND NUMBER BACKED NOT EQUAL *****
Reason:
The number of Volume records defined in the volume ranges of Control records #1 and #3 is not equal to the number of Volume records backed up.
Action:
Execute TMSPTRS and correct any chaining errors. When TMSPTRS executes without any errors, resubmit the job.
****TMS NOT ACTIVE*NO HASH*NO VOLSEQ CHECKING FOR RESTORE****
Reason:
CA 1
has been deactivated or was never initialized. VOLSERs cannot be verified to be in the TMC defined volume ranges or in the correct sequence.
Action:
No action is required. This is an informative message.
**WARNING** BACK-UP TAPE MAY BE INCORRECT
Reason:
The VOLSER or data set name of the TMSCOPY backup tape being used as input to the RESTORE operation are not equal to the value saved when the last TMSCOPY backup was run.
Action:
Verify that the correct TMSCOPY backup tape was used.
CONTROL RECORD #4 HAS BEEN WRITTEN
Reason:
The Audit Control Record has been updated with the latest TMC backup.
Action:
None. This is an informational message.
INVALID DATEFMT.
Reason:
The DATEFMT= parameter value specified on the JCL EXEC parameter to TMSCOPY is invalid.
Action:
See CTSDAT01 message that follows error the for return, reason, and feedback code returned by date processing routine. For more information see TMMDATE in the
Programming.
For valid DATEFMT specifications, see Override the Preferred Date Pattern. Correct the JCL and resubmit the job.
OPEN FOR DATE MODULE FAILED
Reason:
CA 1
could not open the date processing routines.
Action:
See CTSDAT01 message that follows error for return, reason, and feedback code returned by date processing routine. For more information see TMMDATE
.
Correct the errors reported and resubmit the job.
PARM ERROR. CANNOT SPECIFY BOTH BACKUP AND RESTORE
Reason:
Both BACKUP and RESTORE were specified as parameters on the JCL EXEC statement. Either parameter value may be specified, but not both.
Action:
Correct the JCL and resubmit the job.
PARM ERROR. DATEFMT= VALUE MUST BE ENCLOSED WITHIN ()
Reason:
The DATEFMT= parameter value must be enclosed within parentheses.
Action:
For valid DATEFMT specifications, see Override the Preferred Date Pattern
.
Correct the JCL and resubmit the job.
PARM ERROR. NONCURR REQUIRES RESTORE PARM
Reason:
NONCURR was specified as a parameter on the JCL EXEC statement. The NONCURR parameter is valid only when specified with the RESTORE parameter.
Action:
Correct the JCL and resubmit the job.
PARM ERROR. UNKNOWN KEYWORD.
Reason:
The value specified by PARM= on the JCL EXEC statement is invalid.
Action:
Correct the JCL and resubmit the job.
TMC HAS BEEN SUCCESSFULLY BACKED UP
Reason:
The TMC data set has been successfully backed up.
Action:
No action is required. This is an informative message.
xxxxxx IS AN INVALID TMC RECORD
Reason:
The TMC (excluding the three Control Records) was read, and the number of Volume records backed up is less than the number of Volume records defined in the volume ranges in the TMC Control Records #1 and #3.
Action:
Execute TMSPTRS and correct any chaining errors. Contact Technical Support at http://ca.com/support for assistance.
***** NUMBER OF AUDIT RECORDS GENED nnnnnnnn AND NUMBER BACKED UP NOT EQUAL ***** nnnnnnnn
Reason:
The number of Audit records generated does not equal the number of Audit records backed up.
Action:
Verify that the AUDIT dataset was formatted properly and that TMSFORMT did not abend with a SD37/SB37. Also, if the Audit dataset was copied or moved, verify that the operation did not abend with a SD37/SB37. Alternatively, verify using TMSBINQ that the number of records generated (TMAUDIT1) has not been updated with incorrect values.