Global Type Sequencing › How to Enable Global Type Sequencing › Review Prerequisite Information › Type Processing of Batch Jobs › How Global Type Sequencing Affects Concurrent Action Processing

How Global Type Sequencing Affects Concurrent Action Processing

Global Type sequencing is required when using Concurrent Action Processing (CAP). You can make CAP more efficient by including a category definition for Types that can be processed simultaneously. Categories are defined in the Global Type Sequence table.

Important: Specifying a category in the Global Type Sequencing table does not affect how sequenced Type and nonsequenced Type requests are built and sorted. The category only affects how the actions are dispatched by Concurrent Action Processing.

CAP processes requests as follows:

1. When CA Endevor SCM is dispatching element actions to process concurrently, it refers both to the Type and to the category associated with the Type when deciding which action requests to dispatch.
   1. If the next request in the sequenced Type chain contains the same category value as the previous request, that element action can be dispatched to an available STC.

      With categories, CA Endevor SCM continues dispatching element actions from the sequenced Type chain as long as the category value matches the previous request. Available STCs only have to wait if sequenced Type requests from one category value are still processing and there are no non-sequenced Type requests to process.

   2. If the next request does not have the same category value, CA Endevor SCM attempts to dispatch a request from the nonsequenced Type chain.

      Without categories, element actions of the next sequenced Type number have to wait until all actions of the previous sequenced Type have completed processing. Nonsequenced Type element actions are then dispatched as STCs become available or after all the sequenced Type requests are dispatched. Available STCs remain idle if there are sequenced Type requests still processing, and there are no requests from the nonsequenced Type chain to process.

2. When all the requests have been processed for a particular sequenced Type and category, CA Endevor SCM begins processing requests for the next sequenced Type.
3. When all requests from the sequenced Type chain have been completed, any remaining requests from the nonsequenced Type chain are then dispatched.