IZ56664: After a call to SQLGetDiagField(), the message pointed to by the DiagInfoPtr output argument is padded to the right with garbage

DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

APAR status

• Closed as program error.

Error description

• After you call the CLI (Call Level Interface) function
  SQLGetDiagField(), the message pointed to by the DiagInfoPtr
  output argument might be padded to the right with garbage
  characters.
  
  This problem occurs only when SQLGetDiagField() retrieves the
  message text from a DB2 for zOS database server.
  The problem does not occur when SQLGetDiagField() retrieves the
  message text from local message files on the client.
  
  SQLGetDiagField() retrieves the message from the database server
  only when the CLI configuration keyword UseServerMsgSP
  is set to 1.
  
  Here is an example of the error message that is
  retrieved when you try to create an index that already exists in
  your database:
  
   SQLGetDiagField( pDiagInfo="[IBM][CLI Driver][DB2] THE NAME OF
   THE OBJECT TO BE CREATED OR THE TARGET OF A RENAME STATEMENT IS
   IDENTICAL TO THE EXISTING NAME OWNER.NAME~IDX x 34",
   pcbDiagInfo=154 )
   <--- SQL_SUCCESS Time elapsed - +1.173940E-001 seconds
  

Local fix

• As a workaround, do not set the CLI configuration keyword
  UseServerMsgSP to 1.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users of CLI (Call Level Interface) applications on DB2 for  *
  * Linux, UNIX and Windows that connect to a DB2 database on a  *
  * host server                                                  *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * After you call the CLI (Call Level Interface) function       *
  * SQLGetDiagField(), the message pointed to by the DiagInfoPtr *
  * output argument might be padded to the right with garbage    *
  * characters.                                                  *
  *                                                              *
  * This problem occurs only when SQLGetDiagField() retrieves    *
  * the message text from a DB2 for zOS database server.         *
  * The problem does not occur when SQLGetDiagField() retrieves  *
  * the message text from local message files on the client.     *
  *                                                              *
  * SQLGetDiagField() retrieves the message from the database    *
  * server only when the CLI configuration keyword               *
  * UseServerMsgSP is set to 1.                                  *
  *                                                              *
  * Here is an example of the error message that is retrieved    *
  * when you try to create an index that already exists in your  *
  * database:                                                    *
  *                                                              *
  * SQLGetDiagField( pDiagInfo="[IBM][CLI Driver][DB2] THE NAME  *
  * OF THE OBJECT TO BE CREATED OR THE TARGET OF A RENAME        *
  * STATEMENT IS IDENTICAL TO THE EXISTING NAME OWNER.NAME~IDX x *
  * 34", pcbDiagInfo=154 )                                       *
  * <--- SQL_SUCCESS Time elapsed - +1.173940E-001 seconds       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * .                                                            *
  ****************************************************************
  

Problem conclusion

• Problem was first fixed in Version 9.5 Fix Pack 5
  

Temporary fix

• As a workaround, do not set the CLI configuration keyword
  
  UseServerMsgSP to 1.
  

Comments

APAR Information

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

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

  IC62372 IZ57506

Modules/Macros

• ENGN_CLI
  

Fix information

• Fixed component name

  DB2 CEE AIX

• Fixed component ID

  5765F3000

Applicable component levels

• R910 PSN

     UP

• R950 PSN

     UP