Jihad, We are not using CICS Web Services, but thank you for the pointer.
Bob -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jihad K Kawkabani Sent: Tuesday, April 27, 2010 9:24 AM To: [email protected] Subject: Re: HATS client timeout/performance issue Greeetings We had a similar issue. If you are using CICS Web Services look at PM04061: CICS WEB SERVICES PERFORMANCE. TCP/IP NAGLE ALGORITHM RESULTS INUNNECESSARY DELAYS. See if this could be your issue. Regards, Jihad K. Kawkabani IT Systems Engineer Consultant Voice: 440.395.0740 Network: 575.0740 Cell: 440.465.2969 "Richards, Robert B." Cross post (IBM-Main and TCPIP) We are experiencing an unusual situation and I am wondering if anyone else has seen this at their shop. As phrased by my boss: "We are currently experience a client timeout with HATS applications. I'm calling it a client timeout because the CICS session associated with the user is active but the user received a timeout message. This issue is only with HATS applications and cross over business application lines." My TCP/IP guy wants to implement NODELAYACKS for specific ports for problem resolution per the following IBM recommendation for TCP/IP WAS performance tuning: - Consider specifying NODELAYACKS for ports. This may improve throughput for more trivial transactions, but it does add more overhead for more complex transactions. Using this option will cause the acknowledgments (ACKs) to be sent back immediately to the client, rather than waiting for more data to accumulate. Because CICS still has the session as active, it holds on to the client's too long and, as you might expect, that has a bad ripple effect until CICS terminates the task at its timeout. Any takers? :) Bob ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
