PH64560: Unexpected results when systems using different GDPS xDR protocol types have similar names

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• In a configuration with a z/OS Proxy system named XXX running
  on LPAR YYY.AAAAAAA and a z/VM Proxy system XXX1 running on LPAR
  YYY.BBBBBBBB, the following error message was incorrectly raised
  during Monitor2:
  
  GEO225E MISMATCH CPCNAME.LPARNAME BETWEEN CURRENT YYY.AAAAAAAA
  AND TARGET YYY.BBBBBBBB
  
  The problem occurred because a site table search for system
  name XXX matched entries for both XXX and XXX1.
  
  ADDITIONAL SYMPTOM:
  
  A z/OS Proxy-managed system may be displayed as a z/VM Proxy-
  managed system in the GDPS 3270 panels or GUI, and z/OS
  specific actions will not be accepted for it.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: GDPS Metro installations using two or more   *
  *                 of the following:                            *
  *                                                              *
  *                 - GDPS z/OS Proxy                            *
  *                                                              *
  *                 - GDPS Metro Multiplatform Resiliency        *
  *                 for IBM Z (xDR)                              *
  *                                                              *
  *                 - GDPS Metro Linux in LPAR mode              *
  *                                                              *
  *                 - GDPS Metro Multiplatform Resiliency for    *
  *                 KVM                                          *
  *                                                              *
  *                 - GDPS support for IBM Db2 Analytics         *
  *                 Accelerator for z/OS                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: Unexpected results when systems using   *
  *                      different GDPS xDR protocol types have  *
  *                      similar names.                          *
  ****************************************************************
  If two systems are managed by different xDR protocol types
  (for example a z/OS Proxy-managed system and z/VM Proxy-
  managed system) and one system name contains the other system
  name as a substring, GDPS processing may mistake the one system
  name for the other system name, causing various unexpected
  results.
  
  For example a z/OS Proxy-managed system may be displayed as
  a z/VM Proxy-managed system in the GDPS 3270 panels or GUI,
  and z/OS specific actions will not be accepted for it.
  

Problem conclusion

• This PTF corrects the reported problems. Different system types
  with similar names will correctly be identified.
  
  KEYWORDS: GDPSXDRGUE/K GDPSXDRZOS/K
  

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:

  UO05078 UO05079 UO05080

Modules/Macros

• VPCLSTAT
  

Fix information

• Fixed component name

  GDPS

• Fixed component ID

  694235B00

Applicable component levels

• R460 PSY UO05080

     UP25/09/25 P F509

• R470 PSY UO05079

     UP25/09/25 P F509

• R480 PSY UO05078

     UP25/09/25 P F509

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.