> My point exactly. When VIO went straight to the Locals these recommendations > were valid, but Expanded Storage turned VIO into a real DIM technique, and > it us just as valid for SORTWK as it is for any other dataset. Has it really > been a decade since we got ES?
With the advent of ARCHLVL 2 many things changed - ES going away was one of them. That raised its own issues as regard *ALL* paging now being driven out to AUX. The plumbing for all the windowing services is still there, but with new kit and big memory, the usage of them would have to be questionable if performance is the only/prime consideration. As Frank mentioned DFSORT will use memory objects (i.e. above the bar) if you let it. FWIW we direct almost all SORTWKs away from VIO - the sort in memory phase already has a requirement for backing storage. Adding more pressure on the paging subsystem from the occasional big sort is pointless - especially as some of the (internally called) DB2 sorts are humungous. So big in fact we have a separate pool of mod-9s just for them. I prefer that the DASD folks get beat up for not having enough volumes in the pool and one job fails rather than me getting beat up because the system suffers an AUX shortage. Each to their own. Shane ... ---------------------------------------------------------------------- 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
