PTF Cover Letter
PTF ( Program Temporary Fixes ) Cover letter
Potential security issue
Pre/Co-Requisite PTF / Fix List
REQ LICENSED PTF/FIX LEVEL
TYPE PROGRAM RELEASE NUMBER MIN/MAX OPTION
---- -------- --------- ------- ------- ------
PRE 5770999 V7R2M0 MF99109 00/00 0000
PRE 5770999 V7R2M0 MF64859 00/00 0000
DIST 5770SS1 V7R2M0 SI68285 NONE 0003
DIST 5770SS1 V7R2M0 SI68282 NONE 0003
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
-----------------------------------------------
A potential security problem.
CORRECTION FOR APAR SE69732 :
-----------------------------
The potential security problem has been addressed.
CIRCUMVENTION FOR APAR SE69732 :
--------------------------------
None.
Activation Instructions
None.
Special Instructions
********************************************************************
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 SI69958 :
=================================================
This PTF contains Service Programs that are activated into the System
Default Activation Group. A new job must be started to pick up the new
functionality.
SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI69310 :
=================================================
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, any node without the fix will continue to be a potential
source of the problem.
2. It is recommended to sign off or end any user job that issued any
cluster command or API. After the fix is applied, the job can be
started or can sign on again.
SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI68928 :
=================================================
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, any node without the fix will continue to be a potential
source of the problem.
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)
3. It is recommended to sign off or end any user job that issued any
cluster command or API. After the fix is applied, the job can be
started or can sign on again.
SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI68530 :
=================================================
Perform the following steps on each node with an HMC REST cluster
monitor defined:
1. End clustering on the node.
2. Apply the fix.
2A. Reboot/restart the HMC associated with the HMC REST cluster
monitor. Once this has been completed, proceed to the next step.
3. Start clustering on the node.
Additionally, any HMC which has been monitored by an HMC REST cluster
monitor should be restarted to remove HMC REST server performance
problems resulting from inactive sessions. For best results the HMC
should be restarted when clustering is inactive on systems with HMC
REST cluster monitors (during step 2A of the previous instructions
would be good). If this is not feasible, wait until after all systems
with HMC REST cluster monitors have had the fix applied before
restarting the HMC.
SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI66968 :
=================================================
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)
SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI66494 :
=================================================
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 SI66577 :
=================================================
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 SI66314 :
=================================================
Once the PTF is applied, a new job must be started to pick up the new
code since the service programs contained in the PTF are activated into
the Default Activation Group.
SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI64243 :
=================================================
Start a new job after applying or removing this fix to activate the new
code.
SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI64107 :
=================================================
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 SI63654 :
=================================================
Start a new job after applying this fix to activate the new code.
Additionally, the IASP must be varied off and varied back on for fix to
take effect.
SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI63587 :
=================================================
You must restart clustering on each node this PTF is applied to for the
code to be activated.
SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI63447 :
=================================================
Any vary on or vary off requests AFTER this PTF is applied will contain
the vary request information enhancement.
SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI60579 :
=================================================
IPL after applying or removing the fix.
SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI61808 :
=================================================
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: SI59020 and SI62171.
If REST cluster monitor support is not required the above requirements
can be ignored.
SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI59116 :
=================================================
/* Environment variable name: QIBM_IASP_QDBSRV_JOBS */
/* If the environment variable is set to *CURRENT, the */
/* number of current processors is used to determine the */
/* number of QDBS###Vxx system jobs to be started. */
/* If the environment variable is set to *CALC, the average */
/* of the current and maximum configured processors will be */
/* used to determine the number of QDBS###Vxx jobs to be */
/* started. For example, if current = 7 and max = 10, then */
/* (7 + 10 + 1) / 2 = 9. (the 1 is added intentionally) */
/* If the environment variable is set to *MAX, the maximum */
/* configured processors determines the number of QDBS###Vxx*/
/* system jobs to be started. */
/* The environment variable may also be set to a number */
/* between 5 and 99. This number represents the total */
/* number of QDBS###Vxx jobs to be started. If the number */
/* is an even number, one additional job will be started */
/* for the type 1 server job, to keep an equal number of */
/* type 2 and type 3 jobs. */
/* If the QIBM_IASP_QDBSRV_JOBS environment variable does */
/* not exist or does not contain a valid value, the */
/* current number of processors determines the number of */
/* jobs to be started. */
SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI58880 :
=================================================
Start a new job after applying this fix to activate the new code.
Changes to QDBS###Vxx jobs will be effective at the NEXT VARY ON of
IASP.
SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI58243 :
=================================================
After applying PTF, restart all jobs that will use the new code (any
jobs that use an IASP).
SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI56013 :
=================================================
Start a new job after applying this fix to activate the new code.
SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI55073 :
=================================================
The function of this PTF will be available to any job started after the
PTF is applied.
SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI53649 :
=================================================
The function of this PTF is available in any job started after the PTF
has been applied.
SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI52904 :
=================================================
This fix will be active in any job that is started after the fix has
been applied.
SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI52359 :
=================================================
The function of this PTF is available to jobs started after the PTF has
been applied.
SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI51930 :
=================================================
Apply the fix. The fix will be active in any job started after the fix
is applied.
SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI60757 :
=================================================
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 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 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
-------------- ------------------------------------------------------------
SI70101 HASM-HA-F/CSTADCHGS-T/CSTADCHGS-MSGCPF1059 QAUDLVL SET WITH
SI69958 OSP-OTHER-F/QP0LCCFN-T/QYASPVRYPD-MSGCPFA0A9 DSPASPSTS IASP
SI69958 OSP-INCORROUT Display date Julian *JUL date format in DSPASP
SI69958 OSP-INCORROUT DSPASPSTS does not refresh vary job failed mes
SI69958 OSP-Force DSPASPSTS flight recorder data to DASD to protect
SI69648 OSP-OTHER-MSGCPF3C74 MSGCPF3C74 ENCOUNTERED DURING WRKCADMRE
SI69310 OSP-MSGCPFBB60 CHGCRGPRI may fail
SI69310 OSP-INCORROUT CHGCRGPRI may fail with hyperswap and global m
SI68928 OSP-OTHER-MSGCPDAA02 ADDCADMRE RESULTS IN INCONSISTENT MRE.
SI68530 OSP-OTHER-UNPRED CLUSTER MONITOR DOES NOT PREVENT PARTITION
SI68526 OSP-MSGCPF115A MSGCPF115A INTERMITTENT ERROR INDICATING IASP
SI68245 MSGCPDB1B9 SWITCHOVER, FAILOVER, OR FLASHCOPY IASP VARYON FA
SI68036 OSP NO ROWS RETURNED FOR SELECT OF ASP_VARY_INFO VIEW.
SI68000 OSP-OTHER-INCORROUT CLUSTER ADMINISTRATIVE DOMAIN SHOWS CONS
SI67929 OSP-INCORROUT RMVCLUNODE or DLTCLU may hang
SI67783 OSP-OTHER-F/QCSTCMN-T/QCSTCMN-MSGMCH3601 QCSTCTL EXPERIENCES
SI67783 OSP-OTHER-F/QHACMN-MSGCPFBB60 CHGCRGPRI IN A LUN SWITCH PLUS
SI67647 OSP-OTHER Infrastructure enablement for hyperswap switching
SI67608 MSGCPFBB93 STRCLUNOD may hang if Option 41 license not valid
SI67550 OSP-OTHER-MSGCPF2640 MSGCPF2640 MAY OCCUR DURING VARY OFF OF
SI67550 OSP-SQL Pending work IASP FAILED not marking secondary IASP
SI67423 OSP-OTHER Base infrastructure updates for HyperSwap status
SI67424 OSP-MCH3601 in QYASPACT when doing RCLSTG SELECT(*DBXREF)
SI66968 OSP-OTHER-WAIT STRCAD MAY HANG DUE TO AN INTERNAL LOCK CONDI
SI66962 OSP-incorrectly marking a cancelled vary as FAILED
SI66494 HASM-F/QMHSNDPM-T/QCSTCMN-MSGCPF2499 ADDCADMRE FOR *AUTL FAI
SI66494 OSP-INCORROUT Admin domain losing MRE attribute values
SI66577 OSP-OTHER-UNPRED USER PROFILE LOSES JOB ATTRIBUTE IF MORE TH
SI66314 OSP-OTHER-F/QYASPPG1-T/QYASPPG1-MSGMCH3601 MCH3601 WITH VARI
SI66314 OSP-DISK-OTHER-MSGMCH5203 AFTER FLASHCOPY VARY ON OF IASP FA
SI66314 OSP-OTHER-F/QDCVRD-T/QDCWKFST-RC00000002-MSGCPF980A VARY ON
SI66274 INCORROUT Cluster administrative domain may hang on STRCLUNO
SI66220 OSP-OTHER-MSGCPFBB22 PARAMETERS PASSED DURING CHGCLUMON THAT
SI65824 HASM-HA-UNPRED STRCLUNOD HANG
SI65824 OSP-OTHER-F/QHACMN-MSGCPDAA01 ADD OF A *USRPRF MRE IN ADMIN
SI65645 OSP-OTHER-SRCD90027C0-WAIT SYSTEM HANG DURING IPL DUE TO CLU
SI64633 OS-DB INTERNAL MAINTENANCE
SI65154 INCORROUT Add HMC REST version to logging
SI65093 OSP-OTHER-INCORROUT: Axis.log debug file is not generated
SI65002 INCORROUT QIBM_QCST_STRCLUNOD not unregistered when no regis
SI64845 HASM-HA-MSGCPI93B2 5770 SP/QCSTADSIMP MOD/CSTADJOINS RC56 IN
SI64840 OSP-INCORROUT rare system TI when varying off Geographic Mir
SI64805 OSP-OTHER-INCORROUT GO SAVE 21 DOES NOT SAVE MULTIPLE PRIMAR
SI64729 HASM-HA-F/QCSTCCJOB-T/QCSTCCJOB-MSGCPFBB12 STRCLUNOD RESULTS
SI64368 OSP-INCORROUT vary off CPAB8E6 reply 'C' causes function che
SI64243 OSP-INCORROUT CFGDEVASP creating secondary linking to non-pr
SI64243 OSP-INCORROUT CFGDEVASP creating IASP specifying ENCRYPT(*YE
SI64154 HASM-HA-F/RMSLLOCKCHECK-T/QYASPDDDTA-MSGMCH2601 RETRIEVING D
SI64107 HASM-HA-F/QCAIFLD-T/QSYUPADOH-MSGCPD221E ADDCADMRE FOR A USE
SI64107 INCORROUT MSGCPF3C74 in WRKCADMRE
SI63878 OSP-OTHER-MSGCPFBBCB ADDCLUMON TYPE(*RESTSVR) CPFBBCB RC7.IN
SI63654 OSP-OTHER-THREADS-F/AUUSERPROFILE-T/QLICSLIB- RCFUNCTIONERRO
SI63587 INCORROUT-DSPASPSTS incorrect current time if complete bit n
SI63560 INCORROUT-DSPASPSTS incorrect current time if complete bit n
SI63447 OSP-OTHER-INCORROUT WRKCFGSTS SHOWS IASP AS FAILED, BUT DSPA
SI60579 OSP-Use OptimisticReadMutex to allow quicker reads
SI61808 XPF-NF: Cluster monitor based on HMC REST APIs
SI60762 INCORROUT Cluster fixes
SI60532 OSP-INCOROUT DSPASPSTS not properly showing item counts
SI60255 OSP-OTHER-LOOP SYSTEM JOBS WILL NOT END.
SI59599 OSP-OTHER-MSGMCH3601 IASP VARYON FAILS MCH3601 CPF2777 DAMAG
SI59116 IPL-PERFM ENVIRONMENT VARIABLE TO APPLY TO IASP QDBSRV JOB C
SI59116 OSP-resolve to QSYS00### library fails with MCH3401 before c
SI58880 OSP-duplicate definition for structure
SI58880 OSP-DB-OTHER-PERFM VARY ON OF IASP STARTS NUMBER OF QDBSRV J
SI58243 OSP-OTHER-WAIT JOBS IN MTXW. HOLDER DOING WORK IN QYASPPG1 (
SI57584 OSP-Create System Library macro passing in null parameter
SI57197 OSP-OTHER-PERFM DSPASPSTS SHOWS CONTEXT REBUILD MOVING, HOWE
SI56562 OSP-INCORROUT WRKASPJOB not displaying ASP subsystem jobs
SI56561 F/IODRIVERASPCTORPLUS-MSG5203-X'0014E8' RCLSTG FOR AN IASP F
SI56347 OSP-INCORROUT-MSGCPFB8ED in DSPASPSTS
SI56013 LIC-OTHER-WAIT SETASPGRP APPEARS HUNG WAITING ON MUTEX RELEA
SI55073 OSP-INCORROUT DSPASPSTS does not stop when vary on fails
SI53649 OSP-INCORROUT Add Display ASP Status forward stepping
SI52904 OSP-Enhance DSPASPSTS
SI52813 F/QYASPPG1-QYASPPG1 JOBS GETTING STUCK IN MTXW DURING IASP V
SI52698 OSP-MSG MCH2603 during OS upgrade.
SI52359 INCORROUT- Display ASP Status (DSPASPSTS) command provides i
SI51930 OSP-INCORROUT Invalid device description when accessing IASP
SI51575 OSP-INCORROUT MCH0601 sent during IASP varyon processing.
SI51262 OSP-INCORROUT MCH0601 F/QYASP during IASP varyon
SI54515 OSP-INCORROUT Cannot delete independent ASP when geographic
SI60757 OSP-MSGTCP2901-PAR-940XBASE STRCLUNOD WITH CCSID 5026 FAILS
SI60008 OSP-INCORROUT Cluster Data Fixes
SI57608 OSP-INCORROUT Base Function to Enable Future Extensions
SI57608 OSP-INCORROUT Base Function to Enable Future Extensions
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 SE69732 |
Superseded by:...................... | View fix details for PTF SI79263 |
Recompile........................... | N |
Library............................. | QSYS |
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:
25 March 2022