IBM Support

PH51891: S0C4 MAY OCCUR ON CLOSE OF QSAM FILE AFTER B37 ABEND ISSUED ON WRITE

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • A COBOL 6.x program receives a B37 abend on a WRITE statement,
    writing past the end of volume.  After control returns to the
    COBOL program, which issues a CLOSE statement of the file, a
    s0c4 exception may occur in s0c4 in IGZXQCLS x'A4E'.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of Enterprise COBOL 5 and later        *
    *                 releases running programs which use QSAM     *
    *                 files and get an out of space abend          *
    *                 (e.g., B37 or D37).                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: When closing a QSAM file when the Data  *
    *                      Management buffers are full, the out    *
    *                      of space abend may result in a          *
    *                      subsequent 0C4 abend in IGZXQCLS        *
    *                      within the COBOL Runtime while          *
    *                      executing the CLOSE statement in the    *
    *                      COBOL application.                      *
    ****************************************************************
    * RECOMMENDATION: Install the provided PTF.                    *
    ****************************************************************
    When the Data Management routines issues the B37 or D37 out of
    space abend for a QSAM file that is full, the DCB was
    closed by Data Management and an abend resulted when COBOL
    tried to update a field in the DCB within the COBOL Runtime.
    This would result in an  ABEND0C4 in IGZXQCLS within the
    COBOL Runtime.
    
    COB0501T/K COB0502T/K COB0601T/K COB0602T/K COB0603T/K
    COB0604T/K
    

Problem conclusion

  • The COBOL Runtime close processing logic was corrected to
    bypass the update to the DCB if the file is closed by
    Data Management.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH51891

  • Reported component name

    LE ENT COBOL LI

  • Reported component ID

    568819812

  • Reported release

    7D0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-01-12

  • Closed date

    2023-03-17

  • Last modified date

    2023-03-27

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

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

    UI91010 UI91011

Modules/Macros

  • IGZCEV4  IGZCJNI2 IGZLLIBV IGZXAPI  IGZXCA31 IGZXCDA  IGZXD24
    IGZXDMR  IGZXJNI2 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

  • R7C0 PSY UP

       C

  • R7D0 PSY UP

       C

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SS6SG3","label":"Enterprise COBOL for z\/OS"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"7D0","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
27 March 2023