You have the option of activating all three CA MIM components (CA MIA, CA MIC, and CA MII) in a single CA MIM address space (CA MIA/CA MIC/CA MII), in two CA MIM address spaces (CA MIA/CA MIC, and CA MII), or in three CA MIM address spaces (CA MIA, CA MIC, CA MII). There are a number of other possible combinations as well.
From a performance standpoint, it is best to have CA MII running in an address space separated from CA MIA and CA MIC. Because enqueue service times are critical to most data centers, eliminating CA MIA and CA MIC activity in the CA MII task will improve CA MII enqueue service times. It is therefore a general recommendation that data centers requiring optimum enqueue service rates run CA MII separately from CA MIA and CA MIC.
Another benefit of running CA MIM components in separate address spaces is that problems affecting one component will not affect the others. For example, if you run all components in a single CA MIM address space, a problem involving the tape resource management may adversely affect DASD resource management or console resource management. Running CA MIM components in separate address spaces will limit the degree of impact component-specific problems may have on your data-sharing environment.
Each CA MIM component has unique performance parameters and tuning suggestions to optimize component-specific processes:
|
Component |
Where to Look for Details |
|---|---|
|
CA MIA |
In Performance Considerations in the chapter “Advanced Topics” in the CA MIA Programming Guide. |
|
CA MIC |
In Performance Considerations in the chapter “Advanced Topics” in the CA MIC Programming Guide. |
|
CA MII |
In Performance Considerations in the chapter “Advanced Topics” in the CA MII Programming Guide. |
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |