IBM Support

PK90031: PROHIBIT AUTHORIZATION IN DBRC FLAG LEFT ON WHEN DOING A RECOVER ON HALDB TO LASTIC

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • /DBR GLOBAL turns PROHIBIT AUTH ON. /STA GLOBAL turns PROHIBIT
    AUTH OFF. At (RECOVER) START, DSPRWV00 returns the status of the
    PROHIBIT AUTH flag in the field rwcr_prohibit_auth.
    FRXTAU00 checks rwcr_prohibit_auth before calling IB and turns
    PROHIBIT AUTH OFF if it is ON. It calls DBRC to do this.
    After calling IB, it checks rwcr_prohibit_auth again and if it
    is on, calls DBRC again to turn the PROHIBIT AUTH flag back on.
    .
    In other words, we need the PROHIBIT AUTH flag off for IB so
    turn it off if needed. But we want to leave it in the same
    status it was before recovery started so we turn it back on if
    it was on to start with. But in this case it was not on to start
    with. It's only on because of the /DBR GLOBAL command we issued.
    This explanation only makes sense if we are issuing the /STA
    GLOBAL before FRXTAU00 turns it back on.
    Thesuggested fix is to reset the rwcr_prohibit_auth flag when we
    issue the /STA GLOGAL. This would prevent FRXTAU00 from turning
    on the PROHIBIT AUTH flag incorrectly.  The /STA GLOBAL command
    is documented to turn the PROHIBIT AUTH off in DBRC, so it is
    safe to reset the flag in DRF
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of DRF are affected when using     *
    *                 DBRCMD(GLOBAL) STACMD(GLOBAL)                *
    ****************************************************************
    * PROBLEM DESCRIPTION: DRF issued a STA db GLOBAL, which will  *
    *                      reset PROHIBT AUTH flag, and then       *
    *                      restored the environment to an earlier  *
    *                      state which left the PROHIBIT AUTH      *
    *                      status on. This has been addressed to   *
    *                      not restore the environment when STA db *
    *                      GLOBAL is issued.                       *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    PROHIBIT AUTH flag was incorrectly restored to a point after DBR
    GLOBAL.
    

Problem conclusion

  • This problem was caused by a incorrect sequence of events, and
    has been corrected.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK90031

  • Reported component name

    IMS DB RECOVERY

  • Reported component ID

    5655I4400

  • Reported release

    310

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2009-06-26

  • Closed date

    2009-07-07

  • Last modified date

    2009-08-03

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

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

    UK48156

Modules/Macros

  • FRXVRCV0
    

Fix information

  • Fixed component name

    IMS DB RECOVERY

  • Fixed component ID

    5655I4400

Applicable component levels

  • R310 PSY UK48156

       UP09/07/09 P F907

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX88Z","label":"IMS Database Recovery Facility"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 August 2009