IBM Support

SI31600 - OSP-INCORROUT Incorrect data may be merged

PTF Cover Letter


PTF ( Program Temporary Fixes ) Cover letter


Order this fix

Abstract

OSP-INCORROUT Incorrect data may be merged


Pre/Co-Requisite PTF / Fix List

REQ  LICENSED      PTF/FIX  LEVEL

TYPE PROGRAM  REL  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

-----------------------------------------------
Cluster device domain data may become corrupted when recovering
from a network partition.

CORRECTION FOR APAR SE33299 :
-----------------------------
A network merge is properly detected to prevent potential
device domain data loss.

CIRCUMVENTION FOR APAR SE33299 :
--------------------------------
None.


DESCRIPTION OF PROBLEM FIXED FOR APAR SE33300 :
-----------------------------------------------
After adding a non-IASP device to a device cluster resource

group (CRG), the resource name associated with the device can

incorrectly be deleted on the CRG primary. If the device is

switched from the primary to a backup, and then switched back

to the primary, the resource may be assigned a different

resource name which may cause some CRG functions to fail.

CORRECTION FOR APAR SE33300 :
-----------------------------
The add CRG device entry protocol is fixed to reserve the

resource name on the primary node.

CIRCUMVENTION FOR APAR SE33300 :
--------------------------------
None.


DESCRIPTION OF PROBLEM FIXED FOR APAR SE33301 :
-----------------------------------------------
A device cluster resource group (CRG) may fail switchover after
adding a non-IASP device to the CRG before the switchover. The
CRG may incorrectly add the device if the device has a resource
name conflict.

CORRECTION FOR APAR SE33301 :
-----------------------------
Resource name conflict is now properly detected when adding a

non-IASP device to a CRG.

CIRCUMVENTION FOR APAR SE33301 :
--------------------------------
None.


DESCRIPTION OF PROBLEM FIXED FOR APAR SE33302 :
-----------------------------------------------
A CPFBBB1 may occur with a device cluster resource group (CRG)
when starting the CRG primary node, causing the CRG to go
InDoubt.

CORRECTION FOR APAR SE33302 :
-----------------------------
The CPFBBB1 will no longer cause the CRG to go InDoubt. The

CPFBBB1 will be sent as a diagnostic message indicating there

is a possible misconfiguration with the CRG.

CIRCUMVENTION FOR APAR SE33302 :
--------------------------------
None.


DESCRIPTION OF PROBLEM FIXED FOR APAR SE33303 :
-----------------------------------------------
Changing a device cluster resource group (CRG) device entry to
add/change a server takeover IP address fails for the CRG with
Metro/Global mirror configuration.

CORRECTION FOR APAR SE33303 :
-----------------------------
The cluster resource group (CRG) is now using the correct
device type.

CIRCUMVENTION FOR APAR SE33303 :
--------------------------------
None.


DESCRIPTION OF PROBLEM FIXED FOR APAR SE33304 :
-----------------------------------------------
In certain cases, an inactive node is incorrectly been
identified as part of cluster resource group (CRG) recovery
domain.

CORRECTION FOR APAR SE33304 :
-----------------------------
An inactive node is now correctly identified to be or not to be

part of cluster resource group (CRG) recovery domain.

CIRCUMVENTION FOR APAR SE33304 :
--------------------------------
None.


DESCRIPTION OF PROBLEM FIXED FOR APAR SE33305 :
-----------------------------------------------
With an Active device cluster resource group (CRG), the CRG job
fails to start with CPFBB99 RC 34 while trying to start
clustering on mirror site primary node due to missing hardware
on the node.

CORRECTION FOR APAR SE33305 :
-----------------------------
cluster resource group (CRG) job start process changed to allow
the hardware not to be present on the mirror site primary node
regardless of the CRG status.

CIRCUMVENTION FOR APAR SE33305 :
--------------------------------
None.


DESCRIPTION OF PROBLEM FIXED FOR APAR SE33306 :
-----------------------------------------------
Cluster Resource Group (CRG) job may get hung while trying to
backout the changes made during a failed switchover attempt.

CORRECTION FOR APAR SE33306 :
-----------------------------
Switchover process changed to fix the hang issue while backing
out changes made to the cluster resource group (CRG) during a
failed switchover attempt.

CIRCUMVENTION FOR APAR SE33306 :
--------------------------------
None.


DESCRIPTION OF PROBLEM FIXED FOR APAR SE33325 :
-----------------------------------------------
QcstRefreshEventQ API fails with MSGCPFBB4D. MSGMCH3601 found

in QCSTCRGM job.

CORRECTION FOR APAR SE33325 :
-----------------------------
The problem has been fixed in the QcstRefreshEventQ API.

CIRCUMVENTION FOR APAR SE33325 :
--------------------------------
This problem will only occur if auditing is active. To disable

auditing, set the QAUDCTL system value to *NONE.


Activation Instructions


None.




Special Instructions


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.

********************************************************************
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 SI31128 :
=================================================

If clustering is active on the node, end clustering on the node before
applying the PTF using the appropriate cluster interface.

SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI30927 :
=================================================

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.  Under the QSYSWRK
subsystem look for two 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 SI30895 :
=================================================

End clustering on the node using the appropriate interface before
applying this PTF.

SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI30426 :
=================================================

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.

SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI29412 :
=================================================

End the cluster node first using your cluster management interfaces.

SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI29213 :
=================================================

Follow the special instructions below for PTF SI28829.


Default Instructions

THIS PTF CAN BE APPLIED IMMEDIATE OR DELAYED.



Supersedes

PTF/FIX NO(S).  APAR TITLE LINE
--------------  ------------------------------------------------------------
   SI31280      OSP-MSGCPF3C55 CHGCRGPRI fails
   SI31207      OSP-INCORROUT Incorrect CRG status for metro mirror
   SI31175      OSP-MSGCPF9D8D reported for xsm.log
   SI31128      OSP-INCORROUT Multiple site nodes for metro mirror
   SI30928      OSP-MSGCPF9801 Dasd Management Operation Fails
   SI30927      OSP-INCORROUT CHGCRG producing CPFBB80 RC 26
   SI30895      OSP-WAIT STRCLUNOD hangs
   SI30813      OSP-INCORROUT STRASPSSN incorrectly allowed
   SI30798      OSP-INCORROUT QYASSDMO option Reset ASP IO fails
   SI30751      OSP-INCORROUT CHGCRGPRI fails for metro mirror
   SI30729      OSP-MSGCPFBB5B Incorrect resource name in message
   SI30697      OSP-INCORROUT CHGCRG fails with XSM configured
   SI30616      OSP-INCORROUT QYASSDMO option Define ASP IO fails
   SI30426      OSP-INCORROUT Switching failure has hardware on wrong node
   SI30250      OSP INCORROUT - ENDCLUNOD may result in false partition
   SI30250      OSP-INCORROUT Dataport IP addresses incorrectly removed
   SI29264      OSP-INCORROUT Incorrect behavior of device domain data
   SI29742      RCHLTSC1 - Cluster switchover does not complete successfully
   SI29640      OSP-INCORROUT Cluster event messages not always sent
   SI29412      OSP-INCORROUT CPFBB60, RC11 Switchover may fail
   SI29412      OSP INCORROUT - During CHGCRG, site primary node forcibly ta
   SI29143      OSP INCORROUT - Peer CRG hangs during failover if the CRG ob
   SI29213      UNPRED SUSPECT CODE GENERATION DURING PTF BUILD
   SI28829      OSP-INCORROUT RMVCLUNODE loops on a 2 node cluster

Summary Information

System..............................System i
Models..............................
Release.............................V6R1M0
Licensed Program...............5761SS1
APAR Fixed..........................SE33299
SE33300
SE33301
SE33302
SE33303
SE33304
SE33305
SE33306
SE33325
Superseded by:......................View fix details for PTF SI59103
Recompile...........................N
Library.............................QSYS
MRI Feature ........................NONE
Cum Level...........................C8288610


System 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 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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG15V","label":"PTF Cover Letters - OS\/400 General"},"Component":"","ARM Category":[],"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"V6R1M0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG16A","label":"PTF Cover Letters - i5\/OS V6R1 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"V6R1M0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
23 May 2008