PI08824: GDPS/PPRC CODE AND PANEL CHANGES FOR HEAT MAP TRANSFER

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Password update fails for HMC userid from HMT panel.
  HMT actions incorrectly allowed in alternate K-sys.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: GDPS/PPRC and GDPS/PPRC HM users who have    *
  *                 implemented GDPS Heat Map Transfer support.  *
  ****************************************************************
  * PROBLEM DESCRIPTION: Password updates for HMC userid fail.   *
  *                      Command failed, rc=8 is returned in HMT *
  *                      panel.                                  *
  *                      HMT actions were allowed in alternate   *
  *                      K-system. Should only be allowed in     *
  *                      master K-sys.                           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When the password update failed, the BPXCMD command execution
  ended with rc=10.(written to netlog)
  

Problem conclusion

• The HMT utility command for password management was changed.
  Added check that HMT commands are issued from a master K-sys.
  
  PRODUCT DEPENDENCY
  This PTF supports REWORK(2014085) or later of the GDPS Heat Map
  Transfer Utility package.  However, the PTF can also be used
  with REWORK(2013340) of the package. The latest package can be
  obtained from the GDPS/PPRC and GDPS/PPRC HyperSwap Manager
  FTP sites. See file GDPS_HMTU_V1R1.Readme.txt in directory
  fromibm/code for details.
  
  DOCUMENTATION CHANGES
  The following changed text affects the GDPS Heat Map Transfer
  support information in the GDPS/PPRC and GDPS/PPRC HyperSwap
  Manager Installation and Customization Guides (ZG24-6703 and
  ZG24-6746).
  
  The GDPS Controlling systems must be connected via TCP/IP to
  all the HMCs of each of the Site1 and the Site2 disk subsystems
  that will be managed by GDPS Heat Map Transfer.
  
  The GDPS HMT function uses the DS Network Interface (ESSNI)
  server on the Hardware Management Console (HMC). This interface
  is accessed by a number of IBM applications, including DSCLI
  that use a DS Network Interface client.
  If you are not familiar with the specific requirements and
  setup (such as enabling ESSNI, TCP/IP port numbers and so on)
  for this interface, consult with your IBM disk subsystem support
  specialist.
  
  Also include your networking specialist on this discussion to
  ensure you cover any firewall or routing considerations as
  applicable to your installation. It is essential for Heat Map
  Transfer function that the GDPS systems running the GDPS Heat
  Map Transfer component has network access to the ESSNI"s TCP/IP
  ports on the disk subsystems HMCs.
  
  
  The JVM (Java Virtual Machine) executable, with file name
  "java", for one of the supported SDKs must be available through
  the PATH environment variable as set in /etc/profile. As of
  APAR PI08824, PATH can also be set in the  AUTETHM/.profile
  (see 'GDPS auto operator for Heat Map Transfer') or a file
  pointed to by the ENV environment variable.
  The ENV environment variable must, if used, be set in
  /etc/profile or  AUTETHM/.profile to take effect.
  
  For GDPS 3.10, APAR PI08824 allows the Heat Map Transfer
  Utility to be installed in an alternate file system location
  than the default.
  Doing this requires that the directory containing the hmtu.sh
  shell script (default directory /usr/lpp/GDPS/hmtu) is
  available through the PATH environment variable.
  Specifying the directory in the PATH environment variable can
  be done in the same manner as for the JVM.
  We recommend adding the directory to PATH environment
  variables regardless of whether the default file system
  location is used or not.
  
  The following changed text affects the 'Heat Map Transfer auto
  operator' information in the 'Using the System Automation
  dialogs to create the GDPS policy' section.
  
  A USS home directory must be created for AUTETHM with the
  following additional properties:
  
  - A .profile file (/u/autethm/.profile) may optionally be
    created in the home directory.
    This file is, if present,   processed after /etc/profile
    and before the Heat Map Transfer Utility is called making
    it possible to specify needed setting in it instead of in
    /etc/profile.
    If the environment variable ENV is set after /etc/profile
    and .profile processing and specifies an existing file, it
    is processed before the Heat Map Transfer Utility is called.
  
  - The USS filesystem containing the AUTETHM user home
    directory (/u/autethm) must have sufficient free storage
    for HMTU configuration files, log files and temporary files
    used during operation:
    - 60 MB for base HMUT operation log files
    - 150 MB for log files each group, (such as CKD)
    - Up to 610 MB configuration and temporary data for each
      group. The actual size depends on the actual number of
      mirrored volume pairs.
    The file system free space should be kept well above the
    numbers given above to avoid problems during operation.
  

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:

  UI16494

Modules/Macros

•    VPCEEHMT VPCEETMO VPCEET01 VPCEET02 VPCEET04
  

Fix information

• Fixed component name

  GDPS-GEO DISP P

• Fixed component ID

  694235B00

Applicable component levels

• R3AH PSY UI16494

     UP14/04/01 P F403

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.