Job control via process limitation is generated using the TACCLASS statement. Process limitation depends on the TAC classes, i.e. you can issue a separate TACCLASS statement for every TAC class.
 | TACCLASS statement in section "TACCLASS - define the number of processes for a TAC class" |
TASKS=
The maximum number of processes that are allowed to process jobs for this TAC class.
TASKS-FREE=
The minimum number of processes that are to be kept free for the processing of jobs from other TAC classes or of jobs that are not assigned a TAC class.
In this method the number of the TAC class says nothing about the priority with which its jobs are processed. Only the number of processes that you allow for this TAC class specifies how strongly the processing of the jobs is suppressed as compared to other TAC classes.
This method can then be used sensibly when only a few different types of jobs (and therefore only a few TAC classes) in a application and, for example, when you want to prevent long-running jobs from reserving all the processes of an application and therefore unnecessarily slowing down the processing of other important jobs, e.g. administration jobs.
| For information on the use of TAC classes in UTM cluster applications, see also the applicable openUTM manual “Using UTM Applications on Unix, Linux and Windows systems”, section "Using global memory areas" in the chapter "UTM cluster applications". |
