PH64641: Incorrect profiles and/or initial commands may be used for GDPS automation operators

Obtain the fix for this APAR.

APAR status

• Closed as unreproducible in next release.

Error description

• GDPS Metro documentation indicates "For automation operators,
  define VPCCGEIC as the Initial Command". This is not correct
  for the AUTWEBUI operator, whose IC should be VPCUDMON.
  
  Also, some of the automation operator definitions supplied in
  the GEOOP* members have incorrect PROFILEN specifications.
  All GDPS operators should have PROFILEN GEOPRFAO, with the
  exception of AUTWEBUI which should have PROFILEN GEOPRFUI.
  
  In addition, some clients with OPERSEC SAFDEF configurations
  have requested that the GDPS documentation more clearly
  indicate the need to specify the proper GDPS Initial Command
  in the NetView segment of the SAF profiles for the GDPS
  automation operators.
  
  Failure to define the correct initial command for an operator
  can lead to unpredictable results. The operator may be unable
  to perform its expected function, or function completion may
  be delayed during critical periods, which could lead to severe
  problems such as replication failure or system outages.
  
  For GDPS release 4.6 see related APAR PH69251
  
  ADDITIONAL RELATED ENHANCEMENT
  
  This APAR will also provide a Monitor1 enhancement to check
  if GDPS automation operators have executed the correct initial
  command, and if a standard GDPS EMCS console has been assigned
  (for all operators) and activated (for critical operators).
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All GDPS users                               *
  ****************************************************************
  * PROBLEM DESCRIPTION: Incorrect profiles and/or initial       *
  *                      commands may be used for GDPS           *
  *                      automation operators                    *
  *                                                              *
  ****************************************************************
  Some of the automation operator definitions supplied in
  the GEOOP* members have PROFILEN specifications that cause
  execution of initial commands other than those required by
  GDPS. Further, GDPS documentation needs clarification that
  installations with OPERSEC SAFDEF must define the proper GDPS
  initial command in SAF profiles for the automation operators.
  
  Failure to define the correct initial command for an operator
  can lead to unpredictable results. The operator may be unable
  to perform its expected function, or function completion may
  be delayed during critical periods, which could lead to severe
  problems such as replication failure or system outage.
  

Problem conclusion

Temporary fix

Comments

• This PTF also provides a Monitor1 enhancement that will check
  if GDPS automation operators have executed the correct initial
  command and if a standard GDPS EMCS console has been assigned
  (for all operators) and activated (for critical operators).
  
  ACTION REQUIRED
  
  This PTF changes the GDPS-supplied GEOOP* operator definition
  members to ensure that all GDPS automation operators specify the
  name of the GDPS-supplied profile. Previously, only some of the
  operator definitions had this specification.
  
  The PTF also standardizes EMCS console names for GDPS automation
  operators. The application program identifier (APPLID) for the
  task is used as the console name. APPLID is the NetView domain
  ID appended with a 3-character hexadecimal suffix assigned by
  the NetView program.
  
  Take the opportunity prior to installing this PTF to check your
  local GDPS automation operator definitions. With the PTF
  applied, Monitor1 will check if the correct initial command was
  executed for each operator, and that the standard EMCS console
  names have been assigned and activated as appropriate.
  
  If your installation uses OPERSEC SAFDEF, ensure that the SAF
  profiles for all GDPS automation operators except AUTWEBUI
  specify VPCCGEIC for the Initial Command in the NetView segment
  of their SAF profiles. For AUTWEBUI (or its equivalent) specify
  VPCUDMON.
  
  If your installation uses an OPERSEC value other than SAFDEF,
  review your local DSIPARM members to ensure that the OPERATOR
  statements for all GDPS automation operators except AUTWEBUI
  specify PROFILEN GEOPRFAO. For AUTWEBUI (or its equivalent)
  specify PROFILEN GEOPRFUI.
  
  Once you've ensured that the GDPS automation operators for a
  NetView domain are correctly defined. install the PTF in the
  domain, and confirm that all phases of GDPS initialization
  complete successful. Look in SDF for any GEO324W, GEO327W or
  GEO328E alerts, and if any are found, identify and correct
  the underlying reported problems.
  
  Repeat this for all GDPS NetView domains in your installation.
  
  NEW MESSAGES
  
  Messages GEO320E, GEO321W, GEO322W, GEO323W, GEO324W, GEO325E,
  GEO326E, GEO327E, and GEO328E are added to the GDPS Messages
  and Codes Reference Guide (ZG24-6762). See DOC hold for details.
  
  DOCUMENTATION CHANGES
  
  Publications affected:
  ZG24-6755 ZG24-6756 ZG24-6757 ZG24-6761 ZG24-6763
  
  The Installation and Customization Guides for GDPS Metro,
  GDPS Metro HyperSwap Manager, GDPS Global - GM, GDPS Logical
  Corruption Protection Manager, and GDPS Continuous Availability
  are updated.
  
  Various topics are changed to provide clearer guidance on how
  to define operator profiles and to make it easier to identify
  which operators need to be defined.
  
  Please refer to the PH64641 entries in the Summary of Changes
  for the online documentation, which can be found using the
  following links to the IBM Documentation web site:
  
  4.7 Metro:    https://ibm.biz/Bdm9Fh
  4.7 Metro HM: https://ibm.biz/Bdm9Fu
  4.7 GM:       https://ibm.biz/Bdm9F9
  4.7 CA:       https://ibm.biz/Bdm9FT
  4.7 LCP:      https://ibm.biz/Bdm9Fk
  
  4.8 Metro:    https://ibm.biz/BdnXJJ
  4.8 Metro HM: https://ibm.biz/BdnXJA
  4.8 GM:       https://ibm.biz/BdnXJu
  4.8 CA:       https://ibm.biz/BdnXJ9
  4.8 LCP:      https://ibm.biz/BdnXJC
  
  KEYWORDS: GDPS/K
  
  ×**** PE25/12/31 FIX IN ERROR. SEE APAR PH69520  FOR DESCRIPTION
  

APAR Information

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

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

  UO06307 UO06308 UO06310 UO06311

Modules/Macros

• DSIGEO32 GEO32    GEOAUTAA GEOAUTAS GEOAUTGM GEOAUTHM GEOAUTMM
  GEOCME00 GEOCMEAA GEOCMEAS GEOOPFA1 GEOOPFAL GEOOPFG1 GEOOPFLO
  GEOOPFMT GEOOPGA1 GEOOPGAL GEOOPGG1 GEOOPGLO GEOOPGMT VPCAMON1
  VPCCGEI2 VPCCGEIC VPCCOPEM VPCCOPEX VPCECONS VPCEMON  VPCSGEI2
  VPCSGEIC VPCSMON1 VPCSOPEM VPCSOPEX VPCUDMON
  

Fix information

• Fixed component name

  GDPS

• Fixed component ID

  694235B00

Applicable component levels

• R470 PSY UO06310

     UP25/12/18 P F512 ¢

• R47B PSY UO06311

     UP25/12/18 P F512 ¢

• R480 PSY UO06307

     UP25/12/18 P F512 ¢

• R48B PSY UO06308

     UP25/12/18 P F512 ¢

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.