IBM Support

PH63733: WHEN BATCH JOB ISSUE SQL, AN ABEND0C4 OCCURS ON CREATE THREAD

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • An abend0c4 can occur on create thread after application issue
    SQL. The db2 control block structure is not being cleaned up
    correctly for RRS batch job.
    The abend0C4 was result of a reuse of an ASCE from a prior job
    that used RRSAF. All of the resources/storage from the prior job
    were released by MVS at jobstep end.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Db2 for z/OS RRSAF users.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: ABEND0C4 in Create Thread module        *
    *                      DSNVCRTH during Identify processing.    *
    *                      The abend0C4 was result of a reuse of   *
    *                      an ASCE from a prior job that used      *
    *                      RRSAF                                   *
    ****************************************************************
    * RECOMMENDATION: Apply corrective PTF when available          *
    ****************************************************************
    This APAR is resolved as a serviceability APAR that is adding
    diagnostic trace footprints to Db2 EOT (End of Task)
    processing.
    The ABEND0C4 in DSNVCRTH occurred because the Db2 ASCE was not
    cleaned up during EOT processing for a previous batch job,
    and the next batch job that executes in the JES initiator
    tried to connect to Db2.
    This problem may occur with some RRSAF multi-threaded batch
    jobs that do not explicitly call RRSAF Terminate Thread and
    Terminate Identify.
    

Problem conclusion

  • Db2 will be updated to add diagnostic footprints to EOT
    processing.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH63733

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    D10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-10-16

  • Closed date

    2025-07-30

  • Last modified date

    2025-08-31

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

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

    UO04326 UO04327

Modules/Macros

  • DSN3ID80 DSN3SSES DSN3SSI1 DSN3SSI2 DSNYALLI
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RC10 PSY UO04326

       UP25/08/07 P F508

  • RD10 PSY UO04327

       UP25/08/07 P F508

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":"BU048","label":"IBM Software"},"Product":{"code":"SSEPEK","label":"DB2 for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"D10","Line of Business":{"code":"LOB76","label":"Data Platform"}}]

Document Information

Modified date:
31 August 2025