Completing Performance Warehouse setup

To complete setup of Performance Warehouse, grant the user ID/group ID DB2PM the required Db2 privileges to create and maintain the Performance Warehouse database and to make the Performance Warehouse started job executable. you can find all listed members in the library rHilev.rte_name.RKD2SAM.

1. If your z/OS system is already configured to support started jobs, skip this step. If you perform this step, ensure that you have UPDATE privileges on the system PARMLIB.
   Your z/OS system must be configured to search started jobs in the PROCLIB of the started tasks, so that the OMEGAMON Collector can create the Performance Warehouse at startup.
   The master JCL MSTJCLxx in your system PARMLIB defines started job PROCLIBs either by an IEFJOBS or an IEFPDSI DD statement. As the Performance Warehouse job will be copied to the started tasks PROCLIB, this PROCLIB data set must be part of the IEFJOBS or IEFPDSI concatenation.
   1. Open the master JCL in your system PARMLIB and find the IEFJOBS or the IEFPDSI DD statement. If no IEFJOBS or IEFPDSI DD statement exists, add a new IEFJOBS DD statement to the master JCL.
   2. Add a further partitioned data set to the IEFPDSI or IEFJOBS concatenation for your started tasks PROCLIB.
2. Grant the Db2 privileges to the USERID/GROUPID DB2PM. Open and submit the following members: PWG1db2ssid
3. Make the Performance Warehouse started jobs executable. For each Db2 subsystem for which Performance Warehouse is activated, a started job is generated. Complete the following steps for each of the listed Performance Warehouse started jobs (for example, IBMPWH1):
   1. Open the Performance Warehouse started job JCL and edit it:
      • Replace JOBACC with your job accounting information.
      • Replace JOBPROGRAMMER with the job owner name information.
   2. Copy the Performance Warehouse started job JCL to your started task PROCLIB (for example, SYS1.PROCLIB).
4. Connect the Performance Warehouse started job to the userid DB2PM.
   For example, by using the following RACF commands:

   RDEFINE STARTED pwh_stc.* STDATA(USER(DB2PM))
   SETR RACLIST(STARTED) REFRESH

   If the group ID DB2PM is used instead of the user ID DB2PM, assign the Performance Warehouse started job to the user ID <USER> that was added to the group ID DB2PM.

   RDEFINE STARTED pwh_stc.* STDATA(USER(user) GROUP(DB2PM))
   SETR RACLIST(STARTED) REFRESH

   where pwh_stc is the Performance Warehouse started task (for example, IBMPWH1).

5. Create the Performance Warehouse database.
   Note: This step is not required if you use the same prefix for the Performance Warehouse started job as for the OMEGAMON started tasks and have connected the prefix to the user ID/group ID DB2PM in the mandatory step 1 already.
   1. Start the OMEGAMON Server started task by using one of the following commands:

      S server_stc (system console)
      /S server_stc (SDSF)

   2. Open the SYSPRINT data set or log and wait until the following message is displayed:

      FPEV5005I  xxxx DATABASE UPDATE COMPLETE

      This message indicates that the creation of the Performance Warehouse database is complete (xxxx is the name of your Db2 subsystem). It is printed for every Db2 subsystem that was configured to use Performance Warehouse.

   3. Verify that each user ID for which you want to allow access to the Performance Warehouse is available in your z/OS security system. Otherwise create the z/OS user IDs.
   4. Open the following members to grant Db2 privileges to a Performance Warehouse user:
      PWG2db2ssid. Replace each occurrence of %pwuser% with the user ID that you want to allow access for to the Performance Warehouse. Submit the edited member.

      Note:

      • %pwuser% may also be customized using parameter KD2_OMPE_GRANT_*
      • Instead of assigning the privileges to each Performance Warehouse user ID, you can also connect all Performance Warehouse user IDs to a group ID and grant the privileges to this group ID.