Resolving the problem Determine what timeout value has been configured on the firewall. We needed to increate IDACK from 30 to 50, MAXDBAT from 64 to 200 and CONDAT from 64 to 200 and CTHREADS from 130 to 200. This leads to various unexpected DSNL511I messages and other unpredictable symptoms that can occur as a result of unexpected socket close conditions that appear to be randomly generated. Message DSNL425I. .
SQLSTATE=08001 This corresponds to some messages in the DB2 started task running on the MF: 10.30.57 STC11095 DSNL511I -DB2C DSNLIENO TCP/IP CONVERSATION FAILED 866 866 TO LOCATION 18.104.22.168 866 IPADDR=22.214.171.124 PORT=2655 Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. Your feedback is appreciated. What version of DB2 are you on?
The system returned: (22) Invalid argument The remote host or network may be down. Subscribe You can track all active APARs for this component. Cathy Taddei -----Original Message----- From: IDUG DB2-L [mailto:[login to unmask email] On Behalf Of Stevens, Wayne Sent: Tuesday, April 12, 2011 11:20 AM To: [login to unmask email] Subject: [DB2-L] DSNL511I Watson Product Search Search None of the above, continue with my search PM37030: DSNL511I DSNLIENO TCP/IP CONVERSATION FAILED SOCKET=RECV RETURN CODE=1121 REASON CODE=00000000 z/os A fix is available Obtain the fix
Alternatively, this can be set to the value ENABLE if the INTERVAL value on the TCPCONFIG statement in the TCPIP PROFILE is already shorter. Reason Code=77a9733d A completion of connection termination processing in situations where connection termination processing happens to be interrupted. No changes have fixed this problem for more than a month!) I am going to have -30081 etched on my grave... (We run DB2 Client on Windows V8 fp 11, DB2 As a result, the best approach is to apply the APAR solution to the system reporting the symptom, if DB2 11 for z/OS, and any DB2 11 for z/OS partner(s).
There might not be any other reported problems being caused by these failures. Both servers are configured the same. In all 4 cases, the IP addresses appeared to be client workstations. The entire risk arising out of the use or performance of the sample code is borne by the user.
Inner Exception Type: IBM.Data.DB2.DB2Exception ;Inner Exception Message: ERROR  [IBM][CLI Driver] CLI0106E Connection is closed. Watson Product Search Search None of the above, continue with my search Repeated distributed DB2 connection failures Technote (troubleshooting) Problem(Abstract) The distributed DB2 server is working properly most of the time, Dsnl511i Return Code 1127 Location where the error was detected: ‘126.96.36.199'. Reason Code=74520442 Communication API being used: ‘SOCKETS'.
See Trademarks or appropriate markings. weblink However, the information provided is for your information only. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. What version of DB2 are you on? Z/os Unix System Services Messages And Codes
I don't know enough about DB2 Connect Server to say whether this is normal, but I just took a look at our MSTR message logs and found several instances of DSNL511I The condition appears to be prevalent relative to connections with remote DB2 for z/OS partners, and this is due to the use of DRDA two phase commit support which tends to Inner Exception Type: IBM.Data.DB2.DB2Exception ;Inner Exception Message: ERROR  [IBM][CLI Driver] CLI0106E Connection is closed.
You will be required to sign in. ERROR  [IBM][CLI Driver] SQL30081N A communication error has been detected. communic
In other words, the communication errors did not show the root cause, and actually it also spent me quite some time to identify the root cause problem. We are using DB2 Connect via a gateway which has 2 servers assigned to it. Post your question and get tips & solutions from a community of 419,235 IT Pros & Developers. his comment is here Confirm the cause by contacting the firewall administrator and having them check the firewall system's logs at the times of the DSNL511I messages.
Document information More support for: DB2 for z/OS Software version: 9.1 Reference #: PM13608 Modified date: 14 October 2010 Site availability Site assistance Contact and feedback Need support? A console dump taken while the problem is happening will show ASXBSENV has 0's for the ssidDIST address space. Symptoms may be unpredictable but the following symptoms have been observed at, either or both, the DB2 11 for z/OS server and remote (usually also DB2 for z/OS) requester partners: . We think our problem is load related - b/c we only encounter under productin load and more so on our busiest servers.
We typically receive one of these IBM.Data.DB2.DB2Exception messages: ERROR  [IBM][CLI Driver] SQL30081N A communication error has been detected. As a result, the DB2 TCP/IP Listener task will wait indefinitely for this "non-existing" connection request. We think our problem is load related - b/c we only encounter under productin load and more so on our busiest servers. All Rights Reserved.
Message DSNL406I and an unexpected entry in the Display Thread Indoubt command report. A performance improvement that is achieved by utilizing TCP/IP Synchronous, as opposed to Asynchronous, Receive operations while the server thread (DBAT) is processing an active transaction. SQLSTATE=08003 So the communication problem (whatever it is) seems to manifest in the first exception - Communication problem - and this must hose up some of our connections so at that Document information More support for: DB2 for z/OS Software version: B10 Reference #: PI25682 Modified date: 04 November 2014 Site availability Site assistance Contact and feedback Need support?
All material , files, logos, and trademarks within this site are properties of their respective organizations. The sample code is provided on an "AS IS" basis. Hence, DB2 rejects the connection. APAR status Closed as program error.