IBM Support

OA61375: WHEN A FREEZE WITH SUSPEND FAILS, HYPERSWAP PROCESSING STOPS WITHOUT ISSUING A THAW AND RESUME IO LEAVING UCBS AT DDR LEVEL.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Systems will have multiple IO related errors after a Freeze with
    Suspend request where there is a Freeze failure message:
    
    IOSHM0308I PPRC suspension requested for replication session XXX
               FreezeAll failed. Reason: 0024.
    
    After a CSM initiated Freeze with Suspend, if the Freeze fails
    on any system in the SYSPLEX, resume processing does not run
    leaving all UCB's of devices in the HyperSwap configuration at
    DDR (9) level which prevents all normal level IO's from
    resuming.
    
    KNOWN IMPACT:
    z/OS HyperSwap users with CSM Copy Services Manager
    are affected.
    z/OS HyperSwap users with GDPS Geographically Dispersed
    Parallel Sysplex are -NOT- affected.
    

Local fix

  • BYPASS/CIRCUMVENTION:
    None
    
    RECOVERY ACTION:
    IPL the systems in the SYSPLEX.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users at HBB77B0 and above who use z/OS                      *
    * HyperSwap                                                    *
    * z/OS HyperSwap users with CSM Copy Services Manager          *
    * are affected.                                                *
    * z/OS HyperSwap users with GDPS Geographically Dispersed      *
    * Parallel Sysplex are -NOT- affected.                         *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Devices unavailable after failed                             *
    * PPRC Suspension processing                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * After a PPRC Suspension event, if the Freeze step fails on   *
    * any                                                          *
    * system, then the Run or Stop step may not be performed. This *
    *                                                              *
    * may leave devices at a high UCB level, preventing            *
    * application                                                  *
    * I/O.                                                         *
    *                                                              *
    ****************************************************************
    

Problem conclusion

  • PPRC Suspension processing is updated to continue with the
    Run processing after a failed Freeze, preventing devices from
    being stuck at a high UCB level.  Message IOSHM0423I will now
    be issued to identify a system that timed out during PPRC
    suspension processing.
    
     The following messages will be updated:
     - IOSHM0423I
    
       IOSHM0423I hh:mm:ss.nn System {sysname} timed out doing
                  HyperSwap function
    
    |  Explanation: During HyperSwap or PPRC Suspension processing
    |           the indicated system member did not respond within
    |           the defined time period.
    
       In the message text:
         hh:mm:ss.nn
           The actual time of the request. The time is represented
           as hours 'hh'(00-23), minutes 'mm'(00-59), seconds 'ss'
           (00-59), and hundredths of a second 'nn'(00-99).
    
    
       System action: Processing continues. Additional messages
               and/or diagnostic 2E0 abend dumps may be requested.
               Recovery actions depend on the swap policy option in
               effect when the time out occurred.
    
       Operator response: Follow installation procedure for
                     reporting problems.
    
       System programmer response: Follow installation procedure
                     for analyzing problems.
    
    |  Module: IOSHMHST, IOSHMEPT
    
       Routing code: 2
    
       Descriptor code: 4
    
    HYPERSWP/K
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    OA61375

  • Reported component name

    IOS

  • Reported component ID

    5752SC1C3

  • Reported release

    7C0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-05-12

  • Closed date

    2021-08-02

  • Last modified date

    2022-01-21

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

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

    UJ06261 UJ06262 UJ06263

Modules/Macros

  • IOSHMEPT
    

Fix information

  • Fixed component name

    IOS

  • Fixed component ID

    5752SC1C3

Applicable component levels

  • R7D0 PSY UJ06263

       UP21/08/18 P F108 ¢

  • R7C0 PSY UJ06262

       UP21/08/18 P F108 ¢

  • R7B0 PSY UJ06261

       UP21/08/18 P F108 ¢

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":"IOS"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"7C0"}]

Document Information

Modified date:
22 January 2022