>> For new JCL I always recommend just putting an ample region size on the job card and be done with it. But I would certainly not change running JCL for no reason. >> >> I always say if it ain't broke don't break it.
I say implement an IEFUSI exit that isn't from the dark ages and not worry about (or ignore) what users code for (at least most) JCL. I shouldn't talk too much because I still haven't changed the default from 256M above. The below default is 7M and I'm sure 8M or even 9M wouldn't be a problem and would leave plenty of room for LSQA below the line (which I reserve 512K anyway). None of the LPARs I work with have less than 10M private below the line. Typically STCs code REGION=0M which I only allow (don't ignore) for STCs and that gives them everything they need anyway. BATCH that codes REGION=0M is "penalized" by getting the default, but I haven't found a batch job that ever needed more than 256M. If it did need more, I allow whatever is specified except for 0M (throw back to "the old days" - even the smallest LPAR I support has 1.5G real and a robust paging subsystem). Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
