PM76773: AN ATTEMPT TO CONNECT TO DB INACCURATELY REPORTS BIP2338E

APAR status

• Closed as program error.

Error description

• The first time WMB tries to connect to the database, it will
  issue multiple SQLGetTypeInfo calls in order to ensure that the
  database supports all of the types that broker needs. If the
  SQLGetTypeInfo does not return a successful return code,
  we assume it is because the datatype is unsupported and throw
  a recoverable exception stating as much. The failure of the
  SQLGetTypeInfo may not be related to an invalid
  SQL data type and we should report the actual database error.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of WebSphere Message Broker V6.1.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM SUMMARY:
  After upgrading the level of the broker database, the customer
  failed to correctly rebind one of the DB2 packages. As a result,
  the broker admin agent reported that the failure to connect
  was as a result of type SQL_INTEGER being invalid. This is not
  accurate, in fact the failure to connect was because of the
  unbound DB2 package. Broker did not catch and report the
  original database exception, but instead incorrectly assumed
  that the failure to connect was related to an invalid data type.
  This was very misleading and caused delays with resolving the
  issue.
  

Problem conclusion

• WebSphere Message Broker has been modified to report the
  original database exception.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Platform           v6.1
  --------           --------------------
  Multiplatforms     6.1.0.12
  
  The latest available maintenance can be obtained from
  'WebSphere Message Broker Recommended Fixes'
  http://www.ibm.com/support/docview.wss?rs=849&uid=swg27006041
  
  If the maintenance level is not yet available, information on
  its planned availability can be found in 'WebSphere Message
  Broker Planned Maintenance Release Dates'
  http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
  ---------------------------------------------------------------
  

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:

Fix information

• Fixed component name

  WMB Z/OS V6

• Fixed component ID

  5655M7400

Applicable component levels

• R100 PSY

     UP