I had this asked of me recently and I cannot think of a simple way to do it. Is there some way to stop the binder from adding/replacing a program object in a library if the binder detects any kind of an error which would result in a return code > 4?
I know of the STORENX=NO, but that does not do what I want. The closest that I have been able to think of is to have the binder put the program object(s) into a temporary library, then have a subsequent IEBCOPY step copy the members from the temporary library into the permanent library. What happened is that a "bad" module (binder rc>4) replaced a "good" module. The programmer is asking why would the binder do this? I don't really have a good answer other than "that is the way it works", which is not really very comforting. -- John McKown Senior Systems Programmer UICI Insurance Center Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its' content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. ---------------------------------------------------------------------- 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
