TMSREMOV Messages

* ERRORS HAVE OCCURRED . . . .* NEW TMC IS INVALID
ca1tms
* ERRORS HAVE OCCURRED . . . .* NEW TMC IS INVALID
Reason:
Errors in TMSREMOV processing are listed on the output describing the problem. TMSREMOV destroys the new TMC by writing over Control Record #1.
Action:
Correct the errors listed and perform the TMSREMOV process again. If it is necessary to reestablish the original TMC into production, ensure that the TMCDSN parameter in member TMOOPTxx of CAI.CTAPOPTN correctly references the old TMC and the system catalog, and execute TMSINIT to reinitialize
CA 1
DSNB VOL SER xxxxxx (REL REC yyy,yyy,yyy) NOT IN NEW TMC
Reason:
A DSNB record in the old TMC is referencing VOLSER xxxxxx that has no corresponding Volume record in the new TMC.
Action:
Reestablish addressability to the old TMC as described in the action for the first error message. Execute TMSPTRS, correct any reported chaining errors, and perform the TMSREMOV process again.
NEW DSNB'S GENED (xxx,xxx,xxx)MUST EQUAL OLD DSNB'S GENED (yyy,yyy,yyy)
Reason:
The number of DSNBs formatted in the new TMC is not identical to the number in the old TMC.
Action:
Perform the TMSREMOV process again and ensure the new TMC is formatted with the same number of DSNBs as the old TMC.
NEW TMC AND OLD TMC RANGES ARE THE SAME - CHECK OS CATALOG
Reason:
Information on the ranges formatted in the old and new TMC is identical.
Action:
Ensure that the new TMC was properly addressed by TMSINIT and that the TMC and OLDTMC DD statements correctly reference the proper data sets. Perform the TMSREMOV process again.
NEW TMC HAS NOT BEEN FORMATTED CORRECTLY
Reason:
The first three records in the new TMC are not Control Records.
Action:
Ensure the TMC DD correctly references the new TMC and perform the TMSREMOV process again.
NEW TMC RANGE DOES NOT MATCH INTERNAL RANGES - REINITIALIZE WITHNEW TMC
Reason:
The TMC referenced by the TMC DD does not have the same ranges that were loaded into the
CA 1
resident module during TMSINIT processing.
Action:
Ensure that the TMOOPTxx member in CAI.CTAPOPTN correctly references the new TMC and the system catalog entry. Perform the TMSREMOV process again.
xxxxxx HAS A yyyyy VOL OF zzzzzz WHICH IS NOT IN NEW TMC
Reason:
The Volume record from the old TMC for VOLSER xxxxxx contains a yyyyy volume pointer of FIRST, NEXT or PREV (1STVOL, NEXTVOL or PREVVOL) that references volume zzzzzz, which is not formatted in the ranges of the new TMC.
Action:
Reestablish addressability to the old TMC as described in the previous error message. Use TMSUPDTE to clear the invalid pointer from the appropriate Volume record and perform the TMSREMOV process again.
xxxxxx IS NOT IN NEW TMC AND NOT IN DELETE STATUS
Reason:
A Volume record for VOLSER xxxxxx is not reflected in the new TMC, and not in inactive (DELETE) status in the old TMC.
Action:
Reestablish addressability to the old TMC as described in the action for the first error message. If the volume is in scratch status, use TMSDELET or
CA 1
online facilities to mark the volume inactive and perform the TMSREMOV process again. If the volume is not in scratch status, ensure that it is expired and execute TMSCLEAN before marking the volume inactive. Then perform the TMSREMOV process again.
XXX,XXX,XXX DSNBS ALREADY ALLOCATED ON THE NEW TMC
Reason:
The number of used DSNBs in the new TMC (as set in Control Record#2) is not zero.
Action:
Ensure that the new TMC was properly addressed during TMSINIT processing and that the JCL for TMSREMOV correctly identifies the old and new TMCs, and perform the TMSREMOV process again.