The data sets for the table spaces and indexes might be user or DB2 managed. How these data sets are managed determines what you must do to enlarge table spaces and indexes.
DB2 common server users: QMF table spaces are defined as system managed space (SMS).
Prior to Version 3.2, DB2 managed the space for the control table indexes and table spaces. This required the use of a storage group for each table space and index. A storage group is a named set of DASD volumes from which space can be drawn for the objects that the storage group supports. For each control table with an index, the index and the table space share a common storage group, as Table 61 indicates.
Workstation database server users: Storage groups do not apply.
Table | Table space | Storage group |
---|---|---|
Q.PROFILES | DSQTSPRO | DSQSGPRO |
Q.ERROR__LOG | DSQTSLOG | DSQSGLOG |
Q.OBJECT__DIRECTORY | DSQTSCT1 | DSQSGCT1 |
Q.OBJECT_REMARKS | DSQTSCT2 | DSQSGCT2 |
Q.OBJECT__DATA | DSQTSCT3 | DSQSGCT3 |
You need a VSAM cluster for each table space and each index to manage the control-table data sets. You define these clusters using VSAM statements, and link the resulting clusters to DB2 with SQL CREATE queries. The link between a cluster and its DB2 object is in the name of the cluster and the name of the ICF (Integrated Catalog Facility) in which the cluster is cataloged.
[ Previous Page | Next Page | Contents | Index ]