Well, now with DB2 Cloning Processes (I know of IBM's DFHSM and EMC Timefinder/CLONE) the small-medium-large pools are changing.
To clone a DB2 Subsystem you need to have a separate pool dedicated to just that subsystem. This process also requires 2 User Cats (One for the DB2 SYSTEM databases, files and one for the Application Data Bases) that are all SNAPPED at the same time. The amazing part is the time it takes to snap the entire DB2 Subsystem; it is really fast. The need for more dasd and specialized SMS Pools is offset by the faster process to clone the subsystem. I too use to believe in the small-medium-large functions. But if you have DB2 and need to clone it - then you have a whole new direction to take. I also see this as a direction for other subsystems that need cloning like IMS or MQ or CICS. And yes - EMC does a rename of all data sets to the new HLQ for the cloned copy, and DFHSM requires the 2 Ucats be disconnected and then imported. Times sure are a changing. Lizette -- Snip -- --(note this information is slightly dated .. we implemented SMS 10 years --ago) When we did the analysis, it was found that 80% of the data sets --were 5 tracks or under. So, we created a small pool, medium pool and --large pool. Worked very well and eliminated most of the need to run --defrag. YMMV -- -- UnSnip -- ---------------------------------------------------------------------- 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
