IBM Support

PI71356: After SVC LOAD and DELETE of a COBOL v5+ NORENT program abend0C4in enclave termination

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The Migration Manual notes that an SVC LOAD and DELETE of a
    COBOL v5+ NORENT program is permitted, however at enclave
    termination the run-time attempts to access control blocks that
    were part of the now DELETEd executable, leading to an abend0c4.
    
    The COBOL legacy run-time is not affected.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Enterprise COBOL users running assembler     *
    *                 programs that do SVC delete to remove COBOL  *
    *                 V5+ NORENT programs.                         *
    *                                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Runtime ABEND0C4: When an Enterprise    *
    *                      COBOL V5+ NORENT program is deleted     *
    *                      from storage by an SVC delete, the      *
    *                      application may fail with an 0C4 ABEND  *
    *                      during LE enclave termination.          *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION: Apply the provided PTF                       *
    ****************************************************************
    When a COBOL NORENT program is deleted from storage by an SVC
    delete, LE is not notified to do the proper resource cleanup at
    the time of the delete. Subsequently during LE enclave
    termination, the COBOL runtime would attempt to cleanup
    resources used during the enclave execution, for example, to
    close any files that were left open. However, the NORENT
    storage containing relevant control blocks has already been
    released, resulting in access to those control blocks raising
    an 0C4 exception.
    

Problem conclusion

  • The COBOL runtime has been corrected to protect against
    accesses to potentially unavailable storage.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI71356

  • Reported component name

    LE ENT COBOL LI

  • Reported component ID

    568819812

  • Reported release

    790

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-10-26

  • Closed date

    2016-11-16

  • Last modified date

    2016-12-01

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

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

    UI42659 UI42660

Modules/Macros

  • IGZCEV4  IGZLLIBV IGZXAPI  IGZXDMR  IGZXD24
    IGZXLPIO IGZXLPKA IGZXLPKB IGZXLPKC IGZXLPKD IGZXLPKE IGZXLPKF
    IGZXLPKG IGZXPK2
    

Fix information

  • Fixed component name

    LE ENT COBOL LI

  • Fixed component ID

    568819812

Applicable component levels

  • R7A0 PSY UI42659

       UP16/11/26 P F611

  • R790 PSY UI42660

       UP16/11/26 P F611

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":"SSCVR7X","label":"Runtime"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
14 December 2020