VM65712: DYNAMICALLY MIGRATE THE Z/VM SSI PDR

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• Currently a cluster-wide shutdown is required
  when the SSI Persistent Data Record (PDR) is
  relocated to a new volume. This requirement
  contradictsthe SSI value proposition to avoid
  planned outages, and hinders moving to a new
  or reconfigured DASD subsystem.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of z/VM with SSI clusters in their *
  *                 configuration must be shut down during       *
  *                 relocation of the SSI Persistent Data Record *
  *                 (PDR) to a new DASD volume.                  *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION: APPLY PTF                                    *
  ****************************************************************
  APAR VM65712 provides a support of relocating SSI Persistent
  Data Record (PDR) without an SSI cluster-wide planned outage.
  This support allows migrations to new or reorganized DASD
  subsystems to be planned and executed so that SSI cluster
  disruptions are avoided, thus simplifying the planning and
  approval process.
  

Problem conclusion

Temporary fix

• FOR RELEASE VM/ESA CP/ESA R630 :
  PREREQ: VM65401 VM65583 VM65358 VM65600 VM65514 VM65586
  CO-REQ: NONE
  IF-REQ: NONE
  

Comments

• The PTF for APAR VM65712 adds support that allows the SSI
  Persistent Data Record (PDR) to be relocated from its current
  DASD to another in a coordinated and non-disruptive manner.
  This support allows migrations to new or reorganized DASD
  subsystems to be planned and executed so that SSI cluster
  disruptions are avoided, thus simplifying the planning and
  approval process. Currently a cluster-wide shutdown is
  required when the SSI Persistent Data Record (PDR) is relocated
  to a new volume.
  
  The PTF for APAR VM65712 adds a new option to the SET SSI
  command to allow a new DASD volume to be specified as the PDR
  repository. The new DASD volume will be designated by volume
  serial number and must have been previously initialized by
  FORMSSI with the same cluster name. The SET SSI command with
  this new option will only be accepted when the SSI cluster is
  in stable mode, and all joined members have this support
  and valid accessibility (online and attached to the system) of
  the new volume. Also, all changes will be synchronized by the
  SSI cluster manager.
  
  CP Command and Utility Changes
  
   CP SET SSI Command
  
    A new option PDRVOLUME will be added to relocate PDR. Also,
    information in Usage Note 1 was clarified, and Usage Note 10
    and Example 3 were added.
  
   FORMSSI
  
    A new response line of the message HCP6619I will be added
    to display replacement PDR. Also a new error message
    HCP6620E will be displayed when a FORMSSI UPGRADE or
    FORMSSI UNLOCK is issued on an obsolete PDR.
  
  Command Response Changes
  
   There are no new responses added but a new line is added to
   the messages displayed by the FORMSSI utility to display
   replacement PDR information.
  
   HCPPDF6619I replacement: {None|<volid>}
  
  CP Message Changes
  
   New messages
  
   o New informational message 1630 will be displayed to the
      system operator when a SET SSI PDRVOLUME command returns
      successfully.
  
   HCP1630I PDR volume <volid1> has been replaced with PDR
   volume <volid2>.
  
   o New informational message 1631 might be displayed when a
      member joins the SSI cluster during system IPL.
  
   HCP1631I PDR on volume <volid1> is obsolete. Please
   update the system configuration file with replacement PDR
   volume <volid2>.
  
   o New error message 1640 with 6 variations might be
      displayed when a SET SSI PDRVOLUME is issued.
  
      HCP1640E Volume <volid> is already the PDR volume
  
      HCP1640E Replacement PDR volume <volid> is not properly
      formatted
  
      HCP1640E Replacement PDR volume <volid> is not online
  
      HCP1640E Replacement PDR volume <volid> is not attached
      to the system
  
      HCP1640E SET SSI PDRVOLUME feature is not available on
      all member systems
  
      HCP1640E SET SSI PDRVOLUME was rejected on system
      <sysname>
  
    o New error message 6620 will be displayed when a FROMSSI
       UPGRADE or FROMSSI UNLOCK is issued on an obsolete PDR.
  
      HCP6620E Persistent Data Record on device <vdev1> is
      obsolete
  
  o New wait state message 9053 with three variations may be
     displayed when there is an error on locating or accessing
     the replacement PDR.
  
      HCP9053W PDR on volume <volid1> is obsolete and
      replacement PDR volume <volid2> is not online
  
      HCP9053W PDR on volume <volid1> is obsolete and
      replacement PDR volume <volid2> is not attached to the
      system
  
      HCP9053W Non-obsolete PDR is not found
  
   Changed messages:
  
   o Message 6609E is modified as below.
  
     HCP6609E Existing Persistent Data Record cannot be
     upgraded because a newer PDR version was found on device
     <vdev>
  
   Configuration Statement Changes
  
    A new usage note will be added to the SSI system
    configuration statement as below.
  
    8. The SET SSI PDRVOLUME command can be used to replace the
        current PDR volume with a new PDR volume. After each
        successful SET SSI PDRVOLUME command, always update the
        SSI statement with the new PDR volume and make sure that
       the new PDR volume appears in either the CP-owned or user
       volume list in the system configuration file.
  
   Monitor Record Changes
  
    One new monitor record is added - MRSSIPDR - D11R8 - SSI PDR
    volume change
  
   Support Use Information in "z/VM: CP Planning and
   Administration"
  
     For information about relocating the SSI PDR,
     see the "Relocating the PDR" section in "Chapter 26.
     Setting up for System Image Clusters".
  
     For information about migrating the SSI common volume,
     see the "Considerations for Migrating the SSI Common
     Volume" section in "Chapter 26. Setting Up z/VM
     Single System Image Clusters".
  
   For more information, see:
   z/VM: CP Commands and Utilities Reference
   z/VM: CP Planning and Administration
   z/VM: CP Messages and codes
   z/VM: Performance
  

APAR Information

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

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

  UM34735 UM34736

Modules/Macros

• FORMSSI  HCPEQUAT HCPMES   HCPMESA  HCPMESB
  HCPMONEQ HCPMXRBK HCPMYX   HCPPDA   HCPPDF   HCPPDR   HCPPDRBK
  HCPPLM   HCPPLMBK HCPPLS   HCPPXMSY HCPRP    HCPSCFBK HCP1630I
  HCP1631I HCP1640E HCP6609E HCP6619I HCP6620E HCP9053W LOAD
  MRSSIPDR SRM      SSI
  

Fix information

• Fixed component name

  VM CP

• Fixed component ID

  568411202

Applicable component levels

• RA63 PSY UM34735

     UP16/03/30 P 1601

• R630 PSY UM34736

     UP16/02/08 P 1601

• R620 PSN

     UP

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.