Home > Return Code > Socket Return Code 1121

Socket Return Code 1121

Contents

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? Communication protocol being used: TCP/IP'. Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility United States English English IBM® Site map IBM IBM Support Check here to It's quick & easy. http://1pxcare.com/return-code/socket-recv-return-code-3448.html

We are using DB2 Connect via a gateway which has 2 servers assigned to it. We are using DB2 Connect via a gateway which has 2 servers assigned to it. This blocks all subsequent connection requests to the DB2 server and effectively causes the DB2 TCP/IP Listener task to be non-functional. Subscribe You can track all active APARs for this component. http://www-01.ibm.com/support/docview.wss?uid=swg1PM37030

Dsnl511i Return Code 1127

Tim Reynolds Verizon Data Services Nov 12 '05 #1 Post Reply Share this Question 3 Replies P: n/a dps027 Hi - some time ago I got similar communication errors in an Communic P: n/a Tim Reynolds I support a .Net application running on a SERVER accessing MF Db2 data. Web Scale Globally scale websites with innovative content management and infrastructure approaches Modernization UX and app modernization to powerfully navigate todays digital landscape Omni-Channel Engagement Content-focused web and mobile solution for

  1. Temporary fix ********* * HIPER * ********* Comments APAR Information APAR numberPI25682 Reported component nameDB2 OS/390 & Z/ Reported component ID5740XYR00 Reported releaseB10 StatusCLOSED PER PENoPE HIPERYesHIPER Special AttentionNoSpecatt Submitted date2014-09-12
  2. Temporary fix Comments APAR Information APAR numberPM13608 Reported component nameDB2 OS/390 & Z/ Reported component ID5740XYR00 Reported release910 StatusCLOSED PER PENoPE HIPERNoHIPER Special AttentionNoSpecatt Submitted date2010-05-03 Closed date2010-05-13 Last modified date2010-10-14
  3. SQLCODE -30081. .
  4. The system returned: (22) Invalid argument The remote host or network may be down.
  5. and/or other countries.
  6. All Rights Reserved.
  7. 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.
  8. 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).
  9. 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
  10. How often are you getting them?

Additionally, DSNL511I with SOCKET=CLOSE RETURN CODE=112 REASON CODE=05230138 may also be seen. *************************************************************** Additional Symptoms and Keywords: DSNL511I MSGDSNL511I DSNLIENO SOCKET=CLOSE CLOSE RETURN CODE=112 REASON CODE=05230138 RC112 112 05230138 RETURN CODE=113 RETURN CODE 1121 is ECONNRESET The message is informational. Our C# instansiates a DB2Connectin object and issues an open against it. So you may want to check if there are other errors besides the communication errors.

This seemed to fix the issue. Z/os Unix System Services Messages And Codes We think our problem is load related - b/c we only encounter under productin load and more so on our busiest servers. The ip address is always from the same server in the gateway. http://www-01.ibm.com/support/docview.wss?uid=swg1PI25682 Can anybody help in finding the cause of the problem.

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 112.64.103.172 866 IPADDR=112.64.103.172 PORT=2655 APAR status Closed as program error. SQLSTATE=S1010 while using ADO Communication error SQL30081N ? A completion of connection termination processing in situations where connection termination processing happens to be interrupted.

Z/os Unix System Services Messages And Codes

Resolution Reproduced the issue with Connect for ODBC 5.2 and 5.3 Defect DD00037949 was filed and the issue is no longer reproducible using builds of 5.2 and 5.3 dated after January But repeated instances are likely associated with a firewall that silently discards packets for sessions that it has timed out for inactivity. Dsnl511i Return Code 1127 Hung inactive connection or DBAT, as observed in the Display Thread Inactive command report. . Reason Code=74520442 Both servers are configured the same.

Note: Not all remote client systems that access a DB2 server using TCP/IP will cause this message DSNL511I to occur. http://1pxcare.com/return-code/return-code-157.html You will be required to sign in. 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 My AccountSearchMapsYouTubePlayGmailDriveCalendarGoogle+TranslatePhotosMoreDocsBloggerContactsHangoutsEven more from GoogleSign inHidden fieldsSearch for groups or messages 419,234 Members | 923 Online Join Now login Ask Question Home Questions Articles Browse Topics Latest Top Members

Progress Software Corporation makes no explicit or implied claims to the validity of this information. There might not be any other reported problems being caused by these failures. Confirm the cause by contacting the firewall administrator and having them check the firewall system's logs at the times of the DSNL511I messages. his comment is here Steps to ReproduceClarifying InformationDSNL511I  -DBA7 DSNLIENO TCP/IP CONVERSATION FAILED 985 TO LOCATION 157.133.215.28 IPADDR=157.133.215.28 PORT=1183 SOCKET=RECV RETURN CODE=1121 REASON CODE=00000000 Error MessageDefect/Enhancement NumberDefect DD00037949Cause This is due to the way the

Cross reference information Segment Product Component Platform Version Edition Information Management DB2 for z/OS z/OS 7.0, 8.0, 9.0, 10.0 Enterprise Document information More support for: z/OS Communications Server All Software version: 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. Error description DB2DDF DDFL09 DB2TCPIP Remote client connections may hang when connecting to DB2 z/os and issue the following messages.

Most symptoms occur relative to the failing DB2 11 for z/OS server system in which case the APAR solution can be applied at the DB2 11 for z/OS system where the

After I installed the FP11, the problem was resolved. 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 112.64.103.172 866 IPADDR=112.64.103.172 PORT=2655 The entire risk arising out of the use or performance of the sample code is borne by the user. We have been getting about 50 -30081's per day every since we switched from SNA to TCP/IP four years ago.

The sample code is provided on an "AS IS" basis. Any help greatly appreciated. APAR status Closed as program error. weblink The system returned: (22) Invalid argument The remote host or network may be down.

The conditions may also appear to occur after z/OS 1.13 maintenance (see APARs PM80004 and OA39810), or migration to z/OS 2.1, due to the MsgConnTerm support that now becomes available to DSNL511I @DB2P DSNLIENO TCP/IP CONVERSATION FAILED 527 TO LOCATION :: xx.xxx.xx.xxxx IPADDR=::xx.xxx.xx.xxxx PORT=#### SOCKET=RECV RETURN CODE=1121 REASON CODE=00000000 Wayne Stevens _________________________________________________________________ Register NOW for the IDUG DB2 Tech Conference in Anaheim, Both servers are configured the same. Your cache administrator is webmaster.

Can anybody help in finding the cause of the problem. We typically receive one of these IBM.Data.DB2.DB2Exception messages: ERROR [40003] [IBM][CLI Driver] SQL30081N A communication error has been detected. This issue does not occur with versions 5.0 and 5.1. Using the DDF Installation CLIST, go to DDF Panel 2 (DSNTIP5), set TCP/IP Keepalive (TCPKPALV) to a value shorter than the firewall's timeout.

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. An increase in LOGREC entries describing 04E-00E50013 abend (interruption) conditions. You will be required to sign in. Protocol specific error code(s): '10053', '*', '*'.

Characters Remaining: 255 Copyright © 2016, Progress Software Corporation and/or its subsidiaries or affiliates.