In a recent note, McKown, John said: > Date: Wed, 31 Aug 2005 08:36:38 -0500 > > 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? > Are there cases in which RC>4 but the load module is nonetheless marked executable? Ugh!
But I have experienced frustration on the opposite side of this behavior. I have UNRESOLVED EXTERNAL(S). I have XREF in PARM. Yet I get no cross reference map. Why? Because the load module is marked NX, and does not replace an earlier executable version. So Binder fails to provide a cross reference map in one case where I most need it. Infuriating! Binder ought responsibly to provide a cross reference map if requested in the PARM regardless of whether the load module is saved or not. What cognitive failure moved the designers to believe that I don't want the map if the module was not saved? -- gil -- StorageTek INFORMATION made POWERFUL ---------------------------------------------------------------------- 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
