Limiting the amount of CPU consumed by a task in IDMS

Products

• IDMS
• IDMS - Database
• IDMS - ADS

Issue/Introduction

Question:  

Is there a parameter, a limit, or a method that will limit the amount of CPU consumed by a task in IDMS? 

 

Answer: 

There are several types of limits that you can set for tasks in the sysgen, but CPU consumption is not one of them. You can set limits for the number of calls, the number of locks, the amount of I/O against the database, and the amount of storage consumed.

You can also set limits on: 
1- the amount of time the system permits a task to wait for a resource (Inactive Interval); 
2- the amount of time the system permits an external request unit to wait for a resource (internal wait); 
3- the amount of time the system permits a task to wait for a quiesce operation to terminate (Quiesce wait); 
4- the amount of time the system permits a terminal or external request unit to be inactive (Inactive Interval); 
5- the amount of time the system permits a task to execute without returning control to the system (Runaway Interval); 
6- the amount of time the system waits for an external request unit to issue a database request (External Wait); 

All CICS tasks will run as external tasks (ERUs). The most effective limit to apply for those tasks is probably a limit on calls, either at the system or program level. 

Environment

Release: IDADSO00100-18.5-ADS-for CA-IDMS
Component: