Importing queries, forms, and procedures in OS/390 data sets

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.

Enlarging the table space for the QMF object control tables

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:

  1. Run the STOSPACE utility on the table space's storage group.
  2. Run the following query:
    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:

  1. Make an image copy of the table space.

    You can use this for restoration if the procedure fails.

  2. Create a storage group for the table space.

    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.

    E
    Indicates that the data sets for the table space are user managed (no associated storage group).
    I
    Indicates that the data sets for the table space are DB2 managed.

    Table 57. Table spaces for control tables that store QMF objects

    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

    Table 58. Node groups for control tables that store QMF objects using a DB2 Parallel Edition V1R2 database or DB2 UDB
    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.
  3. Stop the database.

    Use the command -STOP DATABASE(DSQDBCTL).

  4. Change the table space description.
  5. Move the table space data.

    Simply changing the table space description does not effect enlargement. You must instead do something that causes the table space to be refilled.

  6. Start the database with the statement:
    -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 ]