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
