IBM Support

PH45668: ABEND0C4 IN IGVCPDEL OR ABENDC78 IN EZASMI RESMGR

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When a task that had issued EZASMI calls ends without having
    done an EZASMI TYPE=TERMAPI, the EZASMI resource manager is
    invoked and calls program EZBSORM2 to clean up the EZASMI
    resources.  This processing includes deleting the EZBSOH03
    AUTODATA cell pool and releasing the EZBSOH03 AUTODATA storage.
    Sometimes these structures get released by customization exits
    before EZBSORM2 is called (this is particularly common in IMS
    environments).  If the cell pool has already been deleted, then
    the CPOOL DELETE might result in a S0C4 ABEND in IGVCPDEL.  If
    the AUTODATA storage has already been released. then the STORAGE
    RELEASE might result in a SC78 ABEND.  If the task is ending due
    to previous ABENDs, then the TCPIP stack might leave the SYSPLEX
    after message EZZ4215I.
    
    ANALYSIS:
    EZBSORM2
    CPOOL DELETE
    CPOOL_ID_PTR
    STORAGE_RELEASE
    FIXED_AUTODATA
    
    KNOWN IMPACT:
    Dump taken.
    TCPIP leaves the SYSPLEX.
    
    ADDITIONAL SYMPTOMS:
    ABEND0C4
    ABENDS0C4
    0C4
    S0C4
    EZZ4215I
    MSGEZZ4215I
    

Local fix

  • BYPASS/CIRCUMVENTION:
    If possible, add a recovery routine to the application that does
    an EZASMI TYPE=TERMAPI.
    
    RECOVERY ACTION:
    Use the "VARY TCPIP,,SYSPLEX,JOINGROUP" command to rejoin the
    SYSPLEX.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users of the IBM Communications Server for z/OS Version  *
    * 2 Release 4 and 5 IP: EZASMI                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * ABEND0C4 in IGVCPDEL or ABENDC78 in EZBSORM2 during EZASMI   *
    * resource manager processing.                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply PTF.                                                   *
    ****************************************************************
    When a task that had issued EZASMI calls ends without having
    done an EZASMI TYPE=TERMAPI, the EZASMI resource manager is
    invoked and calls program EZBSORM2 to clean up the EZASMI
    resources.  This processing includes deleting the EZBSOH03
    AUTODATA cell pool and releasing the EZBSOH03 AUTODATA storage.
    Sometimes these structures get released by customization exits
    before EZBSORM2 is called (this is particularly common in IMS
    environments).  If the cell pool has already been deleted, then
    the CPOOL DELETE might result in a S0C4 ABEND in IGVCPDEL.  If
    the AUTODATA storage has already been released. then the STORAGE
    RELEASE might result in a SC78 ABEND.  If the task is ending due
    to previous ABENDs, then the TCPIP stack might leave the SYSPLEX
    after message EZZ4215I.
    

Problem conclusion

  • EZASMI resource manager program EZBSORM2 has been updated with a
    recovery exit to allow normal processing to continue if the
    delete of the AUTODATA cell pool or the release of the AUTODATA
    storage fails.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH45668

  • Reported component name

    TCP/IP MVS

  • Reported component ID

    5655HAL00

  • Reported release

    240

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-04-13

  • Closed date

    2022-06-27

  • Last modified date

    2022-08-02

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

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

    UI81203 UI81204

Modules/Macros

  • EZBSORM2
    

Fix information

  • Fixed component name

    TCP/IP MVS

  • Fixed component ID

    5655HAL00

Applicable component levels

  • R250 PSY UI81204

       UP22/07/30 P F207

  • R240 PSY UI81203

       UP22/07/30 P F207

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":"SSSN3L","label":"z\/OS Communications Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"240","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
02 August 2022