How to resolve "IEFTMS38 xxxxxxx FOUND CPU nnnn HAS FLAGS LEFT ON FROM A PRIOR EXECUTION OF TMSXTEND". (IEFTMS78 WARNING: CA 1 TMC EXTEND INDICATOR IS ON with TMSXTEND)
Article ID: 48095
Updated On:
Products
Issue/Introduction
Description:
When running TMSINIT, or TMSCOPY, you may encounter the below sequence of messages in the SYSLOG:
*IEFTMS38 xxxxxxx FOUND CPU nnnn HAS FLAGS LEFT ON FROM A PRIOR EXECUTION OF TMSXTEND.
PLEASE CONTACT CA 1 SUPPORT FOR ASSISTANCE IN CLEARING TMSCTL#4 OF THE CA 1 AUDIT DATASET.
During the processing of either TMSCOPY or TMSINIT, the CA 1 Audit Control Record was found to have values indicating that a TMSXTEND is still in progress.
When TMSXTEND runs, it turns on multiple flag bits in Control Record #4 (TMSCTL#4) in the audit file.
Some of these bits indicate the systems that were active at the time TMSXTEND was run, and whether TMSRINIT was run on those systems.
NOTE: Running TMSXTEND with PARM='TEST' will also turn these flag bits on, so if a test run did not complete successfully, the flag bits could be left on.
Environment
Release: ONE...00200-12.6-One-TAPE MANAGEMENT
Component:
Resolution
If applicable, you should execute TMSXTEND with PARM='RECOVER', prior to performing the steps described in the Solution section just below, to reset the relevant flag bits in TMSCTL#4.
If TMSXTEND,PARM='RECOVER' does not resolve the problem, or is not applicable, continue with the steps described below.
Solution:
- Execute TMSBINQ with the HEADERS control statement.
- Review the TMSBINQ output and locate the "AUDIT CTL REC #4 TMSCTL#4" information.
3. Please call CA1 Support for assistance in determining the cause and how to correct.
Upon successful correction, the IEFTMS38 warning message should no longer be issued when TMSCOPY or TMSINIT are executed.
Additional Information
For mapping of the TMSCTL#4 record, see the section 'Audit Data Set TMSCTL 4 - Control Record 4' in the CA1 Programming manual found here.
Feedback
