Previous Topic: Review PrerequisitesNext Topic: How Concurrent Action Processing Works


Concurrent Action Processing Overview

Concurrent Action Processing (CAP) speeds up the processing of batch jobs and packages. CAP causes certain element action requests to be executed concurrently, thus reducing the elapsed time that it takes to process multiple actions.

CAP uses Global Type Sequencing to determine which actions can be processed at the same time. The CAP facility processes certain element actions of the same type concurrently, and must complete the processing of all actions of the same type before starting to process elements of the next type. However, any action types that are not defined in the Global Type Sequence can be processed concurrently with any other action. The following actions can be processed concurrently: ADD, ALTER, UPDATE, RETRIEVE, MOVE, GENERATE, DELETE, SIGNIN, and TRANSFER CA Endevor SCM to CA Endevor SCM. All other actions on the request are processed serially.

The administrator can specify whether CAP is allowed and how many additional started tasks a single job can create for concurrent processing. These parameters are set in the C1DEFLTS table. Through the External Security Interface, the administrator can limit who is authorized to use CAP. This method of processing is not initiated automatically; users must request CAP at the job level.

Note: Concurrent action processing with CA CM Enterprise Workbench is available only for packages and enterprise packages, not for element actions.