On 18 Mar 2008 08:55:20 -0700, in bit.listserv.ibm-main you wrote: >>it's possible to zap a module and not leave footprints, though it's not the >default.< > >Yikes! > >Our programmers occasionally ZAP a load module in a test load library, which >is >fine. When the time comes to promote the load module into a production load >library, however, I would like our change management package to prevent the >promotion of any load module which has been zapped. I'm prepared to do that >check programmatically via an exit, if I have a reasonable way of doing it.
Why do they zap rather than just recompile? Superzap may be needed when source isn't available but with the speed of compile and link these days, it just seems to be asking for trouble. > >David ---------------------------------------------------------------------- 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
