View Only
  • 1.  Endevor Multiple SCL

    Posted Sep 08, 2023 02:12 PM


    I have a special requirement in Endevor.

    Want to ADD and transfer  Cobol element SCLs in single job.

    Ideally it should add cobol program then add linkcard then transfer cobol program then transfer linkcard. but the processing sequence is all jumbled here.

    I checked "TYPE PROCESSING SEQUENCE" in the region and cobxdb2 is declared at 81 while linkxdb2 is declared at 46, how can we move COBXDB2 before linkxdb2.

    How to make this work.



  • 2.  RE: Endevor Multiple SCL

    Posted Sep 09, 2023 06:26 PM

    to edit the TYPE Seq Parmlib member first go into Endevor, Select Display opt 1 then Site opt 3.

    Press the enter key once and go to the second pane. 

    at the bottom of that panel look for this. the Parmlib dataset and member is shown there.

    If you have edit authority to the dataset then simply move the cobxdb2 before linkxdb2. and save the member.

    Also suggest you read about Type Sequencing in the Endevor Guide.


  • 3.  RE: Endevor Multiple SCL

    Broadcom Employee
    Posted Sep 12, 2023 03:41 AM

    Hello Alamelu,

    I agree with Russ, I just want to point that from Endevor 18.0 the Global Type Sequencing (GTS)  is mandatory and is the only action sequencing option available, system type sequencing has been phased out of the product.
    -> https://techdocs.broadcom.com/us/en/ca-mainframe-software/devops/ca-endevor-software-change-manager/18-0/release-notes-ce18/cumulative-list-of-v18-0-enhancements.html
    Also see, https://knowledge.broadcom.com/external/article?articleId=36545 and https://techdocs.broadcom.com/us/en/ca-mainframe-software/devops/ca-endevor-software-change-manager/19-0/installing/implementation-and-customization/defining-maps-and-inventory-structures/type-sequencing.html


  • 4.  RE: Endevor Multiple SCL

    Broadcom Employee
    Posted Sep 12, 2023 09:20 AM

    There really are two kinds of link cards.  One that specifies linking instructions that follow a compile or assembly, and another that applies to building "composites" from completely built programs. Moreover, the expected timing differs for each link card type. The first kind should be early in the type sequence (before COBOL, assembler, and C), and the other should be much later in the sequence (after COBOL, assembler, and C). Would it be possible for you to use two types of link cards instead of just one? <o:p></o:p>