> > But, are you so memory constrained that this is an issue? Everyone is memory constrained at some point. That's what paging storage on AUX is for and even though you may not have done any paging since the Reagan administration, its still the way the system will work if you let it.
Are there steps you can take to limit individual usage? Sure. IEFUSI is your friend. You can make it as generous or as tight as you want. I'd lean toward very generous allocations because its so tedious to undo that when you find the case of a legitimate user who's got a deadline and can't get there because of your (ahem) rules. The key question is how much virtual does the user population (on average) need, in order to get their job done? Multiply that by the number of users and some handy fudge factor of your own choice and then size your AUX to meet that demand. Alternately, look at your slot utilization when things are going bad and start thing in terms of doubling or tripling the number of slots. I would also do whatever it took to configure ISPF and user profiles to use BROWSE instead of VIEW. I don't understand why they foisted that half baked sack of dog stuffing on us in the first place. But I guess my feelings about ISPF are somewhat well known by now. If you use a logon clist/exec you can pull almost any stunt you want during logon processing, so it ought to be relatively straightforward to coerce the right setup in relatively short order. > > Some users may need more than your arbitrary limit to do their job. > > Some/most may not. Set the size limit to a reasonable number. Then, let > each user justify the requirement for more. Unjustified users shouldn't be > allowed to open huge files in edit/view mode. Too many such users can > bring even a system with "lots" of real storage to its knees. Yeah. Yeah. But how about providing a reasonable amount of paging storage? The whole point of that zillion dollar box is for your users to get their jobs done on behalf of the business. Arbitrarily deciding to throw anti-personnel mines in their way doesn't look like a good use of your time or theirs. It's 2005! It is long past time to get off the dime and ditch these crufty old rules of thumb. They're not worth the neurons they are taking up in decades-old memories. That box is there to get work done and your job is to make sure it accomplishes that. Is anything gained by placing barriers in the user's path to getting the job done? I would guess not. CC ---------------------------------------------------------------------- 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
