Starting with Endevor V18.0  Type Sequencing is required to define the processing order of SCL and API Element actions, regardless of the inventory location.  With Type Sequencing enabled, SCL and API Element actions are executed in the order that the Types are listed in the Type Sequence member in the PARMLIB.   

Prior to Endevor V18.0, if not using the Global Type Sequencing option, element actions executed in the same order that the Types were defined to the System and Stage by the administrator.  This order could be different for different Systems. 

How can different a Type Sequencing be set up for different Systems using Global Type Sequence?

Release:   All Supported versions
Component: ENDBAS

Update the Type Sequence member in the PARMLIB and add the SYSTEM clause to create a unique order of Types within a specific System.

Type records use the following syntax:

TYPe ‘Type-name’ [SYStem ‘system-name’] [CATegory ‘category-value’] DESCription ‘Sample Type Description’.

SYSTEM system-name

(Optional) Specifies the one- to eight-character System name where the Type is located. Enclosing the name in single quotes is optional. If Types with the same name are located in different Systems, this clause lets you specify different processing orders for each Type and System combination. If this clause is omitted, the Type sequence order for the Type name applies to the entire site. The name is converted to uppercase characters.

The following general rules apply to the Type record syntax:

•  The ending period (.) delimiter is required.
•  The Type name and description fields can be on separate lines.
•  Each record is 80 bytes.
•  No text can appear in columns 73 to 80.
•  Comments can appear in the file by placing an asterisk in the first column position.

For more information see Type Sequencing in Endevor TechDocs