V10 How many collection IDs to use on one system ?

A Shepard

V10 How many collection IDs to use on one system ?

    A big part of V10 upgrade is converting plans to packages. No problem.
    We have about eight differnt collection IDs for online CICS transactions divided by program function or subsystem.
    The question is what to do with, how to convert, about 1,237 plans to packages with collection IDs.

   Should they all go in one collection ID called BTCH ?   (does not sound good)
   Is there an optimum number of items to have in a collection ?  (must be, but what is it?)
   Should I take the default and let each plan create a new DSN_DEFAULT.collectionID.pacakageID  ?  (Eeek!, that scares me)

   Please, any thoughts would be appreciated.  DB2 V10 upgrade in progress running on z OS 1.13 with a single DBA.  (Well I'm married but there is only one of me)

William Powers

RE: V10 How many collection IDs to use on one system ?
(in response to A Shepard)

We just went through that exercise in 2011. We had to convert over 25K plans/dbrm's to 140K packages

across our environments.   Shoot me an e-mail if you would like to discuss.. [login to unmask email]

A Shepard

RE: V10 How many collection IDs to use on one system ?
(in response to William Powers)



In Reply to William Powers:

We just went through that exercise in 2011. We had to convert over 25K plans/dbrm's to 140K packages

across our environments.  


Wow you are much larger than us. I'm leaning to one collection ID for maintenace reasons. I'll shoot you an email to see the hows and whys of 25K plans/DBRMs creating almost five times as many packages. 

   It is not just about quick index to data, but quick index to DBRM.