On Tue, 9 Dec 2008 07:30:32 -0800, Edward Jaffe wrote: > >And, if IBM, ISV, and customer in-house developers would use >IgvInitGetmain and IgvInitFreemain on their test/development systems--as >we do--nobody would have experienced this issue to begin with. Of >course, it's hard to fault someone for not using an undocumented >feature. These TRAPs have been around since OS/390 V2R6. They work. >Perhaps it's time they were documented, too! > What are we on this list allowed to know about what the IgvInit* traps do? Realistically, the most one could expect is that at GETMAIN/FREEMAIN (or newer counterparts?) random, unpredictable data would be written over the affected storage with the intent of causing program checks.
Unrealistically, one might wish that additionally each GETMAIN should allocate a separate page which would be read-protected until it was written, and that each FREEMAIN would immediately read and write protect any entirely freed page. -- gil ---------------------------------------------------------------------- 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
