Re: IBM's CCCA and customized LCPs for Enterprise COBOL migration

Larry Kahm wrote:
In various sites, I've seen differences in compile options at different stages. Sometimes this was deliberate, other times it was based on history. I believe the options should be set once for all levels - and overrides used if at all necessary.

With ChangeMan, you compile once for the lowest level of the promotion path, and the source and load module are copied (in tandem) through each level of the path. With Endevor, you compile at each level of the promotion path - and with that comes the risk that the options >may< not be the same. I believe SCLM handles things the same way that ChangeMan does. I can't speak for other products.

One of the aspects of this Enterprise COBOL migration that I want to ensure is that the options are a) reviewed, b) understood in context, and c) standardized across promotion levels. Because I'm still idealistic, I'd like them to be consistent across applications (but I know better)....

Larry Kahm
Heliotropic Systems, Inc.

Just a minor correction. I work in a shop that uses CA-Endevor to manage source code and object code, and Endevor can be configured either to recompile every time a program is promoted to a new environment/stage, or to be compiled only once when it is first added. Our sysprogs chose to compile once and promote source and executable without recompiling. This guarantees that the code installed is the code that was actually tested.

It's also possible to configure Endevor to either allow or prohibit PROCESS/CBL compile time options. It is also normal with Endevor to create multiple compile templates, for example to support plain batch COBOL compiles, batch COBOL with DB2 compiles, COBOL CICS compiles, COBOL CICS with DB2 compiles, et cetera. So even if PROCESS/CBL is prohibited, you can create a unique compile processor that enforces a different set of compile time options for special cases (compile with only production copybooks instead of development copybooks). We also use it to manage assembler, JCL, proc, easytrieve, and runtime documentation.

Endevor is a large and flexible tool. Our biggest problem with it is managing concurrent or parallel development. If a production program needs an emergency fix we can do it, jumping over in-flight development, but the code change must then be manually retrofitted to multiple in-flight versions for various product releases. Much of that problem is bureaucratic red tape.

And no, I do not work for CA. Naturally, Endevor was written by someone else before CA acquired it.

With kindest regards,


--
http://arnold.trembley.home.att.net/
.

Relevant Pages

  • Re: Quicksort recursiv
    ... My shop uses Endevor, and I have no problems embedding PROCESS or CBL compile directives in my COBOL source code, and they work as expected. ... We recently had a problem with a CICS program that extracted EDSA usage numbers from CICS, and it would not work correctly without TRUNC, which is discouraged for performance reasons. ... If PROCESS/CBL commands could not be specified in the COBOL source file, they would need to build a special Endevor compile processor just for that one program. ...
    (comp.lang.cobol)
  • Re: Pro*COBOL and CLOB Columns
    ... :>>Our Endevor is also configured with several different environments, ... :>>and we only compile into the earliest environment and stage, ... :>>configure Endevor so that the program will be automatically recompiled ... :>It escapes me why shops recompile tested code. ...
    (comp.lang.cobol)
  • Re: Pro*COBOL and CLOB Columns
    ... >>configure Endevor so that the program will be automatically recompiled ... > It escapes me why shops recompile tested code. ... They want it to work even when some maintenance programmer has to ... to compile into STG1TEST using Endevor, ...
    (comp.lang.cobol)
  • Re: IBMs CCCA and customized LCPs for Enterprise COBOL migration
    ... With ChangeMan, you compile once for the lowest level of the promotion path, ... With Endevor, you compile at each level of the promotion path - ... to load it into Endevor for unit testing. ... the choice in the change management product when they compile the ...
    (comp.lang.cobol)
  • Re: COBOLs Influence on C
    ... Cobol, along with most compiled languages, is the same. ... learn of missing external names either at link or execution time. ... name at compile time and attempt to link the OBJ at link-edit time. ... Create an EXE that uses some of the subroutines in the DLL. ...
    (comp.lang.cobol)