PM41211: ABEND5C4 S05C4 S5C4 5C4 RC082C0019 082C0019 C=810.ASMC-DSNVSRX M=DSNVSRRX,PSW=070C0000810BCE5E,A=0100

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Dump Title:
    XXXX,ABND=5C4-082C0019,U=nnnnnnnn,M=(N),C=810.ASMC-DSNVSRX
    M=DSNVSRRX,PSW=070C0000810BCE5E,A=0100
    This abend occurred after Websphere stopped their server.
    

Local fix

  • User should issue DB2 -Cancel Thread command against the
    Websphere threads before stopping the Websphere server so that
    DB2 can perform propr clean up.  It appears that the stopping
    of the Wbsphere server incurred an MVS CANCEL against the
    Websphere threads that are still running in DB2.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 for z/OS users.                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: An ABEND5C4 RC082C0019 occurred after a *
    *                      WebSphere server was stopped.           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    An ABEND5C4 RC082C0019 occurred after a WebSphere server was
    stopped. If a DB2 thread running in DB2 for commit or abort
    processing is MVS canceled (for example ABEND13E) and subsequent
    recovery processing also fails, the DB2 thread may remain hung.
    After several minutes an ABEND30D and ABEND5C4 will occur for
    the WebSphere server.
    DB2 RRSAF code should be changed to defer abort recovery to
    asynchronous end of task processing if the RRSAF recovery is
    being called by RRS during end of task.
    If possible a -DISPLAY THREAD(*) and
    -CANCEL THREAD(thread-token) for active DB2 threads should
    be issued before MVS cancel.
    

Problem conclusion

  • DB2 RRSAF code has been changed to defer abort recovery to DB2
    asynchronous end of task processing if the RRSAF Backout exit is
    driven by MVS end of task.
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PM41211

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    810

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-06-09

  • Closed date

    2011-11-24

  • Last modified date

    2012-01-01

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

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

    UK74203 UK74204 UK74205

Modules/Macros

  • DSN3RRSF DSN3RRSM
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK74203

       UP11/12/15 P F112

  • R810 PSY UK74204

       UP11/12/15 P F112

  • R910 PSY UK74205

       UP11/12/15 P F112

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.



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

DB2 for z/OS

Software version:

810

Reference #:

PM41211

Modified date:

2012-01-01

Translate my page

Machine Translation

Content navigation