A fix is available
APAR status
Closed as program error.
Error description
See problem summary
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * GDPS Metro * * GDPS Global - GM * * GDPS Global - XRC * * keywords: GDPSMETRO/K GDPSXRC/K GDPSGM/K GDPSLCPMGR/K * **************************************************************** * PROBLEM DESCRIPTION: * * GDPS METRO AND GLOBAL FIX PACKAGE 2022-01 * * * **************************************************************** * RECOMMENDATION: * **************************************************************** Problems addressed in GDPS Metro, GDPS GM, and GDPS XRC: - In the GEOGROUP management panel, if the user has more than one group defined, the refresh action will not occur in some partners (4.3, 4.4) - A CPC suspend or resume using the panel action on VPCPCOPS is causing GDPS to incorrectly mark the monitor for this CPC as running. This causes GDPS to issue GEO929W HMC AUTOMATION INTERFACE MONITORING SKIPPED for each monitor1 execution. (4.4, 4.5) - During GDPS initialization, if the BCPii session to the local SE is suspended, GDPS will report the CPC status as 'UNKNOWN' on panel VPCPCOPS and this status will remain UNKNOWN even after the connection is resumed. (4.4, 4.5) Problem addressed in GDPS Metro and GDPS XRC: - When &GDPSMODE = NO_DASD (for Metro) or TEST, TEST_FC1, or TEST_FC2 (for MZGM4SITE) the Metro GDPS Environment Information panel VPCPSTA1 does not display GDPS-lvl and MT status correctly. (4.4) Problem addressed in GDPS Metro and GDPS GM: - In a multiple consistency group configuration, a disk subsystem may have have duplicate entries in the Disk Subsystem List panel (VPCPDLST) panel. (4.3, 4.4) Problems addressed in GDPS Metro only: - DASD configuration information is lost if an unplanned event (like HyperSwap) occurs, or planned action is initiated by one user while another user is attempting to load a configuration from the VPCECOMM panel.(4.3, 4.4) - Text truncated on GDPS Metro Config Management help panel VPCPHCGR. (4.3, 4.4) - User is prevented from removing devices in an external LCP Manager environment where the candidate devices are cascaded from an MGMnSITE solution. - When a GDPS K-sys is IPLed and takes the master role, if there is an outstanding GEO2669A, this prompt is lost during the new master initialization. (4.3, 4.4, 4.5) - Following a freeze event in a PPRCFAILURE=STOP environment, the primary volumes are soft fenced. The first attempt at executing START SECONDARY following the freeze fails and presents a GEO2621E and plan 909 is reported in the GEO2618I message block indicating that the primary volumes are still Soft Fenced. Re-running START SECONDARY will refresh the data and successfully restart replication. (4.3, 4.4) - START SECONDARY does not detect presence of Outboard Copy Inhibit on PPRC secondary volumes. With this PTF, it is detected and reported with plan 915 in the GEO2618I message block. (4.3, 4.4) - GDPS incorrectly allows a Standard action to run when a GEO2669A failure notification is active. (4.3, 4.4) - START SECONDARY ends with RC=8 when it is unable to restore relationships which are in the following state: Pri-Sus(10)->Sec-(Any-state). These relationships are flagged with plan 999 as reported in the GEO2618I message block indicating 'A non-restorable relationship was found'. They will now be correctly handled by a new plan 17. (4.3, 4.4) - Corrected 'SENSENOT PROVIDED' typo in GEO399E message when AOM I/O ERROR RC:0008 RSN:0028 occurs. (4.3, 4.4) - In START SECONDARY, the combination Pri-Pnd->Pri-Sus(n) replication states is currently not recognized as restoreable. This PTF now recognizes this combination and will perform restore plan 9. (4.4) - In configurations with multiple consistency groups, Monitor3 does not perform Soft Fence checking for FBA consistency groups (4.3, 4.4) Problems addressed in GDPS Metro HyperSwap Manager only: - Options are not correctly propagated to the other system(s) following a REFRESH OPTIONS action. (4.3, 4.4)
Problem conclusion
This PTF fixes the reported problems.
Temporary fix
Comments
APAR Information
APAR number
PH43016
Reported component name
GDPS
Reported component ID
694235B00
Reported release
420
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
YesSpecatt / Pervasive / Xsystem
Submitted date
2021-12-23
Closed date
2022-04-28
Last modified date
2022-05-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI80346 UI80347
Modules/Macros
VPCETDAS VPCCMCPC VPCESYSM VPCEGEO1 VPCEBCPO VPCPHRI1 VPCESSEX VPCESTA1 VPCETINI VPCEITGO VPCESSCR VPCESTD1 VPCES VPCCDEFO VPCPHCGR VPCEDLST VPCEXMVA GEOLABEL VPCEMON3
Fix information
Fixed component name
GDPS
Fixed component ID
694235B00
Applicable component levels
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"420"}]
Document Information
Modified date:
04 May 2022