IBM Support

V 5.2.0: Update to the Configuration and Customization manual of IBM Tivoli OMEGAMON for DB2 Performance Expert and Performance Monitor on z/OS

Product documentation


Abstract

This document describes updates to the IBM® Tivoli® OMEGAMON XE for DB2® Performance Expert and Performance Monitor on z/OS Configuration and Customization manual, GH12-6998-00, for Version 5.2.0.

Content

  • Update 1: Update relating to subtask commands to the Event Collection Manager in PK90683 (December 2013)
  • Update 2: Technote title changed in instructions for downloading the program files in PI13916 (March 2014)
  • Update 3: The procedure to install Performance Expert Agent silently by using a response file in Chapter 17. "Installing and configuring components on the workstation" has been modified (April 2016)
  • Update 4: This update applies only if you have the latest PARMGEN level. Changes to PARMGEN workflow and panel navigation in Chapter 10. Configuration scenarios and Chapter 15. Completing the configuration for z/OS components (February 2017)



Update 1: Up date relating to subtask commands to the Event Collection Manager in PK90683 (December 2013)

Subtask commands to the Event Collection Manager

You can issue specific subtask commands to the Event Collection Manager subtask (EVENTMGR). The subtask commands must be preceded by the MODIFY command of the OMEGAMON Collector.

Specific subtask commands are:

START DB2=value

Starts the object and volume analysis collectors for one or more DB2® subsystems. The DB2 subsystems are specified by subsystem IDs.

Requirement: If you specify more than one DB2 ID, you must enclose the string in parentheses.

You can use this parameter with the START and MODIFY commands for the Event Collection Manager. Use the MODIFY command if the Event Collection Manager is already started.

F cccccccc,START EVENTMGR
F cccccccc,F EVENTMGR,START DB2=(db2ssid1,db2ssid2,...db2ssidn)
where:

  • cccccccc is the started task name that you specify for the OMEGAMON Collector during the configuration within the Configuration Tool
  • db2ssid is the identifier of the DB2 subsystem for which object and volume analysis collectors should be started


Update 2: Technote title changed in instructions for downloading the program files in PI13916 (March 2014)

In chapter 17, there are three sections explaining how to download the program files of Performance Expert Agent (Windows, UNIX and Linux) and Performance Expert Client. The download instructions are contained in a technote and the title of this technote changed from "OMPE: web-based delivery and updates for Windows- and UNIX-based components" to "OMEGAMON XE for DB2 PE/PM: web-based delivery and updates for Windows- and UNIX-based components."

Update 3: The procedure to install Performance Expert Agent silently by using a response file in Chapter 17. "Installing and configuring components on the workstation" has been modified (April 2016)

Step 1 of the procedure for Windows 32-bit:

1. From the directory of the installation image for Performance Expert Agent, run the following command:

On Windows 32-bit:
db2pe.agent.*.install-on-win32.exe -i silent -f response_file_name
db2pe.agent.*.install-on-win64.exe -i silent -f response_file_name

Update 4: This update applies only if you have the latest PARMGEN level. Changes to PARMGEN workflow and panel navigation in Chapter 10. Configuration scenarios and Chapter 15. Completing the configuration for z/OS components (February 2017)

Chapter 10. Installing OMEGAMON XE for DB2 PE from scratch with the most basic configuration
This scenario shows how to install OMEGAMON XE for DB2 PE from scratch.

Before you begin
Apply SMP/E before you start with this scenario.

About this task
To keep the setup effort to a minimum, monitoring functions are not enabled. After the configuration, you will be able to open the Classic interface and check the performance of your DB2 subsystem.

Procedure

  1. Start the Configuration and Installation Tools user interface by issuing the command ex on the TKANCUS library in your SMP/E installation.
    ex ‘&trghlq.TKANCUS’
  2. Use option 3 Configuration Workflow to open the PARMGEN workflow user interface.
    KCIPQPGW                                                                  
           Welcome to the z/OS Installation and Configuration Tools for      
                          z Systems Management Suites                        
    1. Checklist: System preparation checklists                                
      Tip: Read/Print Checklists prior to installation and configuration.
    2. Installation Workflow:                                                  
      SMP/E-install z/OS products with Install Job Generator (JOBGEN)        
      Conditional: JOBGEN is not required when using SystemPac or ServerPac.            
    3. Configuration Workflow (Post-installation):    
      Configure z/OS products with Parameter Generator Workflow (PARMGEN)
    I. What's New in PARMGEN?  <=== Revised      
3. As this is the first setup, you must provide GBL_TARGET_HILEV information in this panel:
KCIP@TLV ------------- SPECIFY GBL_TARGET_HILEV PARAM  VERIFY GBL_TARGET_HILEV      
PARMGEN stores configuration values in the TSO user's ISPF profile.            
If this is the first-time your MIS1 TSO user ID is invoking PARMGEN,          
enter the GBL_TARGET_HILEV-related values appropriate for your deployment:    
                                                                             
                                                      UNIT     / STORCLAS /  
                                                      VOLSER     MGMTCLAS    
GBL_TAGET_HILEV: SYS1.KO2.V540______________________  ________ / ________ /  
                 HLQ of SMP/E target (TK*) datasets  ______     ________    
                                                                             
Note:
If this is not the first time your user ID (in this example, MIS1) invokes PARMGEN, this
panel is also displayed if the GBL_TARGET_HILEV stored value changed
from the last time you invoked PARMGEN. Verify GBL_TARGET_HILEV, UNIT,
VOLSER, STORCLAS, and/or MGMTCLAS values accordingly.    
                     
4. This is the first setup, so you must provide some basic information on the second panel:
KCIPQPGA -------- PARAMETER GENERATOR (PARMGEN) WORKFLOW MENU ---------------
Command ===>                                                                
                       Quick Configuration Mode                            
Enter parameter values appropriate for the LPAR runtime environment (RTE).  
                                                                           
GBL_USER_JCL:   SYS1PMO.O310.V540.PARMGEN.JCL_______________                
               (for example, SYS1.KO2.V540.SYSPLEX.PARMGEN.JCL)            
               Specify the dataset name of the PARMGEN common/global        
               library for the different LPAR runtime environments (RTEs).  
               Use the same dataset for managing the different LPAR RTEs.  
               Multiple users can specify the same dataset to manage RTEs.  
                                                                           
RTE_PLIB_HILEV: SYS1PMO.O310____________                                    
               Specify the High-Level Qualifier (&hlq)   portion of the    
               PARMGEN interim staging and work libraries for this LPAR RTE:
               - &hlq.&rte_name.IK* (IKANCMDU,IKANPARU,IKANSAMU)            
               - &hlq.&rte_name.WK* (WKANCMDU,WKANPARU,WKANSAMU)            
               - &hlq.&rte_name.WCONFIG                                    
                                                                           
RTE_NAME:       RTE0A___  (Type ? for a list of configured RTEs)            
               Specify the runtime environment (&rte_name)   for this LPAR.


5. Add common PARMGEN-related information for the parameter GBL_USER_JCL.
For example, which RTE did you use last, what jobs where run, when were they run, and what are their return codes.

6. Add high-level a qualifier for your runtime environments for parameter RTE_PLIB_HILEV.

7. Add the name of your new RTE for parameter RTE_NAME.

8. This example uses the following values for these parameters:
  • GBL_USER_JCL: SYS1PMO.O310.V540.PARMGEN.JCL
  • RTE_PLIB_HILEV: SYS1PMO.O310
  • RTE_NAME: RTE0A
Note: The length of RTE_PLIB_HILEV plus RTE_NAME must not exceed 18 characters.

9. Press Enter to commit your settings. The next panel is displayed:
KCIPQPGB  PARAMETER GENERATOR (PARMGEN) WORKFLOW - PRIMARY OPTION MENU --------
Option ===>                                                                    
                       Quick Configuration Mode                              
GBL_USER_JCL:   SYS1PMO.O310.V540.PARMGEN.JCL                                  
RTE_PLIB_HILEV: SYS1PMO.O310                                                  
RTE_NAME:       RTE0A                                                          
                                                                             
Notes: Perform steps 1 through 5 in sequence, repeating steps as necessary.    
      If reconfiguring this RTE, see Maintenance Scenarios F1=Help topic.    
      Enter n (1-5) to perform tasks.                                        
      Enter ns (1s-5s) for detailed job/task status.                          
                                                                             
                   Description                  Job/Label  Status      Date  
   -------------------------------------------- --------- --------- ----------
1.  Set up/Refresh PARMGEN work environment.      KCIJPCFG                    
2.  Customize PARMGEN configuration profiles.     RTE0A                        
3.  Create this RTE's runtime members and jobs.            Enter 3 for details.
4.  Submit batch jobs to complete PARMGEN setup.  SUBMIT   Enter 4 for details.
5.  Perform post configuration steps.             POSTCFG                      
R   Create next RTE - Reset fields.               New RTE                      


10. Use option 1 KCIJPCFG to start the setup of the PARMGEN work environment for this new RTE. As PARMGEN is workflow-based, this walkthrough follows steps 1 to 4, as shown in the list below the RTE names.

11. On KCIPQPG1, fill in your jobcard that is used for all jobs at the bottom of the screen. If you need more lines for your jobcard, you can edit the $JOBCARD member in your user JCL data (provided by parameter GBL_USER_JCL).
Note: If you change $JOBCARD, the user interface only shows the first four lines.

12. Press Enter to display the next panel.

13. On KCIP@PG2, provide a value for parameter GBL_TARGET_HILEV. This parameter is the high-level qualifier of your SMP/E target data sets. Fill out UNIT, VOLSER, STORCLAS, MGMGCLAS, GBL_SYSDA_UNIT, and GBL_REGION as appropriate for your system.

14. Press Enter to display the next panel.

15. On KCIP@PG3 you find a number of RTE-specific parameters. For this walkthrough, review the following:
  1. RTE_HILEV is the high-level qualifier as previously defined by parameter RTE_PLIB_HILEV, which is why it is set as default.
  2. RTE_VSAM_HILEV is the high-level qualifier for VSAM runtime libraries. The same applies here as for RTE_HILEV.
  3. RTE_TEMS_CONFIGURED_FLAG is the enablement flag for the Tivoli Enterprise Monitoring Server. Change the default to N, as this walkthrough does not cover the enablement of the Tivoli Monitoring infrastructure.
  4. RTE_X_SECURITY_EXIT_LIB is the security exit library. If you changed RTE_HILEV or RTE_VSAM_HILEV, ensure that the high-level qualifier is the same as for RTE_PLIB_HILEV.
  5. Leave the rest of the parameters as is and press Enter.
    KCIP@PG3  SET UP/REFRESH PARMGEN WORK ENVIRONMENT FOR AN RTE (3 OF 3) ---------
    Command ===>                                                  Scroll ===> CSR  
                                                                                 
    Enter parameter values appropriate for the LPAR RTE=RTE0A.                    
    Press F1=Help for more information.                                            
                                                                       
    RTE_DESCRIPTION:     RTE0A description_______________________________          
                                                                                 
    RTE_TYPE:            FULL____       (Full, Sharing)                            
    RTE_HILEV:           SYS1PMO.O310____________________________ (ex.: SYS1PMO.O31
                        (&hlq  portion of Non-VSAM RK* HLQ=&hlq.&rte_name)        
    RTE_VSAM_HILEV:      SYS1PMO.O310____________________________ (ex.: SYS1PMO.O31
                        (&hlq  portion of VSAM RK* HLQ=&hlq.&rte_name)            
                                                                                 
    If any RTE dataset HLQ-related parameter values are NONSMS-managed:            
     RTE_SMS_UNIT:          ________   (Non-VSAM disk UNIT type)                  
     RTE_SMS_VOLUME:        ________   (Non-VSAM disk VOLSER)                    
     RTE_SMS_MGMTCLAS:      ________   (Non-VSAM disk MGMTCLAS)                      
     RTE_SMS_STORCLAS:      ________   (Non-VSAM disk STORCLAS)                  
     RTE_SMS_VSAM_VOLUME:   ________   (VSAM disk VOLSER)                        
     RTE_SMS_VSAM_MGMTCLAS: ________   (VSAM disk MGMTCLAS)                      
     RTE_SMS_VSAM_STORCLAS: ________   (VSAM disk STORCLAS)                      
                                                                                 
    RTE_SMS_PDSE_FLAG:       Y    (Y, N)   (Allocate Non-VSAM PDSE libraries)      
                                                                                 
    If RTE_TYPE is SHARING:                                                        
     RTE_X_HILEV_SHARING:   ___________________________________ (ex.: SYS1PMO.O310
                            (&hlq  portion of shared RTE's HLQ=&hlq.&rte_share)  
     RTE_SHARE: ___________________________________ ("SMP" value or *&rte_share)  
                (*&rte_share  portion of shared RTE's HLQ=&hlq.&rte_share)        
     RTE_LOAD_SHARED_LIBS:  Y    (Y, N)   (Is RTE updater of RO shared libs)      
                                                                                 
    If symbolics (system variables or user-defined variables) will be used:        
     RTE_SYSV_SYSVAR_FLAG:  N    (Y, N)   (System/User variables flag)            
                                                                                 
    Security settings:                                                            
     RTE_SECURITY_USER_LOGON:   NONE____  (RACF, ACF2, TSS, NAM, None)            
     RTE_SECURITY_FOLD_PASSWORD_FLAG: Y   (Y, N)  (Fold password to upper case)  
     RTE_SECURITY_CLASS:        ________________________________________________  
     RTE_X_SECURITY_EXIT_LIB:   SYS1PMO.O310.V520.SE11.RKANSAMU_________________  
     GBL_DSN_ACF2_MACLIB:       ________________________________________________  
     GBL_DSN_ACF2_MACLIB1:      ________________________________________________  
                                                                                 
    Local Tivoli Enterprise Monitoring Server (TEMS) settings in this LPAR RTE:    
     RTE_TEMS_CONFIGURED_FLAG:  Y         (Y, N)  (Configure TEMS in this RTE)    
     RTE_TEMS_NAME_NODEID: RTE0A:CMS__________________________ (e.g.,RTE0A:cms))))
     KDS_TEMS_TYPE:             HUB_____  (Hub, Remote)                          
     KDS_TEMS_HA_TYPE:          __        (HA=High Availability Hub TEMS type)    
                                                                                 
    ITM components' communication-related and started tasks settings:              
     RTE_TCP_PORT_NUM:       1918__________________ (1-65535 port number)        
     RTE_VTAM_APPLID_PREFIX: CTD___________________ (1-4 char.VTAM APPLID prefix)
     RTE_STC_PREFIX:         IBM___________________ (1-4 char.started task prefix)

16. On KCIP@PGI, you see a list of products that can be configured, as a result of the components found. In general, you can exclude specific products if you do not want PARMGEN to run through their configuration processing. For OMEGAMON XE for DB2 PE you must not exclude the Tivoli Enterprise Monitoring Server (KDS). Even if you disabled the Tivoli Enterprise Monitoring Server using RTE_TEMS_CONFIGURED_FLAG on KCIP@PG3, this product is still required for the configuration. For this example, do not exclude anything and confirm this with Y in the appropriate field.

17. Press Enter to display a dialog that asks you whether you want to back up your existing configuration.

18. Press Enter, as the backup is only required if you rerun the KCIJPCFG job.

19. Submit the KCIJPCFG job that is open, then press PF3 once to go back to the main menu. You see in the status field of the KCICPFG job that the job is submitted.

20. Press Enter until the KCIJPCFG field contains a return code. The expected return code is zero. If you have a higher return code, inspect the job log and take appropriate actions.

21. Use option 2 RTE0A (name of the RTE) to open the list of available PARMGEN profiles.

22. The list of available PARMGEN profiles is displayed on KCIP@PG6.
 
KKCIP@PG6 ------ CUSTOMIZE PARMGEN CONFIGURATION PROFILE MEMBERS ---------------
Command ===>                                                  Scroll ===> CSR                                                                            
                                                                             
(Required) Customize the RTE profile and the $GBL$USR user profiles:          
(Tip) Review KCIJPDLA autodiscovery job in Utility menu or type DLAJOB cmd.  
   1. RTE0A    RTE LPAR-specific CONFIG profile in WCONFIG (User copy)        
   2. $GBL$USR Global parameters CONFIG profile in WCONFIG (User copy)        
                                                                             
(Not Required) Customize the RTE Variables profile if RTE_SYSV_SYSVAR_FLAG=Y:
   3. RTE0A    Variables (system, user) CONFIG profile in GBL_USER_JCL PARMGEN
               global library (SYS1PMO.O310.V540.PARMGEN.JCL).                
               Add or override system or user-defined symbols and their      
               resolution values for symbols used in the user profiles.      
                                                                             
(Tip) Review/Customize WCONFIG Kpp$C*/Kpp$P*/Kpp$S* user imbeds:              
(Cloning Tip) Review KCIJPCCF job in Utility menu prior to customization.    
   4. WCONFIG  SYS1PMO.O310.RTE0A.WCONFIG                                    
                                                                             
(Tip) Review if you want to compare with IBM-supplied default profile values:
   5. $CFG$IBM RTE LPAR-specific CONFIG profile in WCONFIG (IBM copy)        
   6. $GBL$IBM Global parameters CONFIG profile in WCONFIG (IBM copy)        
                                                                             
(Optional) Override SYSIN member to supply additional (User) profiles:        
   7. $SYSIN   $PARSE/$PARSESV SYSIN controls (CONFIG/SELECT MEMBER)  

       
PARMGEN profiles contain the parameter value pairs that make up the configuration. RTE0A contains all product/component-specific parameters. $GBL$USR contains all global configuration parameters.

23. Use option 1 RTE0A to open the PARMGEN user profile for the products/components and adjust the following parameters with the given values:
  1. RTE_X_STC_INAPF_INCLUDE_FLAG = Y When this parameter is set to Y, the started task contains an imbed that does the APF authorization for you. If you need to set the APF authorizations in your environment by hand, leave this parameter to N and follow the steps in the Complete the Configuration for the OMEGAMON XE for DB2 Performance Expert/Monitor Technote at the end of this walkthrough.
  2. KD2_CLASSIC_DB2PM_PLANPKG_OWNER = DB2PM This is the name of the plan and package owner that is used to access the OMEGAMON XE for DB2 PE packages in DB2.
  3. KD2_OMPE_GRANT_PEUSER = <user for Started tasks> This is the user for the RACF userid/groupid in OMGPssid grant job in xKD2SAM DB2 job. Under this user Classic Interface Started task and other Started tasks should run.
  4. KD2_DB01_DB2_SSID = <SSID of the subsystem you want to monitor> Use this parameter to specify the SSID of the subsystem that you want to monitor at the end of this walkthrough.
  5. KD2_DB01_DB2_VER = <DB2 version of the subsystem that you want to monitor> Specify the DB2 version of your subsystem that you want to monitor. This can be either 10, 11 or 12.

24. Use PF3 to get back to KCIP@PG6. This walkthrough covers only a very basic setup. After you complete all the steps, you can adjust all parameters, add subsystems, and configure your monitoring profiles accordingly. For now, keep all other parameters as is.

25. Use option 2 $GBL$USR to open the global PARMGEN user profile and adjust the following parameters with the given values:
  1. GBL_DSN_DB2_RUNLIB_Vxx = <Path to your DB2 runlib> This is the path to the data sets that holds your DB2 RUNLIB. You must specify the corresponding library of the DB2 version that is provided by KD2_DB01_DB2_VER. This parameter and the following parameters are commented out by default. To comment them in, remove the asterisk (*) at the beginning of the line.
  2. GBL_DSN_DB2_LOADLIB_Vxx = <Path to your DB2 loadlib> This is the path to the data sets that hold your DB2 LOADLIB. You have to specify the corresponding library of the DB2 version that is provided by KD2_DB01_DB2_VER.
  3. GBL_DSN_DB2_DSNEXIT = <Path to your DB2 exit library> This is the path to the data sets that hold your DB2 exit library.
26. Press PF3 twice to get back to KCIPQPGB, the workflow user interface welcome page.

27. Use option 3 $PARSE to open KCIP@PR1.

28. Use option 1 $PARSE to open the composite job that generates the work libraries. The resulting set of libraries is a complete environment that can be used to test the configuration before deploying it to the production environment. In other words, $PARSE generates all the configuration members in the corresponding work data sets WK*.

29. Submit the job. The expected return code is zero.

30. Use PF3 twice to get back to KCIPQPGB the workflow user interface

31. Use option 4 SUBMIT to open KCIP@SUB. This panel contains several more jobs, most of which are conditional and are used to finish the configuration. This includes the allocation of the runtime libraries and the copy of the program code from the target libraries to the runtime libraries. Not all jobs that are listed here are submitted by the composite job automatically. This depends on your environment and your monitoring needs.
KCIP@SUB -------- SUBMIT BATCH JOBS TO COMPLETE PARMGEN SETUP -----------------
Option ===>                                                                    
                                                                             
Select option 1 to SUBMIT the composite jobs in WKANSAMU for RTE0A RTE.        
Tip: Review the SUBMIT commands in the KCIJPSUB composite job.                
                                                                             
Alternatively, select other options (2-12) to submit each job individually.    
Enter ns (1s-12s) for detailed job/task status.                                
                                                                             
                  Description               REQ  Job Name   Status     Date  
   --------------------------------------- ----- -------- --------- ----------
                                                                             
1.  Composite SUBMIT job (See JCL comments)       KCIJPSUB RC= 00000 2017/02/09
   ** or **                                                                  
2.  Allocate runtime RO and RW datasets     (Yes) KCIJPALO RC= 00000 2017/02/09
3.  Copy SMP/E mbrs from TK*->RK* RO libs   (Yes) KCIJPLOD RC= 00000 2017/02/09
4.  Run product security steps              (Yes) KCIJPSEC RC= 00000 2017/02/09
5.  Update variable-named runtime mbrs      (No ) KCIJPUPV                    
6.  (Re)Create USS runtime mbrs in RKANDATV (No ) KCIJPUSP RC= 00000 2017/02/09
7.  Create USS dirs./ (Re)Copy USS files    (No ) KCIJPUSS                    
8.  Copy runtime mbrs to SYS1-type libs (Caution) KCIJPSYS                    
9.  Run post-SMP/E RKANMODU ASM/LINK steps  (No ) KCIJPLNK RC= 00000 2017/02/09
10. Verify the configuration jobs           (Tip) KCIJPIVP                    
11. Back-up RK* product execution user libs (Tip) KCIJPCPR RC= 00000 2017/02/09
12. Copy runtime mbrs from WK*->RK* RW libs (Yes) KCIJPW2R RC= 00000 2017/02/09


32. Select option 1 KCIJPSUB to open the composite SUBMIT job and submit it. The expected return code is zero.

33. Use PF3 to get back to the KCIP@SUB panel. Press Enter until all jobs are finished. The expected return codes are zero. If you have a higher return code, check the job logs and take appropriate actions.

34. Use PF3 to get back to the KCIPQPGB panel.

35. As a final step, refer to the Complete the Configuration for the OMEGAMON XE for DB2 Performance Expert/Monitor Technote or see see Completing the configuration for z/OS. This guide contains several mandatory steps to set up the server correctly. Most of these steps only have to be done once. After you finished the steps in the Complete the Configuration for the OMEGAMON XE for DB2 Performance Expert/Monitor Technote, you can start the server and open the Classic Interface to start monitoring your subsystem.

What to do next

After having installed OMEGAMON XE for DB2 PE from scratch, you can continue by enabling more functions. Functions that can be enabled are, for example, Near-Term History and Snapshot History.

You can continue with other scenarios in order to configure more than one DB2 subsystem, even if they are spread over different LPARs in your environment.


Chapter 10. Configuration scenarios
Section: Configuration scenario specific to OMEGAMON XE for DB2 PE/OMEGAMON XE for DB2 PM

This scenario describes how to configure Near-Term History in an RTE that is enabled for system variable support.

Before you begin
As a prerequisite, you need an RTE having OMEGAMON® XE for DB2® PE already configured and system variable support enabled.

Procedure

  1. Start the Configuration and Installation Tools user interface by issuing the command ex on the TKANCUS library in your SMP/E installation.
    ex ‘&trghlq.TKANCUS’
  2. Use option 3 Configuration Workflow to open the PARMGEN workflow user interface.
  3. Enable your existing RTE that has been already enabled for system variable support.
  4. Use option 2 to open the PARMGEN profile selection menu.
  5. Use option 1 to open the RTE LPAR configuration profile.
  6. Enable Near-Term History for those profiles that you use for monitoring your DB2 subsystems by setting parameter KD2_PFnn_HIS_START to Y. nn is the profile ID. Previously, with the Configuration Tool, you had to enable system variable support for Near-Term History separately on the panel KD261PI Global Control Parameters. This in turn prevented the use of %DB% and %SY% in the Near-Term History data sets. This limitation is no longer valid. In addition, you do not have to enable system variable support for Near-Term History separately.
  7. Use PF3 to get back to the main workflow panel KCIPQPGB.
  8. Use option 3 to open the $PARSE job panel KCIP@PR1.
  9. Use option 1 to open the composite $PARSE job and submit it. The expected return code is zero.
  10. Use PF3 twice to get back to the main workflow panel KCIPQPGB.
  11. Use option 4 to open the SUBMIT job panel KCIP@SUB.
  12. Use option 5 to open the KCIJVUPV job that regenerates the Near-Term History configuration and submit it. The expected return code is zero.
  13. Use option 12 to open the KCIJPW2R deployment job and submit it. The expected return code is zero.
What to do next
Now that you configured Near-Term History, restart the OMEGAMON XE for DB2 PE server. Use the Classic Interface to look at the history data.

Section: Configuring InfoSphere Optim Performance Manager and Performance Expert Client

This scenario describes how to configure the InfoSphere® Optim™ Performance Manager in order to get end-to-end SQL monitoring (Extended Insight) and stored procedure monitoring. This feature is only for OMEGAMON XE for DB2 PE only (not for OMEGAMON XE for DB2 PM).

Before you begin
As a prerequisite, you need a runtime environment having OMEGAMON XE for DB2 PE already configured.

Procedure

  1. Start the Configuration and Installation Tools user interface by issuing the command ex on the TKANCUS library in your SMP/E installation.
    ex ‘&trghlq.TKANCUS’
  2. Use option 3 Configuration Workflow to open the PARMGEN workflow user interface.
  3. Enable the runtime environment where you want to configure InfoSphere Optim Performance Manager.
  4. Use option 2 to open the PARMGEN profile selection menu.
  5. Use option 1 to open the RTE LPAR configuration profile and adjust the following parameters:
    Table 1. Parameter values of the RTE LPAR configuration profile
    Parameter
    Value
    Description
    KD2_OMPE_E2E_MON_SPRT
    Y
    Enables Extended Insight Dashboard (end-to-end SQL monitoring)
    KD2_DBnn_DB2_PORT_NUM
    <port>
    Mandatory. This specifies the port that is used to connect InfoSphere Optim Performance Manager to the OMEGAMON XE for DB2 PE server. You can keep the default port 2000. You need this port information for later.
    KD2_PFnn_TRACES_318
    Y
    Enables the automatic start of IFCID 318.
    KD2_PFnn_TRACES_400
    Y
    Enables the automatic start of IFCID 400. Set this parameter to Y only if you want to monitor DB2 10 and above.
    KD2_PFnn_READA_SPMON
    Y
    Enables stored procedure monitoring.
  6. Use PF3 to get back to the main workflow panel KCIPQPGB.
  7. Use option 3 $PARSE to open the job panel KCIP@PR1.
  8. Use option 1 to open the composite $PARSE job and submit it. The expected return code is zero.
  9. Use PF3 to get back to the main workflow panel KCIPQPGB.
  10. Use option 4 to open the SUBMIT job panel KCIP@SUB.
  11. Use option 12 to open the KCIJPW2R to copy the configuration from the work libraries to the runtime libraries. Submit the upcoming job. The expected return code is zero.

What to do next

For integration of the InfoSphere Optim Performance Manager into Tivoli Enterprise Portal find more information in section Enabling InfoSphere Optim Performance Manager integration in Completing the configuration for z/OS components.

Install InfoSphere Optim Performance Manager and configure it for the monitored database. For more information, see the IBM® InfoSphere Optim Performance Manager in the Knowledge Center.

Chapter 15. Completing the configuration for z/OS components

Go through the steps in the post-configuration README to complete the configuration.

About this task
After you configured OMEGAMON® XE for DB2® PE, go through the list of mandatory steps in the post-configuration README in PARMGEN. Also consider going through the optional steps in that README to see whether further configuration steps are desired. To open the post-configuration README follow these steps:

  1. In PARMGEN, navigate to the Primary Option Menu on panel KCIPQPGB.
  2. Either:
Select option 5 POSTCFG to open KCIP@FNL.
or:
a. Type U as primary command to show the utilities panel KCIPQPGU.
b. Select 13 Display a consolidated list of post-configuration README.
3. In the product list, select KD5.

Publication number

GH12-6998-00

Document information

More support for: DB2 Tools for z/OS
IBM Tivoli OMEGAMON XE for DB2 PE / PM / BPA

Software version: 5.2.0

Operating system(s): z/OS

Reference #: 7040576

Modified date: 20 February 2017


Translate this page: