JR29942: SQLALLOCENV() AND SQLALLOCHANDLE(SQL_HANDLE_ENV,...) WILL TURN OFF A PREVIOUSLY DYNAMICALLY ACTIVATED CLI TRACE

DB2 Version 9.1 Fix Pack 7  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7a  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 8  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 9  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

APAR status

• Closed as program error.

Error description

• A previously dynamically enabled CLI trace wil get turned off by
  the next SQLAllocEnv()/SQLAllocHandle(SQL_HANDLE_ENV,...) call.
  Turning CLI trace on dynamically is done by setting
  TraceRefreshInterval=number in the db2cli.ini file and setting
  Trace=1 later on, when the application is already running.
  

Local fix

• Avoid SQLAllocEnv(), SQLAllocHandle(SQL_HANDEL_ENV,...) calls
  after turning on CLI trace dynamically.
  

Problem summary

• A previously dynamically enabled CLI trace wil get turned off by
  the next SQLAllocEnv()/SQLAllocHandle(SQL_HANDLE_ENV,...) call.
  Turning CLI trace on dynamically is done by setting
  TraceRefreshInterval=number in the db2cli.ini file and setting
  Trace=1 later on, when the application is already running.
  

Problem conclusion

• First fixed in DB2 UDB Version 9.1, FixPak 7.
  

Temporary fix

• See LOCAL FIX.
  

Comments

APAR Information

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

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

  JR29956 JR29992

Fix information

• Fixed component name

  DB2 CEE WINDOWS

• Fixed component ID

  5765F3001

Applicable component levels

• R810 PSN

     UP

• R820 PSN

     UP

• R910 PSN

     UP

• R950 PSN

     UP