IBM Support

PK30581: RLT MODE RSR TRACKING IMS FAILED WITH ABENDU0014 IN DFSFLLG0 DURING RESTART

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Tracking IMS in RLT mode failed with abendU0014 RC4 in DFSFLLG0.
    DFSLRCAS tried to write 490E log (USTB : UPDATE SEQUENCE NUMBER
    TRACKING BLOCK for Full Function DB) log, whose LL=x'67B4' as
    SCDLLOGL = 67B2.
    The length of 490E log is becoming 8 bytes longer at every
    warm /ere restart and the same size is kept while tracker is
    running in RLT mode. In case of DLT mode tracker, the initial
    490E has "plus 8" bytes length and the subsequent milestone
    (DFSDT250) processing builds and refreshes 490E log record
    with valid length.
    The problem would happen when the number of USTB enties becomes
    more than 662(decimal) at this 28K OLDS block size installation,
    and a tracker is restarted twice in RLT mode
    

Local fix

  • Applied the following ZAP and the RLT tracker could start up.
     NAME DFSLROUT DFSLRRST  (HMK7700-UQ63272 / PQ57485 )
     VER 071A 41B0,0008
     REP 071A 41B0,0010
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All IMS V8 Remote Site Recovery (RSR) users  *
    *                 of Database Level Tracking (DLT) may be      *
    *                 affected.                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: ABENDU0014 RC=04 while restarting the   *
    *                      IMS RSR tracker.                        *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    The L490E log record is used to hold the FF DB Tracker Update
    Sequence Number (USN) across RSR tracker restarts.  It is
    written to the OLDS during end-milestone processing.  When it is
    built it has an incorrect length 8 bytes longer than it should
    be.  The next restart reads the log record and builds its own
    copy, again 8 bytes longer than it should be.  So the L490E log
    record grows across restarts.  In this case after 2 restarts the
    record exceeded the blksize of the OLDS which resulted in
    ABENDU0014.
    

Problem conclusion

  •  AIDS: RIDS/SYS RIDS/CNTRL SYS CNTRL
      DEP: NONE
      GEN:
    rsrimp RSRImpact
    
    *** END IMS KEYWORDS ***
    DFSLRRST has been changed to resolve this problem.  The LL field
    of the log record should be the existing length minus the log
    suffix length.  The code was only subtracting half of the
    suffix which caused the log record to grow by 8 bytes during
    each restart.  The code has been corrected to subtract the
    entire length of the log suffix.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK30581

  • Reported component name

    IMS V8

  • Reported component ID

    5655C5600

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2006-08-28

  • Closed date

    2006-09-12

  • Last modified date

    2007-02-13

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

    PK30419

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

    UK17943

Modules/Macros

  •    DFSLRRST
    

Fix information

  • Fixed component name

    IMS V8

  • Fixed component ID

    5655C5600

Applicable component levels

  • R800 PSY UK17943

       UP06/09/15 P F609

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCVRBJ","label":"System Services"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"800","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
13 February 2007