IBM Support

OA44240: NEW FUNCTION APAR TO PROVIDE HYPERSWAP API SUPPORT FOR DS8K 7.4 MULTI-TARGET PPRC

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • New Function APAR
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users at HBB7780 and above that use Basic    *
    *                 HyperSwap or GDPS HyperSwap function.        *
    ****************************************************************
    * PROBLEM DESCRIPTION: New function APAR to provide HyperSwap  *
    *                      API support for DS8K 7.4 Multi-target   *
    *                      PPRC.                                   *
    *                      This APAR also provides infrastructure  *
    *                      updates in Basic HyperSwap to support   *
    *                      DS8K 7.4 Multi-target PPRC. Basic       *
    *                      HyperSwap support for Multi-target PPRC *
    *                      will be made available with APAR        *
    *                      OA46683.                                *
    *                      This support allows the establishment   *
    *                      and management of PPRC relationships    *
    *                      between one primary device and          *
    *                      multiple secondary devices. Note that   *
    *                      initial DS8K support allows PPRC        *
    *                      relationships between one primary and   *
    *                      two secondary devices. D/T2107          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    New function APAR to provide HyperSwap API support for DS8870
    7.4 Multi-target PPRC. This support allows the establishment
    and management of PPRC relationships between one primary
    device and multiple secondary devices.
    
    This APAR also provides infrastructure updates in Basic
    HyperSwap to support DS8K 7.4 Multi-target PPRC. Basic HyperSwap
    support for Multi-target PPRC will be made available with APAR
    OA46683.
    

Problem conclusion

Temporary fix

Comments

  • New function APAR to provide HyperSwap API support for DS8870
    7.4 Multi-target PPRC.
    IOS, Basic HyperSwap Management address space and HyperSwap API
    address space have been updated to support multiple PPRC
    relationships from one primary device. However, Basic HyperSwap
    will allow only one such relationship with this APAR.
    Subsequent APAR OA46683 will enable the full support in Basic
    HyperSwap.
    
    In order to identify and manage devices after a HyperSwap, IOS
    required devices in a PPRC relationship to have the same 4-digit
    device number if one of the devices resides in an alternate
    subchannel set. IOS also required one of the devices in the
    PPRC relationship to reside in the primary subchannel set 0.
    With Multi-target PPRC, devices in a PPRC relationship can both
    reside in alternate subchannel sets. However, they must still
    have the same 4-digit device number. Moreover, if one secondary
    device resides in an alternate subchannel set then the other
    secondary device must reside in another separate alternate
    subchannel set.
    
    Multi-target PPRC will require PPRC relationships to be
    established in one of two ways:
     1- All primary and secondary devices reside in the primary
        subchannel set.
     2- If one secondary device resides in an alternate subchannel
        set that is different from the primary device's
        subchannel set then the other secondary device must also
        reside in another separate alternate subchannel set.
    
    The following issues have also been corrected with this APAR:
      - Abend0C4 in IOSVCMBH during an ACTIVATE RECOVER=SOURCE
        request.
      - Abend7C6-nn in IOSHSSUB during UNPIN due to residual data in
        the ESTAE parameter list.
    
    Documentation updates:
      Note: This is a subset of the documentation changes. For full
            updates, please view the actual PTF ++HOLD information.
    
      New/Changed Messages: MSGIOS500I, MSGIOS583I,
                            MSGIOSHM0201I, MSGIOSHM0303I,
                            MSGIOSHM0304I, MSGIOSHM0399I,
                            MSGIOSHM0401I, MSGIOSHM0420I,
                            MSGIOSHM0806I, MSGIOSHM0818I,
                            MSGIOSHM0819I
    
    In z/OS MVS System Commands (SA22-7627, SA38-0666), the
    chapter describing the DISPLAY HS command:
    
     - New parameter NAME(configname) is added to the command.
    
    ============================================================
    In z/OS MVS System Commands (SA22-7627, SA38-0666), the
    chapter describing the SETHS command:
    
     - New parameter NAME(configname) is added to the command.
    
    ============================================================
    In z/OS HCD Planning (GA22-7525, GA32-0907), chapter 4
    Dynamically changing an I/O configuration, section Making
    dynamic changes to I/O devices, the following paragraph:
    
      After a HyperSwap failover swap has occurred, ensure
      that if a Special Secondary (3390D) device is being
      added, a 3390B PPRC primary device with the same
      four-digit device number is also being added. If one
      device in a Special PPRC pair (3390B/3390D) is not
      being added when the other device in the pair is
      being added, the dynamic activate will fail.
    
    will be replaced with:
    
      In general, devices, including PPRC secondary
      (3390D) devices in an alternate subchannel set, can
      be added via Dynamic Activate at any time.
      However, since 3390D devices are accessible
      through their corresponding partner devices in
      the primary subchannel set, adding such devices
      without their primary partners either already
      existing or being added at the same time will
      leave those 3390D devices inaccessible and
      therefore not usable.
    
      After a HyperSwap has occurred, adding PPRC
      secondary (3390D) devices to the active
      subchannel set while their corresponding partners
      in the primary subchannel set already exist will
      not be allowed since the newly added devices
      which may not contain the most up to date data
      will replace their primary partner devices as the
      active devices.
    
    
    Also, the following paragraph:
    
      After a HyperSwap failover swap has occurred, ensure
      that if a Special Secondary (3390D) device is being
      deleted, a 3390B PPRC primary device with the same
      four-digit device number is also being deleted. If
      one device in a Special PPRC pair (3390B/3390D) is
      not being deleted when the other device in the pair
      is being deleted, the dynamic activate will fail.
    
    will be replaced with:
    
      In general, PPRC secondary (3390D) devices can be
      deleted with or without their corresponding primary
      partners also being deleted.
    
      After a HyperSwap has occurred, deleting devices
      in the primary subchannel set while their PPRC
      secondary (3390D) devices exist in the active
      subchannel set is not allowed since the 3390D
      devices will be left inaccessible without their
      corresponding primary partners if and when the
      system is re-IPL'ed.
    
    =============================================================
    In MVS System Messages, Volume 9 (SA22-7639, SA38-0676),
    the following messages are updated as follows:
    
    - Message IOS500I is updated to include reasons 148 and 149.
    
    - Message IOS583I is deleted.
    
    - Message IOSHM0201I is updated to include failure reasons:
        Reason: Configuration priority is not valid
        Reason: Prohibited by multi-target policy
        Reason: Configuration priority conflicts with active
                configuration
        Reason: Configuration replacement must be for the same
                type
      and reason codes 84 and 88.
      Reason code 74 is deleted.
    
    - Message IOSHM0303I is updated to include new text lines:
        Number of configurations: 'numofconfig'
        Swap Highest Priority:  Yes|No
        Disallow Non-MultiTarget System:  Yes|No
    
    - Message IOSHM0304I is updated to include new response lines
      that include configuration name, type, priority, HyperSwap
      status and number of systems to be removed.
    
    - Message IOSHM0399I is updated to include a new reason
      for command rejection:
        'name not found'
    
    - Message IOSHM0401I is updated to include a configuration
      name.
    
    - Message IOSHM0420I is updated to include a new reason
      for HyperSwap failure:
        'configuration not found or not usable'
    
    - Message IOSHM0806I is updated to include a configuration
      name.
    
    - Message IOSHM0818I is added to indicate a HyperSwap
      configuration is selected as the preferred configuration
      for HyperSwap.
    
    - Message IOSHM0819I is added to indicate a HyperSwap
      configuration is no longer considered the preferred
      configuration for HyperSwap.
    
     KEYWORDS: HYPERSWP/K
    ×**** PE15/02/23 FIX IN ERROR. SEE APAR OA47113  FOR DESCRIPTION
    ×**** PE15/07/24 FIX IN ERROR. SEE APAR OA48281  FOR DESCRIPTION
    ×**** PE15/09/21 FIX IN ERROR. SEE APAR OA48844  FOR DESCRIPTION
    ×**** PE15/10/22 FIX IN ERROR. SEE APAR OA49183  FOR DESCRIPTION
    ×**** PE16/03/29 FIX IN ERROR. SEE APAR OA49885  FOR DESCRIPTION
    ×**** PE16/03/29 FIX IN ERROR. SEE APAR OA50196  FOR DESCRIPTION
    

APAR Information

  • APAR number

    OA44240

  • Reported component name

    IOS

  • Reported component ID

    5752SC1C3

  • Reported release

    780

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / New Function / Xsystem

  • Submitted date

    2014-01-14

  • Closed date

    2014-12-18

  • Last modified date

    2016-08-15

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

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

    OA46173 UA90740 UA90741 UA90742

Modules/Macros

  • BHIP1HSB BHIP1INT IEAIPL03 IEAIPL71 IEAVNP02
    IECVIOPM IEEDMDEV IEEVVCU  IOSCACDR IOSCDCM  IOSCRRSC IOSCSSCB
    IOSDDSE  IOSE148  IOSE149  IOSHFMTR IOSHIAIT IOSHIMSG IOSHIXUS
    IOSHMAIT IOSHMBLK IOSHMCFG IOSHMCF2 IOSHMCMT IOSHMCNS IOSHMCTL
    IOSHMDSP IOSHMEDS IOSHMEPT IOSHME64 IOSHMGPE IOSHMHBT IOSHMHST
    IOSHMIOS IOSHMISC IOSHMNTE IOSHMOPR IOSHMPAR IOSHMPCR IOSHMPED
    IOSHMRSM IOSHMSND IOSHMSUS IOSHMXUS IOSHSADR IOSHSAPI IOSHSENF
    IOSHSPCR IOSHSRDR IOSHSSUB IOSHVMTT IOSIUCB  IOSVBIND IOSVCAPR
    IOSVCAPU IOSVCMBH IOSVCMBO IOSVCMES IOSVCMMN IOSVCMUB IOSVCMUD
    IOSVCMUP IOSVCMV1 IOSVCMV2 IOSVCSR  IOSVCSRL IOSVDATA IOSVFMTC
    IOSVFMTH IOSVFMTR IOSVHASH IOSVLSSR IOSVNPTH IOSVPIN  IOSVSCAN
    IOSVSDEX IOSVSWAP IOSVUCBS IOSVUPCR IOSVUSER
    

Publications Referenced
GA22752500GA32090700SA22762700SA38066600SA22763900
SA38067600    

Fix information

  • Fixed component name

    IOS

  • Fixed component ID

    5752SC1C3

Applicable component levels

  • R78H PSY UA90742

       UP15/01/09 P F501

  • R780 PSY UA90740

       UP15/01/09 P F501

  • R790 PSY UA90741

       UP15/01/09 P F501

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.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"780","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"780","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
15 August 2016