IBM Support

SI29033 - OSP-INCORROUT Add MRE fails in mixed release admin domain

PTF Cover Letter


PTF ( Program Temporary Fixes ) Cover letter


Order this fix

Abstract

OSP-INCORROUT Add MRE fails in mixed release admin domain


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

-------------------------------------------------
Adding a monitored resource entry (MRE) to a cluster
administrative domain in a cluster at cluster version 5 may
fail. If there is at least on cluster node in the
administrative domain at release V5R4, and the MRE is being
added on a V6R1 node, and the resource type is *USRPRF with the
HOMEDIR, LOCALE or TEXT attribute specified, or the resource
type is *ASPDEV, *JOBD, or *CLS with the TEXT attribute
specified, the add mre operation will fail.

CORRECTION FOR APAR 'SE30280' :
-------------------------------
Adding a monitored resource entry to a cluster administrative
domain in a version 5 cluster will be succesful.

CIRCUMVENTION FOR APAR 'SE30280' :
----------------------------------
Adding a *USRPRF, *JOBD, *CLS, or *ASPDEV MRE in a cluster
administrative domain at cluster version 5 will succeed if the
add mre operation is done from a V5R4 cluster node, in a mixed
release cluster. Alternatively, the add mre operation can be
done successfully from a V6R1 node if the HOMEDIR, LOCALE or
TEXT attributes are not specified for a *USRPRF, or the TEXT
attribute is not specified for a *JOBD, *CLS or *ASPDEV mre.

DESCRIPTION OF PROBLEM FIXED FOR APAR 'SE30682' :
-------------------------------------------------
Adding a monitored resource entry (MRE) for a *USRPRF without
the PASSWORD attribute fails when QRETSVRSEC is set to 0 and
the user profile exists on all nodes in the cluster
administrative domain

CORRECTION FOR APAR 'SE30682' :
-------------------------------
This fix will allow customers to add monitored resource entries

for *USRPRF resources to a cluster administrative domain when

the QRETSVRSEC system value is set to 0, as long as the

PASSWORD attribute is not specified as an attribute to be

monitored. The *USRPRF must exist on all nodes in the cluster

administrative domain for the operation to succeed.

CIRCUMVENTION FOR APAR 'SE30682' :
----------------------------------
None.


Activation Instructions


None.




Special Instructions

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)


Default Instructions

THIS PTF CAN BE APPLIED IMMEDIATE OR DELAYED.



Supersedes

PTF/FIX NO(S).  APAR TITLE LINE
--------------  ------------------------------------------------------------
     NONE

Summary Information

System..............................System i
Models..............................
Release.............................V6R1M0
Licensed Program...............5761SS1
APAR Fixed..........................SE30280
SE30682
Superseded by:......................View fix details for PTF SI56943
Recompile...........................N
Library.............................QSYS
MRI Feature ........................NONE
Cum Level...........................C7355610


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:
18 February 2008