Endevor

  • 1.  SCLM to ENDEVOR migration

    Posted Feb 06, 2019 02:17 PM

    Hi All,

    IS there automation tool available for migrating the code from SCLM to Endevor.



  • 2.  Re: SCLM to ENDEVOR migration
    Best Answer

    Broadcom Employee
    Posted Feb 07, 2019 05:52 AM

    Hi. There are utilities with Endevor. (Analyze & Load). They are described in manuals, and will be usefull. I have used them in similar situations in my pre-sale role.

    Our people in Services have developed even more advanced utilities, so if you want access to these programs we need to establish contact to our services people.. 

    You can mail me directly at jorgen.dam@broadcom.com.

    BR

    Jorgen



  • 3.  Re: SCLM to ENDEVOR migration

    Posted Feb 11, 2019 08:44 AM

    Yes, I too have used the Inventory Analyzer and Load process to covert many applications to Endevor.  You have the option to Load the Source and have a toeprint to the load module to marry the two entities or you can choose to have a full footprint to LOAD the source and then Generate to get the output for the full footprint synchronization. 

     

    BTW - Welcome to Endevor you have an awesome community backing as well as CA Support to assist you when needed.

     

    Best of luck,

    Phon



  • 4.  Re: SCLM to ENDEVOR migration

    Broadcom Employee
    Posted Feb 13, 2019 03:54 PM

    Hello, I am also from the Mainframe Division at Broadcom (Services)...Welcome - We help clients with conversions - our observations are that since SCLM uses PDSE's, that simplifies the migration - it is not a challenging migration, the generic tools (inventory analyzer and the BPI) would work well. 

    You can reach out to me directly,

    martha.dewey@broadcom.com

    Cheers,

    Martha



  • 5.  Re: SCLM to ENDEVOR migration

    Broadcom Employee
    Posted Feb 15, 2019 10:52 AM

    A product team within Broadcom (CA, at the time) migrated form SCLM to Endevor.  Here's their comments:

     

    If the customer has someone who understands the SCLM translators and how they were created the conversion should be simple,  if they have the original JCL that was used create the models for the SCLM translators that would be a good start.

     

    One thing that we with our conversion was to make use of a lot of symbols in our processors.   The symbols were setup to support using different levels of DB2 macros to be used and easily overridden without requiring a new processor, just a processor group.   We also created Endevor processor statements that could be reusable within the processor group by changing the symbols on input.

     

    Other than that, there weren't any tricks other than taking an inventory of the existing SCLM translators and trying to get to as few Endevor processors as possible.

     

    I hope this information was helpful.

     

    Pete McCullough