Back when I was responsible for this sort of thing, I simply allocated any large space requests with Primary and secondary of 250 CYLS and let it overflow as many volumes as was needed to get the job to completion. It worked, it performed, and I slept because the space problems went away.
They could request anything they wanted in the JCL... We agreed to everything. We simply enforced good practice at allocation rather than JCL coding time. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Ted MacNEIL > Sent: Friday, April 11, 2008 2:23 PM > To: [email protected] > Subject: Re: [IBM-MAIN] Question On Space Allocation > > >The user says he doesn't want to lest his data get 'chunked up'...his > NO CLUE light is on.... > > The performance impact of fragmented datasets disappeared years ago. > The whole purpose of SMS is to reduce the end-user management of > datasets and storage. > > Tell him that it would be better to have a 'chunked up' multi-volume > dataset, rather than no dataset at all. > > If he doesn't listen, tell him that he is to stop wasting your (and > his) time; you've already given a solution. > > - ---------------------------------------------------------------------- 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
