Re: Forcing connection limits on CICS Sockets
On Wed, 26 Aug 2009 16:14:03 -0500, Henrique Seganfredo wrote: >The issue is that the stress test just draw too much CPU attention and other >CICS/Sockets clients (other software being tested) have their connections >refused. Is this an issue of the CICS transactions consuming too much, or are you running out of available connections into the listener? I would suggest a TRANCLASS with some limitations could prevent the former (but may well aggravate the latter...) You could set up a second listener (CSKL) on a different port and thus separate the development from the acceptance. Each listener can then be configured separately to accept a given number of connections. >I am thinking on a way of limiting the % of acceptance of sockets calls to the >mainframe coming from the J2EE 'stress-test' servers. Is there anything that >provides a way of forcing connection limits on CICS/Sockets? EZAC Read the fine z/OS Communications Server IP CICS Sockets Guide Document Number SC31-8807 Cheers, Jantje. P.S. You may get better answers on the CICS-L. Have a peek at http://cicswiki.org/cicswiki1/index.php?title=CICS_List to know how to join. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Forcing connection limits on CICS Sockets
On Wed, 26 Aug 2009 16:14:03 -0500, Henrique Seganfredo wrote: >... >I am thinking on a way of limiting the % of acceptance of sockets >calls to the mainframe coming from the J2EE 'stress-test' servers. >Is there anything that provides a way of forcing connection limits >on CICS/Sockets? >... I assume there is a CICS parm to do this (and someone will tell you how), but if not, you can do this using the z/CS Policy Agent. Doing it in CICS is probably easier, though. Pat O'Keefe -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Forcing connection limits on CICS Sockets
Hello, Here at my work we have an Test environment that actually serves for two purposes: 1) test of software under development and 2) stress tests. Many external systems (J2EE based) that are stress-tested rely on CICS/Sockets communication to call some mainframe (Natural) routines. The issue is that the stress test just draw too much CPU attention and other CICS/Sockets clients (other software being tested) have their connections refused. I am thinking on a way of limiting the % of acceptance of sockets calls to the mainframe coming from the J2EE 'stress-test' servers. Is there anything that provides a way of forcing connection limits on CICS/Sockets? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
