All, You can find datasets like this from your SMF data. Look at 14 and 15 records and find those datasets that are being closed with more than 32 extents and you know you will have a problem with just two volumes. Back in the day this was standard practice for any SMS conversion or volume consolidation (I remember checking this for 3380-D to 3390-3).
You could also look at converting to Extended Format, but that still needs you to check SMF records for any unsupported access methods. Ron > >---------------------------------------------------------------------- > That is exactly my point. If previously a user coded per say a primary > of > 50 cyl and a seconary of 5 cyl with a volume count of 5, they might be > able to acquire the space that step needed whereas if the volume count > is dimished to 2, then the allocation is more likely to fall short of > it's > previous capacity which would require adjusting the allocation > requests. > > I agree with Tom Merchant who said "Too many small storage "puddles" > makes it difficult to manage. It sounds to me as if you are micro- > managing your SMS." > > Micro managing was not my intention at all. If the DBAs request that > they want their archive logs separate from their bootstraps and so on, > then I am simply trying to accomodate the users requests. > > Plus, there is definitely a culture change when working with larger > volumes such as a mod 27 because what seemed like an acceptable > storage pool of 10 volumes is quickly diminished when it is reduced > into > 2 volumes so it may be necessary to merge some pools together. > > I certainly appreciate everyone's feedback which is what I was looking > for because this is new territory for me. > > Gil. > ---------------------------------------------------------------------- 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
