PTF Cover Letter
PTF ( Program Temporary Fixes ) Cover letter
HASM-HA-NF COPY SERVICES MANAGER/HYPERSWAP+GLOBAL MIRROR NEW
Pre/Co-Requisite PTF / Fix List
REQ LICENSED PTF/FIX LEVEL
TYPE PROGRAM RELEASE NUMBER MIN/MAX OPTION
---- -------- --------- ------- ------- ------
PRE 5770SS1 V7R2M0 SI69310 00/00 0000
PRE 5770SS1 V7R3M0 SI69297 00/00 0000
PRE 5770SS1 V7R3M0 SI62512 00/00 0000
PRE 5770SS1 V7R3M0 SI60242 00/00 0000
DIST 5770HAS V7R2M0 SE70743 NONE 0000 (SEE MRI PTF/FIX LIST BELOW)
MRI PTF/FIX LIST
----------------
APAR SE70743 AFFECTS THESE LANGUAGES. IF YOU HAVE ANY OF THESE
LANGUAGES INSTALLED, INSTALL THE DISTRIBUTION REQUISITE MRI PTF THAT
CORRESPONDS TO THE LANGUAGE(S) INSTALLED ON YOUR SYSTEM.
-----------------------------------------------------------------
: FEATURE LICENSED PTF/FIX :
: CODE LANGUAGE PROGRAM NUMBER :
: ------- ------------------------------- -------- ------- :
: 2924 ENGLISH UPPER/LOWER CASE SBCS 5770HAS SI69234 :
: 2902 ESTONIAN 5770HAS SI69235 :
: 2903 LITHUANIAN 5770HAS SI69236 :
: 2904 LATVIAN 5770HAS SI69237 :
: 2905 VIETNAMESE 5770HAS SI69238 :
: 2906 LAO 5770HAS SI69239 :
: 2909 BELGIAN ENGLISH 5770HAS SI69240 :
: 2911 SLOVENIAN 5770HAS SI69241 :
: 2912 CROATIAN 5770HAS SI69242 :
: 2913 MACEDONIAN 5770HAS SI69243 :
: 2914 SERBIAN 5770HAS SI69244 :
: 2922 PORTUGUESE 5770HAS SI69245 :
: 2923 DUTCH 5770HAS SI69246 :
: 2925 FINNISH 5770HAS SI69247 :
: 2926 DANISH 5770HAS SI69248 :
: 2928 FRENCH 5770HAS SI69249 :
: 2929 GERMAN 5770HAS SI69250 :
: 2930 JAPAN LOWER CASE 5770HAS SI69251 :
: 2931 SPANISH 5770HAS SI69252 :
: 2932 ITALIAN 5770HAS SI69253 :
: 2933 NORWEGIAN - BOKMAL 5770HAS SI69254 :
: 2937 SWEDISH 5770HAS SI69255 :
: 2938 ENGLISH UPPER CASE DBCS 5770HAS SI69256 :
: 2939 SWISS GERMAN 5770HAS SI69257 :
: 2940 SWISS FRENCH 5770HAS SI69258 :
: 2942 SWISS ITALIAN 5770HAS SI69259 :
: 2954 ARABIC 5770HAS SI69260 :
: 2956 TURKISH 5770HAS SI69261 :
: 2957 GREEK 5770HAS SI69262 :
: 2958 ICELANDIC 5770HAS SI69263 :
: 2961 HEBREW 5770HAS SI69264 :
: 2962 JAPANESE 5770HAS SI69265 :
: 2963 BELGIUM DUTCH 5770HAS SI69266 :
: 2966 BELGIUM FRENCH 5770HAS SI69267 :
: 2972 THAI 5770HAS SI69268 :
: 2974 BULGARIAN 5770HAS SI69269 :
: 2975 CZECH 5770HAS SI69270 :
: 2976 HUNGARIAN 5770HAS SI69271 :
: 2978 POLISH LANGUAGE 5770HAS SI69272 :
: 2979 RUSSIAN 5770HAS SI69273 :
: 2980 BRAZILIAN PORTUGUESE 5770HAS SI69274 :
: 2981 CANADIAN FRENCH 5770HAS SI69275 :
: 2984 ENGLISH UPPER/LOWER CASE DBCS 5770HAS SI69276 :
: 2986 KOREAN 5770HAS SI69277 :
: 2987 TRADITIONAL CHINESE 5770HAS SI69278 :
: 2989 SIMPLIFIED CHINESE 5770HAS SI69279 :
: 2992 ROMANIAN 5770HAS SI69280 :
: 2994 SLOVAKIAN 5770HAS SI69281 :
: 2995 ALBANIAN 5770HAS SI69282 :
: 2996 PORTUGUESE MNCS 5770HAS SI69283 :
: 2998 FARSI 5770HAS SI69284 :
-----------------------------------------------------------------
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
-------------------------------------------------
New Features:
1. Integration of PowerHA IASP-based replication with IBM Copy
Services Manager for DS8000 Metro Mirror and DS8000 Global
Mirror replication solutions.
2. PowerHA has been enhanced to enable DS8000 HyperSwap
configuration in conjunction with Global Mirror for regional
outage protection.
3. The RPG Header files located in QHASM/QRPGLESRC for PowerHA
APIs have been enhanced to use free-form RPG for easier
usability and readability.
Other Fixes:
1. When one or more storage devices are down or inaccessible,
HyperSwap status screens and APIs now properly show the
HyperSwap status as unknown, instead of reporting a potentially
incorrect cached status.
2. PowerHA has been updated so that it no longer leaves QHASM in
the product portion of the library list after the execution of
commands.
3. The number of HAC0026 and CPCBB01 joblog messages that
contain a reason code of success, on many PowerHA commands has
been reduced for enhanced usability.
Compatibility:
1. The CHGHYSSTS command default parameter for ASP device has
been changed from *ALL to *SYSBAS. The *ALL option for the ASP
device parameter is no longer available.
2. The ADDHACFGD and CHGHACFGD command parameter HYSSTGTYPE has
been renamed to SUBTYPE.
Any existing CL programs that use these commands might have to
be be modified.
CORRECTION FOR APAR 'SE70742' :
-------------------------------
PowerHA SystemMirror for i has been enhanced with new
functionality and corrected to fix the problems.
CIRCUMVENTION FOR APAR 'SE70742' :
----------------------------------
None.
Activation Instructions
None.
Special Instructions
On each node in the cluster, end clustering, apply the fix, and then
restart clustering. It is not necessary to update all nodes at the same
time, however, any node without the fix may continue to be a potential
source of the problem.
After applying the PTF on all nodes in the cluster that have PowerHA
installed, you must upgrade the PowerHA version to 3.2 to enable the
new functionality. Removal of the PTF after upgrading the PowerHA
version to 3.2 is not supported.
If your cluster is currently at PowerHA version 1.0, you must do the
following to increase your PowerHA version to version 2.0:
CHGCLUVER CLUSTER(<cluster-name>) HAVER(*UP1VER)
CLUVER(*SAME)
If your cluster is at PowerHA version 2.0, you must do the following to
increase your PowerHA version to 3.0:
CHGCLUVER CLUSTER(<cluster-name>) HAVER(*UP1VER)
CLUVER(*SAME)
If your cluster is at PowerHA version 3.0, you must do the following to
increase your PowerHA version to 3.1:
CHGCLUVER CLUSTER(<cluster-name>) HAVER(*UP1MOD)
CLUVER(*SAME)
If your cluster is at PowerHA version 3.1, you must do the following to
increase your PowerHA version to 3.2:
CHGCLUVER CLUSTER(<cluster-name>) HAVER(*UP1MOD)
CLUVER(*SAME)
********************************************************************
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.
********************************************************************
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.
In order to fix the problems described by this PTF, 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.
The *ADMIN HTTP server must be restarted to activate this fix if it is
applied immediate.
To do so, run: ENDTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)
Once the server has ended, run STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN).
The fix will now be activated.
Before applying this PTF, the PTF SI46592 for product
5770SS1 must be applied.
Before applying or removing this PTF you must run:
ENDTCPSVR SERVER(*IAS) INSTANCE(ADMIN2)
After applying or removing this PTF you must run:
STRTCPSVR SERVER(*IAS) INSTANCE(ADMIN2)
Before applying or removing this PTF you must run:
ENDTCPSVR SERVER(*IAS) INSTANCE(ADMIN2)
After applying or removing this PTF you must run:
STRTCPSVR SERVER(*IAS) INSTANCE(ADMIN2)
In order for this fix to be fully activated, you must restart the
ADMIN2 instance of the HTTP server. You can do this with the following
commands:
ENDTCPSVR SERVER(*IAS) INSTANCE(ADMIN2)
STRTCPSVR SERVER(*IAS) INSTANCE(ADMIN2)
You must restart the HTTP server after this PTF is applied:
ENDTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)
STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)
This fix is not activated until you restart the HTTP server ADMIN
instance. This is done by the following two commands:
ENDTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)
Once all of the HTTP server ADMIN instance jobs have ended, do the
following command to activate this fix.
STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)
When the HTTP server ADMIN instance has completely started, this fix
will be active.
The helptext for RTVASPSSN has an incorrect structure for the ASPCPY
parameter. The Number of ASP Copy Descriptions and the Length of each
ASP copy description entry fields have been reversed. The helptext
will be updated in a future release to show the correct layout.
The current help text indicates the field layout is:
Position Length Field
1 4 byte integer Offset from beginning of
ASPCPY to the first ASP copy
description entry
5 4 byte integer Number of ASP copy
description entries
9 4 byte integer Length of an ASP copy
description entry
The correct field layout is:
Position Length Field
1 4-byte integer number Offset from beginning of
ASPCPYLST
to first ASP copy
description list entry
5 4-byte integer number Length of each ASP copy
description list entry
9 4-byte integer number Number of ASP copy
description entries
This PTF is an Add Function PTF which must be permanently applied.
Removal of this PTF after step #4 below is not supported.
You must have the most recent level of PTF group SF99368.
Step #1:
In order for this PTF to be fully activated, you must end and restart
the QHASVR job. You can do this by ending and starting the cluster
node using the commands:
ENDCLUNOD CLUSTER(<cluster-name>) NODE(<node-id>)
STRCLUNOD CLUSTER(<cluster-name>) NODE(<node-id>)
Or, you can end the QHASVR job under QSYSWRK subsystem:
ENDJOB JOB(<job-num>/QHAUSRPRF/QHASVR) OPTION(*IMMED)
where <job-num> is the job number.
Issue the WRKCLU command to restart the QHASVR job.
Step #2:
You must restart the *ADMIN instance of the *HTTP server. Do this
with the following commands:
ENDTCPSVR SERVER(*HTTP) INSTANCE(*ADMIN)
STRTCPSVR SERVER(*HTTP) INSTANCE(*ADMIN)
Step #3:
Users must sign off any active sessions which may be using,
PowerHA and sign back on after the PTF has been applied.
Step #4:
After the PTF has been applied on all of the nodes in the
cluster which have PowerHA installed, you must upgrade
the PowerHA version to 2.2.
If your cluster is currently at PowerHA version 1.0,
you must:
CHGCLUVER CLUSTER(<cluster-name>) HAVER(*UP1VER)
CLUVER(*SAME)
After your cluster is at PowerHA version 2.0, you must:
CHGCLUVER CLUSTER(<cluster-name>) HAVER(*UP1MOD)
CLUVER(*SAME)
After your cluster is at PowerHA version 2.1, you must:
CHGCLUVER CLUSTER(<cluster-name>) HAVER(*UP1MOD)
CLUVER(*SAME)
In order for the issue to be resolved completely, this fix needs to be
on all the active cluster nodes participating in the cluster
administrative domain. Failure to do so would cause PRTDEV MREs with
IGCFEAT as one of the monitored attributes to go INCONSISTENT in
certain circumstances.
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)
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 must 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)
If you are a multiple system user, and intend on installing this PTF on
a system, then saving and restoring product 5770HAS onto other systems,
then you need to run the following command on the other systems after
restoring product 5770HAS:
QSYS/CALL PGM(QHASM/QPZ1HA03)
In order for this PTF to be fully activated, you must end and restart
the QHASVR job. You can do this by ending and starting the cluster
node using the commands:
ENDCLUNOD CLUSTER(<cluster-name>) NODE(<node-id>)
STRCLUNOD CLUSTER(<cluster-name>) NODE(<node-id>)
Or, you can end the QHASVR job under QSYSWRK subsystem:
ENDJOB JOB(<job-num>/QHAUSRPRF/QHASVR) OPTION(*IMMED)
where <job-num> is the job number.
Issue the WRKCLU command to restart the QHASVR job.
Step 1:
In order for this PTF to be fully activated, you must end and restart
the QHASVR job. You can do this by ending and starting the cluster
node using the commands:
ENDCLUNOD CLUSTER(<cluster-name>) NODE(<node-id>)
STRCLUNOD CLUSTER(<cluster-name>) NODE(<node-id>)
Or, you can end the QHASVR job under QSYSWRK subsystem:
ENDJOB JOB(<job-num>/QHAUSRPRF/QHASVR) OPTION(*IMMED)
where <job-num> is the job number.
Issue the WRKCLU command to restart the QHASVR job.
Step 2:
You must restart the ADMIN2 instance of the *HTTP server. Do this
with the following commands:
ENDTCPSVR SERVER(*IAS) INSTANCE(ADMIN2)
STRTCPSVR SERVER(*IAS) INSTANCE(ADMIN2)
Step 3:
Users must sign off any active sessions which may be using
PowerHA and sign back on after the PTF has been applied.
This PTF is an Add Function PTF which must be permanently applied.
Removal of this PTF after step #4 below is not supported.
You must have the most recent PTF group SF99368.
You must install PRPQ 5799-HAS in order to use the functions
provided in this PTF.
Step #1:
In order for this PTF to be fully activated, you must end and restart
the QHASVR job. You can do this by ending and starting the cluster
node using the commands:
ENDCLUNOD CLUSTER(<cluster-name>) NODE(<node-id>)
STRCLUNOD CLUSTER(<cluster-name>) NODE(<node-id>)
Or, you can end the QHASVR job under QSYSWRK subsystem:
ENDJOB JOB(<job-num>/QHAUSRPRF/QHASVR) OPTION(*IMMED)
where <job-num> is the job number.
Issue the WRKCLU command to restart the QHASVR job.
Step #2:
You must restart the *ADMIN instance of the *HTTP server. Do this
with the following commands:
ENDTCPSVR SERVER(*HTTPSVR) INSTANCE(*ADMIN)
STRTCPSVR SERVER(*HTTPSVR) INSTANCE(*ADMIN)
Step #3:
Users must sign off any active sessions which may be using,
PowerHA and sign back on after the PTF has been applied.
Step #4:
After the PTF has been applied on all of the nodes in the
cluster which have PowerHA installed, you must upgrade
the PowerHA version to 2.1.
If your cluster is currently at PowerHA version 1.0,
you must:
CHGCLUVER CLUSTER(<cluster-name>) HAVER(*UP1VER)
CLUVER(*SAME)
After your cluster is at PowerHA version 2.0, you must:
CHGCLUVER CLUSTER(<cluster-name>) HAVER(*UP1MOD)
CLUVER(*SAME)
End Cluster Resource Services on the node using the ENDCLUNOD command,
apply the PTF, signoff/signon, and then restart Cluster Resource
Services using the STRCLUNOD command.
In order for this PTF to be fully activated, you must restart
the ADMIN2 instance of the *HTTP server. Do this with the
following commands:
ENDTCPSVR SERVER(*IAS) INSTANCE(ADMIN2)
STRTCPSVR SERVER(*IAS) INSTANCE(ADMIN2)
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)
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.
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.
Step #1:
In order for this PTF to be fully activated, you must end and restart
the QHASVR job. You can do this by ending and starting the cluster
node using the commands:
ENDCLUNOD CLUSTER(<cluster-name>) NODE(<node-id>)
STRCLUNOD CLUSTER(<cluster-name>) NODE(<node-id>)
Or, you can end the QHASVR job under QSYSWRK subsystem:
ENDJOB JOB(<job-num>/QHAUSRPRF/QHASVR) OPTION(*IMMED)
where <job-num> is the job number.
Issue the WRKCLU command to restart the QHASVR job.
Step #2:
In order for this PTF to be fully activated, you must restart
the ADMIN2 instance of the *HTTP server. Do this with the
following commands:
ENDTCPSVR SERVER(*IAS) INSTANCE(ADMIN2)
STRTCPSVR SERVER(*IAS) INSTANCE(ADMIN2)
Step #3:
Users must sign off any active sessions which may be using,
PowerHA and sign back on after the PTF has been applied.
Step #1:
In order for this PTF to be fully activated, you must end the cluster
and HTTP server. You can do this by ending the cluster node and server
using the commands:
node using the commands:
ENDCLUNOD CLUSTER(<cluster-name>) NODE(<node-id>)
ENDSBS SBS(QHTTPSVR) OPTION(*IMMED)
Step #2:
Users must sign off any active sessions which may be using,
PowerHA and sign back on after the PTF has been applied.
Step #3:
Start the server and cluster using the commands:
STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)
STRCLUNOD CLUSTER(<cluster-name>) NODE(<node-id>)
Default Instructions
THIS PTF CAN BE APPLIED IMMEDIATE OR DELAYED.
Supersedes
PTF/FIX NO(S). APAR TITLE LINE
-------------- ------------------------------------------------------------
SI68212 HASM-HA-MSGHAI2002 HAI2002 LOGGED IN QSYSOPR
SI67828 HASM-HA-MSGHAI000C MSGHAI000C POSTED TO QSYSOPR BY JOB QHASV
SI67828 HASM-HA-MSGCPF2277 MESSAGE MCH1001 OR CPF2277 COULD BE SEEN
SI67129 HASM-HA-INCORROUT POWERHA GUI DISPLAYS A RED X ON *RESTSVR C
SI67129 HASM-HA-INCORROUT MISCELLANEOUS FIXES TO IBM i PowerHA
SI66976 HASM-HA-MSGCPI9E77 MSGCPI9E77 BEING LOGGED IN QSYSOPR MSGQ F
SI66502 HASM-HA-INCORROUT EXCESSIVE SPOOLFILES BEING GENERATED BY US
SI66502 HASM-HA-INCORROUT Miscellaneous fixes to IBM i Power HA
SI65314 HASM-HA-INCORROUT: ASP COPY DESCRIPTION CMDS MAY RECEIVE INT
SI65314 Miscellaneous fixes to IBM i Power HA
SI64991 MFG: install of HAS PTF SI64529 fails due to CCSID issue in
SI64990 INCORROUT Improve retrieving IASP information
SI64713 HASM-HA-MSGMCH1001 RTVSVCSSN MSGMCH1001
SI64603 OSP MSGHAE2032 PowerHA plug-in not installed
SI64603 HASM-HA-MSGHAE9898 ENDSVCSSN RECEIVES MSGHAE9898, XSM.LOG SH
SI64529 HASM-HA-UNPRED RTVSVCCPYD ISSUE
SI64529 MFG: install of HAS PTF's in C7061730 CUM fails with Japanes
SI64166 OSP-PAR-940XMISC WRKCLU OPTION 9, 6, THEN 5 RESULTS IN A MSG
SI64166 INCORROUT PowerHA not registering SVC exit point programs pr
SI64166 HASM-HA-UNPRED STRASPSSN *FLASHCOPY FAILS DUE TO NUMBER OF V
SI64166 HASM-HA-MSGHAE2015 STRASPSSN *MMIR FAILS HAE2015 RC2
SI61908 PowerHA cluster monitor based on HMC REST APIs
SI61908 HASM-HA-INCORROUT DSPSVCSSN SHOWS THE STORAGE STATE AS UNKNO
SI61908 HASM-HA-UNPRED POWERHA SHOULD HAVE PREVENTED RESUME OF DETAC
SI61908 HA-INCORROUT HyperSwap Command Error Message
SI62490 HASM-HA-INCORROUT POWERHA GUI MISSING IN IBM NAVIGATOR FOR I
SI62180 HASM-HA-F/QHACMN-T/QHAWRKCPP-RC5-MSGHAE0047 WRKCLU FAILS WIT
SI62155 HASM-HA-MSGMCH3601 CHGCRGPRI ENCOUNTERS MSGMCH3601.
SI61243 HASM-HA-MSGHAE2057 STRSVCSSN *FLASHCOPY V7000 FAILS HAE2057
SI60530 INCORROUT PowerHA fixes
SI60530 In a DS8000 PowerHA MetroMirror environment, a resume of the
SI60530 HASM-INCORROUT Fix Device Domain Data
SI60530 HASM-INCORROUT Fix Device Domain Data Session Serviceability
SI60530 OSP-OTHER-MSGHAE2040 CHGCRGPRI GMIR SVC FAILS MSGHAE2040
SI57509 HAS-NEW HYPERSWAP FUNCTION MRM
SI57509 Hyperswap LUN Switch Fixes
SI57509 HASM-HA-UNPRED CHGCRGPRI IS NOT DROPPING AND ADDING ALL HOST
SI57509 HASM-HA-MSGCPI096E EVERY TIME THEY IPL THE TARGET FLASH COPY
SI59974 i SW FST: DSPASPSSN Results in a CPF6A39 Message (Variable b
SI57636 HyperSwap Stage 2
SI57636 HASM-HA-UNPRED PREVENT QHAUSRPRF FROM LOSING AUTHORITY TO /Q
SI57636 OSP AFTER UPGRADE TO R720 ON FLASH TARGET - STRFLASH FAILS -
SI55011 HA-INCORROUT RTVASPSSN Value does not match DSPASPSSN value
SI58036 HASM-HA-WAIT LARGE SVC ENVIRONMENT RESULTS IN INELIGIBLE TAR
SI58000 HASM-HA-LOOP DSPASPSSN HANG WHEN A NODE IS IN PARTITION STAT
SI58000 HASM-HA-F/QCARULE-T/QC2SYS-MSGCPD0030 WRKASPCPYD WITH OPTION
SI57958 HA-Adding Support for FlashCopy option -multiinc
SI57302 HASM-HA-UNPRED AUTHORIZATION LIST ENTRIES ARE CHANGED TO *EX
SI57177 OSP-INCORROUT Correct minor PowerHA license problems
SI56917 PowerHA GUI - Support of Liberty infrastructure
SI55982 Fixed a problem on PowerHA GUI that extra messages will pop
SI55603 HASM-INCORROUT MCH3601 RECEIVED ON STRASPSSN AT HA VER 2.2
SI55303 INCORROUT GUI problems - Multiple GUI fixes for PowerHA GUI
SI54321 HASM-INCORROUT INCONSISTENT DEVICE DOMAIN DATA
SI54321 HASM-HA-F/QHACMN-T/QYASPSSN-MSGCPF22E6/MSGCPF22E7 ENCOUNTERE
SI53938 HASM-HA-UNPRED straspssn command parameters not working
SI53938 HASM-HA-LOOP RUNNING ENDSVCSSN RESULTS IN LOOPING CONDITION
SI53638 HASM-WAIT ENDSVCSSN hangs when SVC volume status is degraded
SI53631 HASM-INCORROUT REATTACH of ASP Session inquiry instead of co
SI53608 HASM-HA MULTIPLE LUNS IN 1 VOLUME GROUP AT POWERHA VERSION 1
SI53608 HASM-HA CPFAF02 INTERNAL APPLICATION ERROR. DIAGNOSTIC CODE
SI53480 HASM-HA-INCORROUT CHGCRGPRI GLOBAL MIRROR POWERHA
SI53476 New function to support SVC and Storwize Global Mirror with
SI53476 MSGCPIB711-HLIC-94XXDISK IN MULTIPATH ENVIRONMENT, ENDSVCSSN
SI53003 INCORROUT No target flash copy not allowed when source node
SI52665 INCORROUT - Fixes of the bugs found in PowerHA in 7.2 releas
SI51113 PowerHA 7.2 TVT
SI51913 OSP-INCORROUT PowerHA pre-GA fixes
SI51913 HA-INCORROUT Node Fails to Join Recovery Group when Cluster
Summary Information
System.............................. i
Models..............................
Release............................. V7R2M0
Licensed Program.................... 5770HAS
APAR Fixed.......................... View details for APAR SE70742
Superseded by:...................... View fix details for PTF SI80112
Recompile........................... N
Library............................. QHASM
MRI Feature ........................ NONE
Cum Level........................... NONE
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:
18 June 2022