Info-messages i db2diag.log even if diaglevel set to 3

[oddbande]

We have just upgraded a test enviroment to db2 9, and have set both the
notifylevel and diaglevel to 3. But even so I get a lot of these
messages in my db2diag.log:

2006-11-02-00.10.11.951000+060 I326548H465 LEVEL: Info
PID : 3008 TID : 4072 PROC : db2dasstm.exe
INSTANCE: DB2 NODE : 000
APPID : *LOCAL.DB2.061101231048
FUNCTION: DB2 UDB, DRDA Communication Manager, sqljcReceive, probe:30
MESSAGE : ZRC=0x8136001C=-2127167460=SQLZ_RC_NO_CONNECTION, SQLT_SQLJC
"No connection"
DATA #1 : String, 11 bytes
CCI Error:
DATA #2 : unsigned integer, 4 bytes
71

2006-11-02-00.10.11.998000+060 I327015H840 LEVEL: Info
PID : 3008 TID : 4072 PROC : db2dasstm.exe
INSTANCE: DB2 NODE : 000
APPID : *LOCAL.DB2.061101231039
FUNCTION: DB2 UDB, DRDA Application Requester, sqljrDrdaArExecute,
probe:90
MESSAGE : ZRC=0x80370001=-2143879167=SQLJR_EOF "End Of File"
DIA8000C An unexpected end of file was reached "".
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: 100 sqlerrml: 0
sqlerrmc:
sqlerrp : sqljrifc
sqlerrd : (1) 0x80370001 (2) 0x00000001 (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:

2006-11-02-00.10.12.607000+060 I327857H465 LEVEL: Info
PID : 3008 TID : 4072 PROC : db2dasstm.exe
INSTANCE: DB2 NODE : 000
APPID : *LOCAL.DB2.061101231039
FUNCTION: DB2 UDB, DRDA Communication Manager, sqljcReceive, probe:30
MESSAGE : ZRC=0x8136001C=-2127167460=SQLZ_RC_NO_CONNECTION, SQLT_SQLJC
"No connection"
DATA #1 : String, 11 bytes
CCI Error:
DATA #2 : unsigned integer, 4 bytes
71

2006-11-02-00.10.12.607000+060 I328324H384 LEVEL: Info (OS)
PID : 3008 TID : 4072
FUNCTION: DB2 Common, OSSe, OSSHIPCSemaphore::attach, probe:40
MESSAGE : ECF=0x9000001A File doesn't exist
CALLED : OS, -, OpenSemaphore OSERR:
ERROR_FILE_NOT_FOUND (2)
ARG #3 : String, 51 bytes
Global\OSSEIPC115CIBMSQLLIBDB2DAS00tmpschRes.tmp30 7

2006-11-02-00.10.13.779000+060 I328710H465 LEVEL: Info
PID : 3008 TID : 5212 PROC : db2dasstm.exe
INSTANCE: DB2 NODE : 000
APPID : *LOCAL.DB2.061101231049
FUNCTION: DB2 UDB, DRDA Communication Manager, sqljcReceive, probe:30
MESSAGE : ZRC=0x8136001C=-2127167460=SQLZ_RC_NO_CONNECTION, SQLT_SQLJC
"No connection"
DATA #1 : String, 11 bytes
CCI Error:
DATA #2 : unsigned integer, 4 bytes
71

2006-11-02-00.10.14.842000+060 I329177H465 LEVEL: Info
PID : 3008 TID : 5212 PROC : db2dasstm.exe
INSTANCE: DB2 NODE : 000
APPID : *LOCAL.DB2.061101231054
FUNCTION: DB2 UDB, DRDA Communication Manager, sqljcReceive, probe:30
MESSAGE : ZRC=0x8136001C=-2127167460=SQLZ_RC_NO_CONNECTION, SQLT_SQLJC
"No connection"
DATA #1 : String, 11 bytes
CCI Error:
DATA #2 : unsigned integer, 4 bytes
71

2006-11-02-00.10.15.920000+060 I329644H465 LEVEL: Info
PID : 3008 TID : 5212 PROC : db2dasstm.exe
INSTANCE: DB2 NODE : 000
APPID : *LOCAL.DB2.061101231059
FUNCTION: DB2 UDB, DRDA Communication Manager, sqljcReceive, probe:30
MESSAGE : ZRC=0x8136001C=-2127167460=SQLZ_RC_NO_CONNECTION, SQLT_SQLJC
"No connection"
DATA #1 : String, 11 bytes
CCI Error:
DATA #2 : unsigned integer, 4 bytes
71

2006-11-02-00.10.17.139000+060 I330111H465 LEVEL: Info
PID : 3008 TID : 5212 PROC : db2dasstm.exe
INSTANCE: DB2 NODE : 000
APPID : *LOCAL.DB2.061101231104
FUNCTION: DB2 UDB, DRDA Communication Manager, sqljcReceive, probe:30
MESSAGE : ZRC=0x8136001C=-2127167460=SQLZ_RC_NO_CONNECTION, SQLT_SQLJC
"No connection"
DATA #1 : String, 11 bytes
CCI Error:
DATA #2 : unsigned integer, 4 bytes
71

Why is this writtem to the db2diag.log? It's just Info messages, and
should not be written there with diaglevel set to 3... Or am I
mistaken? Or could this in fact be errors, but falsely set as Info
messages?

There are a lot of these messages filling up my db2diag.log, so I would
like very much to get rid of them....

Regards
Odd B Andersen
ErgoGroup AS, Oslo, Norway

[memmerto]

oddbande wrote:

We have just upgraded a test enviroment to db2 9, and have set both the
notifylevel and diaglevel to 3. But even so I get a lot of these
messages in my db2diag.log:

[ snip messages, all from db2dasstm.exe ]

Why is this writtem to the db2diag.log? It's just Info messages, and
should not be written there with diaglevel set to 3... Or am I
mistaken? Or could this in fact be errors, but falsely set as Info
messages?

There are a lot of these messages filling up my db2diag.log, so I would
like very much to get rid of them....

Have you restarted the DAS service? It's likely that it won't pick up
the DIAGLVL change until it is restarted.

--
Matt Emmerton