Prerequisites

Ensure that you meet the following requirements.

Hardware requirements
You can deploy the product on any zSeries system that is capable of running z/OS®, version 2 release 3, or later.
Software requirements
For a detailed list of the software requirements, refer to the Announcement Letter.
OMEGAMON for Db2 Performance Expert installation
You must install OMEGAMON for Db2 Performance Expert through SMP/E, a tool that installs and maintains software in z/OS systems and subsystems.
Authorization requirements

To set up the product and certain DB2® privileges, such as data set privileges, access privileges are required. You find these in the two tables below. Furthermore, several user IDs are required for the configuration. You must create the following new user IDs or assign existing user IDs to the tasks:

  • DB2PM as user ID or group ID for the OMEGAMON Collector
  • A user ID for the Db2 Connect Monitoring Agent (in case you want to use the function Db2 Connect Monitoring)

During the configuration process, Configuration Manager or PARMGEN create jobs that contain all statements that grant the required Db2 privileges are created. After you successfully complete the configuration, you'll find these jobs in your &rhilev.&rte.RD2SAM library.

The following table lists the Db2 privileges you must grant to different users and the respective grant jobs that you must submit. In the table, <ssid> denotes the Db2 subsystem ID.
Table 1. Db2 privileges
User Db2 privileges/grant jobs
Performance Expert Client (including Performance Warehouse Client) or ISPF Dialogs OMGP<ssid>
This job contains the following privileges:
  • EXECUTE on PLAN KO2PLAN
  • MONITOR1
  • MONITOR2
  • DISPLAY
  • TRACE
If you want to allow certain users to execute CANCEL THREAD in Thread Activity, then you have to grant those privileges additionally (for example SYSOPR).
Db2 Connect Monitoring Agent PWGA<ssid>
The EXPLAIN function EXGP<ssid>
Performance Warehouse PWG2<ssid>
Product setup
  • SYSADM (to submit GRANT jobs)
  • SYSCNTRL (to submit BIND jobs)
OMEGAMON Collector user ID (DB2PM)
  • OMGR<ssid>
  • OMGP<ssid>
    This job contains the following privileges:
    • EXECUTE on PLAN KO2PLAN
    • MONITOR1
    • MONITOR2
    • DISPLAY
    • TRACE
  • If Performance Warehouse is enabled: PWG1<ssid>
Classic User Interface No additional Db2 privileges needed.
The following table lists the required data set authorizations.
Table 2. Data set authorizations
Users Authorizations on data sets
Product setup
  • UPDATE on system VTAMLST
  • UPDATE on system PROCLIB
  • ALTER on the high-level qualifier of your RTE(s) (&rhilev.&rte)
  • EXECUTE on the high-level qualifier of PARMGEN (&shilev)
  • READ on the SMP/E target high-level qualifier of your SMP/E installation (&thilev)

ISPF Dialogs or Buffer Pool Analyzer
  • READ on &rhilev.&rte.RKANCHT
  • READ on &rhilev.&rte.RKANCLI
  • READ on &rhilev.&rte.RKANISP
  • READ and EXECUTE on &rhilev.&rte.RKANMOD
  • READ on &rhilev.&rte.RKANENU
  • READ on &rhilev.&rte.RKANSAMV
  • READ on &rhilev.&rte.RKD2SAM
  • READ on &rhilev.&rte.RKANSAS
OMEGAMON Collector user ID (DB2PM)
  • ALTER on the high-level qualifiers that you want the OMEGAMON Collector to use for work data set allocation. You can specify a high-level qualifier for VSAM data sets and one for non-VSAM data sets.
OMEGAMON Collector started task
  • READ on MVSADMIN.WLM.POLICY RACF® facility class profile.
  • If PE Client is enabled: OMVS access in RACF
  • For information about configuring RRSAF, see Setting up RRSAF.
  • If the ability to dynamically add to link pack area is restricted, the OMEGAMON Collector started task (ompestc_uid) needs update authority to the facility. In RACF this is accomplished by permitting the OMEGAMON for Db2 Performance Expert task update authority to the facility:
    • PERMIT CSVDYLPA.ADD.KO2ZINIB CLASS(FACILITY) ID(ompestc_uid) ACCESS(UPDATE)
    • PERMIT CSVDYLPA.DEL.KO2ZINIB CLASS(FACILITY) ID(ompestc_uid) ACCESS(UPDATE)
    • PERMIT CSVDYLPA.ADD.DGOVRM01 CLASS(FACILITY) ID(ompestc_uid) ACCESS(UPDATE)
    • PERMIT CSVDYLPA.DEL.DGOVRM01 CLASS(FACILITY) ID(ompestc_uid) ACCESS(UPDATE)
  • If the specific facility needs to be defined:
    • RDEFINE FACILITY CSVDYLPA.ADD.KO2ZINIB UACC(NONE)
    • RDEFINE FACILITY CSVDYLPA.DEL.KO2ZINIB UACC(NONE)
    • RDEFINE FACILITY CSVDYLPA.ADD.DGOVRM01 UACC(NONE)
    • RDEFINE FACILITY CSVDYLPA.DEL.DGOVRM01 UACC(NONE)
Tivoli Enterprise Monitoring Agent

Apply to all RTEs that connect to the same Hub TEMS.

Your SAF security rules may need to be changed. The agent address spaces need to have WLM permissions. The agent address spaces need access authority to the resource IWM.SERVER.REGISTER in the FACILITY class. If this resource is not defined, access authority to the FACILITY class resource BPX.WLMSERVER is required.

In RACF, the command is:

PERMIT IWM.SERVER.REGISTER CLASS(FACILITY) ID(userid) ACCESS(READ)

Where userid is the owner user ID of your agent's started task.
The following table lists the required APF authorizations.
Table 3. APF authorizations
Users APF authorizations
Tivoli® Enterprise Monitoring Agent user ID APF authorizations on the libraries in the STEPLIB of the Tivoli Enterprise Monitoring Agent