PI51262: NEW FUNCTION - PRIM & PPRC FAILURE SET TO GO FOR MZGM 4-SITE SDM

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• New function: The active PRIMARYFAILURE and PPRCFAILURE policies
  for GDPS/PPRC are both forced to GO when GDPSMODE=SDM is in
  effect for a GDPS/MzGM 4-site topology.
  

Local fix

• Change the active PRIMARYFAILURE and PPRCFAILURE policies to GO
  in the SDM sysplex.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: GDPS/MzGM 4-site                             *
  *                 KEYWORDS: GDPSPPRC/K MZGM4SITE               *
  ****************************************************************
  * PROBLEM DESCRIPTION: New function: GDPS/PPRC PRIMARYFAILURE  *
  *                      and PPRCFAILURE policies are both       *
  *                      forced to GO for the SDM sysplex in an  *
  *                      MzGM 4-site environment.                *
  *                      This will prevent the ability to set    *
  *                      PRIMARYFAILURE=STOP (or                 *
  *                      SWAP,STOP) and/or PRCFAILURE=STOP that  *
  *                      in turn could impact the availability   *
  *                      of the SDM sysplex and cause an outage  *
  *                      to XRC replication.                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  GDPS/PPRC in the recovery region (the SDM sysplex) of an MzGM
  4-site environment runs the XRC SDM systems as production
  systems. If the active PRIMARYFAILURE policy is set to STOP (or
  SWAP,STOP), all SDM systems will be stopped and reset in
  response to a hybrid swap trigger (for example IOS002A) event in
  the SDM sysplex. The same would occur for a PPRC failure if
  PPRCFAILURE policy is set to STOP.
  All XRC mirroring between the production and recovery region
  will then be stopped until the SDM systems are restarted and XRC
  mirroring can be re-established. This APAR avoids this situation
  by forcing the active PRIMARYFAILURE and PPRCFAILURE policies
  both to GO for the SDM sysplex.
  

Problem conclusion

Temporary fix

Comments

• PRODUCT ENHANCEMENT
   PI51262 introduces a new function for GDPS/PPRC when used in an
   GDPS/MzGM 4-site environment: The active PRIMARYFAILURE and
   PPRCFAILURE settings are both forced to GO by GDPS logic for an
   SDM sysplex (where GDPSMODE is SDM). The active values can not
   changed through the VPCPALTR 3270 panel or VPCWPFRO web panel
   while in SDM mode.
  ACTION REQUIRED and MULTIPLE SYSTEM CONSIDERATIONS
   In environments with two GDPS/PPRC K-systems (Kp-systems) in a
   region, the PTF must be installed in both before the fix is
   fully operational. It must also be installed in both regions to
   ensure correct operation after a region switch.
   When installing the PTFs in the current SDM sysplex, perform
   the following actions:
   Actions prior to installing the PTFs:
   1. Check that both Kp-systems are active.
   2. Ensure that the active PRIMARYFAILURE and PPRCFAILURE
      policies in the SDM sysplex both are GO, change if needed
      using the GDPS 3270 panel VPCPALTR (GDPS-> View/Alter
      Definitions-> Alter PRIMARY and PPRC Failure Options).
   Applying the PTFs:
   3. Install PTFs on the alternate Kp-system, recycle the
      GDPS/PPRC NetView and wait until GDPS is active.
   4. Repeat the install on the master Kp-system and recycle
      the GDPS/PPRC NetView.
   Actions after PTFs are installed:
   5. Verify that the active PRIMARYFAILURE and PPRCFAILURE
      policies both are GO in the SDM sysplex.
   No special actions are needed when installing the PTFs in the
   production region, nor for the GDPS/XRC part of the GDPS/MzGM
   4-site installation.
  DOCUMENTATION CHANGES
   The following updates will be added to a future release of the
   "GDPS/MzGM Planning and Implementation Guide, ZG24-1757".
   Section "Planning for implementation of a GDPS/MzGM 4-site
   configuration", "PRIMARYFAILURE and PPRCFAILURE policy
   considerations":
   The two parts:
    The PRIMARYFAILURE option has no significance ...
    The PPRCFAILURE is also common ...
   are replaced with:
    The active PPRCFAILURE and PRIMARYFAILURE in a SDMplex are
    both forced to GO by GDPS logic. PPRCFAILURE=STOP would
    otherwise result in a stop and reset for all SDM systems in
    case of a freeze trigger. PRIMARYFAILURE=STOP (or SWAP,STOP)
    would result in the same in case of a hybrid trigger. Values
    stored in the policy database are not affected and used in
    LIVE mode.
    Both the PPRCFAILURE=STOP and PRIMARYFAILURE=STOP (or
    SWAP,STOP) settings can thus be used in the production sysplex
    without the need for a change in the SDMplex to avoid having a
    freeze or hybrid trigger stopping the SDM systems and the XRC
    mirroring from production to recovery region.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UI36722 UI36723

Modules/Macros

• VPCEALTR VPCEIPCM
  

Fix information

• Fixed component name

  GDPS-GEO DISP P

• Fixed component ID

  694235B00

Applicable component levels

• R3CH PSY UI36723

     UP16/04/02 P F604

• R3C0 PSY UI36722

     UP16/04/02 P F604

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.