First, the good news. A catalog can have up to 123 (if I recall correctly) extents. If you haven't reached this limit, you should be OK.
If you are at (or near) this limit, it gets a bit fuzzy. If, by creating a new entry in the catalog, you cause a CI split, which in turn causes a CA split, you may need to take another extent. It only takes one entry to cause the CA split; thus, the inability to create this entry makes it look like the catalog is full. On the other hand, there may be room for many thousands of catalog entries which fit into existing CIs and/or CAs. It depends on the name of the entry to be cataloged (and, usually, the high-level qualifier). Also, if I recall correctly, a catalog is limited to 4GB in size (the same as for any other non-extended format KSDS; catalogs do not have an extended format counterpart). You should allocate catalogs with secondary extents. And, if you reach some threshold (determined by your installation ... say 100 extents), you should schedule a re-org. A catalog re-org really doesn't require a stand-alone environment. You just don't want things initiating while the export and import are running. Export the catalog, close and unallocate the catalog, delete and re-define the catalog (larger?), and import (into empty) the catalog; it's rather quick. ---------------------------------------------------------------------- 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
