Read this section to migrate when both releases of QMF are on the same DB2 subsystem.
At the start of a QMF session, a user's QMF profile comes from some row of the Q.PROFILES table. With both releases of QMF in the same DB2 subsystem, the two releases use the same Q.PROFILES table.
If a user has a primary authorization ID different from the TSO logon ID, the DSQSPRID parameter should have a value of TSOID when you start QMF. Otherwise, insert a user row in Q.PROFILES with CREATOR set to the primary authorization ID.
There are no new columns in the Q.PROFILES table if you are migrating from Version 3.1.1.
There are no new columns in the Q.PROFILES table if you are migrating from Version 3.1.
The Q.PROFILES table now has one more column, ENVIRONMENT, which carries a profile parameter that applies to only the new release. This column has a single default value for its entry, as shown in Table 101. The new column has no effect on the execution of Version 2.4; the new column is invisible to the Version 3 releases.
The Q.PROFILES table now has two more columns, MODEL and ENVIRONMENT, which carry profile parameters that apply to only the new release. These columns have single default values for their entries, as shown in Table 101. The two new columns have no effect on the execution of QMF Version 2.2 and Version 2.3; the new columns are invisible to these releases.
MODEL and ENVIRONMENT columns added to existing rows contain NULLS. Through SET or SAVE PROFILE, users can supply only the MODEL column. You need to assign the ENVIRONMENT column.
Column Name | Purpose |
---|---|
MODEL | Identifies each user's conceptual view of the data that Prompted Query utilizes to access the data. Default value is REL. . |
ENVIRONMENT | Identifies the execution environment of the QMF session. |
Version 3.2 added three new columns to the Q.OBJECT__DIRECTORY table. If you are migrating from an older release of QMF, these three columns have no effect on the previous tables. Table 102 shows the three new columns.
Column name | Data type | Length (bytes) | Nulls allowed? | Function/Values |
---|---|---|---|---|
CREATED | TIMESTAMP | Yes | Shows the timestamp value for when an object was created. The value is recorded after SAVE or IMPORT commands. | |
MODIFIED | TIMESTAMP | Yes | Shows the timestamp value for when an object was last modified. The value is recorded after SAVE or IMPORT commands. | |
LAST__USED | DATE | Yes | Shows the date value for when an object was last used. The value is updated only once a day. |
If you are migrating from QMF Version 2.4 to QMF Version 7.2 and you plan to run both QMF Version 2.4 and Version 7.2 on the same database, you need to use the QMF Version 2.4 version of DPRE for both versions of QMF. To provide the QMF Version 2.4 version after installing QMF Version 7.2:
IMPORT PROC Q.DSQAER1P FROM 'QMF240.DSQSAMPE(DSQAER1P)'
When you are no longer using QMF Version 2.4, restore DPRE to the Version 7.2 level as follows:
IMPORT PROC Q.DSQAER1P FROM 'QMF720.SDSQSAPE(DSQAER1P)'
If both releases of QMF are on the same DB2 subsystem, all the DB2 objects (tables and views, for example), are available under QMF Version 7.2 if they are available under the earlier release. All the queries, forms, and procedures are also available, but some might be unusable under QMF Version 7.2. This topic is discussed in Migrating QMF objects.
[ Previous Page | Next Page | Contents | Index ]