This abend is uniquely associated with TMSXTEND. The exact reason for the failure is documented in the reason code in register 15.
TMS OPEN FAILED.TMSXTEND was unable to open the TMC for SVC access.
Verify that the active TMC on the system where TMSBLDVR is a valid TMC.
The user responded to a console message telling TMSXTEND to abend because the list of systems impacted by this extend was not correct.
Correct the CPU table (CPULIST DD) to include the correct systems that should be impacted by this extend. Rerun TMSXTEND.
CTL#4 CPU flag has been corrupted.
Reformat the audit.
SIGNAL ECB NOT ZERO
TMSBLDVR did not post the signal ECB with a zero. This would indicate a problem and TMSXTEND is NOT to signal other CPU's to access the new TMC.
TMSAUDEX NON-ZERO COMPLETION
SubtAask did not end normally. See output from TMSAUDEX.
TMSBLDVR NON-ZERO COMPLETION
Subtask did not end normally. See output from TMSBLDVR.
RNAME ERROR FOR CPU IN CTL#4
Verify all CPUs support Unique RNAME functionality.
TMC.N ----> TMC.O ----> TMC.N
The rename failed, see IDCAMS error messages in the SYSPRINT output.
TMC ----> TMC.O
The rename failed, see message TMSXT30I.
TMC.N ----> TMC
The rename failed, see message TMSXT31I.
TMC.O ----> TMC
The rename failed, see message TMSXT43I.
CTSDIO ERROR ON NEW TMC.
See message TMSXT51I.
BAD ACTIVITY FROM NON-RESP CPU.
See message TMSXT56E.
TMC DSN IS TOO LONG.
See message TMSXT60E.
VOLSER UPDATE ERROR.
See message TMSXT61E.
DSNB UPDATE ERROR.
See message TMSXT62E.
MUTUALLY EXCLUSIVE PARMS.
See message TMSXT63E
INVALID CPU DURING SYNC.
See message TMSXT64E.
UPDATE WITH BAD BATCH-ID.
See message TMSXT65E.
TMC BACKUP > 3HRS OLD.
See message TMSXT66E.
TMSXTEND IS NOT RUNNING FROM AN APF AUTHORIZED LIBRARY
See message TMSXT67E.
EXTEND ALREADY ACTIVE.
See message TMSXT82E
NO EXTEND STATUS RECOVER NOT REQ.
See message TMSXT82E.
TMEXTEND FLAG RESET WHILE EXTEND PROCESSING.
The extend flag in the AUDIT file was set to zero after TMSXTEND started processing.