Ted, DFSMShsm should be set up to migrate/recall these PDS/PDS-E when they exceed some extent threshold I used to use eight extents. This compresses the dataset and consolidates all the extents to single, sometimes larger primary extent.
I used to use the General Pool for all TSO related datasets and with DSMS consolidating PDS like this they were never problem, or cause of a problem. I've also seen this working in a Development environment with a single Storage Group for everything. Ron > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of > Ted MacNEIL > Sent: Thursday, March 04, 2010 11:10 AM > To: IBM-MAIN@bama.ua.edu > Subject: Re: [IBM-MAIN] Defrag > > >I mentioned PDS type datasets in my original post, but didn't say much else. > We have a separate storage group for them. But we don't create and delete > large numbers of PDSes as a rule, so we can manage their storage "by hand". > > What about developer libraries? > You don't leave them in their general storage group (with/without the 'E')? > > And, imo, managing any data by hand defeats the automated function(s) of SMS, > by definition. > > - > Too busy driving to stop for gas! > > ---------------------------------------------------------------------- > 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
