I guess (but am not even certain of this) that *IF* you have the resources to do a "mass recompile", that it doesn't HURT. However, if doing so (and more importantly making certain that everything that NEEDS testing GETS tested) means that you "skip" releases of the compiler (or delay upgrades), I would still go with "gradual" recompile when otherwise touching the program.
I certainly do NOT read, "Chapter 1. Do I need to recompile?" at "http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/igy3mg30/1.1 as RECOMMENDING a "mass re-compile". On the other hand, if you have done this once (and more importantly "automated" how you do it AND the related testing), then I suppose it can work on an ongoing basis. Again, I would PERSONALLY recommend spending more resources on in-house training of what's worth USING in the new release, rather than making every application program be recompiled and retested ... but if you have the RESOURCES, then go ahead and do it (but I do think you are in a very small minority doing so) "Shmuel Metz (Seymour J.)" <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>... > In <[EMAIL PROTECTED]>, on > 08/27/2005 > at 03:14 PM, Bill Klein <[EMAIL PROTECTED]> said: > > >1) Unless you are upgrading from a VERY old compiler, there is > >absolutely NO need to "recompile" every program. > > There are two obvious needs: > > 1. Ensure that you actually know where the source code is. > > 2. Identify any conversion issues, so that you can schedule eventual > remediation. ---------------------------------------------------------------------- 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
