Sysplex-wide impact due to loop in GRS on z/OS 1.9 and higher In z/OS 1.9 GRS recovery for GQSCAN retries with incorrect registers. This can result in an ABEND0A0 followed by repetitive ABEND0C6 or ABEND0C4 in ISGQNX.
As a result of the program check loop in ISGQNX's recovery no GRS work is able to run on the failing system. This may cause sysplex-wide impact for the following reasons: - Global resources held by the failing system cannot be released causing tasks that request the resources on other systems to wait. - If the failing system is a GRS Lock Manager, other systems may not be able to complete their XES requests. - Global GQSCANs may time out. - Global TEST ENQs cannot be processed. - No list ENQ requests can be processed on other systems if the failing system is holding the GRS list lock. Symptoms may also include: - High CPU usage in GRS and *MASTER* on the failing system. - Message ISG361I indicating delays on other systems in the Sysplex. - D GRS, C is unable to complete on the problem system and Message ISG343I only returns local resource data on other systems. Please see APAR OA24741 for further details. Recommended Actions: - Apply the PTFs for OA24741 View all bulletins at https://www14.software.ibm.com/webapp/set2/sas/f/redAlerts/home.html ==================== This email/fax message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution of this email/fax is prohibited. If you are not the intended recipient, please destroy all paper and electronic copies of the original message. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
