PN62536: ABEND0C4 IN DSNAET03 DURING -STOP DB2 MODE(FORCE)

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• On issueing a -STOP DB2 MODE(FORCE), an ABEND0C4 PIC11 in
  DSNAET03 at offset X'27A' because of a freemained FDBK area by
  DSNAPRHX.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 users.                               *
  ****************************************************************
  * PROBLEM DESCRIPTION: ABEND0C4 in DSNAET03 attempting to      *
  *                      translate a failure due to the          *
  *                      loss of an application's connection     *
  *                      with DB2.  The original connection loss *
  *                      could be caused by several things,      *
  *                      including: the loss of the cross memory *
  *                      bind with DB2 (eg. ABEND0Dx), a         *
  *                      -STOP DB2,MODE(FORCE), etc.             *
  *                      This APAR is the DB2 V2.3 retro-fit     *
  *                      of APAR PN49994.                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A customer entered -STOP DB2,MODE(FORCE) on a DB2 system that
  had many active users.  One user that was connected to DB2
  received the expected RC00F30011 (DB2 not up) reason code when
  it attempted an SQL call.  At this point, the program request
  handler (DSNAPRHX) recognized that the connection with DB2 had
  been lost, so it freed the storage that was gotten for this user
  when the connection was first established.  DB2 Translate
  (DSNAET03) was invoked to translate the reason code into a
  SQLCODE and to fill in the SQLCA.  DSNAET03 did the translate
  and, since it was an SQLCODE-923, DSNAET03 attempted to get
  additional error information from the user feedback (FRBFBACK)
  area.  However, FRBFBACK contained a residual pointer to the
  FDBK area, which had been freed by DSNAPRHX when the connection
  was lost.  Since FRBFBACK was non-zero, DSNAET03 attempted to
  use the residual pointer and received an ABEND0C4.
  
  Note that the ABEND0C4 failure is possible in situations other
  than just the -STOP DB2,MODE(FORCE).  This scenario can occur
  whenever a connection lost is detected by DSNAPRHX.  The most
  common occurrences of this would be: the loss of the cross
  memory bind (eg ABEND0Dx) between the allied user and DB2,
  an ABEND0C4 trying to verify the program request handler
  work area (PRHW) storage, or a -STOP DB2,MODE(FORCE).
  
  This APAR is the DB2 V2.3 retro-fit of APAR PN49994.
  

Problem conclusion

• DSNAPRHX has been changed to clear the FRBFBACK pointer if
  it points to the FDBK area that is about to be freed.
  

Temporary fix

Comments

APAR Information

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

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

  UN70055

Modules/Macros

•    DSNAPRHS DSNAPRHX DSNAPRH0
  

Fix information

• Fixed component name

  SUBSYSTEM INIT.

• Fixed component ID

  5740XYR01

Applicable component levels

• R230 PSY UN70055

     UP94/11/23 P F411

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.