I work as a programmer in a small shop and we're pretty much on our own when it comes to compile processes. Over the years we've built our own ISPF application to monitor source code and generate standard compile JCL. Since we have to "eat our own dog food" we have put a lot of effort into making the processes programmer-friendly and productive.
However, to achieve that we've sacrificed the rigor provided by products like Endevor. The in house tool kit does not guarantee source code integrity from start to finish. The programmer can easily shoot himself in the foot by ignoring established procedures and managing his code outside of the tool kit. I have worked at an Endevor shop, and the programmers, almost to a man (or woman), hated the process because it was not well suited to the unit test code/compile/test loop. Many used their own compile JCL for their unit testing, not wanting to wrestle with Endevor until they were obliged to. While I was there I wrote a simple ISPF application to generate compile JCL, and it was by far the most popular tool that I created. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
