What exactly is TCIOWAIT? We have an MNCONV=YES set and have a transaction that is conversational. We get separate 110's for each of the terminal interactions. Unfortunately Tivoli PR appears to aggregate the interactions into a single transaction with a single response time which can be many minutes, even hours. There is an SLA on this and we are not achieving our goal. Can I, safely (accurately) exclude TCIOWAIT from the overall response time as 'user think time'?
I don't know anything about the way this tool accounts for transactions -- but I deduce that as the task number has stayed the same, that's why you are getting longer-than-expected running times.
Although some installations would disagree, I think it reasonable to exclude the terminal interaction time from your performance SLAs. It's somewhat unfair to blaim CICS for taking ages to process a conversational transaction when most of the seconds are going to bevallotted to the end-user thinking about something.
I hope you have considered recoding this long-running conversational process into pseudo-conversational mode...for all the usual CICS and performance reasons.
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.