We have three transactions that constantly get the abend AZTW. Explanation: An attempt was made to attach a task on a remotely owned terminal that was already running a task. User response: Check the terminal control table definitions in the systems involved.We have TCPIP and no other transactions get this abend. How can we stop these from happening?
I don't do remote debugging in this forum. However, I think you have got a mismatch between timeout specified for the real end-user terminal that is running the transaction in a remote CICS region and the timeout set for the link into that remote region. Bump up the link timeout and these abends should go away.
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
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.