If a user has QMF objects that have been exported to OS/390 data sets, you can bring them back with the QMF IMPORT command.
If the exported objects are RACF protected, you need RACF read access to import objects from them. To obtain this access, see your RACF administrator.
Periodically, QMF objects might become too numerous for the table space that contains the QMF object control tables Q.OBJECT_DIRECTORY, Q.OBJECT_DATA, and Q.OBJECT_REMARKS.
Before you enlarge the table space, you must determine its space requirements. One factor in your estimate can be the amount of space currently used.
If the space is DB2 managed, you can get this information by doing the following:
SELECT SPACE FROM SYSIBM.SYSTABLEPART WHERE TSNAME='tttttttt' AND DBNAME='DSQDBCTL'where tttttttt is the table space name. The result (SPACE) gives the number of kilobytes of storage currently allocated to the table space.
If the space is user managed, you can use the TSO LISTCAT command for the space information, if you know the data set name.
To enlarge the table space for the QMF object control tables:
You can use this for restoration if the procedure fails.
Do this only if the table space has user managed data sets, and no storage group is already available.
To determine the type of data set management used for the table space, run the following query:
SELECT STORTYPE FROM SYSIBM.SYSTABLEPART WHERE TSNAME='DSQTSCT3' AND DBNAME='DSQDBCTL'
This should produce a one-line result for the table space DSQTSCT3. In the result, STORTYPE has the value E or I.
Table space name |
Contents |
Default size |
---|---|---|
DSQTSCT1 |
Q.OBJECT__DIRECTORY table |
256 pages |
DSQTSCT2 |
Q.OBJECT__REMARKS table |
256 pages |
DSQTSCT3 |
Q.OBJECT__DATA |
5120 pages |
NODEGROUP Name | Used for | Characteristics |
---|---|---|
DSQTSCTL | For all QMF control tables except as described elsewhere in this table. | Can be distributed across multiple nodes. Growth potential is low. |
DSQTSOBJ | The QMF OBJECT control tables where PROC, Query, and FORM objects are stored. | Can be distributed across multiple nodes. Growth potential is high. |
DSQTSDEF | The default SAVE DATA space as initialized in the QMF Profile. | Should be defined to be restricted to a single node to avoid complications. |
DSQTSAMP | The QMF Sample tables. | Candidate for distributing across multiple nodes. |
Use the command -STOP DATABASE(DSQDBCTL).
ALTER TABLESPACE DSQDBCTL.tttttt USING STOGROUP ssssss PRIQTY pppp SECQTY sssswhere tttttt is the table space name. The statement changes the table space from user managed to DB2 managed and names a storage group (ssssss) for the management. The quantities pppp and ssss are the new primary and secondary allocation sizes (in kilobytes) for the enlarged table space.
ALTER TABLESPACE DSQDBCTL.tttttt PRIQTY pppp SECQTY sssswhere tttttt is the table space name. pppp and ssss are the new primary and secondary allocation sizes, in kilobytes, for the enlarged table space.
Simply changing the table space description does not effect enlargement. You must instead do something that causes the table space to be refilled.
-START DATABASE(DSQDBCTL)
You can also use the DB2 LOAD utility to enlarge a table space.
For more information on enlarging table spaces, see the DB2 UDB for OS390 Uitility Guide and Reference manual.
Note: QMF Version 7.2 creates DB2 managed table space data sets if QMF was not previously installed.
[ Previous Page | Next Page | Contents | Index ]