IBM Support

PM82770: SEE AN INCREASE IN THE NUMBER OF UNCOMMITTED UR INCIDENTS BEING GENERATED IN FM/DB2 V12.1 VS. V11.1

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Client sees an increase in the number of  Uncommitted UR
    incidents being generated by queries being run when viewing DB2
    table data using File Manager V12.1
    

Local fix

  • 1. This issue can be avoided by turning off the 'Read-only
       access' option on the last editor options panel (7/7).
    
    2. Even with the change that will be made in the APAR, DSNU035I
       messages may be issued for a customer using FM/DB2 edit
       (not view or browse) in 'Large table' mode (row count = 0,
       ALL, *).
    
       These messages will not be issued unless the user has the
       'Read-only access' option selected.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of File Manager DB2 component.     *
    ****************************************************************
    * PROBLEM DESCRIPTION: DB2 issues DSNR035I messages under some *
    *                      circumstances, caused by File Manager   *
    *                      DB2 component editor sessions.          *
    ****************************************************************
    * RECOMMENDATION: Apply the provided PTF.                      *
    ****************************************************************
    Certain combinations of File Manager editor options can result
    in fetches against DB2 data using "uncommitted read", without
    a COMMIT after the initial data fetch.  This can lead to DB2
    issuing DSNR035I messages after a DB2-installation-dependent
    delay.
    

Problem conclusion

  • The File Manager DB2 component editor has been changed as
    follows:
    1. For browse and view, always issue a COMMIT after the initial
    data fetch, regardless of the editor's operating mode ("normal"
    or "large").
    2. For edit sessions in "large" mode, issue a COMMIT after the
    initial data fetch when the "Commit after data fetch" is
    selected.
    3. Display a warning panel for any edit session where the
    editor options include "Uncommitted read" and no "Commit after
    data fetch".
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM82770

  • Reported component name

    FILE MANAGER Z/

  • Reported component ID

    5655W6800

  • Reported release

    C12

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-02-13

  • Closed date

    2013-04-17

  • Last modified date

    2013-05-03

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

    PM82521

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

Modules/Macros

  • FMN2LVL  FMN2LVLJ FMN2LVLK
    

Fix information

  • Fixed component name

    FILE MANAGER Z/

  • Fixed component ID

    5655W6800

Applicable component levels

  • RC1B PSY UK93517

       UP13/04/24 P F304

  • RC12 PSY UK93518

       UP13/04/24 P F304

  • RC13 PSY UK93519

       UP13/04/24 P F304

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.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"C12","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSXJAV","label":"File Manager for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"C12","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
03 May 2013