We have a Mainframe Performence issues, that is there are some times the CPU is overloaded.
In the past many cases we see that the Online transactions are causing the problem, We submit the transaction and the transaction kept on running for a quite long time behnd the seen and we are able to track that only when the Region is down where the transaction is holding down all the resources like that...
In the case of a JCL we can have TIME parameter coded to limit the CPU usage of a JOB.
Is there anything like this available with CICS to limit the run time of a transaction??
I could not get enough understandings from other sites on SIT parameter ICVR .
Believe these are system Parameters and not at the Application level. Could you please provide me a detailed idea of these Parameters and the use. And the usage of the variables as an Application level programmer.
It would be helpful if you could provide any other alternatives where we can take preventive measures to avoid any issues with the performence.
There is nothing an application programmer can do to alter transaction behavior as far as time outs. ICVR is an SIT parameter and applies to the entire CICS region, not any particular transaction within the region. The CICS System Definition Guide describes the SIT parameters in detail.
CEDA allows runaway transaction time limits to be set by transaction name, but few sites allow application programmers access to CEDA. CICS does not generally limit transactions to certain amounts of CPU time.
If you have having performance issues (or think you are having performance issues), the absolute best thing you can do is to contact your site support group and have them assist you. It is possible that what you believe to be a transaction issue could be something else entirely -- and your site support group is where the determination would need to be made.