Updating user profiles

You can change the values in a user's profile by using either the SET PROFILE command or SQL UPDATE statements.

Using the SET PROFILE command

Using this command is quicker than using SQL UPDATE statements, because you can enter it from the QMF command line with minimal typing.

Values set using SET PROFILE remain effective only until the user's session ends; use the SAVE PROFILE command to save values you changed. For more information on the SET PROFILE command and its parameters, see QMF Reference.

Because no special SQL privileges are required to use this command, your users can easily update their own profiles. However, they cannot use SET PROFILE to update fields you might use to customize their QMF sessions. These fields are PFKEYS, SYNONYMS, and RESOURCE__GROUP. You can use SQL UPDATE statements or the QMF Table Editor to update these Q.PROFILES fields. The Table Editor is explained in the Using QMF manual.

Using SQL UPDATE statements

SQL UPDATE statements can be used to update all fields of the Q.PROFILES table, including SYNONYMS, PFKEYS, and RESOURCE__GROUP.

Use an SQL UPDATE query similar to the one in Figure 66 to update existing user profiles. This example changes the name of the table that stores a user's command synonyms. On the left is an example query for user JONES in base (English) QMF; on the right is the same query for user SCHMIDT in the German NLF.

Figure 66. Updating user profiles using UPDATE query on Q.PROFILES table

Base QMF (English): German NLF
UPDATE Q.PROFILES: UPDATE Q.PROFILES
SET SYNONYMS='COMMAND__SYNONYMS': SET SYNONYMS='GUMMOW.XYZ'
WHERE CREATOR='JONES' AND: WHERE CREATOR='SCHMIDT' AND
TRANSLATION='ENGLISH': TRANSLATION='DEUTSCH'

Note: When running UPDATE, DELETE, and INSERT queries on the Q.PROFILES table, always include the TRANSLATION column in the query; otherwise, QMF applies the changes you make in all language environments.

Updating the SYSTEM profile

You can change the default values provided in the SYSTEM row of Q.PROFILES. However, any user who needs different values than those you assigned for the SYSTEM row must have a unique profile row.

For example, suppose that your system has two resource groups defined, named PRIME and NONPRIME. Suppose that PRIME is the default value for the RESOURCE__GROUP field of the SYSTEM row in Q.PROFILES. You must formally enroll the users who are in the NONPRIME group by giving them unique profile rows.