obj_type=KC_TASKS_PAR

The values relating to the number of application processes can to be modified, i.e. the total number of processes, maximum number of processes for processing asynchronous jobs and for processing program units with blocking calls and the number of processes reserved for UTM-internal jobs and dialog jobs that do not belong to a TAC class.

You must assign the data structure kc_tasks_par_str in the data area.

Possible modifications

All the modifications described below can be made in a single call.

Field name	Meaning
mod_max_tasks[3]	Change the total number of processes running.
	In this field you specify the maximum number of processes that are running for the application. mod_max_tasks is a target value for the current number of processes. The number of actually active processes that currently process jobs of the application is stored in the curr_tasks field (see kc_tasks_par_str as of "kc_tasks_par_str - Number of processes"). This can differ from mod_max_tasks for a short period at the startup or termination of a process.
	Maximum value: the maximum value (tasks) defined in MAX at KDCDEF generation Minimum value: '1'
mod_max_asyntasks[3]	Modify the maximum number of processes that can process asynchronous jobs simultaneously. Specify in mod_max_asyntasks the maximum number of processes that can simultaneously be used for asynchronous processing.
	The number specified here serves as a upper limit value. The actual maximum number of processes that can be used concurrently for asynchronous processing (see kc_tasks_par_str as of "kc_tasks_par_str - Number of processes", curr_max_asyntasks parameter) may be lower than the value specified in mod_max_asyntasks, because the actual number is limited by the number of processes of the application that are currently running (curr_tasks).
	Minimum value: '0' Maximum value: the maximum value defined in MAX at KDCDEF generation (asyntasks).
mod_max_tasks_in_pgwt[3]	Modifies the maximum number of processes which may simultaneously process jobs for program units in which blocking calls are permitted. Specify in mod_max_tasks_in_pgwt the maximum number of processes in which program units that have blocking calls can run simultaneously.
	The number specified here serves as a upper limit value. The actual maximum number of processes processing program units with blocking calls simultaneously (see kc_tasks_par_str as of "kc_tasks_par_str - Number of processes", curr_max_tasks_in_pgwt parameter) may be lower than the value specified in mod_max_tasks_in_pgwt because the actual number must be at least 1 below the number of currently running processes of the application (curr_tasks).
	mod_max_tasks_in_pgwt='0' is rejected if the application contains transaction codes or TAC classes with pgwt='Y'.
	Minimum value: '0' Maximum value: the maximum value defined in MAX during KDCDEF generation (tasks_in_pgwt).
mod_free_dial_tasks[3]	This value can only be modified if a TAC-PRIORITIES statement was issued during KDCDEF generation.
	In mod_free_dial_tasks, you enter the number of processes in the application reserved for UTM-internal jobs and for dialog jobs that do not belong to a specific dialog TAC class. This portion of the total percentage is then not available for processing jobs to dialog TAC classes.
	If mod_free_dial_tasks >= mod_max_tasks after the process figures have been modified, an application process may still process jobs to dialog TAC classes.
	Minimum value: '0' Maximum value: value in tasks -1

Period of validity / transaction management: type A ("KC_MODIFY_OBJECT - Modify object properties and application parameters")

KDCAPPL ("KDCAPPL - Change properties and limit values for an operation")