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.

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 5 Configure to open the PARMGEN workflow user interface.
3. As this is the first setup, you have to provide some basic information on this first panel:

    
   KCIP@PG0 ------ PARAMETER GENERATOR (PARMGEN) WORKFLOW - WELCOME --------------
   Option ===>                                                   Scroll ===> PAGE 
   Enter PARMGEN parameter values appropriate for your environment:               
   GBL_USER_JCL:   ____________________________________________                   
                   PARMGEN common/global library for RTEs (CONFIG DD lib. in STCs)
   RTE_PLIB_HILEV: ________________________                                       
                   High-Level Qualifier (HLQ) of work libraries (IK*,WCONFIG,WK*) 
   RTE_NAME:       ________  (Type ? for a list of configured RTEs)               
                   Runtime environment (RTE) name for this LPAR                   
                                                                                  
   Note:  Enter n  (1-11) to perform tasks.                     Status     Date   
          Enter ns (1s-11s) for detailed job/task status.     --------- ----------
                                                                      More:     + 
   1.  KCIJPCFG Set up PARMGEN work environment for an RTE.                       
   2.  $JOBINDX Review PARMGEN job index.                                         
   3.  KCIJPCCF Clone customized WCONFIG members.      (COND)                     
   4.  KCIJPUP1 Update interim libraries and create profiles.                     
   5.  KCIJPMC1 Merge profile from backup profile      (COND)                     
   6.  KCIJPMC2 Merge profile from model RTE.          (COND)                     
   7.  KCIJPCNV Convert an ICAT RTE Batch member.      (COND)                     
   8.           Customize PARMGEN configuration profiles.                         
   9.  KCIJPVAL Validate PARMGEN profile parameter values.                        
   10.          Create the RTE members and jobs.                                  
        
                                                                              

4. Add common PARMGEN-related information for 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.
5. Add high-level qualifier for your runtime environments for parameter RTE_PLIB_HILEV.
6. Add the name of your new RTE for parameter RTE_NAME.
7. This example uses the following values for these parameters:
   • GBL_USER_JCL: SAR.PG.V540.JCL
   • RTE_PLIB_HILEV: SAR.PG.V540
   • RTE_NAME: RTE0A
   
   Note: The length of RTE_PLIB_HILEV plus RTE_NAME must not exceed 18 characters.
8. Press Enter to commit your settings.
9. 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 10, as shown in the list below the RTE names.
10. On KCIP@PG1, fill in your jobcard that will be 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 will only show the first four lines.
11. Press Enter to get to the next panel.
12. 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, and MGMGCLAS as appropriate for your system.
13. Press Enter to get to the next panel.
14. 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 PARMGEN WORK ENVIRONMENT FOR AN RTE (3 OF 3) ------------
       Command ===>                                                  Scroll ===> PAGE 
                                                                                      
       Enter parameter values appropriate for your RTE=RTE0A.                         
       Note: See F1=Help for SMS-related and RTE HLQ-related considerations           
       when VOLUME, UNIT, STORCLAS, and MGMTCLAS parameters are required for          
       the global RTE_* parameters and the Kpp_* product-specific parameters.         
                                                                          More:     + 
       RTE_SMS_PDSE_FLAG:     Y               (PDSE flag (Y, N))                      
                                                                                      
       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_HILEV:                 SAR.PG.V540_______________ (Non-VSAM prod. RK* HLQ) 
       RTE_VSAM_HILEV:            SAR.PG.V540_______________ (VSAM production RK* HLQ)
                                                                                      
       RTE_TYPE:                  FULL______  (FULL, SHARING)                         
       RTE_SHARE:                 __________________________ (SMP or shared RTE name) 
       RTE_X_HILEV_SHARING:       __________________________ (HLQ of shared RTE)      
       RTE_TEMS_CONFIGURED_FLAG:  Y           (Y, N)                                  
       RTE_TEMS_NAME_NODEID:      RTE0A:CMS_______________________ (e.g., RTE1:cms)   
       RTE_STC_PREFIX:            CANS______________________ (Started task prefix)    
       RTE_VTAM_APPLID_PREFIX     CTD_______________________ (VTAM APPLID prefix)     
       RTE_SYSV_SYSVAR_FLAG:      N           (Y, N)         (System variable flag)   
       RTE_X_SYSV_OVERRIDE_SYMBOLS: N         (Y, N)         (SysVar override flag)   
                                                                                      
       RTE_SECURITY_USER_LOGON:   NONE______  (RACF, ACF2, TSS, NAM, SAF, None)       
       RTE_SECURITY_FOLD_PASSWORD_FLAG: Y     (Fold to upper case (Y, N))             
       RTE_SECURITY_CLASS:        __________                                          
       RTE_X_SECURITY_EXIT_LIB:   SAR.PG.V540.RTE0A.RKANSAMU__________________        
       GBL_DSN_ACF2_MACLIB:   ____________________________________________  (If ACF2) 
       GBL_DSN_ACF2_MACLIB1:  ____________________________________________  (If ACF2) 
                                                                                      
       KDS_TEMS_TYPE:             HUB_______                 (Hub, Remote)            
       KDS_TEMS_HA_TYPE:          __________                 (Hub TEMS type (HA)) 
             
         

       
15. On KCIP@PG4, you see a list of components that were found in your TKANCUS library, and thus can be configured.
16. Press Enter to get to the next panel.
17. On KCIP@PG5, you see a list of products that can be configured, as a result of the components found in the previous step. 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 N in the appropriate field.
18. Press Enter to open up a dialog that asks you whether you want to back up your existing configuration.
19. Press Enter, as the backup is only required if you rerun the KCIJPCFG job.
20. Submit the KCIJPCFG job that is open and go back to the main menu by pressing PF3 twice. You now see in the status field of the KCICPFG job that the job is submitted.
21. Press Enter until the KCICPFG field contains a return code. The expected return code is zero. If you have a higher return code, then look into the job log and take appropriate actions.
22. Use option 4 KCIJPUP1 to open the KCIJPUP1 job that is used to update the interim libraries and create the PARMGEN user profiles. KCIJPCFG creates the work data sets and KCIJPUP1 fills them with the code that will finally generate the product configuration. For a more detailed explanation on all the jobs and their functions, read the job headers or look at the various PARMGEN documentation and videos.
23. Submit the KCIJPUP1 job and go back to the main panel by pressing PF3 twice. Wait until the job has finished. The expected return code is zero.
24. Use option 8 RTE0A (name of the RTE) to open the list of available PARMGEN profiles.
25. On KCIP@PG6 you see the list of available PARMGEN profiles.

     
    KCIP@PG6 ------ CUSTOMIZE PARMGEN CONFIGURATION PROFILE MEMBERS ---------------
    Option ===>                                                                    
     (Required)* Select option 1 to customize the RTE0A RTE LPAR profile:          
        1. RTE0A    RTE LPAR CONFIG profile in WCONFIG                             
                                                                                   
     (Conditional)* Select option 2 and/or 3 if applicable to this RTE:            
        2. $GBL$USR Global parameters CONFIG profile in WCONFIG                    
                    (Required if this is not an ICAT-to-PARMGEN conversion         
                     or if this is a product upgrade - see F1=Help)                
        3. RTE0A    System Variables CONFIG profile in GBL_USER_JCL                
                    (SAR.PG.V540.JCL)                                              
                    (Required if using user-defined symbols or overriding          
                     system symbols' resolved values - see F1=Help)                
     *Note: The PARMGEN configuration profiles above are preserved                 
            (initially created by KCIJPUP1 or KCIJPUP2 job).                       
     (Reference) IBM-supplied default profiles (refreshed by KCIJPUP1 job):        
        4. $CFG$IBM IBM default RTE LPAR CONFIG profile in WCONFIG                 
        5. $GBL$IBM IBM default Global parameters CONFIG profile in WCONFIG        
        6. $SYSIN   $PARSE/$PARSESV SYSIN controls (CONFIG/SELECT MEMBER)          
                                                                                   
     (Optional) Select option 7 for member list of the WCONFIG library:            
        7. WCONFIG  SAR.PG.V540.RTE0A.WCONFIG                                    
         
     

    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.

26. 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 will contain 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_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.
    4. 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.
27. 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.
28. 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 have to 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, just remove the two asterisks (**) 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.
29. Use PF3 twice to get back to KCIP@PG0, the workflow user interface welcome page.
30. Use option 10 $PARSE to open KCIP@PRS.
31. 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*.
32. Submit the job. The expected return code is zero.
33. Use PF3 to get back to KCIP@PG0. Option 9 on KCIP@PG0 runs a validation over the PARMGEN profiles to check whether the parameter values are valid. This validation is also run during the composite $PARSE. If the validation of at least one parameter fails, nothing is changed or generated. To see the validation report, open $VALRPT in your WCONFIG work library, which you find under your RTE high-level qualifier.
34. Use option 11 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.
35. Use option 1 KCIJPSUB to open the composite SUBMIT job and submit it. The expected return code is zero.
36. Use PF3 to get back to the KCIP@SUB panel.
37. Use option 13 KCIJPW2R to copy the configuration from the work libraries to the runtime libraries. This job is never run automatically by PARMGEN. You can configure anything in PARMGEN but it will not override your existing production environment. Only when you run KCIJPW2R, your production environment is updated with the new configuration.
38. Submit the job that comes up. The expected return code is zero.
39. As a final step, refer to the Complete the Configuration for the OMEGAMON XE for DB2 Performance Expert/Monitor Technote. This guide contains several mandatory steps in order to properly set up the server. 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 in order to start monitoring your subsystem.