PTF Cover Letter
PTF ( Program Temporary Fixes ) Cover letter
HASM-INCORROUT - QYASRTVDDD option 2 allows other nodes to c
Pre/Co-Requisite PTF / Fix List
REQ LICENSED PTF/FIX LEVEL
TYPE PROGRAM RELEASE NUMBER MIN/MAX OPTION
---- -------- --------- ------- ------- ------
NONE
NOTICE:
-------
Application of this PTF may disable or render ineffective programs that
use system memory addresses not generated by the IBM translator,
including programs that circumvent control technology designed to limit
interactive capacity to purchased levels. This PTF may be a prerequisite
for future PTFs. By applying this PTF you authorize and agree to the
foregoing.
This PTF is subject to the terms of the license agreement which
accompanied, or was contained in, the Program for which you are obtaining
the PTF. You are not authorized to install or use the PTF except as part
of a Program for which you have a valid Proof of Entitlement.
SUBJECT TO ANY WARRANTIES WHICH CAN NOT BE EXCLUDED OR EXCEPT AS EXPLICITLY
AGREED TO IN THE APPLICABLE LICENSE AGREEMENT OR AN APPLICABLE SUPPORT
AGREEMENT, IBM MAKES NO WARRANTIES OR CONDITIONS EITHER EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR CONDITIONS OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON INFRINGEMENT,
REGARDING THE PTF.
The applicable license agreement may have been provided to you in printed
form and/or may be viewed using the Work with Software Agreements (WRKSFWAGR)
CL command.
APAR Error Description / Circumvention
-----------------------------------------------
QYASRTVDDD option 2 allows other nodes to change data
CORRECTION FOR APAR SE59582 :
-----------------------------
QYASRTVDDD API has been corrected to fix the problem
CIRCUMVENTION FOR APAR SE59582 :
--------------------------------
None.
DESCRIPTION OF PROBLEM FIXED FOR APAR SE59907 :
-----------------------------------------------
Improve reliability and performance of large clusters.
CORRECTION FOR APAR SE59907 :
-----------------------------
The cluster will send fewer messages and will have cluster
resource group (CRG) jobs only on cluster nodes in the CRG
recovery domain.
CIRCUMVENTION FOR APAR SE59907 :
--------------------------------
None.
DESCRIPTION OF PROBLEM FIXED FOR APAR SE60997 :
-----------------------------------------------
Due to an internal lock conflict with cluster, it may cause
cluster code to hit an exception which results in MSGMCH2601 in
the QCSTCRGM job, causing the job to potentially end. The ending
of that job could result in an unpredictable set of events
depending on which node in a cluster that the job is ending on.
One example of an unpredictable event is that it could trigger
failover activities to start in a geomirror environment. The
iASP or iASPs vary off and then CRG recovery domain roles
change.
CORRECTION FOR APAR SE60997 :
-----------------------------
The QCSTCRGM job will avoid the lock conflict, and so the
unexpected ending of the QCSTCRGM job, by caching queue
information.
CIRCUMVENTION FOR APAR SE60997 :
--------------------------------
None.
DESCRIPTION OF PROBLEM FIXED FOR APAR SE61086 :
-----------------------------------------------
OSP-INCORROUT Fixes for reduced cluster messages
CORRECTION FOR APAR SE61086 :
-----------------------------
Several minor fixes for reduced cluster messages.
1. Adding the same CRG node to a CRG will no longer cause the
CRG job to end.
2. A cluster API request will not hang if there are no active
CRG nodes.
3. A CRG will be deleted from a node not in the recovery domain
if all the CRG nodes have been removed from the cluster.
CIRCUMVENTION FOR APAR SE61086 :
--------------------------------
None.
Activation Instructions
None.
Special Instructions
On each node in the cluster, end clustering, apply the fix, and then
start clustering. It is not necessary to update all nodes at the same
time, however, any node without the fix will continue to be a potential
source of the problem.
********************************************************************
THE FOLLOWING ARE SUPERSEDED SPECIAL INSTRUCTIONS. IF THE SUPERSEDED
PTF HAS ALREADY BEEN APPLIED AND ITS SPECIAL INSTRUCTION FOLLOWED,
IT IS NOT NECESSARY TO FOLLOW THAT SPECIAL INSTRUCTION AGAIN.
********************************************************************
SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI51892 :
=================================================
On each node in the cluster, end clustering, end the QPRFSYNCH job,
apply the fix, and then
start clustering. It is not necessary to update all nodes at the same
time, however, any node without the fix will continue to be a potential
source of the problem.
Default Instructions
THIS PTF CAN BE APPLIED IMMEDIATE OR DELAYED.
Supersedes
PTF/FIX NO(S). APAR TITLE LINE
-------------- ------------------------------------------------------------
SI52828 HASM-INCORROUT CHGCRG *CHGCUR ISSUE XSM WITH GEOGRAPHIC MIRR
SI52648 OSP-INCORROUT Same dataport address allowed for the same CRG
SI51892 OSP-INCORROUT Clustering pre-GA fixes
SI51892 OSP-INCORROUT i SW FST: V7R2: Admin Domain will not start pr
SI51892 INCORROUT ADDDEVDMNE command hangs in mixed-released cluster
Summary Information
System.............................. | i |
Models.............................. | |
Release............................. | V7R2M0 |
Licensed Program............... | 5770SS1 |
APAR Fixed.......................... | View details for APAR SE59582 View details for APAR SE59907 View details for APAR SE60997 View details for APAR SE61086 |
Superseded by:...................... | View fix details for PTF SI79263 |
Recompile........................... | N |
Library............................. | QSYS |
MRI Feature ........................ | NONE |
Cum Level........................... | C5135720 |
IBM disclaims all warranties, whether express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. By furnishing this document, IBM grants no licenses to any related patents or copyrights. Copyright © 1996,1997,1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022 IBM Corporation. Any trademarks and product or brand names referenced in this document are the property of their respective owners. Consult the Terms of use link for trademark information.
Was this topic helpful?
Document Information
Modified date:
25 March 2022