Activating definitions on VM

To enable users to use the customized function key definitions you created:

1. Update the PFKEYS field of the user's profile with the name of your function key definitions table.

   For example, use a query like the one in Figure 155 to assign to English QMF user JONES the table MY__PFKEYS, and to German NLF user SCHMIDT the table MEIN__FKY. Always include a value for the TRANSLATION and ENVIRONMENT columns in a query that updates the Q.PROFILES table.

   Figure 155. Making customized function keys accessible to a user

   Base QMF (English)

   German NLF

   UPDATE Q.PROFILES

   UPDATE Q.PROFILES

   SET PFKEYS = 'MY__PFKEYS'

   SET PFKEYS = 'MEIN__PFKY'

   WHERE CREATOR='JONES'

   WHERE CREATOR='SCHMIDT'

   AND TRANSLATION = 'ENGLISH'

   AND TRANSLATION = 'DEUTSCH'

   AND ENVIRONMENT = 'CMS'

   AND ENVIRONMENT = 'CMS' (or 'TSO')

2. Grant the SQL SELECT privilege to users who need to access the table.

   To allow any user to whom the table is assigned to use it, grant the SELECT privilege to PUBLIC. For example:

   GRANT SELECT ON MY__PFKEYS TO PUBLIC

   To minimize maintenance of function keys at your site, you can assign a view of the table. Grant the SELECT privilege on only the view to prevent users from accessing function keys not meant for their use.

   The procedures for assigning views of a function key table are the same as those for command synonym tables discussed in Minimizing maintenance of command synonym tables Use the strategies discussed in that section to decide whether to assign a table or a view to individual users or groups of users.

3. Instruct users to reconnect to the database to initialize a QMF session with the new function key definitions. For example, user JONES who has the password MYPW needs to enter:

   CONNECT JONES (PA=MYPW