Thanks all. We have looked at the MTU sizes and they all look the same. I will take another look to make sure we did not miss something.
I will update as we move along! Thank You, Terry Martin Lockheed Martin - Information Technology z/OS & z/VM Systems - Performance and Tuning Cell - 443 632-4191 Work - 410 786-0386 [EMAIL PROTECTED] -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Marcy Cortes Sent: Tuesday, August 19, 2008 11:24 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Help with network settings on z/Linux Check your MTU sizes along the way. Try ping with a large packet size (-c ) and see if it gets through. Tracepath command might be useful to see what's happening along the way. Marcy "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Martin, Terry R. (CMS/CTR) (CTR) Sent: Tuesday, August 19, 2008 7:40 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] Help with network settings on z/Linux Hi We have two environments that we are building as part of our POC. We ship data via DB2 Connect from the mainframe DB2 to a Linux guest via a HiperSockets Network. In our DEV environment all of our tables process without issue. In our VAL environment there are six tables that the SQL fails for. We have been engaged with IBM via a PMR on this and have been going back and forth. At this point it appears that the issue is with the number of rows. In the SQL when they do an SELECT * and do not specify the rows it works. When they specify the tables in the Select it apparently increases the size of the SQL and it never gets to the mainframe. It looks like it is a 2k buffer limitation somewhere. Is there anything in the TCP/IP stack in z/Linux or any network setting in z/Linux that would enforce this limitation? IBM says that the TCP/IP and DB2 Connect on the z/OS side appear to be ok. They are sending us back to look at the Linux settings. This is the original error message: DSNL511I .DB1I DSNLIENO TCP/IP CONVERSATION FAILED 922 TO LOCATION 10.4.26.19 IPADDR=10.4.26.19 PORT=32924 SOCKET=RECV RETURN CODE=1121 REASON CODE=00000000 Thank You, Terry Martin Lockheed Martin - Information Technology z/OS & z/VM Systems - Performance and Tuning Cell - 443 632-4191 Work - 410 786-0386 [EMAIL PROTECTED] ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
