> -----Original Message-----
> From: IBM Mainframe Discussion List On Behalf Of David Eisenberg
>
> 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.
Sounds like it's possible for your programmers to roll out to production
programs whose load modules don't match their source. Seems like a
rather large "hole" in change management to me.
Is it not feasible for them to simply recompile a changed source deck,
and avoid this kind of situation?
-jc-
----------------------------------------------------------------------
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
