If you are running the CA MIA or CA MIC address spaces without GDIF active, and those address spaces are using DASD control files (for example, COMMUNICATION=DASDONLY or CTCDASD), tasks in those address spaces issue hardware reserves with QNAME MIMGLOBL that are eligible for conversion by CA MII (running in a separate address space) or by IBM Global Resource Serialization (GRS).
You can optionally let CA MII convert the MIMGLOBL hardware reserves for the CA MIA or CA MIC address spaces if the following conditions are true:
If you are using GDPS/Hyperswap, you need to convert all hardware reserves, so this may be one reason why you would choose to convert the MIMGLOBL reserve for the CA MIA and CA MIC address spaces.
Important! You should not convert the MIMGLOBL hardware reserves if any of the following conditions are true:
If you are running CA MII, consider the following:
MIMGLOBL GDIF=NO
If you are running GRS, do one of the following, but not both:
RNLDEF RNL (CON) TYPE (GENERIC) QNAME (MIMGLOBL)
RNLDEF RNL(EXCL) TYPE(GENERIC) QNAME(MIMGLOBL)
|
Copyright © 2014 CA.
All rights reserved.
|
|