Setting up the work environment

To set up the work environment for an RTE, you specify what type of RTE is being configured, set RTE-specific values, and select the products to be configured in the environment. Then you submit the KCIJPCFG job, which uses the values you provide to allocate the work libraries, update the interim libraries, and create the configuration profiles for the RTE.

Procedure

  1. Select Set up PARMGEN work environment for an RTE from the primary options menu.
    The first Set up PARMGEN work environment for an RTE panel is displayed.

  2. On panel KCIPQPG1, leave the field blank to create a new RTE.
  3. Uncomment out the first two lines of the jobcard and specify values according to your environment.
  4. Press Enter to proceed to the next panel.

    The Set up PARMGEN Work Environment for an RTE (2 of 3) panel (KCIP@PG2) is displayed. The values on this panel are read from the profile library and runtime member name you specified on the preceding panel.

    KCIP@PG2  SET UP/REFRESH PARMGEN WORK ENVIRONMENT FOR AN RTE (2 OF 3) ---------
    Command ===>                                                                   
                            Quick Configuration Mode                               
    GBL_USER_JCL:   MY.RTE.PARMGEN.JCL                                       
    RTE_PLIB_HILEV: MY.RTE                                                   
    RTE_NAME:       SYSA                                                         
                                                                                   
    Enter parameter values appropriate for your environment:                       
                                                           UNIT     / STORCLAS /   
                                                           VOLSER     MGMTCLAS     
    GBL_TARGET_HILEV: IBM.TARGET.ITM63055________________  ________ / ________ /   
                      HLQ of SMP/E target (TK*) datasets   ______     ________     
                                                                                   
    GBL_SYSDA_UNIT:   SYSDA___                                                     
                      Work datasets UNIT name                                      
                                                                                   
    GBL_REGION:       0M______                                                     
                      JCL REGION (specify K/M suffix)                              
    
                                                                                   
    Note: Type BACK to go back one panel.  Type UTIL to access utility menu. 
  5. Review the values on the panel and override them as necessary.
    GBL_TARGET_HILEV
    Specifies the SMP/E high-level qualifier of the SMP/E target (TK*) libraries.
    GBL_SYSDA_UNIT
    Specifies the non-VSAM disk UNIT for global work data sets.
    GBL_REGION
    Specifies the JCL REGION value override if other than the REGION=0M value. This is the required storage value in Kilobytes or in Megabytes for PARMGEN batch jobs and product started tasks. The jobs contain the REGION= parameter on the EXEC statement. The syntax of the JCL REGION parameter is either &valueK or &valueM. Change this value as required by your installation. Specify K/M suffix (ex.: 4096K, 0M). The default is 0M.
  6. Press Enter to proceed to the next panel.
    The Set Up PARMGEN Work Environment for an RTE (3 OF 3) panel (KCIP@PG3) is displayed. The panel contains the values shown in the following figure.
    KCIP@PG3  SET UP/REFRESH PARMGEN WORK ENVIRONMENT FOR AN RTE (3 OF 3) ---------
    Command ===>                                                  Scroll ===> PAGE 
                                                                                   
    Enter parameter values appropriate for the LPAR RTE=SYSA.                     
    Press F1=Help for more information.                                            
                                                                       More:     + 
    RTE_DESCRIPTION:     DESCRIPTION_______          
                                                                                   
    RTE_TYPE:            SHARING_       (Full, Sharing)                            
    RTE_HILEV:           MY.RTE_____________________________ (ex.: MY.RTE
                         (&hlq  portion of Non-VSAM RK* HLQ=&hlq.&rte_name)        
    RTE_VSAM_HILEV:      MY.RTE_____________________________ (ex.: MY.RTE
                         (&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.: TDITN.IDTST)
                             (&hlq  portion of shared RTE's HLQ=&hlq.&rte_share)   
      RTE_SHARE: SMP________________________________ ("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:   MY.RTE.SYSA.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: DEMO:CMS__________________________ (e.g.,DEMO:cms))))
      KDS_TEMS_TYPE:             REMOTE__  (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)
    Depending upon your screen resolution, you might have to scroll down (PF8) to see all the parameters. (Note the More: + which indicates that there is additional content on the panel.)
  7. Provide values to required fields.
    • If your environment is not SMS-managed, specify the VSAM values.
    • Supply the high-level qualifier and the name for the base libraries:
      • RTE_X_HILEV_SHARING
      • RTE_SHARE
  8. Press Enter to proceed to the next panel.
    The Include Products in this PARMGEN RTE panel (KCIP@PGI) is displayed. This panel lists all the products installed in the product library.
    KCIP@PGI - INCLUDE (CONFIGURE) INSTALLED PRODUCT(S) IN THIS LPAR R Row 1 of 26 
    Command ===>                                                  Scroll ===> PAGE 
                                                                                   
    Select ("S" or "/") products to CONFIGURE those product(s) in DEMO RTE.      
    Select or deselect products to include or exclude from configuration.          
    Products configured in the model or current RTE (reconfiguring) are preselected
                                                                                   
    When finished, change N to Y to confirm selections.  Confirm ==> N  (Y, N)     
                                                                                   
      Kpp  Component or Product Name and Version                                   
      ---- ----------------------------------------------------------------------                                                          
    / KDS  Tivoli Enterprise Monitoring Server V630                                                    
    / KJJ  OMEGAMON AI for JVM V610                                        
    / KOB  OMEGAMON Enhanced 3270 User Interface V730                       
    End of data
    If you have other products in the ServerPac that you installed, they will be shown in the list as well.
  9. All products are selected by default in the model. Make sure Tivoli Enterprise Monitoring Server (KDS), OMEGAMON AI for JVM (KJJ), and OMEGAMON Enhanced 3270 User Interface (KOB) selected. Deselect other products if any, then change Confirm ==> N to Y, and press Enter.
    The JCL for the KCIJPCFG job is displayed.
  10. Review the JCL to understand what the job is doing, then submit the job by typing SUBMIT or SUB in the Command line and press Enter.
    The KCIJPCFG jobs submits a second job, KCIJPPRF. Wait for both jobs to complete successfully before proceeding to the next step.
  11. Return to the Workflow - Primary Option Menu by pressing F3.

Results

The configuration software allocates the runtime libraries, creates the configuration profiles, and populates the PARMGEN templates in IKAN* libraries with runtime members for the products selected for configuration.