Zoltan,

     The 22002 code indicates a NULL data indicator - this is how TSM
manages results returned from DB2 in response to a query we perform to the
database.   Please contact IBM support for this issue as this is something
we need to diagnose and fix.

     The DBREPORTMODE is intended for cases like this.  The intent being to
set it to NONE in the short-term to eliminate the chattiness.  But then
once you receive an appropriate fix that addresses the cause of the issue,
the typical or recommended DBREPORTMODE setting would be PARTIAL.

Thanks,
Colin

-----------------------------------------------------
Colin Dawson
TSM Server Development
colind AT us.ibm DOT com



  From:       Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>

  To:         ADSM-L AT VM.MARIST DOT EDU

  Date:       04/07/2009 07:22 AM

  Subject:    [ADSM-L] V6.1 DB/LOG messages






Finally got a V6.1 server up and running, on Linux.

Unfortunately, it is constantly generating "warning" messages every time I
issue a DB type command or select (e.g. "Q DB F=D").

4/7/2009 10:08:56 AM ANR0162W Supplemental database diagnostic
information:  -1:22002:-99999 ([IBM][CLI Driver] CLI0110E  Invalid output
or indicator buffer specified. SQLSTATE=22002).

I see that V6.1 is also very chatty when it comes to DB/LOG type messages.
I already set DBREPORTMODE to "Partial" and am wondering if I should set
it to NONE?  When I do set it to NONE, the messages stop but am concerned
I might miss something important.

Any suggestions on what might be causing this?  I have zero experience
with DB2.