IBM Support

SI57608 - OSP-INCORROUT Base Function to Enable Future Extensions

PTF Cover Letter


PTF ( Program Temporary Fixes ) Cover letter


Order this fix

Abstract

OSP-INCORROUT Base Function to Enable Future Extensions


Pre/Co-Requisite PTF / Fix List

REQ  LICENSED           PTF/FIX  LEVEL

TYPE PROGRAM  RELEASE   NUMBER   MIN/MAX  OPTION
---- -------- --------- -------  -------  ------
PRE  5770999  V7R2M0    MF61035   00/00    0000
PRE  5770999  V7R2M0    MF61022   00/00    0000



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

-----------------------------------------------
Base Function to Enable Future Extensions

CORRECTION FOR APAR SE62125 :
-----------------------------
Base Function to Enable Future Extensions

CIRCUMVENTION FOR APAR SE62125 :
--------------------------------
None.


DESCRIPTION OF PROBLEM FIXED FOR APAR SE63267 :
-----------------------------------------------
Cluster base function to enable future extensions.

CORRECTION FOR APAR SE63267 :
-----------------------------
Cluster base function to enable future extensions.

CIRCUMVENTION FOR APAR SE63267 :
--------------------------------
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 SI54303 :
=================================================

In order to fix the problems described by this PTF, the PTF must be
applied on all nodes (on the same release as this PTF) in the cluster.
However,the entire cluster does not have to be ended to do this.  One
node at a time can be ended, the PTF applied, and the node restarted to
join the cluster.

Note, you must end Cluster Resource Services on the node, apply the
PTF,and then restart Cluster Resource Services before the fix is
available.

To determine if Cluster Resource Services is active on your system, do
a WRKACTJOB from the command line of your system and look for two
system jobs (QCSTCTL and QCSTCRGM).  If either of these jobs exist,
Cluster Resource Services must be ended on this system and you must
sign off all sessions where Cluster Resource Services APIs were used
before the PTF can be applied.  Cluster Resource Services is started
through the Start Cluster Node API.

SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI48772 :
=================================================

After applying the PTF, you must sign off of an interactive session and
then sign in again before the fix is available to that interactive
session.

SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI50858 :
=================================================

In order to fix the problems described by this PTF, the PTF must be
applied on every node in the cluster. You do not have to end the
cluster to do this. However, you should end the CRG jobs associated
with the cluster administrative domain on every cluster node before you
apply the PTF. You can do this one node at a time.

Note, you must end the cluster administrative domain CRG jobs on each
cluster node, apply the PTF, and restart the CRG job before the fix is
available.

The cluster administrative domain CRG jobs will be ended if you end
Cluster Resource Services for each node in your cluster. Cluster
Resource Services can be ended using the End Cluster Node API or CL
command. Optionally, you can end just the cluster administrative domain
jobs without ending your cluster nodes by calling the Change
Cluster Recovery CL command.

To determine if any cluster administrative domain jobs are active on
your system, use the WRKACTJOB command from the command line of your
system. Look for any system jobs which have the same name as any
cluster administrative domains which you have created in your cluster.
If there are any cluster administrative domain jobs on your system,
they must be ended. You can end just the cluster administrative domain
jobs on every node with this command:

CHGCLURCY CLUSTER(<cluster>) CRG(<admin_domain>) NODE(*ALL)
ACTION(*END)

where <cluster> is the name of your cluster and <admin_domain> is the
name of a cluster administrative domain. You should call this command
once for each cluster administrative domain in your cluster.

You must sign off all sessions where any cluster administrative domain
commands or APIs were used before the PTF can be applied.

After the PTF has been applied on a system, you can restart the cluster
jobs that were ended before the PTF was applied. If Cluster Resource
Services was ended, you can use the Start Cluster Node API or CL
command to start Cluster Resource Services for each cluster node. If
you used the Change Cluster Recovery CL command to end just the cluster
administrative domain jobs, they can be restarted on each cluster node
using the Change Cluster Recovery command as follows:

CHGCLURCY CLUSTER(<cluster>) CRG(<admin_domain>) NODE(<node>)
ACTION(*STRCRGJOB)

where <cluster> is the name of your cluster, <admin_domain> is the name
of the cluster administrative domain, and <node> is the cluster node
name for the system. You should call this command once for each cluster
administrative domain in your cluster.

After the PTF has been applied, you should also restart the QPRFSYNCH
job on every node in your cluster.  You can restart the QPRFSYNCH job
with the following commands:

CALL PGM(QSYS/QFPAPRFJ) PARM(END)
CALL PGM(QSYS/QFPAPRFJ) PARM(START)

SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI43999 :
=================================================

You must follow the Special Instructions for the superseded PTF
SI36958.

SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI40059 :
=================================================

End clustering on a node, apply the fix, then re-start clustering on
the node.  When the fix has been applied to all nodes in the cluster,
the fix will be active for the cluster.

SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI39933 :
=================================================

On each node in the cluster, apply the fix and 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.

SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI42297 :
=================================================

End clustering on a node, apply the fix, then re-start clustering on
the node.

SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI42199 :
=================================================

In order to fix the problems described by this PTF on all nodes in the
cluster, the PTF must be applied on all nodes in the cluster.
However,the entire cluster does not have to be ended to do this.  One
node at a time can be ended, the PTF applied, and the node restarted to
join the cluster.

Note, you must end Cluster Resource Services on the node, apply the
PTF,and then restart Cluster Resource Services before the fix is
available.

To determine if Cluster Resource Services is active on your system, do
a WRKACTJOB from the command line of your system and look for two
system jobs (QCSTCTL and QCSTCRGM).  If either of these jobs exist,
Cluster Resource Services must be ended on this system and you must
sign off all sessions where Cluster Resource Services APIs were used
before the PTF can be applied.  Cluster Resource Services is started
through the Start Cluster Node API.

SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI56614 :
=================================================

The PTF must be applied on all nodes in the cluster. However, it is not
necessary to update all cluster nodes at the same time. On each node in
the cluster: end clustering, apply the PTF, then start clustering.

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
--------------  ------------------------------------------------------------
   SI58171      OSP-OTHER-UNPRED GMIR AFTER FAILOVER SECOND NODE IN THE SAME
   SI51570      HASM-HA-MSGCPD000D MSGCPD000D AND MSGCPF3698 EVERY HOUR IN C
   SI58054      HASM-HA-WAIT CHANGING OR DISPLAYING DEVICE DOMAIN DATA WHILE
   SI58030      OSP-INCORROUT QYASRTVDDD Option 2 blocked after QYASCHGDDD w
   SI57154      OSP-INCORROUT RMVCRGNODE followed by ADDCRGNODE may fail
   SI57154      HASM-HA-MSGCPFBBA8 CRG OBJECT CONVERSION FROM V7.1 TO V7.2 E
   SI56614      HASM-HA-F/QCSTADSIMP-T/QCSTADSIMP-MSGMCH0601 MSGMCH0601 DURI
   SI56614      OSP-INCORROUT Admin domain may hang after ADDCADNODE complet
   SI56541      HASM-HA-WAIT CRG STATUS MISMATCH AMONGST NODES IN CLUSTER DU
   SI56541      HASM-INCORROUT RMVCRGNODE Partially Completed then Hung in G
   SI55306      HASM-INCORROUT - QYASRTVDDD option 2 allows other nodes to c
   SI55306      OSP-OTHER-PERFM Improve reliability and performance of large
   SI55306      HASM-HA-F/#CFOCHKR-T/QCSTCMN-MSGMCH2601 MSGMCH2601 ENCOUNTER
   SI55306      OSP-INCORROUT Fixes for reduced cluster messages
   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 SE62125
View details for APAR SE63267
Superseded by:......................View fix details for PTF SI79263
Recompile...........................N
Library.............................QSYS
MRI Feature ........................NONE
Cum Level...........................C6127720


IBM i Support

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.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.2.0","Product":{"code":"SWG60","label":"IBM i"},"Component":"5770SS1","Edition":"","Line of Business":{"code":"LOB57","label":"Power"}}]

Document Information

Modified date:
25 March 2022