PH19840: GDPS GM FIX PACKAGE 2020-01

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• This APAR provides miscellaneous minor fixes for GDPS Global -
  GM and GDPS Metro Global - GM.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users of GDPS Global - GM and GDPS Metro Global - GM.    *
  *                                                              *
  * Keywords:                                                    *
  * GDPSGM/K GDPSMETRO/K                                         *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Miscellaneous GDPS Global - GM and GDPS Metro Global - GM    *
  * fixes                                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Problems addressed in GDPS releases 4.3, 4.2 & 4.1:
  - 2 GM Monitor instances could be started for the same session.
  - Some messages issued by DASD config process do not conform to
    what is described in the help text. The help text is also
  incomplete.
  - GDPSCHG MIGRATE GMMODE(NONMT2MT|MT2NONMT) command GEOTRC
    message listing CCAs still joined to the GM session (after
    being removed) for an LSS may contain wrong data. In
    addition to the CCAs being joined it may also contain
    CCAs from another LSS appended. It also causes the total
    number of volumes still joined to be wrong.
  - GDPSCHG MIGRATE GMMODE(NONMT2MT|MT2NONMT) a time-out when
    waiting for volume removed from a session is not marked as an
    error. This results in a message stating that all volumes
    have been removed when this is not true.
  - Start and stop of X-disk and FC1 HMT groups is not handled
    correctly by GDPS Monitor1. The groups are not started or
    stopped unless the GM session state also changes so that a
    GMSEC HMT group would also be affected.
  - SNMP trap value output by VPCMMSGO is not correct.
  - The SDF alerts GEO627W & GEO628W is displayed using red
    color instead of yellow.
  - There are multiple problems when translating Kg load
    address to corresponding addresses on the Kr:
    - 5-digit primary load addresses in MSS0 are not translated
    - FC1 load addresses with no UCB on the Kr are translated
      into "????"
    - FC1 load parameters where no FC1 disk is defined are
      translated into "XXXX"
    - The GEO625I message indicating that a successful
      retrieve of load address information from a Kg by a Kr
      is issued even on failure.
  - Conditionally suspend A2C or B2C replication during the
    execution of the MGM3SITE_PREPARE_MIRROR_CAS_RSn procedures.
    Prior to this change the user was responsible for ensuring
    that replication for these triplet volumes was suspended
    prior to procedure execution.
  - Colors in the "CU pairs panel" VPCPMSR6 in the Kr-system
    could show wrong colors if the DASD config had subordinates
    and the color for any of the rows should be other than green.
  
  Problems addressed in GDPS releases 4.3 & 4.2:
  - Help panel indicates wrong default value for
    FAILONSIZEMISMATCH.
  
  Problems addressed in GDPS releases 4.2 & 4.1:
  - Script names longer than 31 characters in GDPS GM leads to
    messages:
    CNM421I COMMAND LIST VPCMINIS - INVALID COMMAND 1 ENCOUNTERED
    and REXX errors.
  - VPCMINIP will end in a REXX error if there are no GM
    sessions defined in DSISVRT during GDPS init:
    102 +++ do vi = 1 to vl.0
    EAGREX4100E Error 41 running compiled VPCMINIP, line 102: Bad
    arithmetic conversion
  
  Problems addressed in GDPS release 4.2:
  - GDPSCHG MIGRATE GMMODE(NONMT2MT|MT2NONMT) command does not
    work in a multi-session GM2SITE environment.
  
  Problems addressed in GDPS release 4.1:
  - GDASD=RECOVER may generate REXX arithmetic errors if Non-GDPS
    managed FlashCopy relationships are detected. In this
    scenario, RECOVER should fail. However, the REXX error results
    in the recovery processing continuing.
  

Problem conclusion

• This PTF fixes the reported problems.
  
  DOCUMENTATION UPDATES:
  Manuals "GDPS Metro Global - GM V4R3 Planning and Implementation
  Guide" (ZG24-6758-xx),
  "GDPS Metro Global - GM V4R2 Planning and Implementation Guide"
  (ZG24-6758-xx) and
  "GDPS Metro Global - GM V4R1 Planning and Implementation Guide"
  (ZG24-6758-xx)
  are updated. Text is changed for chapter 4.2.1
  
  4.2.1 Considerations for 3-site configurations
  
  
  
  In a 3-sites configuration where it is possible to define some
  of the
  devices in the MSS1, when specifying the load address using
  either the
  A-disk or the B-disk address, this can be specified as either a
  4-digit
  (In MSS0) or a 5-digit device number (in MSS0 or MSS1). The load
  
  parameters, as with GDPS Metro MSS1 support, must always be
  specified
  with a 4-digit device number. The eventual leading 1 if in MSS1
  will be
  inherited from the load address.
  
  
  
  Figure 4-1 shows an example of a GDPS GM Load Table (Modify
  panel) for a
  system from the Kg-system. As you can see, either the 01600
  A-disk
  address or the 11600 B-disk address are valid load address
  
  specifications.
  
  Manuals "GDPS Global - GM V4R3 Installation and Customization
  Guide" (ZG24-6757-xx) and
  "GDPS Global - GM V4R2 Installation and Customization Guide"
  (ZG24-6757-xx)
  are updated. Information is added to chapter "3.1.8 Security
  definitions" to reflect that if you are protecting the RMTCMD
  using a NetView remote security table also new operators AUTGEO7
  to AUTGEO9 need to be able to communicate with AUTRMT and vice
  versa.
  
  The sample is updated with:
  RMTSEC PASS,TARGOP=AUTGEO7,NET=*,LU=*,RMTOP=AUTRMT,CMD=*
  RMTSEC PASS,TARGOP=AUTGEO8,NET=*,LU=*,RMTOP=AUTRMT,CMD=*
  RMTSEC PASS,TARGOP=AUTGEO9,NET=*,LU=*,RMTOP=AUTRMT,CMD=*
  RMTSEC PASS,TARGOP=AUTRMT,NET=*,LU=*,RMTOP=AUTGEO7,CMD=*
  RMTSEC PASS,TARGOP=AUTRMT,NET=*,LU=*,RMTOP=AUTGEO8,CMD=*
  RMTSEC PASS,TARGOP=AUTRMT,NET=*,LU=*,RMTOP=AUTGEO9,CMD=*
  
  Manuals "GDPS V4R3 Messages and Codes" (ZG24-6762-xx), "GDPS
  V4R2 Messages and Codes" (ZG24-6762-xx) and "GDPS V4R1 Messages
  and Codes" (ZG24-6762-xx) are updated. Explanations are updated
  for the following messages (see DOC hold for details):
  GEO627W
  GEO628W
  GEO686I
  GEO911I
  GEO2676E
  GEO2680I
  GEO2681W
  GEO2682E
  GEO2683I
  GEO2684W
  GEO2685E
  GEO2686I
  GEO2687W
  GEO2688E
  GEO2693E
  GEO2694E
  GEO2695E
  
  CHANGED MESSAGES (see DOC hold for details)
  GEO686I
  GEO911I
  GEO2676E
  

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:

  UI69779 UI69780 UI69781

Modules/Macros

• VPCNPD03 GEO91    VPCMLOAD VPCNETFE VPCMGMPL GDPSCHG  VPCETINI
  VPCMETFE VPCNTECO VPCNOH03 VPCEGINI VPCMFCLT GEO62    VPCMQST1
  VPCMAZDL VPCNFH03 VPCESTD3 VPCESTD2 VPCMINIS GEO268   GEO68
  VPCEQSMT VPCMDASD VPCMINIP GEO267   VPCPHO55 VPCNPH03 GEO269
  VPCMDSDH VPCMFSRV VPCMMSGO VPCNACTA VPCPHO26
  

Fix information

• Fixed component name

  GDPS

• Fixed component ID

  694235B00

Applicable component levels

• R410 PSY UI69779

     UP20/06/02 P F006

• R420 PSY UI69780

     UP20/06/02 P F006

• R430 PSY UI69781

     UP20/06/02 P F006

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.