CA MIM Resource Sharing 12.1 1 CA RS 1604 Service List Release Service Description Type 12.1 RO88317 EARLY START EXIT LEFT ACTIVE IF MIM SYNCHRONIZATION FAILS PTF RO88720 TAPE DEVICE ALLOCATION DEADLOCK VARY ONLINE/OFFLINE GLOBAL **HIPER** RO88873 HIGH CPU USAGE WITH DEQPOST=ALWAYS PTF The CA RS 1604 service count for this release is 3
CA MIM Resource Sharing 2 CA RS 1604 Service List for CBTDC10 FMID Service Description Type CBTDC10 RO88317 EARLY START EXIT LEFT ACTIVE IF MIM SYNCHRONIZATION FAILS PTF RO88720 TAPE DEVICE ALLOCATION DEADLOCK VARY ONLINE/OFFLINE GLOBAL **HIPER** RO88873 HIGH CPU USAGE WITH DEQPOST=ALWAYS PTF The CA RS 1604 service count for this FMID is 3
CA MIM Resource Sharing 12.1 3 CA RS 1604 - PTF RO88317 Release Service 12.1 RO88317 RO88317 M.C.S. ENTRIES = ++PTF (RO88317) EARLY START EXIT LEFT ACTIVE IF MIM SYNCHRONIZATION FAILS PROBLEM DESCRIPTION: When running with the Early Start mechanism, the MIMESNQX exit may be left active if MIM fails to synchronize properly on the first attempt. SYMPTOMS: ENQUEUE and DEQUEUE performance may be slightly degraded. IMPACT: ENQUEUE and DEQUEUE performance may be slightly degraded. CIRCUMVENTION: None. PRODUCT(S) AFFECTED: CA MULTI-IMAGE MANAGER Release 12.0 CA MULTI-IMAGE MANAGER Release 12.1 Related Problem: MII 239 Copyright (C) 2016 CA. All rights reserved. R00083-BTD121-SP1 DESC(EARLY START EXIT LEFT ACTIVE IF MIM SYNCHRONIZATION FAILS). ++VER (Z038) FMID (CBTDC10) PRE ( RO81389 RO83424 ) SUP ( TR88317 )
CA MIM Resource Sharing 12.1 4 CA RS 1604 - PTF RO88720 Release Service 12.1 RO88720 RO88720 M.C.S. ENTRIES = ++PTF (RO88720) TAPE DEVICE ALLOCATION DEADLOCK VARY ONLINE/OFFLINE GLOBAL * Product Error Alert (PEA) * * This Product Error Alert is intended to inform CA MIA * * Customers about a Tape Device Allocation Deadlock * * condition that can occur at CA MIA R11.9 and above in * * z/os 1.13 and above operating environments. * * Creation Date: 17 NOV 2015 * * Revision Date: 17 NOV 2015 * * The Problem described in this Problem Record and the * * related CA MIA R11.9 Information APAR RI86564 has been * * corrected. * * Please read the addendum appended to the bottom of this * * document for a description of the resolving CA and IBM * * PTFs. * Background: CA MIA UNLOAD Serialization, implemented at CA MIM 11.9 (May 2012 GA), was specifically developed to address an IOS003A INTERVENTION REQUIRED problem involving tape volumes remaining in Tape Device transports after deallocation. In the original reported problem, system automation had been implemented to issue and analyze CA MIA DISPLAY GLOBALUNIT command output and issue z/os UNLOAD commands for unallocated tape devices on which tape volumes remained after de-allocation. This unintended use of the DISPLAY GLOBALUNIT command data triggered large volumes of UNLOAD commands, some of which resulted in IOS003A INTERVENTION REQUIRED conditions for target tape devices on external MIAplex systems. CA MIA UNLOAD Serialization was developed in cooperation with IBM, which provided the IEF_ALLC_UNLOAD MVS Installation Exit at z/os 1.13. The IEF_ALLC_UNLOAD Exit is driven when a device is unloaded by processes occurring outside of the normal allocation work flow, such as VARY OFFLINE or UNLOAD command processing. During product initialization at CA MIA releases 11.9 and above, in z/os 1.13 and above operating environments, CA MIA plants module MIMTPUNX at the IEF_ALLC_UNLOAD Exit point. MIMTPUNX globally serializes IEF_ALLC_UNLOAD calls. There are no MIA parameters that control the activation or deactivation of MIA UNLOAD Serialization. Problem: Three years after its implementation, several CA MIA customers recently experienced problems involving CA MIA UNLOAD Serialization. Analysis of the problem documentation identified that a Tape Device Allocation Hang condition can occur in CA MIM 11.9, z/os 1.13 and above environments. Exposure to the problem exists when VARY ONLINE commands and multiple VARY OFFLINE command initiated tape device UNLOAD events are active across an MIAplex, resulting in a cross system serialization deadlock. In the observed cases, sequences of VARY (RANGE),ONLINE and VARY (RANGE), OFFLINE commands, for the same large range of tape devices, were simultaneously routed to all or multiple systems within the MIAplex. Tape Device Allocation for the device type involved in the VARY ONLINE/UNLOAD serialization Deadlock stops. VARY processing, for all device types, stops. ENQUEUE Conflict display commands identify that ALLOCAS owns a SYSIEFSD VARYDEV SHR ENQ and several MIA Tasks wait EXCL for this resource. An MIA DIAGNOSE ALL SYSTEMS DISPLAY identifies that individual LOCKs are held on two or more systems. On one of these systems, the JOBSTATUS portion of the DIAGNOSE display
Release Service CA MIM Resource Sharing 12.1 5 CA RS 1604 - PTF RO88720 shows that GTAF is delaying an ALLOCAS task request for a single device, and that the MIA started task has been released to MVS to serialize VARY ONLINE commands for other individual devices. On the other system(s), the JOBSTATUS portion of the display shows that GTAF is delaying an ALLOCAS task request for a different single device, and that the MIA started task has been released to MVS to serialize VARY ONLINE commands for other individual devices. The MIA started task on each system owns the resources that ALLOCAS requires, and ALLOCAS owns ENQ resources that MIA requires. The result is a serialization deadlock. Problem mitigation: The following actions, if time permits, can be taken to attempt to relieve the deadlock: 1. Issue a VARY (RANGE),PURGE command to all MIAplex systems. Use the same RANGE specified on the original routed VARY commands. 2. Issue the DIAGNOSE ALL command to identify the systems involved in in the deadlock. Systems on which individual LOCKs are held are suspect. Look for ALLOCAS being delayed for a single LOCK and the MIA started task owning single Group LOCKs. 3. Issue the MIM DUMP KILL=(TASKNAME=VARYdddd) for EACH device (Dev) appearing in the DIAGNOSE ALL Active VARY device queue display. 4. Repeat Step 3 on EACH system in the MIAplex. 5. Reissue the DIAGNOSE ALL command to determine whether the serialization deadlock has been cleared. Tape Device Allocation will resume as soon as the deadlock has been relieved. 6. If the deadlock cannot be cleared, it may be necessary to perform a shutdown and restart of the MIA address spaces on the systems directly involved in the deadlock. If the systems directly involved in the deadlock cannot be identified, a GLOBAL SHUTDOWN and RESTART of MIA will clear the problem. In order to expedite MIA SHUTDOWN/RESTART processing: - BEFORE stopping MIA, purge system initiators to minimize Allocation Recovery. - BEFORE restarting MIA, respond to all outstanding Allocation Recovery WTORs. - After MIA is restarted and SYNCHRONIZED on all systems, restart system initiators. Circumvention: While CA and IBM are working to provide a permanent resolution for this problem, a temporary circumvention is available to eliminate the exposure to it. Dynamically disabling the MIA UNLOAD intercept, MIMTPUNX, planted at the z/os IEF_ALLC_UNLOAD Exit point, eliminates exposure to the problem. This can be accomplished by issuing the following z/os SETPROG EXIT command: SETPROG EXIT,MODIFY EXITNAME=IEF_ALLC_UNLOAD,MOD=MIMTPUNX,STATE=INACTIVE Setting the state of MIMTPUNX to INACTIVE indicates that the MIMTPUNX exit routine should NOT be given control when the IEF_ALLC_UNLOAD exit is called. Other ISV product intercepts planted at the IEF_ALLC_UNLOAD Exit (if any) are unaffected by this command. A z/os DISPLAY PROG,EXIT,EXITNAME=IEF_ALLC_UNLOAD command displays all intercepts planted at the IBM unload exit point as well as their status. After issuing the SETPROG command to disable the CA MIA unload exit dynamically on each MIAplex system, add the command to the CA MIA MIMSYNCH parmlib member so that it executes whenever CA MIA is restarted. Taking this action will eliminate exposure to the problem. When a permanent CA MIA and/or IBM PTF solution is made available, removing the SETPROG command from the CA MIA MIMSYNCH parmlib member and restarting CA MIA with the permanent PTFs applied will restore the MIMTPUNX offline exit to active status. PRODUCT(S) AFFECTED: CA MULTI-IMAGE MANAGER Release 11.9 CA MULTI-IMAGE MANAGER Release 12.0 CA MULTI-IMAGE MANAGER Release 12.1
Release Service CA MIM Resource Sharing 12.1 6 CA RS 1604 - PTF RO88720 * Resolving PTF Addendum 07 March 2016 * RO88716 addresses a Tape Device Allocation Hang that can occur in CA MIM R11.9, z/os 1.13 and above operating environments. Exposure to the problem exists when VARY ONLINE commands and multiple VARY OFFLINE command initiated tape device UNLOAD events are active across an MIAplex. A cross system serialization deadlock can result. This problem was originally documented in a Product Error Alert (PEA) distributed via APAR# RI86564 on 17 November 2015. CA MIM and IBM ALLOCAS Development Teams collaborated to provide a two PTF solution to the problem. CA MIA PTF RO88716 and the IBM z/os PTF version specific to your operating environment, documented in IBM APAR OA49722, provide the complete solution. IBM APAR OA49722 introduces an enhanced MVS IEF_ALLC_UNLOAD installation exit parameter list. CA MIA PTF RO88716 utilizes the OA49722 enhanced parameter list to identify the event that triggered the IEF_ALLC_UNLOAD Exit call and makes a granular determination of whether to GLOBALLY serialize it or not. With CA MIA PTF RO88716 applied, CA MIA processes calls to IEF_ALLC_UNLOAD as follows, regardless of whether IBM OA49722 PTFs have been applied: - When CA MIA processes an IEF_ALLC_UNLOAD exit parameter list that has been enhanced by OA49722 PTFs, CA MIA will globally serialize UNLOAD command triggered UNLOAD events. - When CA MIA processes an IEF_ALLC_UNLOAD parameter list that has not been enhanced, indicating that OA49722 has not been applied, CA MIA will not GLOBALLY serialize any UNLOAD event. CA MIA PTF RO88716 can be applied independently of the IBM PTF specific to your environment. If a problem circumvention of disabling CA MIM module MIMTPUNX at the IEF_ALLC_UNLOAD Exit point has been implemented, remove the SETPROG EXIT,MODIFY EXITNAME=IEF_ALLC_UNLOAD,MOD=MIMTPUNX,STATE=INACTIVE command circumvention from MIASYNCH or system automation PRIOR to restarting CA MIA after the application of RO88716. * Related Problem: MIA 151 Copyright (C) 2016 CA. All rights reserved. R00084-BTD121-SP1 DESC(TAPE DEVICE ALLOCATION DEADLOCK VARY ONLINE/OFFLINE GLOBAL). ++VER (Z038) FMID (CBTDC10) SUP ( TR88720 ) ++HOLD (RO88720) SYSTEM FMID(CBTDC10) REASON (ACTION ) DATE (16068) COMMENT ( +----------------------------------------------------------------------+ CA MULTI-IMAGE MANAGER Release 12.1 SEQUENCE Before Restart If the circumvention of disabling CA MIA module MIMTPUNX at the MVS IEF_ALLC_UNLOAD installation exit point has been implemented, remove the 'SETPROG EXIT, MODIFY EXITNAME=IEF_ALLC_UNLOAD,MOD=MIMTPUNX,STATE=INACTIVE' command from the MIASYNCH member of the CA MIA parmlib or from system automation PRIOR to restarting CA MIA after the application of this PTF. PURPOSE CA MIM and IBM ALLOCAS Development Teams collaborated to provide a two PTF solution to the problem documented in this PTFs description and CA MIA Problem Record #151.
Release Service CA MIM Resource Sharing 12.1 7 CA RS 1604 - PTF RO88720 This CA MIA PTF and the IBM z/os PTF version specific to your operating environment(documented in IBM APAR OA49722) provide the complete solution. IBM APAR OA49722 introduces an enhanced IEF_ALLC_UNLOAD installation exit parameter list. This CA MIA PTF utilizes the OA49722 enhanced parameter list to identify the event that triggered the IEF_ALLC_UNLOAD Exit call and makes a granular determination of whether to GLOBALLY serialize the UNLOAD event or not. When CA MIA processes an IEF_ALLC_UNLOAD exit parameter list that has been enhanced by OA49722 PTFs, CA MIA will globally serialize UNLOAD command triggered UNLOAD events. When CA MIA processes an IEF_ALLC_UNLOAD exit parameter list that has not been enhanced, CA MIA will not globally serialize any UNLOAD event. This CA MIA PTF can be applied independently of the IBM OA49722 PTF specific to your operating environment. USERS CA MIA R11.9, R12.0 and R12.1 customers. AFFECTED KNOWLEDGE Familiarity with the CA MIA parmlib or system automation REQUIRED is required to disable the problem circumvention if it has been implemented. ACCESS Update access to the CA MIA parmlib or to system REQUIRED automation is required to disable the circumvention if it has been implemented. ).
CA MIM Resource Sharing 12.1 8 CA RS 1604 - PTF RO88873 Release Service 12.1 RO88873 RO88873 M.C.S. ENTRIES = ++PTF (RO88873) HIGH CPU USAGE WITH DEQPOST=ALWAYS PROBLEM DESCRIPTION: The CA MII address space may perform excessive control file cycles if using a DASD control file and SET GDIF DEQPOST=ALWAYS is in effect. This can result in higher than expected CPU usage by the MII address space. SYMPTOMS: Excessive control file cycles as evidenced by the RATE/CYCLE field in the DISPLAY IO command output. IMPACT: Higher than expected CPU usage. CIRCUMVENTION: Change DEQPOST to a value other than ALWAYS until the ++PTF can be applied. PRODUCT(S) AFFECTED: CA MULTI-IMAGE MANAGER Release 12.0 CA MULTI-IMAGE MANAGER Release 12.1 Related Problem: MII 241 Copyright (C) 2016 CA. All rights reserved. R00085-BTD121-SP1 DESC(HIGH CPU USAGE WITH DEQPOST=ALWAYS). ++VER (Z038) FMID (CBTDC10) SUP ( TR88873 )