Problem solve Get help with specific problems with your technologies, process and projects.

Complications due to the nature of the CICS UnitOfWork processing

I have a program that does a WRITEQ to a TDQ, trigger level=1. When the trigger is reached a second transaction is started and its program does a READQ. The READQ returns a QZERO condition as if the Queue is empty but it's not. When I CEBR the TDQ it has records in it which continue to stack up because the READQ has not been performed to delete them from the Queue.

Both the Queue and programs run in the same CICS regions so what do you think could cause a READQ to return a QZERO condition on a TDQ that has data in it? I'm stumped.

I wonder if you have got a bit of a complication due to the nature of the CICS UnitOfWork processing. You will get the empty Q condition if the putter's UoW is still active when you try to read the TDQ. I suggest just putting in a short wait in the reader transaction to cope with this situation. So if you get an empty Q issue a 1s wait (say, up to 5 goes) before re-reading the TDQ after each wait.

Robert Harris
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

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.