The CA MIM Driver manages global activity of the product components by routing transactions across mainframe images through a control file residing on a shared DASD volume or a Virtual Control File (VCF) residing in CA MIM private storage on a selected master system.
The VCF architecture uses channel-to-channel (CTC) devices or the z/OS XCF component to pass a transaction data buffer between systems.
In a parallel sysplex environment with a CA MIM complex that is equal to or is a subset of the parallel sysplex complex, the control file can be placed in the coupling facility. This provides a significant performance enhancement through the reduction of I/O transfer times as compared to CTC, cached DASD, and non-cached DASD I/O operations.
CA MIM provides the capability to define backup communication methods. This furnishes data centers with the redundancy needed to guarantee uninterrupted resource integrity as the operating environment changes or during hardware outages. While the product is running, migrations can be initiated between DASD control files, between VCF, or between DASD and VCFs.
The CA MIM transaction processing architecture is based on a star configuration. With this architecture, CA MIM on each system needs only a single access to the control file to determine the global status of all managed resources. Frequency of access to the control file is based on the amount of resource activity on a particular system.
The CA MIM Driver can be defined as CA MIM address space control code, which supervises the activities of the CA MIM address space, regardless of which CA MIM facilities are activated. CA MIM Driver code is responsible for the following CA MIM address space activities:
Control:
Housekeeping:
Global Communications:
|
Copyright © 2014 CA.
All rights reserved.
|
|