You cannot set such a constraint within CICS. CICS runaway task control does not apply for activity taking place within a DB2 address space. The closest I can get to, and this is not much of an help, is to use TCLASS facilities to limit the number of concurrent transactions that have a predicatably high DB2 activity.
Dig deeper on Mainframe operating systems and management
Related Q&A from Robert Crawford
The mainframe is IT's original cloud, and there are still ways to float cloud operations onto big iron today. But is it pragmatic?continue reading
With 3270 bridge, you can't stack input messages into one structure. The bridge can't process them all at once. It takes a little more work.continue reading
CICS expert Robert Crawford offers advice on determining the connection between CICS transactions and MQ Queue name.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.