From time to time I get what is known as a deadly embrace between two CICS applications. One will die and the other will go into a suspended status and will not abend without terminating the transaction manually.
1. Can I use the DTIMOUT parameter for the two CICS transactions?
2. How can I determine what to set the DTIMOUT parsmeter to?
The thing to do is find out why you have two different transactions that are getting this deadly embrace. This is not something you should just accept as "one of those things" and live with it. It may be something as trivial as not having enough strings/buffers on a VSAM file. Turn on the trace and find out!
There is no prescriptive setting for DTIMEOUT that I can give. It should not be too large to avoid unnecessary end user waits but again, not too small so that the lock can be resolved. However, I'm slightly concerned that when one transaction abends, the other was still waiting on the former still is stuck.
After an investigation you might want to raise a problem but ensure you do the investigation first!
CICS Technical Strategist -- CICS expert at Search390.com
Editor's note: Do you agree with this expert's response? If you have more to share, post it in one of our .VO7aaqqaAFk.0@/search390>discussion forums.
Dig Deeper on IBM system z and mainframe systems
Related Q&A from Robert Crawford
For better mainframe capacity planning, how do I convert CPU hours to MIPS? And is there a way to calculate the relationship between MIPS and MSUs? Continue Reading
I have two years of experience in mainframe technology, currently working as a mainframe developer. I want to change to Java technology. Continue Reading
I want to replicate DB2 from the mainframe to an AIX box since it's cheaper and the copy can be used for testing. Is this possible? Continue Reading