APAR status
Closed as canceled.
Error description
5740xyr00 DB2DDF DB2DRDA1 From an OS/2 work station, the user is trying to connect to a DB2 database (start using database). But DB2 issues messages DSNL032I and DSNL500I. Example: DSNL032I - DSNLCRTD DRDA EXCEPTION CONDITION IN REQUEST FROM REQUESTOR LOCATION=<SYD2118A> FOR THREAD WITH LUWID=USIBMSY.SYD2118A.A673353C26B7 IFCID=0192 SEE TRACE RECORD WITH IFCID SEQUENCE NUMBER=00000000 DSNL500I - CONVERSATION FAILED TO LOCATION <SYD2118A> RESOURCE=SYD2118A.IBMRDB.01000002.00D70CA8AAD70CA8 RTNCD=00 FDBK2=0B RCPRI=0014 RCSEC=0000 SENSE=08640000 The DSNL032I indicates that DSNLCRTD discovered a DRDA exception condition with IFCID0192. At the OS/2 AR, the user recives SQLCODE30080 with a primary return code of 000E and a secondary return code of 00000000. Example: SQL30080N A communication error "000E-00000000" occurred sending or receiving data from the remote database. This is caused by a user error (incorrect OS/2 directory deffinitions). In this case, the user did not create the 'DCS directory' (Database Connection Services) entry for the 'system database' directory entry. For example: User has a 'system database' directory with a 'database' of 'ABCDEFG'. There is no cooresponding DCS directory with a 'local database' of 'ABCDEFG'. Thus, OS/2 believed it was going to another OS/2 workstation and therefore sent its private protocol flows to the workstation LU (which is the DB2 LU) instead of DRDA flows. Since DB2 did not receive DRDA information, DB2 detects a DRDA exception condition. The user must correctly define the DCS directory entry. *********************** Additional symptoms and keywords: 5740XYR00 DB2 OS/2 DBM DRDA RUW SQLCODE30080 SQLCODE30080N SQL30080 SQL30080N DSNL032I DSNL032 MSGDSNL032I MSGDSNL032 DSNL500I DSNL500 MSGDSNL500I MSGDSNL500 IFCID0192 IFCID192
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
Closing informational APAR.
APAR Information
APAR number
II06447
Reported component name
PB LIB INFO ITE
Reported component ID
INFOPBLIB
Reported release
001
Status
CLOSED CAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
1992-10-16
Closed date
1992-10-16
Last modified date
1993-01-28
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
13 December 2020