PK79879: FDBR TRIES TO ALLOCATE "A" SIDE INSTEAD OF ACTIVE "M" SIDE DATA SET DURING DYNAMIC BACKOUT AFTER AN EARLIER OLR.

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Ran OLR for S83A001 (A -> M). Then started a BMP A460412A to
    update S83A001 with PSB FC5280. Put the BMP into a hold with
    an WTOR and then cancelled IN01CTL. FDBR wanted to backout the
    uncommitted updates from the BMP and abended trying to allocate
    the allocate the A-dataset instead of the active M-Dataset
    
    PK61511 is on ....
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All IMS V10 HALDB users running Online       *
    *                 Reorganization ( OLR ) with FDBR tracking    *
    *                 the active IMS.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: After a CTL region failure / abend on   *
    *                      the active IMS while updates are being  *
    *                      made to a HALDB partition that had      *
    *                      previously been successfully OLR'ed,    *
    *                      the tracking FDBR region failed during  *
    *                      dynamic backout processing trying to    *
    *                      allocate the A-J data sets when the     *
    *                      M-V data sets were active.              *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    The tracking FDBR region failed with the following:
    
    DFS2503W DYNAMIC ALLOCATION   FAILED FOR
    (DFS2503W) DATASET NAME XXX.YYYY.ZZZZZZZZ.A00001
    (DFS2503W) DATABASE AAAAAAA  WITHIN PSB BBBBBB   REASON
               CODE 1708
    DFS629I IMS CTL TCB DUMP  - TYPE UNK
    DFS629I PSW AT ERROR = *** NO SDWA ***
    DFS3932I IMS DUMP REQUEST COMPLETED - RETURN CODE = 000
    DFS984I UNABLE TO OPEN DATA BASE AAAAAAA , PROGRAM BBBBBB
            FOR BACKOUT.
    DFS979I BATCH MESSAGE PROGRAM BBBBBB   WAS ACTIVE AT TIME OF
            FAILURE.
    DFS981I  DBD=AAAAAAA  WITHIN PSB=BBBBBB   STOPPED DUE TO BACKOUT
             FAILURE.
    
    A successful OLREORG had completed on the active IMS prior
    to the active IMS abend and the active OLR data sets for the
    partition being backed out was the M-V data sets, but during
    the backout processing in the FDBR region, an attempt was made
    to allocate the A-J data sets instead.
    
    The failure occurs because the DDIRADDR field ( DMB address ) in
    the DDIR was zero.  There is code in module DFSRDBP0 to skip
    trying to find the SMB and PDIR when processing the x'08' log
    record which caused the scheduling of the PSB to also
    be skipped.   Because the PSB was not scheduled, DFSPSM10 was
    not called to load and initialize the partition structure.
    When the backout was attempted later, fields in the DDIR
    had not been initialized, causing the failure to occur.
    
    This problem only occurs for HALDB when an OLR had previously
    been run for the partition.
    
    Additional Keywords: OLREORG MSGDFS2503W MSGDFS984I
                         MSGDFS981I LOG08 TYPE08.
    

Problem conclusion

  • GEN:
    KEYWORDS:
    
    *** END IMS KEYWORDS ***
    The following module has been modified to correct the reported
    problem:
    
    ************
    * DFSRDBP0 *
    ************
    Code has been modified in the type08 log record processing to
    try to find the PDIR, even if it is the FDBR region, and to
    schedule the PSB when the PSB is for OLR.
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PK79879

  • Reported component name

    IMS V10

  • Reported component ID

    5635A0100

  • Reported release

    010

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-02-03

  • Closed date

    2009-03-12

  • Last modified date

    2009-10-01

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

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

    PK80590 UK44855

Modules/Macros

  • DFSRDBP0
    

Fix information

  • Fixed component name

    IMS V10

  • Fixed component ID

    5635A0100

Applicable component levels

  • R010 PSY UK44855

       UP09/03/19 P F903

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

Document information


More support for:

IMS

Software version:

010

Reference #:

PK79879

Modified date:

2009-10-01

Translate my page

Machine Translation

Content navigation