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