CA MIM Introduction
CA MIM for z/OSis the industry standard for sharing DASD, tape, and console resources safely and efficiently in z/OS and z/VM multiple-image environments. The product streamlines and automates many of the procedures involved in sharing resources and enables multiple-image sites to share data center resources across as many as 32 system images.
This book is intended for system programmers and operators responsible for the installation, customization, and day-to-day operation of
CA MIM for z/OS.
Components and Facilities
CA MIM for z/OSis comprised of three product components and a driver, which manages communications among mainframe systems.
CA MIA Tape Sharing
CA MIA enables z/OS sites, z/VM sites, and mixed z/OS and z/VM sites with CMS users and z/OS guests, to share tape devices automatically and safely. CA MIA provides integrity for data that resides on tape and eliminates the necessity for manual commands typically associated with tape device sharing.
CA MIA consists of the following facilities:
- Global Tape Allocation Facility (GTAF)Prevents jobs on different systems from simultaneously allocating the same tape, and prevents jobs from allocating devices already in use on another system.
- Tape Preferencing and Control Facility (TPCF)Lets you influence device selection during the z/OS allocation process. TPCF also responds automatically to the messages z/OS issues when a job cannot allocate a suitable online device.
CA MIC Message Sharing
CA MIC provides cross-system command routing from any z/OS or z/VM console and allows messages to be imported from external systems and routed to local consoles.
CA MIC facilitates global console management by allowing operations to control and customize the flow of console information so that systems can be monitored from a single point with conveniently accessible console output. This improves operations productivity and performance, and ensures that all systems are monitored consistently.
CA MIC consists of the following facilities:
- Global Command and Message Facility (GCMF)Allows you to route messages and commands to any or all systems in a complex.
- Intersystem Communication Facility (ICMF)Allows you to route cross-system commands and messages using an interface with the CA-L-Serv product.
CA MII Data Sharing
CA MII Data Sharing (CA MII) protects z/OS data integrity automatically, speeds resolution of resource conflicts in shared DASD environments, and adds additional integrity at a local system level.
CA MII consists of the following facilities:
- Global Data Integrity Facility (GDIF)Prevents simultaneous updates that occur when requests for resources are not communicated to all systems.
- Enqueue Conflict Management Facility (ECMF)Helps Time-Sharing Option (TSO) users and system operators identify and resolve conflicting requests for resources
- Enhanced Data Set Integrity Facility (EDIF)Prevents the most common sources of data set damage, such as damage to attributes or due to DISP=SHR updates
CA MIM for z/OSDriver
CA MIM for z/OSDriver manages global activity of the product components by routing transactions across mainframe images through a common control file.
Global activity is managed by the routing of transactions across system images through either a small control file residing on a shared DASD volume or a virtual control file residing in private storage in the address space of a product on a selected master system.
The virtual control file architecture uses CTC devices to pass transaction data between z/OS and z/VM systems.
In a parallel sysplex environment with a
CA MIM for z/OScomplex 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 for z/OSlets you define backup communication methods. This capability 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 virtual control files, or between DASD and virtual control files.
CA MIM for z/OStransaction processing architecture is based on a star configuration. With this architecture, every image 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 image.
CA MIM for z/OSDriver can be defined as
CA MIM for z/OSaddress space control code, which supervises the activities of the
CA MIM for z/OSaddress space, regardless of which
CA MIM for z/OSfacilities are activated.