Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!psuvax1!psuvm!auvm!AUVM!PBURKE
From: PBURKE@AUVM.BITNET (Patty Burke)
Newsgroups: bit.listserv.db2-l
Subject: (no subject given)
Message-ID: <DB2-L%90020609595332@AUVM.BITNET>
Date: 6 Feb 90 14:54:24 GMT
Sender: DB2 Data Base Discussion List <DB2-L@AUVM>
Reply-To: DB2 Data Base Discussion List <DB2-L@AUVM>
Lines: 9
Approved: NETNEWS@AUVM Gateway

I am also interested in answers to Charlie Ridlon's questions
about 3rd-party vendor products that ease restructuring of the
database.
Also, are there any DISADVANTAGES to defining only one ICF catalog
per DB2 subsystem (assuming use of STOGROUPS, not user-defined
datasets)?  In my DBA class, the instructor said that's how they do
it at IBM, but when I attended a 'DB2 Tips' seminar, someone suggested
that there be one ICF catalog per application.  I would prefer one
catalog unless there are disadvantages.