Reason:
During CA MII initialization, it was determined that GDIINIT PROCESS=SELECT was coded in the MIMINIT parmlib member or that the PROCESS parameter is defaulting to SELECT. Customers running CA MII in SELECT mode typically have many DASD data integrity exposures in their DASD data-sharing MIIplex. These exposures occur because system programmers rarely maintain accurate CA MII ENQ management definitions in the MIMQNAME parmlib member. This oversight causes many SCOPE=SYSTEMS ENQs to not be propagated across all MIIplex systems - each of which are a data integrity exposure. These DASD data integrity exposures can result in corrupted DASD data. Because of the critical nature of DASD data loss, CA MII issues this warning message to alert systems programmers that DASD data integrity exposures are likely to exist in their DASD sharing MIIplex. CA MII initialization continues.
Action:
We recommend that you set GDIINIT PROCESS=ALLSYSTEMS rather than PROCESS=SELECT. Running CA MII in ALLSYSTEMS mode causes GDIF to propagate all SCOPE=SYSTEMS ENQs across all MIIplex systems. This mode eliminates DASD data integrity exposures, and eliminates the need to constantly maintain ENQ management definitions in the MIMQNAME parmlib member.
Note: For more information on how to implement ALLSYSTEMS mode, see the chapter “Advanced Topics” in the CA MII Programming Guide. Note that due to the complexities involved in converting CA MII from SELECT to ALLSYSTEMS mode, we recommend contacting CA MIM Technical Support for assistance in converting to ALLSYSTEMS mode.
|
Copyright © 2014 CA.
All rights reserved.
|
|