|
Problem IC62279
|
Status: Closed |
A DRDA CONTROL BLOCK IS NOT INITIALIZED TO 0 WHICH CAUSES INCORRECT MGRLVLLS MAYBE PICKED UP WHEN CONCENTRATOR TURNED ON. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
A DRDA control block is not initialized to 0 which causes
incorrect MGRLVLLS maybe picked up when Concentrator turned on.
SQLJR_BADCOM error maybe returned in db2diag.log
From db2diag.log
----------------
2009-07-01-11.04.11.203808-240 I27036A954 LEVEL: Error
PID : 8600 TID : 2199325239648PROC :
db2sysc
INSTANCE: dbctib01 NODE : 000 DB : N090DSN
APPHDL : 0-28197 APPID: GA099D5E.CDDA.0A0531150220
AUTHID : E0413X1
EDUID : 30 EDUNAME: db2agent (N090DSN)
FUNCTION: DB2 UDB, DRDA Application Requester,
sqljrReportServerErrReply, probe:20
MESSAGE : ZRC=0x80370084=-2143879036=SQLJR_BADCOM "Op not
supported"
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -30005 sqlerrml:
43
sqlerrmc: N090DSN DSN08015 0x1055"("02")"
sqlerrp : sqljrerm
sqlerrd : (1) 0x80370084 (2) 0x00000084 (3)
0x00000000
(4) 0x00000000 (5) 0x00000000 (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:
..
----------------- |
| Problem Summary: |
A DRDA control block is not initialized to 0 which causes
incorrect MGRLVLLS maybe picked up when Concentrator turned on.
SQLJR_BADCOM error maybe returned in db2diag.log
From db2diag.log
----------------
2009-07-01-11.04.11.203808-240 I27036A954 LEVEL: Error
PID : 8600 TID : 2199325239648PROC :
db2sysc
INSTANCE: dbctib01 NODE : 000 DB : N090DSN
APPHDL : 0-28197 APPID: GA099D5E.CDDA.0A0531150220
AUTHID : E0413X1
EDUID : 30 EDUNAME: db2agent (N090DSN)
FUNCTION: DB2 UDB, DRDA Application Requester,
sqljrReportServerErrReply, probe:20
MESSAGE : ZRC=0x80370084=-2143879036=SQLJR_BADCOM "Op not
supported"
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -30005 sqlerrml:
43
sqlerrmc: N090DSN DSN08015 0x1055"("02")"
sqlerrp : sqljrerm
sqlerrd : (1) 0x80370084 (2) 0x00000084 (3)
0x00000000
(4) 0x00000000 (5) 0x00000000 (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:
..
----------------- |
| Local Fix: |
Turn off Connection Concentrator |
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Fist fixed in V9.7 FP1 |
| Workaround |
Turn off Connection Concentrator |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 30.07.2009
21.12.2009
21.12.2009 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
