I don't have any DB2 specific advice regarding user catalogs, but when you ask about each member having its own catalog, if you mean "member" in the sense of DB2 data sharing, that really won't work, since DB2 treats the whole group as a logical entity. Now if you are referring to individual subsystems, I would recommend that you have at least one user catalog per DB2 subsystem or DSG, or at a minimum that you don't define the aliases for development and production in the same user catalog.
=============================================== Wayne Driscoll OMEGAMON DB2 L3 Support/Development wdrisco(AT)us.ibm.com =============================================== From: Rodney Krick <r...@aformatik.de> To: IBM-MAIN@bama.ua.edu Date: 11/10/2011 12:56 PM Subject: [DB2 z/OS] USER CATALOG - Rules of Thumb and best practices Sent by: IBM Mainframe Discussion List <IBM-MAIN@bama.ua.edu> Hi, I'm looking for some DB2 specific recommendations regarding User Catalogs, specially if there are any rules of thumb as a start point for defining the infrastructure for DB2 (like each member has its own catalog or something like that). I've searched the forum and asked daddy google, but didn't get smarter. The guys from DB2-L recommended me to post this to this list (IBM-Main). If some of you guys could share one or two links I would be very grateful! Thank you in advance! Rodney ---------------------------------------------------------------------- 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
