IBM Support

PI94692: ABENDOC4 MAY OCCUR IN DLISAS DLS TASK IF A DATABASE IN RECALL HAS /DBR COMMAND COMPLETED BEFORE RECALL IS COMPLETE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • THE SEQUENCE OF EVENTS FOR THIS PROBLEM APPEARS TO BE...
    1. DBD IS BEING RECALLED
        2. /DBR COMMAND IS COMPLETED FOR DATABASE
        3. ABEND0C4 MAY OCCUR
    THIS PROBLEM OCCURS BECAUSE MODULE DFSDYA00 HAS A COPY OF THE
    ADDRESS OF THE DFSMDA MEMBER FOR THE DATABASE.  WHEN THE /DBR DB
    COMMAND OCCURS, IT APPEARS THE DFSMDA MEMBER IS RELEASED.  WHEN
    THE RECALL SUBSEQUENTLY COMPLETES, DFSDYA00 TRIES TO REFERENCE
    THE RELEASED DFSMDA MEMBER CAUSING ABEND0C4.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All IMS v13 users using DBR command and      *
    *                 recalling database.                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: Abend 0C4 occurs when DBR command       *
    *                      is issued during recall of a database.  *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    An ABEND 0C4 may result when a database is being recalled and
    a /DBR command is issued against the same database. The module
    DFSDYA00 reference DFSMDA member for the database recall
    request, but the DFSMDA member is released when the /DBR
    command is processed. DFSDYA00 tries to reference the DFSMDA
    member after it was released by the /DBR command and receives
    the 0C4 ABEND.
    

Problem conclusion

  • GEN:
    KEYWORDS:
    
    *** END IMS KEYWORDS ***
    The module DFSDYA00 has been modified to check whether the
    allocation request block is available before using it.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI94692

  • Reported component name

    IMS V13

  • Reported component ID

    5635A0400

  • Reported release

    300

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-03-05

  • Closed date

    2018-04-30

  • Last modified date

    2018-06-04

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

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

    PI96376 PI96377 UI55573

Modules/Macros

  •    DFSDYA00
    

Fix information

  • Fixed component name

    IMS V13

  • Fixed component ID

    5635A0400

Applicable component levels

  • R300 PSY UI55573

       UP18/05/02 P F805

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":"APARs - z\/OS environment"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"300","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
14 December 2020