IBM Support

PI75024: RRSAF THREADS MAY REMAIN IN DB2 AS IN-DOUBT AFTER RRS THREADS ARE BACKED OUT.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After RRS threads were cancelled, the DB2 UR abort was deferred
    to EOT processing and remained until DB2 recycle even though the
    application threads finished aborting.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * DB2 for z/OS users of RRSAF.                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * If an application using DB2 RRSAF is                         *
    * canceled, a DB2 UR may remain in-doubt                       *
    * after DB2's deferred EOT process has                         *
    * finished.  The application may have                          *
    * already terminated and z/OS RRS has                          *
    * ended the z/OS RRS UR.  The in-doubt                         *
    * DB2 UR may remain until it is manually                       *
    * resolved or DB2 is recycled.                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If an application using DB2 RRSAF is canceled, a DB2 UR may
    remain in-doubt after DB2 deferred EOT processing has finished.
    The application may have already terminated and z/OS RRS has
    ended the z/OS RRS UR.  The in-doubt DB2 UR may remain until it
    is manually resolved or DB2 is stopped and restarted.
    

Problem conclusion

  • DB2 module DSN3TM00 has been updated to ensure that a DB2
    in-doubt UR that was processed for an RRS implicit backout will
    be automatically aborted.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI75024

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    C10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-01-16

  • Closed date

    2017-04-04

  • Last modified date

    2017-05-01

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

    PI74733

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

    UI46154

Modules/Macros

  • DSN3TM00
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RC10 PSY UI46154

       UP17/04/21 P F704

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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"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":"12.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 May 2017