IBM Support

PI62033: CUSTOMER IS USING FILE MANAGER DB2 AND IT IS KEEPING A LOCK IN DYNAMIC STATEMENT CACHE.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Customer is using File Manager DB2 and it is keeping a lock in
    dynamic statement cache.  File manager for DB2 is keeping a
    lock on the statement   in the dynamic statement cache.
     The customer has to cancel the TSO userid    to release the
    lock.
    .
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of File Manager DB2 component.     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Message DSNT408I SQLCODE = -904, ERROR: *
    *                      UNSUCCESSFUL EXECUTION CAUSED BY AN     *
    *                      UNAVAILABLE RESOURCE. REASON 00E70081,  *
    *                      TYPE OF RESOURCE 00000C00,              *
    *                      attempting to execute DDL to drop DB2   *
    *                      objects.                                *
    ****************************************************************
    * RECOMMENDATION: Apply the provided PTF.                      *
    ****************************************************************
    In the following situation no DB2 commit is issued, this
    results in the SQL statement that refers to the DB2 object
    being edited remaining active in the DB2 dynamic statement
    cache.
    An FM/DB2 user edits a DB2 object (A), selects the
    'edit template' option and then either:
    a.  remains in the template editor (no DB2 data is displayed)
    b.  cancels out of the template editor
    (no DB2 data is displayed).
    The presence of the 'active' SQL statement in the DB2
    dynamic statement cache prevents any attempt to execute DDL
    against any DB2 object (eg data base, table space)
    that is dependent on the DB2 object A.
    

Problem conclusion

  • File Manager DB2 component has been updated to correct the
    problem.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI62033

  • 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

    2016-05-06

  • Closed date

    2016-11-24

  • Last modified date

    2016-12-01

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

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

    PI62088

Modules/Macros

  • FMN0LVL  FMN2LVL
    

Fix information

  • Fixed component name

    FILE MANAGER Z/

  • Fixed component ID

    5655W6800

Applicable component levels

  • RC10 PSY UI42873

       UP16/12/01 P F611

  • RC12 PSY UI42874

       UP16/12/01 P F611

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:
01 December 2016