PM94517: DIRECT CONNECTING NON-JAVA CLIENT DRIVERS ISSUE SQL1034C IN RESPONSE TO DB2 FOR Z/OS SERVER THREAD TERMINATION

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DB2DDF defects pm94517 dpm94517
  Direct connecting non-java client drivers issue SQL1034C
  (The database is damaged.) in response to DB2 for z/os server
  thread termination for a cancel , idle thread timeout or abend.
  
  CLI for example would be a non-java client driver that may issue
  the SQL1034C
  
  This apar will help older clients runing level lower than DB2
  for LUW 10.1 Fixpack 2
  **************************************************************
  Additional Symptoms and Keywords:
   SQL1034 SQLCODE1034 SQL1034C SQLCODE1034C
   IDTHTOIN 00D3003B RC00D3003B
   SRVCOD 64 SRVCOD64 SRVCOD0064 SRVCOD 32 SRVCOD32 SRVCOD0032
   AGNPRMRM
   Database Damaged DatabaseDamaged
  

Local fix

• no local fix/workaround
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
  *                 Specifically those which use the non-java    *
  *                 IBM Data Server client which can directly    *
  *                 connect to DB2 for z/OS.                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: Client applications receive SQL1034C,   *
  *                      "database damaged" messages.            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Whenever a DB2 distributed server thread (DBAT) is terminated
  via a DB2 -CANCEL THREAD command or the IDLE THREAD TIMEOUT
  (DSN6FAC IDTHTOIN) subsystem parameter, DB2 generates a DRDA
  AGNPRMRM reply to report this termination event back to the
  client, and DB2 associates this condition to a severity code
  (SRVCOD) of 64.  Changes made by APARs PM43293 and PM81671
  allow the AGNPRMRM reply to be returned more frequently in
  order to accurately reflect DBAT termination events.
  Unfortunately, non-java IBM Data Server client drivers older
  than Version 10.1 fixpak 2 consider the receipt of an AGNPRMRM,
  with a SVRCOD of 64, to indicate a "database damaged" condition
  and hence return SQLCODE -1034 back to the client application.
  Example:
   SQL1034C -The database is damaged. All applications processing
             the database have been stopped.
  This causes unnecessary alarm and concern to users because no
  actual damage has really occurred in the DB2 database.
  

Problem conclusion

• During DB2 distributed server termination events, DB2 has been
  changed to generate an AGNPRMRM reply with a SVRCOD value
  of 32 when the level of the client/driver is older than
  Version 10.1 fixpack 2.
  

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:

  UK97867 UK97868

Modules/Macros

• DSNLDALB
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UK97867

     UP13/10/10 P F310

• RB10 PSY UK97868

     UP13/10/10 P F310

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.