When running TMSXTEND, you may encounter the below scenario.
In the SYSLOG, during the execution of TMSXTEND, you see that Health Checks are getting IEFTMS34, and the TMSXTEND is also getting IEFTMS34, as well as an IEFTMS35 :
CAHCHECK IEFTMS34 WAITING ON EXCLUSIVE ENQUEUE OF TMSQNAME RESOURCE TMSINIT
TMSXTEND IEFTMS34 WAITING ON EXCLUSIVE ENQUEUE OF TMSQNAME RESOURCE TMSINIT
TMSXTEND IEFTMS35 WAITING ON TMSQNAME RESOURCES TMSINIT, TMS-TMC AND TMS-AUD
- De-activate the CA 1 Health Checks, prior to running the TMSXTEND.
Note: To back-out the extend process, it may be necessary to Cancel TMSXTEND and then execute TMSXTEND with PARM=RECOVER,
- There are 2 recommended methods to De-activate (and Re-activate) the CA 1 Health Checks :
Via a Modify command, you can De-activate all CA_1 checks simultaneously.
- To De-activate all CA_1 checks:
- After you have De-activated all the CA 1 Health Checks, re-run TMSXTEND
- To Re-activate the CA_1 checks:
Via SDSF, you can De-activate CA_1 checks individually.
Enter command CK to display all Health Checks.
- For each CA_1 check that is in an 'ACTIVE(ENABLED)' state, put an "H" beside it to De-activate it.
- After you have De-activated all the CA 1 Health Checks, re-run TMSXTEND.
- To Re-activate the check, put an "A" beside each one.
Refer to the CA 1 Tape Management Programming Guide, in section 'CA Health Checker Integration'.
Refer to the CA 1 Tape Management Administration Guide and Best Practices Guide for details about the individual CA 1 Health Checks.