PH19297: GDPS GM DASD CONFIG FAILURE AFTER MIGRATION TO V4R1

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Problem occurs when devices are removed from the Global Mirror
  configuration after migration from V3R14 to V4R1. When the CHECK
  option is used on DASD CONFIG, errors occur on the Kr system.
  VPCEGINI produces a GEO9999E INTERNAL ERROR, due to a REXX
  syntax error 40 - Incorrect call to routine, with the following
  source line indicated:
  pqmp_mgm_0dev = cglobal('VPC_MGM.'pqmp_p1'.0DEV.'pqmp_p3)
  
  The following errors can also be observed in the netlog on the
  Kr system during GDPS init until a successful DASD config has
  been made:
  
  REXX error in VPCNACTA:
    3295 +++ do i = 1 to noof_pairs
  EAGREX4100E Error 41 running compiled VPCNACTA, line 3295: Bad
  arithmetic conversion
  
  Several GEOTRC messages from VPCMDSDH about invalid device
  status:
  VPCMDSDH: CheckStatus: GM secondary device RMTDEV has invalid
  status
  
  REXX error in VPCEDEV:
    2859 +++   devk = devk!!right(x2c(secssid),2,'0'x)
    2151 +++  Call Collect_gm_ckd  Coll_type sess
     348 +++ Call build_pair_ckd_gm
  EAGREX4000E Error 40 running compiled VPCEDEVC, line 2859:
  Incorrect call to routine
  EAGREX4008I Argument not a valid hexadecimal string
  

Local fix

• If you are sure that the new configuration will not leave
  "orphans" (devices that may not have been removed from the
  running Global Mirror, but are removed from the GEOPARM), you
  may run the DASD Config with CHECK set to No.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * GDPS Metro Global - GM                                       *
  * keywords: GDPSGM/K                                           *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * A GDPS GM DASD config in a GDPS Metro Global - GM setup      *
  * fails with a REXX error on the Kr if GM secondary device     *
  * configuration is missing.                                    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The root cause of the failed GDPS config, and errors seen on the
  Kr during GDPS init, is that the DASD configuration for GM
  secondary devices is missing. This may the case when migrating
  from a GDPS/MGM solution to GDPS Metro Global - GM. The missing
  secondary device DASD configuration will then result in errors
  on the Kr during GDPS init and GDPS config.
  

Problem conclusion

• This PTF fixes the reported problems:
  * a DASD config can now be done with CHECK=YES although the
  secondary device configuration is missing on the Kr
  * the DASD configuration on the Kr will be marked in ERROR
  during GDPS init if the secondary device configuration is
  missing. This also eliminates the errors seen during GDPS init.
  

Temporary fix

Comments

• ×**** PE20/03/09 FIX IN ERROR. SEE APAR PH19297  FOR DESCRIPTION
  ×**** PE20/02/26 FIX IN ERROR. SEE APAR PH22675  FOR DESCRIPTION
  

APAR Information

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

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

  UI67170 UI67171

Modules/Macros

• VPCEGINI VPCMDSDH
  

Fix information

• Fixed component name

  GDPS

• Fixed component ID

  694235B00

Applicable component levels

• R410 PSY UI67170

     UP19/12/24 P F912  

• R420 PSY UI67171

     UP19/12/24 P F912  

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.