IBM Support

V 5.3.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-7054-00, for Version 5.3.0.

Content

The most recent update is listed first.



Update 9
Date of change: December 2017
Topics: “Enabling Options in OMEGAMON for DB2 PE Collector Realtime Customer Options (OMPEOPTS)” section of Chapter 14
Change description: The default value for DP2RTCPU and DB2REMIO options have been changed to YES.

See the following PDF for documentation changes:
techdocko2cc.pdf


Update 8
Date of change: February 2017
Topics: Multiple
Change description: 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:

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.V530______________________  ________ / ________ /  
                 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.V530.PARMGEN.JCL_______________                
               (for example, SYS1.KO2.V530.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.V530.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.V530.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.V520.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.



Update 7
Date of change: January 2017
Topics: Chapter 11. "Configuring basic components on z/OS"
Change description: The list of possible values for the near-term history data collection options keyword ACCTG in Chapter 11. "Configuring basic components on z/OS" has been modified from 1,2,3,7,8,10 to 1,2,3,7,8,10,11:

ACCTG - Near-term history data collection options keyword:
Specifies the type of Accounting data to collect.

ACCTG
( type)
type
1 collects data from Accounting class 1 (IFCID 0003, and 0106, no In-DB2 or I/O and lock wait times).
2 collects data from Accounting class 1 and 2 (IFCID 0003 In-DB2 elapsed and CPU time).
3 collects data from Accounting class 1, 2, and 3 (IFCID 0003 all wait times I/O and lock wait times).
7 collects data from Accounting class 7 (IFCID 0003, 0239 Package In-DB2 time).
8 collects data from Accounting class 8 (IFCID 0003, 0239 Package I/O and lock wait times).
10 collects data from Accounting class 10 (IFCID 0239 Package detail).
11 collects data from Accounting class 11 (IFCID 0003 and 0200). For DB2 11 and above only.

Accounting class 10 data contains package detail data from IFCID 239. To avoid unnecessary system overhead, collect this data only if required.

To reduce the number of IFCIDs collected and not collect the IFCID 239, class 11 should be requested without classes 7, 8 and 10.

No default is applied. If this keyword is not specified, no Accounting data is collected.



Update 6
Date of change: August 2016
Change description: IRLM parms from IFCID 106 missing in member RKO2SAMP(DGOWC106) in OMEGAMON XE for DB2 PE V530:

The PDB System Parameter Table DB2PMSYSPAR_106 (IFCID 106)for OMEGAMON XE for DB2 PE V530 is defined in member RKO2SAMP(DGOWC106). The following columns are not available:

IRLM_LOCAL_CYCLES
IRLM_WAIT_TIME
IRLM_LOCK_HASH_ENT
IRLM_MAX_CSA_USAGE
IRLM_PEND_HASH_ENT
IRLM_LOCK_LIST_ENT
IRLM_TIMEOUT_INT
IRLM_PC_FLAG

To store these fields from your DB2 trace into the table, do the following:
  1. The new load module FPECMAIN writes the additional fields to file whenever you run a SYSPARMS report with the FILE option.
  2. Edit RKO2SAMP sample member DGOWUPDB. Run the DDL statements for this PTF to add the new columns to your table. If you have not yet created a System Parameter table for IFCID 106, create the table using member DGOWC106 of this PTF.
  3. Run a load job using sample member DGOWL106 in this PTF and the newly-created file from (1) as input.

RKO2SAMP member DGOWB106 contains the field descriptions.
RKANSAMF member FPEPW106 is for spreadsheet creation.



Update 5
Date of change: August 2016
Topics: "Upgrading the Performance Database"
Change description: Support for migrating system parameter tables from V5.2.0 to V5.3.0 has been added to the section "Upgrading the Performance Database":

Migrating System Parameter tables

In OMEGAMON XE for DB2 PE V5.3.0 the layout of Performance Database System Parameter tables for IFCIDs 106, 201, 202 have changed.

The table names are DB2PMSYSPAR_106, DB2PMSYSPAR_201 and DB2PMSYSPAR_202.

If you want to preserve the data in these tables, this APAR provides a DDL to support data migration from V5.2.0 to V5.3.0. The member DGOWMIDB of TKO2SAMP in this PTF includes an INSERT statement for each affected table that inserts all data from the V5.2.0 table into the V5.3.0 table. All columns in the V5.3.0 table that have matching columns in V5.2.0 are filled by the values from the V5.2.0 table. "Matching columns" include columns with identical names and columns with changed names that contain the same fields from DB2. Values of new columns in V5.3.0 are NULL by default.

Make sure you kept the V5.2.0 table with a different name from that of the V5.3.0 table (RENAME), then, before you run the INSERT, edit the names of the "from" and "into" table in this sample as appropriate.

These columns from the V5.2.0 tables do not exist any more in table of V5.3.0:

Table DB2PMSYSPAR_106:

ALLOC_STORAGE
ASYNC_DRAIN_START
ASYNC_DRAIN_STOP
CHARSET
COMPAT
CONV_FACTOR
CRIT_SPACE
DB1_MAX
DBCHK
DBPROTCL
DECDIV3
DECP_INDICATOR
DEF_DELIMITER
DEF_SQL_DELIMITER
EDMBFIT
EDMDSMAX
EDMDSPAC
HASH_TABLE5
HOPAUTH
IO_ACTIV
IRLM_INIT_TIME
IRLM_LOCAL_CYCLES
IRLM_LOCK_HASH_ENT
IRLM_LOCK_LIST_ENT
IRLM_MAX_CSA_USAGE
IRLM_PC_FLAG
IRLM_PEND_HASH_ENT
IRLM_TIMEOUT_INT
IRLM_WAIT_TIME
LOC_TR_TAB_SIZE
LOGAPSTG
MAX_EXT_SERV
MAX_MEMBER_NMBR
MINDVSCL
MSGVP
MSGVP2
MVS_ENVIRONMENT
NEWFUN
NOT_FOUND_#
OFFLOAD
ONL_CORR_ID_MON
ONL_PARM_TYPE
ONL_TIME_CHANGED
ONL_USER_ID_MON
PARTKEYU
PROCS_DESC
RELCURHL
SJMXPOOL
SOS_SPACE
STORPROC
VERSION
Table DB2PMSYSPAR_201:
NEW_CASTOUT
NEW_HPOOL_SEQ_THR
NEW_HPOOL_SIZE
NEW_VPTYPE_ATTR
OLD_CASTOUT
OLD_HPOOL_SEQ_THR
OLD_HPOOL_SIZE
OLD_VPTYPE_ATTR
Table DB2PMSYSPAR_202:
CASTOUT
NAME
HPOOL_SIZE
HPOOL_SSEQ_THRESH
VPTYPE_ATTRIBUTE




Update 4
Date of change: August 2016
Topics: "Migration data to new statistics tables"
Change description: Support for migrating Performance Database Statistic Tables from V5.2.0 to V5.3.0 has been added the section "Migration data to new statistics tables":

Support for migrating Performance Database Statistic Tables from V5.2.0 to V5.3.0

In OMEGAMON XE for DB2 PE V5.3.0 the Performance Database statistic table for GENERAL data (DB2PM_STAT_GENERAL) exceeded the DB2 750 column constraint. For this reason all storage related fields have been released to a new table STORAGE data (DB2PM_STAT_STORAGE).

In V5.3.0 the GENERAL data table consists of information that is related to IFCID 1 and 2. The STORAGE data table contains data from IFCID 225. APAR PI63414 supports all customers who want to migrate from a standard V5.2.0 GENERAL data table to V5.3.0 GENERAL data and to version V5.3.0 STORAGE data tables.

Note: If you customized the V5.2.0 table format (for example, dropped, added or renamed columns) you cannot use the sample members shipped in PI63414.


To migrate the remaining PDB statistic tables from V5.2.0 to version V5.3.0, follow the SQL statements provided in TKO2SAMP member DGOSUPDB.
1. Install the latest V5.2.0 PTFs. Make sure that your V5.2.0 Performance Database statistic tables are up-to-date. Verify that you run all SQL commands provided in V5.2.0 TKO2SAMP member DGOSUPDB.
2. Unload your V5.2.0 GENERAL data table to disk. Use the DB2 UNLOAD utility to unload your V5.2.0 GENERAL data table (DB2PM_STAT_GENERAL) to disk. The result is two datasets:

  • A CNTL (Control) dataset that can be used to reload the original data (for example, JOHN.DA21.CNTL.MYPDB.TSASP32K).
  • A dataset that contains the real DB2 table (for example, JOHN.DA21.UNLD.MYPDB.TSASP32K). You need this data later to "fill" the V5.3.0 Performance Database tables.
3. Rename your V5.2.0 GENERAL data table (DB2PM_STAT_GENERAL) The structure of the V5.3.0 GENERAL data is completely different to the V5.2.0 format. Use the SQL command RENAME TABLE to rename your existing V5.2.0 table:

RENAME TABLE DB2PM_STAT_GENERAL TO DB2PM_STAT_GENERAL_V520

You need to rename the existing V5.2.0 table because the same name for the new V5.3.0 GENERAL table is used in the samples.
4. Create the V5.3.0 GENERAL data table (DB2PM_STAT_GENERAL). In your V5.3.0 TKO2SAMP dataset, locate the sample member DGOSCGEN. It provides the SQL command to create the new V5.3.0 GENERAL table in your local Performance Database:

CREATE TABLE DB2PM_STAT_GENERAL                                
(DB2PM_REL            SMALLINT          NOT NULL WITH DEFAULT,
 DB2_REL              CHAR(2)           NOT NULL WITH DEFAULT,
 MVS_ID               CHAR(4)           NOT NULL WITH DEFAULT,
 LOCAL_LOCATION       CHAR(18)          NOT NULL WITH DEFAULT,
 GROUP_NAME           CHAR(8)           NOT NULL WITH DEFAULT,
 SUBSYSTEM_ID         CHAR(4)           NOT NULL WITH DEFAULT,
 MEMBER_NAME          CHAR(8)           NOT NULL WITH DEFAULT,
 ...
 ABENDS_ISSUED        DOUBLE PRECISION  NOT NULL WITH DEFAULT)
 IN DB2PE.TSSGE32K        

Replace the placeholders DB2PE (Database) and TSSGE32K (Tablespace) to fit your local PDB database and table space names. Afterwards run the SQL command to create the V5.3.0 GENERAL data table in your local PDB.
5. Create the V5.3.0 STORAGE data table (DB2PM_STAT_STORAGE). In your V5.3.0 TKO2SAMP dataset, locate the sample DGOSCSTG. It provides the SQL command to create the new V530 STORAGE Data table in your local Performance Database:

CREATE TABLE DB2PM_STAT_STORAGE                                
(DB2PM_REL            SMALLINT          NOT NULL WITH DEFAULT,
 DB2_REL              CHAR(2)           NOT NULL WITH DEFAULT,
 MVS_ID               CHAR(4)           NOT NULL WITH DEFAULT,
 LOCAL_LOCATION       CHAR(18)          NOT NULL WITH DEFAULT,
 GROUP_NAME           CHAR(8)           NOT NULL WITH DEFAULT,
 SUBSYSTEM_ID         CHAR(4)           NOT NULL WITH DEFAULT,
 MEMBER_NAME          CHAR(8)           NOT NULL WITH DEFAULT,
 ...
 QW0225_RS            INTEGER           NOT NULL WITH DEFAULT)
 IN DB2PE.TSPSSTG    
   

Replace the placeholders DB2PE (Database) and TSPSSTG (Tablespace) to fit your local Performance Database database and table space names. Afterwards run the SQL command to create the V5.3.0 STORAGE data table in your local PDB.
6. Load the V5.3.0 GENERAL data. Now you are ready to fill the V5.3.0 GENERAL data using the data that you stored in step 2. Use the TKO2SAMP member DGOSLMGE (shipped in PI63414) in a DB2 Load Job and specify the data you unloaded. For example:
...
//* 520 DB2PM_STAT_GENERAL UNLOADED TO DISK:
//SYSREC   DD DISP=SHR,DSN=JOHN.DA21.UNLD.MYPDB.TSASP32K
...
//* LOAD INSTRUCTIONS FOR 530 DB2PM_STAT_GENERAL:
//SYSIN     DD DISP=SHR,DSN=OMPE.V530.TKO2SAMP(DGOSLMGE)

Submit this LOAD job. The return code should either be 0 or 4. If DB2 provides a return code of 4, run a REORG on the tablespace.
After you have run the load job, verify the following:

  • Open the SYSPRINT DD that LOAD provided and check that the number of records loaded is identical to the number of records in your V5.2.0 GENERAL data table.
  • Scan your V5.2.0 GENERAL data (that you copied in step 3) and V5.3.0 GENERAL data and compare the common columns in both tables. You should see identical values for the existing columns. New fields introduced in V5.3.0 are empty.
  • If your return code is higher than 4, the SYSPRINT also gives you more information why the LOAD failed (which should not happen).
7. Load the V5.3.0 STORAGE Data. Use the data that you stored in step 2 to fill the V5.3.0 STORAGE Data. Use the TKO2SAMP member DGOSLMST (shipped in PI63414) in a DB2 Load Job and specify the data you unloaded. For example:
...
//* 520 DB2PM_STAT_GENERAL UNLOADED TO DISK:
//SYSREC   DD DISP=SHR,DSN=JOHN.DA21.UNLD.MYPDB.TSASP32K
...
//* LOAD INSTRUCTIONS FOR 530 DB2PM_STAT_STORAGE:
//SYSIN     DD DISP=SHR,DSN=OMPE.V530.TKO2SAMP(DGOSLMST)

Submit this LOAD job. The return code should either be 0 or 4. If DB2 provides a return code of 4, run a REORG on the tablespace.

After you have run the load job, verify the following:

  • Open the SYSPRINT DD that LOAD provided and check that the number of records loaded is identical to the number of records in your V5.2.0 GENERAL Data table.
  • Scan your V5.2.0 GENERAL Data (that you copied in step 3) and V5.3.0 STORAGE Data and compare the common columns in both tables. You should see identical values for the existing columns. New fields introduced in V5.3.0 will be empty.
  • If your return code is higher than 4, the SYSPRINT also gives you more information why the LOAD failed (which should not happen).



Update 3
Date of change: May 2016
Topics: "Installing the program files of Performance Expert Client" in Chapter 17
Change description: The procedure "Installing the program files of Performance Expert Client" in Chapter 17 has been modified:

Step 3 of the procedure has been updated:

Run the *.exe file. With Windows 8 or later, ensure that you run the *.exe file in Windows 7 Compatibility mode.



Update 2
Date of change: April 2016
Topics: Chapter 17. "Installing and configuring components on the workstation"
Change description: 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.

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 1
Date of change: December 2015
Topics: Chapter 11. "Configuring basic components on z/OS"
Change description: The description of the near-term history data collection options keyword NEGSQL in Chapter 11. "Configuring basic components on z/OS" has been modified

NEGSQL( toggle)
toggle
  • YES: Collect negative SQL code IFCID 58 and produce the Negative Application Codes SQL report.
    Note:
    Set NEGSQL to YES only if WRITEOPTION(VSAM, SEQ) is selected. In this case the negative SQL data is written to the sequential data set and can then be analyzed in the SQL Activity Report.
  • NO: Do not collect negative SQL code IFCID 58 and produce the Negative Application Codes SQL report.


Publication number

GH12-7054

Copyright date

1985, 2015

Original publication date

2015/5/29

Document information

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

Software version: 5.3.0

Operating system(s): z/OS

Reference #: 7046041

Modified date: 14 December 2017


Translate this page: