IBM Support

SI66971 - OSP-OTHER-WAIT STRCAD MAY HANG DUE TO AN INTERNAL LOCK CONDI

PTF Cover Letter


PTF ( Program Temporary Fixes ) Cover letter


Order this fix

Abstract

OSP-OTHER-WAIT STRCAD MAY HANG DUE TO AN INTERNAL LOCK CONDI


Pre/Co-Requisite PTF / Fix List

REQ  LICENSED      PTF/FIX  LEVEL

TYPE PROGRAM  REL  NUMBER   MIN/MAX  OPTION
---- -------- ---  -------  -------  ------
PRE  5770999  710  MF99006   00/00    0000
PRE  5770999  710  MF52057   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

-----------------------------------------------
When performing STRCAD a hang may occur due to an internal lock
condition.

Due to damage on internal QFPATMAP index, it can cause an issue
where locks are not being released properly and allowing proper
handling of the index by admin domain.

Code is being enhanced to handle appropriately and prevent.

Work Around: With Cluster Active on all nodes in the cluster and
all related jobs, admin domain can be in an Inactive status. The
node where the damaged index resides can be removed from the
admin domain, then admin domain can be started to ensure all
other nodes get updated and show consistent MREs. The problem
node can then be added back into the admin domain.

CORRECTION FOR APAR SE68852 :
-----------------------------
The index lock is now removed if any exception is signaled.

CIRCUMVENTION FOR APAR SE68852 :
--------------------------------
None.


Activation Instructions


None.




Special Instructions


There are two special instructions.

1. 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, until all nodes have the fix the problem may still
occur.

2. After the PTF has been applied and the cluster node ended, restart
the QPRFSYNCH job on the node with the following commands:

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

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

There are two special instructions.

1. 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, until all nodes have the fix the updated code will not
be used.

2. After the PTF has been applied and the cluster node ended, restart
the QPRFSYNCH job on the node with the following commands:

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

SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI66576 :
=================================================

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.

SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI66198 :
=================================================

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
problem.

SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI64138 :
=================================================

To activate these fixes, 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.

If you have had the reported problem with WRKCADMRE or displaying Admin
Domain Monitored Resource Entries (MREs) with WRKCLU, or are unsure
that you have the problem, then it is recommended that you activate the
fixes by:
1.  End clustering on each node in the cluster.
2.  Apply this fix if not already applied.
3.  Run "CALL PGM(QSYS/QCSTADFIX)" on each node.
4.  Start clustering on each cluster node.

SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI62513 :
=================================================

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.

To make use of the Representational State Transfer (REST) support for
the cluster monitor, the Extended Base Directory Support (Option 3 of
the IBM i operating system) must be installed any nodes where a REST
cluster monitor is declared.  The REST cluster monitor support also
requires the following PTFs to be applied: SI59019 and SI62170.
If REST cluster monitor support is not required the above requirements
can be ignored.

SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI60754 :
=================================================

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 SI60027 :
=================================================

This PTF must be applied on all nodes in the cluster. On each node,
end clustering (or end just the cluster administrative domain CRG job),
end QPRFSYNCH job, apply the PTF, start QPRFSYNCH job, and then start
clustering (or the cluster administrative domain CRG job).

To end and start clustering:
ENDCLUNOD CLUSTER(<cluster-name>) NODE(<node-id>)
STRCLUNOD CLUSTER(<cluster-name>) NODE(<node-id>)

To end and start the cluster administrative domain CRG job:
CHGCLURCY CLUSTER(<cluster-name>) CRG(<admin_domain>) NODE(<node-id>)
ACTION(*END)
CHGCLURCY CLUSTER(<cluster-name>) CRG(<admin_domain>) NODE(<node-id>)
ACTION(*STRCRGJOB)

To end and start the QPRFSYNCH job:
CALL PGM(QSYS/QFPAPRFJ) PARM(END)
CALL PGM(QSYS/QFPAPRFJ) PARM(START)

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.


Default Instructions

THIS PTF CAN BE APPLIED IMMEDIATE OR DELAYED.



Supersedes

PTF/FIX NO(S).  APAR TITLE LINE
--------------  ------------------------------------------------------------
   SI66964      OSP-INCORROUT Admin domain losing MRE attribute values
   SI66576      OSP-OTHER-UNPRED USER PROFILE LOSES JOB ATTRIBUTE IF MORE TH
   SI66276      INCORROUT Cluster administrative domain may hang on STRCLUNO
   SI66221      OSP-OTHER-MSGCPFBB22 PARAMETERS PASSED DURING CHGCLUMON THAT
   SI66198      OSP-OTHER-F/QYASCHGDDD-RC2-MSGCPFB71B CALL PGM(QYASCHGDDD) R
   SI65823      OSP-OTHER-F/QHACMN-MSGCPDAA01 ADD OF A *USRPRF MRE IN ADMIN
   SI65823      HASM-HA-UNPRED STRCLUNOD HANG
   SI65646      OSP-OTHER-SRCD90027C0-WAIT SYSTEM HANG DURING IPL DUE TO CLU
   SI65153      INCORROUT Add HMC REST version to logging
   SI65016      INCORROUT QIBM_QCST_STRCLUNOD not unregistered when no regis
   SI64877      HASM-HA-MSGCPI93B2 5770 SP/QCSTADSIMP MOD/CSTADJOINS RC56 IN
   SI64290      OSP-OTHER-INCORROUT: Axis.log debug file is not generated
   SI64138      INCORROUT MSGCPF3C74 in WRKCADMRE
   SI64097      HASM-HA-F/RMSLLOCKCHECK-T/QYASPDDDTA-MSGMCH2601 RETRIEVING D
   SI63879      OSP-OTHER-MSGCPFBBCB ADDCLUMON TYPE(*RESTSVR) CPFBBCB RC7.IN
   SI62513      XPF-NF: Cluster monitor based on HMC REST APIs
   SI60761      HASM-HA-INCORROUT CRG RECOVERY DOMAIN NOT CHANGING GMIR TARG
   SI60761      INCORROUT Cluster fixes
   SI60754      HASM-HA-MSGMCH3402 MSGMCH3402 ENCOUNTERED WHEN QCSTINETD TRI
   SI60027      INCORROUT - Enhance Admin Domain Logging
   SI58529      OSP-MSGTCP2901-PAR-940XBASE STRCLUNOD WITH CCSID 5026 FAILS
   SI58209      HASM-HA-WAIT CHANGING OR DISPLAYING DEVICE DOMAIN DATA WHILE
   SI58164      OSP-OTHER-UNPRED GMIR AFTER FAILOVER SECOND IASP IN THE SAME
   SI57526      OSP-INCORROUT QYASRTVDDD Option 2 blocked after QYASCHGDDD w
   SI57145      OSP-INCORROUT RMVCRGNODE followed by ADDCRGNODE may fail
   SI57145      OSP-INCORROUT Admin domain may hang after ADDCADNODE complet
   SI57145      HASM-INCORROUT RMVCRGNODE Partially Completed then Hung in G
   SI56594      HASM-HA-F/QCSTADSIMP-T/QCSTADSIMP-MSGMCH0601 MSGMCH0601 DURI
   SI56080      HASM-HA-WAIT CRG STATUS MISMATCH AMONGST NODES IN CLUSTER DU
   SI56080      OSP-INCORROUT Fixes for reduced cluster messages
   SI56080      HASM-HASME CHGCLUNODE POWERHA GMIR
   SI55764      HASM-HA-F/#CFOCHKR-T/QCSTCMN-MSGMCH2601 MSGMCH2601 ENCOUNTER
   SI54303      OSP-OTHER-PERFM Improve reliability and performance of large
   SI48772      OSP-UNPRED ENHANCEMENT TO CHGCLURCY COMMAND
   SI53886      HASM-INCORROUT - QYASRTVDDD option 2 allows other nodes to c
   SI45198      OSP-MSGCPFBB70 Incorrect reason code sent by QYASRTVDDD
   SI44568      OSP-INCORROUT Error code parameter not used for APIs
   SI38580      OSP-INCORROUT QYASRTVDDD Fails
   SI51569      HASM-HA-MSGCPD000D MSGCPD000D AND MSGCPF3698 EVERY HOUR IN C
   SI51234      HASM-UNPRED ENHANCEMENT TO CLUSTER MESSAGE HANDLING.
   SI50858      OSP-INCORROUT *AUTL MRE RECEIVING MSGCPDAA02 AND MSGCPFAA0B
   SI50400      HASM-INCORROUT ENHANCEMENT TO CLUSTER MESSAGE HANDLING.
   SI49737      HASM-WAIT HUNG CRG OBJECT DOESN'T INFORM QCSTCRGM TO CONTINU
   SI49598      OSP-OTHER-UNPRED ADMIN DOMAIN FAILS TO CREATE MUTEX
   SI49530      OSP-OTHER-MSGCPDBB11 Admin domain fails to start MSGCPDBB11
   SI49425      OSP-INCORROUT: Cluster Resource Group object is locked when
   SI49260      OSP-NF: Allow add / remove MREs when not all Admin Domain no
   SI48938      OSP-OTHER-INCORROUT ADMIN DOMAIN MRE HAS INCORRECT STATUS
   SI48301      OSP-OTHER-INCORROUT NO ERROR MSG IN ADMIN DOMAIN JOB LOG
   SI46616      OSP-OTHER-INCORROUT ADMIN DOMAIN MRE HAS INCORRECT STATUS
   SI45092      OSP-OTHER-MSGMCH0601 MSGMCH0601 IN ADMIN DOMAIN JOBLOG WHEN
   SI43999      OSP-OTHER-F/IXMACHINEINDEXEXTEND-T/QMRSP1-MSGMCH2804 MSGMCH2
   SI43999      OSP-INCORROUT MSGCPD1421 ADMINISTRATIVE DOMAIN CANNOT SYNCH
   SI38884      MSGMCH3601 for PRTCADMRE using *usrprf for RSCTYPE(*USRPRF)
   SI43692      OSP-OTHER-MSGCPF2499 INTERNAL ERROR CODE PARAMETER NOT SET I
   SI43470      OSP-OTHER-LOOP ADMINISTRATIVE DOMAIN JOB LOOPS DUE TO HAVING
   SI43227      OSP Cluster Admin Domain Changes.
   SI39263      OSP Cluster Admin Domain Changes.
   SI36958      OSP-INCORROUT MSGMCH0601 from ADDCADMRE
   SI48950      OSP-OTHER-UNPRED ENHANCEMENT TO CLUSTER MESSAGE HANDLING.
   SI48302      OSP-MSGMCH6801 Admin Domain job log contains C2M1212 msg
   SI47176      OSP-OTHER-RC23-MSGCPFBB80 STRCRG MSGCPFBB80 RC23
   SI46608      HASM-UNPRED AUTHORITY FAILURE (AF) FOR CLUSTER INFORMATION O
   SI45802      MSGCPF9898 CHGCRG may fail when using CHGCRG and SVC
   SI45802      OSP-MSGCPFBB80 Message sometimes incorrectly sent with CHGCR
   SI45802      HASM-UNPRED Allow sharing of cluster resource group dataport
   SI45802      OSP-INCORROUT XSM health check fails and causes failover due
   SI45488      OSP-MSGCPFBB46 Start cluster node operation fails with MSGCP
   SI45083      OSP-MSGCPFBB26 Sent after changing cluster version
   SI43997      OSP-INCORROUT CHGCRG can not switch both site primaries in a
   SI43997      OSP-MSGCPFBB26-PAR-940XBASE MSGCPFBB26 CLUSTER RESOURCE SERV
   SI43997      MSGCPFBB17 CHGCRG can not switch to backup because cluster i
   SI43997      INCORROUT Cluster not handling LPAR partition migration corr
   SI43997      MSGMCH3802 issued during start admin domain
   SI40059      OSP-OTHER-RC2-MSGCPFBB98
   SI39933      OSP-OTHER-INCORROUT CLUSTER HANG CONDITION PREVENTING INACTI
   SI39451      OSP-INCORROUT Add disk unit to ASP fails
   SI42297      OSP-OTHER New Function Cluster N-3 Version Support
   SI41516      OSP-INCORROUT Cluster trace information wraps quickly
   SI40857      OSP-MSGCPFBB05 Start cluster node process fails with CPFBB05
   SI40857      OSP-INCORROUT DMPCLUTRC does not print the cluster group nam
   SI37375      OSP-MSGCPFBBD3 ADDCRGNODE fails when adding a switchable LUN
   SI37375      OSP-MSGCPFBBD6 Error when adding a mirror site to a LUN swit
   SI36799      OSP-OTHER-LOOP Global Mirror CRG hang after system 7.1 upgra
   SI36436      OSP-OTHER-INCORROUT  Fixes for Cluster Resource Services
   SI42199      OSP Don't allow logical partition suspension when clustering
   SI39194      OSP-OTHER-INCORROUT the id of the sending cluster node needs

Summary Information

System..............................i
Models..............................
Release.............................V7R1M0
Licensed Program...............5770SS1
APAR Fixed..........................View details for APAR SE68852
Superseded by:......................
Recompile...........................N
Library.............................QSYS
MRI Feature ........................NONE
Cum Level...........................NONE


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 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":"V7R1M0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG16D","label":"PTF Cover Letters - IBM i 7.1 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"V7R1M0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
26 March 2018