<snip> Not so fast. It isn't quite that simple. The problem is virtual storage allocation has changed with V1R10. Rather than starting at the top of a page and working down until you have to actually get a new page, GETMAIN/STORAGE allocations start at the bottom of a page and work up. This apparently was done to address storage fragmentation issues.
The problem is, if the code had been relying on "knowing" that a new page was being obtained (nuances being taken advantage of) which must be cleared to X'00' (security thing here), it may no longer be true -- and now you have the gotcha because you may run into residual stuff... And this problem may hit various programs, not just from ISVs. It can happen to older code that was in-house developed. </snip> That makes sense, however, either way the result is the same, storage will have residual data in it. This could be a show stopper for 1.10 since we have no way of knowing if all of our old assembler code was coded properly (ala programming 101, initialize any storage that you plan on using). I don't want to find out in production that someone even older than me was too lazy to initialize his storage. Jon L. Veilleux [EMAIL PROTECTED] (860) 636-2683 This e-mail may contain confidential or privileged information. If you think you have received this e-mail in error, please advise the sender by reply e-mail and then delete this e-mail immediately. Thank you. Aetna ---------------------------------------------------------------------- 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
