PM80853: DFS2503W DYNAMIC ALLOCATION FAILED FOR A-SIDE HALDB PARTITION WHEN FDBR IN USE. M-SIDE SHOULD BE ALLOCATED

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Emergency restart had a HALDB partition allocation error.
    OLR had been used and complete successfully. The current
    dataset is the M-side.The restart error is
    DFS2503W DYNAMIC ALLOCATION   FAILED FOR
    (DFS2503W) DATASET NAME xxxxxxxxxxxxxxxxxxxx.A00001
    (DFS2503W) DATABASE x REASON CODE 1708 IMSA
    The M-side of the dataset should be allocated. This error only
    occcurs if FDBR is in use.
    We suspect an additional symptom is an ABENDU0845 RC33
    (invalid RPL) with DDIRORAM bit ON and AMP pointing to A-J,X
    data sets.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All IMS V11 users of High Availability Large *
    *                 Databases ( HALDB ) who use HALDB online     *
    *                 reorganization ( OLREORG OLR ) on an IMS     *
    *                 system which is tracked by a Fast Database   *
    *                 Recovery ( FDBR ) region.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: The following was received during       *
    *                      restart of an IMS that was canceled     *
    *                      with an F IMS,STOP and FDBR completed   *
    *                      its processing. OLR was run to          *
    *                      successful completion and the data set  *
    *                      listed in the MSGDFS2503W was deleted   *
    *                      at the end of the OLR.                  *
    *                      DFS2503W DYNAMIC ALLOCATION FAILED FOR  *
    *                      (DFS2503W) DATASET NAME xxxxxxx.A00001  *
    *                      (DFS2503W) DATABASE x REASON CODE 1708  *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    The user has an IMS that is monitored by an FDBR system.  An OLR
    is run and completes and the old active A-J data sets are
    deleted.  Now the active data sets are M-V.  Then IMS is brought
    down with an F IMS,STOP command and FDBR completed its database
    recovery processing.
    The IMS is restarted and during restart processing the following
    messages are received because the allocation request is for the
    deleted A-J data sets when it should be for the active M-V data
    sets.
    DFS2503W DYNAMIC ALLOCATION   FAILED FOR
    (DFS2503W) DATASET NAME xxxxxxxxxxxxxxxxxxxx.A00001
    (DFS2503W) DATABASE x REASON CODE 1708 IMSA
    *
    The problem occurs because of code in the DFSOLRAU routine in
    DFSDBAU0. During restart authorization the DFSOLRAU routine is
    called after the authorization call to DBRC has been made. The
    routine will update the DDIR to reflect what DBRC returned with
    regards to the following OLR flags:
    DDIRORAM, DDIROLRA, DDIROLRM, DDIROLRO.
    Upon entry to the routine, DDIRORAM is off, indicating A-J data
    sets are active.  DBRC indicates M-V data sets are active and
    the DMB points to the M side.  Since DDIRORAM is off the routine
    swaps DMBs and turns DDIRORAM on.  Now the DMB points to the A
    side but DDIRORAM indicates M-V data sets are active.  This
    results in allocation being attempted for the deleted A-J data
    sets which causes MSGDFS2503W to be issued.
    *
    Additional symptoms:
    In the case where the old input data sets were not deleted,
    allocation could be successful and could result in a variety
    of errors because the wrong data sets were read or updated.
    The old input data sets could be missing updates, or have
    pointer errors because OLR only updates the active record
    pointers.
    Note: This can only happen on a restarted IMS that was being
    monitored by an FDBR system and an OLR was run to completion
    prior to the IMS abnormally terminating.
    

Problem conclusion

  • GEN:
    KEYWORDS:
    
    *** END IMS KEYWORDS ***
    The DFSOLRAU routine in DFSDBAU0 has been changed to correctly
    set DDIRORAM and point to the correct data sets according to
    what DBRC has returned.
    
    DFSORR00 was changed to clean up some comments and correct the
    release status.  No code was changed.
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PM80853

  • Reported component name

    IMS V11

  • Reported component ID

    5635A0200

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-01-17

  • Closed date

    2013-02-01

  • Last modified date

    2013-03-04

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

    PM70750

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

    UK91346

Modules/Macros

  •    DFSDBAU0 DFSORR00
    

Fix information

  • Fixed component name

    IMS V11

  • Fixed component ID

    5635A0200

Applicable component levels

  • R100 PSY UK91346

       UP13/02/07 P F302

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.



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

IMS

Software version:

100

Reference #:

PM80853

Modified date:

2013-03-04

Translate my page

Machine Translation

Content navigation