IBM Support

PQ83071: FAILURES FOLLOWING AN LP POINTER.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Failures occur attempting to follow an LP pointer.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: IMS Database Repair Facility for OS/390 ,    *
    *                 Version 1.1                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: Several problems addressed. Following   *
    *                      an LP pointer, the target segment is    *
    *                      not mapped correctly. Out of memory     *
    *                      failure. Added more error checking on   *
    *                      data entry fields. Panel fabzp02        *
    *                      sometimes proceeds to panel fabzps0 in  *
    *                      error.                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Several problems addressed. 1) Following an LP pointer ends up
    at panel fabzps2,the data looks correct, but the prefix mapping
    is wrong, it appears to be the mapping of the segment that
    contained the LP.  2) When viewing many OSAM blocks or segments,
    you may incur a memory failure such as S878 or S106. 3) There
    are many data entry fields on various panels. More error
    checking was added to detect incorrect entries. 4) Normally, the
    next logical panel after fabzp02 is one of the 'initial
    selection' panels. Sometimes, after hitting enter on fabzp02,it
    goes backwards to panel fabzps2, and stays in this loop until
    you choose a different dbd.
    

Problem conclusion

  • The LP problem was caused by code that failed to create a new
    segment map for the target segment. this code was fixed. any
    failures beyond this, related to following logical pointers,
    will be addressed in other apars. The other problems were all
    fixed by logic correction.
    110Y
    FABZCHRO
    FABZDATA
    FABZDIRM
    FABZGDBD
    FABZIADR
    FABZMAIN
    FABZOSIO
    FABZPROC
    FABZPRO2
    FABZPS1
    FABZPS1I
    FABZPS1P
    FABZPS1R
    FABZPS2
    FABZPS2F
    FABZPS7
    FABZPS8
    FABZPS9
    FABZRAND
    FABZ02
    FABZ06
    FABZ07
    

Temporary fix

Comments

APAR Information

  • APAR number

    PQ83071

  • Reported component name

    IMS DATABASE RE

  • Reported component ID

    5655E0300

  • Reported release

    110

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2004-01-09

  • Closed date

    2004-01-22

  • Last modified date

    2004-02-04

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

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

    UQ84366

Modules/Macros

  • FABZCHRO FABZDATA FABZDIRM FABZGDBD FABZIADR
    FABZMAIN FABZOSIO FABZPROC FABZPRO2 FABZPS1  FABZPS1I FABZPS1P
    FABZPS1R FABZPS2  FABZPS2F FABZPS7  FABZPS8  FABZPS9  FABZRAND
    FABZ02   FABZ06   FABZ07
    

Fix information

  • Fixed component name

    IMS DATABASE RE

  • Fixed component ID

    5655E0300

Applicable component levels

  • R110 PSY UQ84366

       UP04/01/25 P F401

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.

[{"Line of Business":{"code":null,"label":null},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX892","label":"IMS Database Repair Facility"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"110"}]

Document Information

Modified date:
14 December 2020