PH63308: xDR looping to determine correct z/VM dump device when multiple dump devices exist in configuration

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• On the GDPS xDR dump management panel (VPCPXDRM) when the
  z/VM configuration has more than one dump volume, the display
  incorrectly states there is no valid dump configuration which
  causes a repeated xDR z/VM proxy command sequence to determine
  correct dump device. The z/VM proxy log shows repeated
  error-rc: 5 returned by switchDumpVolumes()
  
  Additionally, the xDR HealthChecker will show no GDPS managed
  dump volumes for the HOSTNAME(s) that have multiple dump
  devices.
  
  HIPER symptom: In configurations with a large number of z/VM
  proxy systems, the repeated commands cause the xDR dispatcher
  to become constantly busy and unable to perform other critical
  processing.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: GDPS Metro xDR users with z/VM proxy systems *
  *                 using multiple dump devices.                 *
  *                                                              *
  *                 keywords: GDPSXDRGUE/K                       *
  ****************************************************************
  * PROBLEM DESCRIPTION: xDR z/VM proxy looping to determine     *
  *                      correct dump device when multiple dump  *
  *                      devices exist in configuration          *
  ****************************************************************
  On the GDPS xDR dump management panel (VPCPXDRM) when the
  z/VM configuration has more than one dump volume, the display
  incorrectly states there is no valid dump configuration which
  causes xDR z/VM proxy looping to determine correct dump device.
  
  Additionally, the xDR HealthChecker will show no GDPS managed
  dump volumes for the HOSTNAME(s) that have multiple dump
  devices.
  
  HIPER symptom: In configurations with a large number of z/VM
  proxy systems, the looping may cause the xDR dispatcher to
  become constantly busy and unable to perform other critical
  processing.
  

Problem conclusion

• This PTF corrects the reported problems.
  

Temporary fix

Comments

APAR Information

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

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

  UI99067 UI99068

Modules/Macros

• VPCLVMD1
  

Fix information

• Fixed component name

  GDPS

• Fixed component ID

  694235B00

Applicable component levels

• R460 PSY UI99068

     UP24/11/16 P F411 ¢

• R470 PSY UI99067

     UP24/11/16 P F411 ¢

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.