On Thu, 4 May 2006 14:38:08 -0700, Edward Jaffe <[EMAIL PROTECTED]> wrote: > >IBM recommends no secondary extent allocation for data sets on LNKLST. >
I have allowed them at times to be allocated with a secondary so SMP/E maintenance doesn't have space problems. COMPRESS(ALL) only does so much on apply. But then I run post apply FDR COMPAKTOR jobs to release unused space, combine extents, etc. prior to cloning a production sysres. It has all depended on how full my sysres or sysres set of volumes have been - which is always changing with new OS versions and sysres device type (3380/1/2/3, 3390/1/2/3, etc.). Anyone using a mod-27 or custom size larger than a 3390-3 for their sysres to keep it on 1 volume? I haven't had an issue with too many DSNs/extents in the LNKLST since prior to DFSMS/MVS 1.3. And since no one updates the "MVS" data sets on the live sysres, I don't see the harm. Well.. at least until a rookie comes along. :-) Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group mailto: [EMAIL PROTECTED] Systems Programming expert at http://expertanswercenter.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- 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
