Global Type Sequencing establishes a processing sequence for CA Endevor SCM Types that must be processed in a specific order. For example, COBOL copybooks must be processed before COBOL programs.
Other Types, such as JCL, can be processed in any order. You do not need to define such Types in the Type processing sequence.
For Global Type Sequencing to be in effect, both the PARMLIB data set which contains the Type Sequence member and the Type Sequence member must be created and defined in the C1DEFLTS table.
All supported versions of CA Endevor
1 - Allocate the PARMLIB data set.
The PARMLIB data set is required and contains the Type Sequence member.
To allocate the PARMLIB data set, edit the BC1JEPRM member in the CA Endevor CSIQJCL data set and execute the batch job.
2 - Create Your Type Sequence Member
The order of the Type records in the Type Sequence member represents the processing sequence.
Create the file using one of the following methods:
Col 1 Col 16 Col 72 C1DEFLTS TYPE=MAIN, X . . PARMLIB='BST.CASCMMF.PARMLIB', X TYPESEQMBR=ETYPESEQ, X .
4. 2 - When CA Endevor appears, open the Type Sequence display in Foreground.
The processing sequence displayed matches the sequence defined in the Type Sequence member.
For more detailed information on Type Sequencing, how it works, how it affects Concurrent Action Processing,
and how to implement it, go to the CA Documentation site ---
+ Defining Maps and Inventory Structures
>> Type Sequencing