And I have DFSORT set to to totally ignore whether SORTWK DD statements are coded or not. I use ICEPRM00 in PARMLIB like:
JCL, DYNALOC=(SYSDA,31), DYNAUTO=IGNWKDD INV, DYNALOC=(SYSDA,31), TMAXLIM=10000000 TSO, DYNALOC=(SYSDA,31) TSOINV, DYNALOC=(SYSDA,31) JCL coders here did not think it was wise to make them determine the SORTWK needed. I think that I agree. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM > -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Mike Schwab > Sent: Thursday, March 24, 2011 1:03 PM > To: IBM-MAIN@bama.ua.edu > Subject: Re: Region size > > On Thu, Mar 24, 2011 at 12:37 PM, Ron Hawkins > <ron.hawkins1...@sbcglobal.net> wrote: > > Shmuel, > > > > Blockset may resemble paging IO in the way it would track > switch over a CYL > > as it laid down blocks, but that's probably not an > advantage any more with > > cache all storage and CKD encapsulation into FBA. This > behavior is one > > reason why the cache hit rate for Local Page datasets is > somewhat poor, but > > I haven't observed how block paging behaves in polluted or > small cache. > > > > DFSORT's IO to the SORTWK are explicitly requested in > response to DFSORT > > deciding it has exhausted its own memory. At startup it > attempts to, and > > usually succeeds in selecting memory boundaries that avoid > paging, using the > > SORTWK as the memory overflow area. This could be viewed as > DFSORT doing its > > own paging, or at least its own memory management. > > > > Otherwise AFAIK DFSORT will have pages stolen and demand > page with or > > without block paging just like any other batch job. > > > > I'm sure you know all this already, so what's your point? > > > > Ron > > The DB2 people wanting 150GB in paging packs refused to code SORTWK DD > statements to force in-core sorts. I have always coded SORTWKs even > if they were never needed. > -- > Mike A Schwab, Springfield IL USA > Where do Forest Rangers go to get away from it all? > > ---------------------------------------------------------------------- > 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 > > ---------------------------------------------------------------------- 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
