| Latest versions | fixlist |
| 11.1.0.7 |
 |
| 10.5.0.9 |
|
| 10.1.0.6 |
|
| 9.8.0.5 |
|
| 9.7.0.11 |
|
| 9.5.0.10 |
|
| 9.1.0.12 |
|
| Have problems? - contact us. | |
| Register for free |
|
| Contact form |
|
DB2 - Problem description
| Problem IC91805 | Status: Closed |
DIA5000C "INVALID DDM REQUEST" AND SYNTAX ERROR REPORTED WHEN DB2 FOR ZOS ATTEMPTS TO SWITCH ID ON A TRUSTED CONNECTION | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problem description: | |
DB2 for zOS reports an error like this:
STC29848 DSNL031I -DBT3 DSNLZDJN DRDA EXCEPTION CONDITION IN
990
RESPONSE FROM SERVER LOCATION=NRDAIRD4 FOR THREAD WITH
LUWID=WZYZ.ABCDEF.AB0712341234=0
REASON=00D351FF
ERROR ID=DSNLZRPA0001
CORRELATION ID=USERIDA
CONNECTION ID=TSO
IFCID=0191
SEE TRACE RECORD WITH IFCID SEQUENCE NUMBER=00000001
While messages similar to these are written to the db2diag.log:
2013-03-08-10.31.36.035000-360 E22635645F759 LEVEL: Error
PID : 5756 TID : 140 PROC :
db2syscs.exe
INSTANCE: DB2INST1 NODE : 000 DB : SAMPLE
APPHDL : 0-62679 APPID: WXYZ.ABCDEF
AUTHID : TRUSTUSER
EDUID : 140 EDUNAME: db2agent (SAMPLE)
FUNCTION: DB2 UDB, DRDA Application Server,
sqljsParseRdbAccessed, probe:8
MESSAGE : DIA5000C A DRDA AS token "RECOVERABLE" was detected.
The diagnostic
data returned is (SRVDGN): "FUNCTION ID = 0185 , PROBE
POINT = 0008 ,
TRACE POINT = 0010 , SUBCODE1 = FFFFFFFF804B008D,
SUBCODE2 =
0000000000002001, SUBCODE3 = 00000000000000F4, ERROR
MSG = AGENT:
Invalid DDM Request".
2013-03-08-10.31.36.035000-360 I22636406F620 LEVEL: Error
PID : 5756 TID : 140 PROC :
db2syscs.exe
INSTANCE: DB2INST14 NODE : 000 DB :
SAMPLE
APPHDL : 0-62679 APPID: WXYZ.ABCDEF
AUTHID : TRUSTUSER
EDUID : 140 EDUNAME: db2agent (SAMPLE)
FUNCTION: DB2 UDB, DRDA Application Server,
sqljsParseRdbAccessed, probe:10
MESSAGE : ZRC=0x804B008D=-2142568307=SQLJS_SYNTAX "SYNTAX ERROR"
DATA #1 : DDM Object, PD_TYPE_DDM_OBJECT, 16 bytes
data length : 240
codepoint : 0x2001 ( ACCRDB )
length : 244 ( COMPLETE ) P | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * DB2 for zOS users establishing a Trusted Connection to DB2 * * for LUW * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 10.1 FP3 * **************************************************************** | |
| Local Fix: | |
| available fix packs: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
| Solution | |
Problem fixed in DB2 10.1 FP3 | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.04.2013 07.10.2013 07.10.2013 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.1.0.3 |
|
| 10.1.0.3 |
|