What happens when MAXIMUM TASKS is exceeded?
Article ID: 25878
Updated On:
Products
Issue/Introduction
What happens when MAXIMUM TASKS is exceeded? Do the additional tasks wait or abend? If they abend, what messages should we see?
Environment
Release: All supported releases
Resolution
MAXIMUM TASKS (The number of TCE/DCE control blocks allocated for the CV to execute tasks) is calculated by adding together MAXIMUM TASKS and MAXIMUM ERUS from the IDMS SYSGEN SYSTEM statement plus the number of SYSTEM Tasks (MASTER, DBRC, Line Drivers and Service Drivers).
If the CV is currently at the MAX TASKS (MAXTASKS) condition (use the command "DCMT DISPLAY STATISTICS SYSTEM" at the Enter Next Task Code to check for this condition) and a request for a new task is issued, no abend occurs. The LTERM from which the new request was issued is put into a queue to wait for an available TCE/DCE.
There are several conditions that are similar to MAX TASK that will result in error messages:
- MAXIMUM ERUS. This specification determines how many External Request Units (Batch or CICS programs) are allowed in the CV at any one time.
It determines how many ERE control blocks are allocated for the CV.
If the CV is at a MAX ERUS condition and a new BATCH or CICS program attempts to start a new database transaction it will receive error-status 1473. - If you are using Max Concurrent Thread on the Task (use the command "DISPLAY TASK taskname" in the SYSGEN to check if this parameter is on) and you do not specify optional apar bit 47 (Original optional apar GS18646) then you will receive message DC055010 for tasks that have exceeded Max Concurrent Thread.|
If the 47 bit is on, the tasks are queued internally and run when the Max Concurrent Thread allows.
Additional Information
See the following IDMS 19.0 documentation sections:
Tuning for Improved Performance and Lower TCO heading Tailor System Generation Parameters
Feedback
