Creating the table on OS/390

After you decide which function keys you want to customize, follow these steps to create a table that links your customized function key definitions with the appropriate panels:

1. Use an SQL CREATE TABLE statement similar to the one shown in Figure 148 to create the table. Substitute your own name for MY__PFKEYS. Under TSO, substitute your own table space for TBSPACE1.
   Figure 148. Creating a function key table

   CREATE TABLE MY_PFKEYS
     (PANEL                CHAR(18)       NOT NULL,
      ENTRY__TYPE           CHAR(1)        NOT NULL,
      NUMBER               SMALLINT       NOT NULL,
      PF__SETTING           VARCHAR(254),
      REMARKS              VARCHAR(254))
      IN TBSPACE1

   See the appropriate DB2 UDB Administration Guide for information on creating a new table space.

2. Add comments to the DB2 system catalog using an SQL statement similar to the following:

   COMMENT ON TABLE MY__PFKEYS IS 'PF KEYS RESERVED FOR FINANCIAL ANALYSTS'

   The phrase PF KEYS RESERVED FOR FINANCIAL ANALYSTS appears in the REMARKS column of the DB2 system catalog. For more information on adding comments to the system catalog, see the DB2 UDB for OS390 Administration Guide.

   You do not need to add comments about your new table to the DB2 system catalog, but if you do, one comment might be about the table; others might describe the columns. For example, suppose that MY__PFKEYS has a column named AUTHID that distinguishes private from public function keys. To add a comment to explain this, run a query:

   COMMENT ON COLUMN MY__PFKEYS.AUTHID
     IS 'PRIVATE PFKEY: USE AUTH ID. PUBLIC PFKEY: USE NULL'

   By running a subsequent COMMENT ON query, you can replace the current one. For more on COMMENT ON queries, see the DB2 UDB for OS390 SQL Reference manual.

3. Create an index using an SQL statement similar to the following:

   CREATE UNIQUE INDEX MY__PFKEYSX
     ON MY__PFKEYS (PANEL, ENTRY__TYPE, NUMBER)

   Use the UNIQUE keyword to index the PANEL, ENTRY__TYPE, and NUMBER columns to ensure that no two rows of the table can be identical.

   If you choose not to use the UNIQUE keyword, QMF allows duplicate key definitions. QMF displays warning messages on the Home panel if it finds more than one key definition for the same key, and writes information about the warning messages to the user's trace data. Multiple key definitions for window panels cause no messages; QMF uses the last definition it finds.