Further requirements

The following data base requirements exist for each database that QMF is installed in. The sections that follow describe the items in this list.

• QMF DBSPACE requirements

  There are ten DBSPACEs required for QMF. They are established during installation.

  QMF must have a DBSPACE to store user tables created as a result of using the QMF SAVE DATA command. You can use an existing DBSPACE or you can create a new one during the installation of QMF.

• QMF control tables

  There are eight QMF control tables. Each table is created in its own DBSPACE.

• QMF catalog views

  There are three QMF catalog views required for the QMF LIST command, enabling users to list database objects that they are authorized to use.

• QMF sample tables

  There are nine sample tables that are created in one DBSPACE.

• QMF SQL packages

  QMF contains several SQL packages that must be loaded into each database into which you install QMF. The packages are loaded after the QMF control tables are created during installation.

QMF DBSPACE requirements

DB2 for VM stores tables and indexes in tables within DBSPACEs. A DBSPACE is a logical allocation of space in the database. A DBSPACE holds data in 4,096-byte blocks called pages. QMF requires the use of public DBSPACEs, which allow multiple user access at the same time; any one user can be doing update, insert, or delete functions.

Because you cannot extend DBSPACEs after they are defined, you should overestimate the required number of pages. The penalty for overestimating DBSPACE pages is nominal because the unused DBSPACE pages are not stored. On the other hand, the penalty for underestimating DBSPACE pages can be quite expensive in terms of reorganization activities required to reestablish the data in a larger DBSPACE later.

DBSPACEs must first be created and then acquired for use through the DB2 ACQUIRE DBSPACE command. Because QMF issues the ACQUIRE DBSPACE command, you must be sure you have already created the appropriate DBSPACEs.

The DBSPACEs required by QMF, as well as their contents and default sizes, are shown in Table 27.

1. The default size of these DBSPACEs may not be correct for your installation. You should evaluate the DBSPACE requirements of your installation before creating the DBSPACEs.
2. DSQTSCT3 should be your largest DBSPACE because it contains all your QMF queries, procedures, and forms. DBSPACEs DSQTSCT1 and DSQTSCT2 are created and acquired with a size of one page for each 25 pages in DBSPACE DSQTSCT3.
3. DSQTSDEF is the default name for the DBSPACE to be used by the QMF SAVE DATA command. This DBSPACE name can be changed.
4. Do not use SYS as the first three characters of a DBSPACE name; SYS denotes a DBSPACE reserved for DB2 system usage.
5. The smallest DBSPACE size that DB2 for VM allows is 128 pages. DB2 may actually give you more pages than you request because it acquires storage in units of 128 pages. DB2 determines the number of pages you receive by rounding the number you specify to the next higher multiple of 128 pages.

   Example:  If you specify PAGES=53, DB2 acquires a block of 128 pages; if you specify PAGES=130, DB2 acquires 256 pages.

To determine how many of the ten DBSPACEs you need to create for your installation, perform these steps:

1. Identify the number of additional DBSPACEs that you need, based on the following considerations:
   • If you are installing QMF Version 7.2 into a database that does not contain any version of QMF, you need to create all ten DBSPACEs shown in Table 27.
   • If you have QMF Version 3.1 or a later release installed in the same database in which you are installing QMF Version 7.2, no new DBSPACEs are needed.
2. Run the following query to list the DBSPACEs defined and their sizes. To run this query, you must have DB2 for VM DBA authority or have SELECT authority on table SYSTEM.SYSDBSPACES. Run this query using QMF or ISQL:

   SELECT * FROM SYSTEM.SYSDBSPACES
     WHERE  DBSPACETYPE=1 AND OWNER=''

   Note: If you plan to create DBSPACEs while installing QMF, see the discussion in Step 2--Creating DB2 for VM DBSPACEs: DSQ2DBSC. If you need to create additional DBSPACEs after QMF is installed, use the procedures described in DB2 Server for VSE & VM Database Administration

QMF control tables

There are eight QMF control tables, each created in its own DB2 for VM DBSPACE. (Separate DBSPACEs improves performance.) The contents of each control table are:

QMF catalog views

QMF requires the following three catalog views for the QMF LIST command and Prompted Query functions:

• Q.DSQEC_TABS_SQL is a view on the SYSTEM.SYSCATALOG and SYSTEM.SYSTABAUTH DB2 for VM system tables.
• Q.DSQEC_COLS_SQL is a view on the SYSTEM.SYSCOLUMNS and SYSTEM.SYSTABAUTH DB2 for VM system tables.
• Q.DSQEC_QMFOBJS is a view on the QMF control tables Q.OBJECT_DIRECTORY and Q.OBJECT_REMARKS.

QMF sample tables

The sample tables are placed in DBSPACE DSQ2STBT. The table contents are described in the following list. (Each table provided by QMF contains information on the fictional J & H Supply Company.)

Table

Contains Information on:

Q.ORG

The company organization

Q.STAFF

The company personnel

Q.APPLICANT

New candidates for hire

Q.PRODUCTS

The company's products

Q.SALES

Sales and commissions

Q.PROJECT

Projects undertaken, by department

Q.INTERVIEW

Interviews of new hires

Q.SUPPLIER

Vendor information

Q.PARTS

Product parts data

QMF SQL packages

QMF contains SQL packages which must be loaded into each database in which QMF is installed. QMF Version 7.2 access modules contain the DSQD prefix in the SYSTEM.SYSACCESS table. For more information on access modules see DB2 Server for VM System Administration.