---- "Veilleux wrote: > When we lost our system we had an IEFUSI exit coded and active. >
I'm sorry, but I find this whole discussion a bit overblown. The ability to crash a system certainly didn't surface with 64-bit addressing. Since this is hardly a "mainstream' storage allocation method, it is no more risky than allowing programmers to code privileged code, or create thousands of dataspaces (or for that matter allowing systems programmers to do so). There is quite obviously no programming need to hold 64-bits worth of code, so the amount of storage available is ultimately based on holding data buffers. There isn't necessarily any need to back large virtual storage allocations with paging data sets. This was amply illustrated by using hiperspaces (ESO), that simply caused data misses and retrieved the data from the data set. There was no need for paging support. As for an IARV64 loop ... it's no more risky than a DSPSERV loop. <End of rant> Adam ---------------------------------------------------------------------- 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
