OA46030: BCPII CPC NAME CHANGE SYSTEM STATUS DETECT SSD

APAR status

• Closed as documentation error.

Error description

• z/OS MVS Programming: Callable Services for High-Level
  Languages, SA23-1377-xx
  
  Chapter 19. Base Control Program Internal Interface (BCPii)
  |-> Setup and installation
  |-> BCPii Configuration Considerations  *NEW*
      |-> Dynamic modification of CPC name *NEW*
  
  An installation that implements a dynamic CPC name change
  on a CPC which either has BCPii active on one or more of
  its z/OS images or is a CPC that is targeted by other
  images on remote CPCs in the HMC network needs to
  review the following considerations before performing the
  name change.
  
  BCPii does not currently provide support for changing
  the name of a CPC with ACTIVE images. Therefore, the only
  way BCPii can "learn" of the new name change is to
  recycle the HWIBCPII address space.  Please evaluate the
  following 3 sections to determine which applies to your
  installation.
  
  1) Applications that dynamically learn of new CPC names when
  BCPii is restarted.
  ---------------------------------------------------------
  If ALL BCPii applications on a z/OS image will learn of the
  new CPC name dynamically when BCPii is restarted, perform
  the following steps:
    1) Review security definitions impacted by CPC name change.
       See "Security definition considerations for CPC name
       changes" for details.
    2) Stop BCPii.  See "Ending the BCPii address space" for
       details.
    3) Change the CPC name.
    4) Make the required security definition changes if
       necessary.
    5) Restart BCPii. See "Restarting the HWIBCPii address
    space" for details.
  
  2) Applications that do not dynamically learn of new CPC
  names when BCPii is restarted.
  ---------------------------------------------------------
  If any BCPii application maintains a persistent copy of the
  changed CPC name (whether it is the local or remote name)
  regardless of BCPii being restarted will need to also be
  restarted.
    1) Review security definitions impacted by CPC name change.
       See "Security definition considerations for CPC name
       changes" for details.
    2) Stop the BCPii application(s).
    3) Stop BCPii.  See "Ending the BCPii address space" for
       details.
    4) Change the CPC name.
    5) Make the required security definition changes if
       necessary.
    6) Restart BCPii. See "Restarting the HWIBCPii address
    space" for details.
    7) Restart the BCPii application(s).
  
  3) System Status Detect partitioning protocol (SSD)
  ---------------------------------------------------------
  In the case of XCF's System Status Detect partitioning
  protocol, while SSD can be recycled through the use of the
  SETXCF command, SSD will not pick up the CPC name change
  through this mechanism. Therefore, an IPL is necessary in
  order for XCF to learn of the CPC name change.  If the
  installation has SSD active, it is necessary to perform a
  rolling IPL of all images in the sysplex on the CPC whose
  name was changed that utilize SSD.  This will allow XCF to
  pick up the name change on all systems in the sysplex
  utilizing SSD.
  
  Security definition considerations for CPC name changes
  --------------------------------------------------------
  It is necessary to review the security definitions for
  HWI.TARGET.netid.nau, HWI.TARGET.netid.nau.imagename, and
  HWI.CAPREC.netid.nau.caprecname profiles whenever a CPC
  name change is implemented to ensure the proper security
  configuration is in effect.  Review possible profiles which
  will need to be modified before the name change takes
  place.  Ensure any changes to security profiles are made
  prior to the restart of BCPii.  See "Setting up authority
  to use BCPii" for general information on configuring the
  appropriate security definitions.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of z/OS BCPii that dynamically         *
  *                 modify the name of a CPC without             *
  *                 re-IPLing the images on that CPC.            *
  ****************************************************************
  * PROBLEM DESCRIPTION: The System z hardware provides a        *
  *                      mechanism to dynamically change         *
  *                      the CPC name, while images (LPARs)      *
  *                      active and running.  z/OS BCPii         *
  *                      needs to document the procedure         *
  *                      required when one or more of the        *
  *                      images running on this CPC are          *
  *                      running with BCPii active.              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  See the problem description.
  

Problem conclusion

• The following is the documenation update required by this
   APAR.
  
   z/OS MVS Programming: Callable Services for High-Level
   Languages, SA23-1377-xx
  
   Chapter 19. Base Control Program Internal Interface (BCPii)
   |-> Setup and installation
   |-> BCPii Configuration Considerations  *NEW*
       |-> Dynamic modification of CPC name *NEW*
  
   An installation that implements a dynamic CPC name change
   on a CPC which either has BCPii active on one or more of
   its z/OS images or is a CPC that is targeted by other
   images on remote CPCs in the HMC network needs to
   review the following considerations before performing the
   name change.
  
   BCPii does not currently provide support for changing
   the name of a CPC with ACTIVE images. Therefore, the only
   way BCPii can "learn" of the new name change is to
   recycle the HWIBCPII address space.  Please evaluate the
   following 3 sections to determine which applies to your
   installation.
  
   1. Applications that dynamically learn of new CPC names when
   BCPii is restarted.
   ---------------------------------------------------------
   If ALL BCPii applications on a z/OS image will learn of the
   new CPC name dynamically when BCPii is restarted, perform
   the following steps:
     1. Review security definitions impacted by CPC name
        change.  See "Security definition considerations for
        CPC name changes" for details.
     2. Stop BCPii.  See "Ending the BCPii address space" for
        details.
     3. Change the CPC name.
     4. Make the required security definition changes if
        necessary.
     5. Restart BCPii. See "Restarting the HWIBCPii address
     space" for details.
  
   2. Applications that do not dynamically learn of new CPC
   names when BCPii is restarted.
   ---------------------------------------------------------
   If any BCPii application maintains a persistent copy of the
   changed CPC name (whether it is the local or remote name)
   regardless of BCPii being restarted will need to also be
   restarted.
     1. Review security definitions impacted by CPC name
        change.  See "Security definition considerations for
        CPC name changes" for details.
     2. Stop the BCPii application(s).
     3. Stop BCPii.  See "Ending the BCPii address space" for
        details.
     4. Change the CPC name.
     5. Make the required security definition changes if
        necessary.
     6. Restart BCPii. See "Restarting the HWIBCPii address
     space" for details.
     7. Restart the BCPii application(s).
  
  
   3. System Status Detect partitioning protocol (SSD)
   ---------------------------------------------------------
   In the case of XCF's System Status Detect partitioning
   protocol, while SSD can be recycled through the use of the
   SETXCF command, SSD will not pick up the CPC name change
   through this mechanism. Therefore, an IPL is necessary in
   order for XCF to learn of the CPC name change.  If the
   installation has SSD active, it is necessary to perform a
   rolling IPL of all images in the sysplex on the CPC whose
   name was changed that utilize SSD.  This will allow XCF to
   pick up the name change on all systems in the sysplex
   utilizing SSD.
  
   Security definition considerations for CPC name changes
   --------------------------------------------------------
   It is necessary to review the security definitions for
   HWI.TARGET.netid.nau, HWI.TARGET.netid.nau.imagename, and
   HWI.CAPREC.netid.nau.caprecname profiles whenever a CPC
   name change is implemented to ensure the proper security
   configuration is in effect.  Review possible profiles which
   will need to be modified before the name change takes
   place.  Ensure any changes to security profiles are made
   prior to the restart of BCPii.  See "Setting up authority
   to use BCPii" for general information on configuring the
   appropriate security definitions.
  

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:

Fix information

Applicable component levels