Valid values for the profile and keyword setting for SPACE

Users using the QMF SYSTEM profile have a default database and table space of DSQDBDEF.DSQTSDEF. Newer installations will have a default SPACE value of DATABASE "DSQDBDEF". This value may be overridden by using the keyword value SPACE on the commands.

You can set the SPACE option of the profile or keyword with the following values:

• databasename.spacename

  Specify both a database and a table space to have QMF save the table in that specific table space. Throughout this topic, this is known as an explicit table space. The table space that you specify must have already been created. QMF will not create the table space.

  For example, the following query configures the profile of a QMF user named SMITH to save tables in table space TSPACE1, in database DBASE1:

  UPDATE Q.PROFILES
    SET SPACE='DBASE1.TSPACE1'
    WHERE CREATOR='SMITH' AND TRANSLATION='ENGLISH'

  However, if all users are using the same table space, you could experience resource contention.
• DATABASE "databasename"

  When you specify the DATABASE keyword followed by a database name in quotes, each table is created in a separate table space created implicitly and exclusively for that table by Db2®. Such implicit table spaces have default LOCKSIZE, BUFFERPOOL, STOGROUP, and space attributes, and have names that match the name of the table that was created. QMF recommends this method.

  For example, the following value for the SPACE field of the Q.PROFILES table saves each table in a separate table space in the DSQDBDEF database:

  DATABASE "DSQDBDEF"

  Limiting each table space to one table only minimizes resource contention. Both partitioned and universal table space schemes impose a limit of one table per table space. QMF recommends this method for SAVE DATA operations.

• NULL or blank

  If the SPACE field of the QMF profile is null or blank, SAVE DATA or IMPORT TABLE commands create tables in implicitly generated table space names in the DSNDB04 database by default.