what does AMBLIST tells you about "patched" module.
Nothing one should care about.... I've also compared the listings of AMBLIST (patched and unpatched module) and they just differ in the hex-listing (only at the expected locations).
Why don't you use AMASPZAP for such kind of patches?
Well,.... now as I fight with this stuff for some days, I really think I should try to argue our management that we should use AMASZAP.
The problem is, that the bytes we have to patch are on different byte offsets with every release - so we also have to create new control cards for AMASZAP for every release.
Currently I wonder if it is possible to 1. build our application, 2. analyze all needed program objects 3. find the offsets to patch 4. write control cards for AMSZAP I guess this would be fewest pain for all ;) Bye, Michael ---------------------------------------------------------------------- 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
