IBM Support

PQ77809: FIX MULITPLE DB REPAIR FACILITY PROBLEMS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Errors across all DB types, and all functions of DB Repair
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: IMS Database Repair Facility -Version 1      *
    *                 Release 1                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: This apar fixes many problems spanning  *
    *                      the whole range of databases supported  *
    *                      ,and all functions of DBRF. DBRF may    *
    *                      work fine for a particular dbd          *
    *                      definition, and if you do limited       *
    *                      work on that dbd. For example, display  *
    *                      a block,or segment and perhaps zap it.  *
    *                      If your useage of DBRF will span many   *
    *                      dbds, and you intend to use             *
    *                      'navigation'  or 'zapping' heavily      *
    *                      then you will most likely encounter     *
    *                      problems. The problem summary lists     *
    *                      many of the major problems fixed,       *
    *                      there are numerous other small          *
    *                      problems fixed.                         *
    *                                                              *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    1. Navigation on the 'segment prefix'
     panel. Problems with the 'F' 'B' 'U'
     and F3 functions. Definition of these
    functions is changed.
    2. On the 'initial selection' panel,
    specifying blk= and fse=Y or RAPS=y
    will fail if it is a bitmap block.
    3. If you work with one dbd, then
    switch to another, there will be
    problems working with the second dbd.
    Some of the panels will be incorrect,
    or the data in them may be residual
    from the first dbd.
    4. If your dbd has multiple dsg,
    switching to any dsg other than '1'
    may fail, or display incorrect data.
    5. There will be incorrect data or
    failures if your dbd is type=PSINDEX.
    6. HIDAM dbds, key access on
    'initial selection' panel may fail.
    7. If your dbd is type PDB, it will
    fail. DBRF does not support these
    dbds,and will now give a message.
    8. SHISAM may have failure or
    incorrect output
    9. dbd that has fewer PCL than PCF
    will not display correctly on
    'segment prefix' panel.
    10. dbd with logical pointers will
    not display correctly on 'segment
    prefix' panel.
    11. If you run DBR a long time, you
    may get 'out of memory' type abends.
    For example, in 'initial selection'
    panel,you keep entering different blk=
    values. Or, if you switch dbds often.
    12. 'segment prefix' panel, following
    a pointer may fail,giving an
    'end of chain' message.
    13. HISAM, 'logical record' panel,
     incorrect data.
    14. 'logical record' panel, 'get next
    overflow record' fails. Also, if dg=ov
    ,problems trying to zap data in panel
    15. Zapping data on 'segment prefix'
    panel, or on any panel that displays
    segment or block data may not work.
    For example, zapping 2 different
    lines on a panel will not work,the
    2nd line is ignored.
    

Problem conclusion

  • New Messages
    
    FABZ059W: PDB detected.
    Response: PDB database is not
    supported by DBR.
    
    FABZ061I: Partition DBD name is not
       valid
    Response: you get this if you type in
    an invalid dbd name on panel=fabzps1p
    
    FABZ071I: xxx option requires yyy ptr
       to exist
    Response: valid xxx,yyy pairs are
     F,PTF   B,PTB   U,PP . you cannot do
    the option without seeing that
    
    FABZ073I: FSE option not valid for
    IMS bit map blocks/CIs or unused CIs
    Response: set FSE=n for this BLK
    
    FABZ074I: RAPS option not valid for
    IMS bit map blocks/CIs or unused CIs
    Response: set RAPS=n for this BLK
    
    FABZ075I: Only one partition selectable
    at once. Multiple partition
    selection not supported.
    Response: just select 1 partition
    
    New, or changed functionality.
    
    Navigation functions on 'segment
     prefix' panel. Now, 'F' means follow
    the PTF pointer. 'B' means follow the
    PTB pointer.  Previously, 'U' meant go
    'up' in the physical hierarchy, but
     now that DBRF lets you navigate via
    logical pointers, that definition is
     no longer valid. Therefore, 'U' now
    means follow the PP pointer.  If any
    of these pointers don't exist,and you
    do these functions, you will get an
    error message.
    
    On the 'initial selection' panel for
    HISAM,INDEX,SINDEX,PSINDEX there is an
    RBA field. This field is only used when
     DG=OV.  Entering anything in RBA field
    when DG is not 'OV' will yield an error
     message.
    
    Logical pointers. When these appear on
    'segment prefix' panel, the tgt-sc and
    tgt-dg columns will be blank.
    
    Once a logical pointer is selected,
    then DBR follows it to its target DBD.
    If indeed, the logical pointer does go
    to a different DBD,the next panel you
    see will be 'update libraries' , where
    you can specify either a dbdlib , or
    list of datasets for this dbd.... then
    you will end up in the 'segment prefix'
     panel of the target segment of the
    original logical pointer.
    110Y
    FABZDATA
    FABZDBLS
    FABZDBMP
    FABZGDBD
    FABZMAIN
    FABZPROC
    FABZPRO2
    FABZPS1R
    FABZPS2
    FABZPS3
    FABZPS3I
    FABZ05
    FABZ06
    FABZ07
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PQ77809

  • Reported component name

    IMS DATABASE RE

  • Reported component ID

    5655E0300

  • Reported release

    110

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2003-08-25

  • Closed date

    2003-12-10

  • Last modified date

    2004-01-03

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

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

    UQ83013

Modules/Macros

  • FABZDATA FABZDBLS FABZDBMP FABZGDBD FABZMAIN
    FABZPROC FABZPRO2 FABZPS1R FABZPS2  FABZPS3  FABZPS3I FABZ05
    FABZ06   FABZ07
    

Fix information

  • Fixed component name

    IMS DATABASE RE

  • Fixed component ID

    5655E0300

Applicable component levels

  • R110 PSY UQ83013

       UP03/12/12 P F312 Ž

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