How do I implement Endevor Global Type Sequencing?

Products

• Endevor Software Change Manager (SCM)
• Endevor Software Change Manager - Natural Integration (SCM)
• Endevor Software Change Manager - ECLIPSE Plugin (SCM)
• Endevor Software Change Manager - Enterprise Workbench (SCM)

Issue/Introduction

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.

 

Cause

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.

 

Environment

Release:
Component: ENDBAS

All supported versions of CA Endevor 

 

Resolution

 

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:

1.   Use the BC1JBTSE utility to build a Type sequence file to a sequential work file, and then edit this file.

•   See the Build a Type Sequence Member using the BC1JBTSE Utility section in Create Your Site Type Sequence Member

2.   Use the standard ISPF editor. Add Type sequence records, as appropriate for your site.

•   See the Build a Type Sequence Record Using an Editor section in Create Your Site Type Sequence Member 

3.  Define the Type Sequence PARMLIB and Member in the C1DEFLTS table: 

Col 1       Col 16                                           Col 72
            C1DEFLTS TYPE=MAIN,                              X
            .
            .
            PARMLIB='BST.CASCMMF.PARMLIB',                   X
            TYPESEQMBR=ETYPESEQ,                             X
            .

4.  Verify the Type Sequence Member
   4. 1 -  Launch an CA Endevor CLIST.

• •   If the Type Sequence table has been defined correctly, CA Endevor starts.
  •   If there is a coding error in the table, console messages appear that identify the error.
  •   For example: 
    
    • + TYPE TYPE1 SYSTEM SYS1 CATEGORY 12345678A    DESCRIP    
    • +BSTPPARS: E006 VALUE SPECIFIED IS TOO LONG: 12345678A    
    • +h:mm:ss  B1TS011E  TYPE SEQUENCE TABLE HAS ERRORS       
    • +h:mm:ss  B1TS012E  SCL PROCESSING IS NOW DISABLED.

• •   Correct any errors, and launch the CLIST again. 

             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.

 

 

Additional Information

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 ---

  https://docops.ca.com

•  Logon using your email address and CA Support Online password
•  In the Select Product drop down box, search for Endevor and select the appropriate version
•  In the Table of Contents on the right, go to :

+ Implementation

+ Defining Maps and Inventory Structures

>> Type Sequencing