Best Practice Implementation › How to Perform the Best Practice Implementation › BPI Software Inventory Lifecycle › Global Type Sequencing

Global Type Sequencing

By default, the BPI enables Global Type Sequencing. When this feature is enabled, API element actions (if wildcarded or masked) and SCL element actions are processed by a single Type sequence defined at the site level in the Type Sequence member created by the administrator.

Global Type Sequencing is a prerequisite for the following features:

• Concurrent Action Processing (CAP)— When CAP is specified for a batch job or packages submitted for processing, certain element action requests are executed concurrently. CAP uses Global Type Sequencing to determine which actions can be processed at the same time.
• Autogen option for Add, Update, and Generate actions— When Autogen is specified for an element, elements that use this component element are automatically generated. Autogen requires Global Type Sequencing so that the elements that use a component are generated after all of the components have been processed (for example, macros before source, source before load modules).

To enable Global Type Sequencing during the BPI process, you define the type sequence order in the table T#GLBSEQ. Types and System names need to match those you specify in the T#TYPES and T#SYSTMS tables.