Creating the runtime environment

Edit online

Creates a runtime environment consisting of a monitoring server, and enhanced 3270 user interface, and an OMEGAMON AI for JVM monitoring agent.

Procedure

  1. Submit a job that performs the CREATE action.

    Copy and customize the job TKANSAM(KFJJMCM) to perform the CREATE action of Configuration Manager, then submit that job. The CREATE action creates a runtime environment definition library, rte_plib_hilev.RTEDEF, and populates it with an initial set of parameters.

    Edit the example job statement to match your site's standards for job name, class, and message class. Consider changing the example job name prefix, UID, to your TSO user ID.

    //UID#ZMCM JOB ,CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID
/*JOBPARM SYSAFF=<lpar>
//S1       EXEC PGM=KCIOMEGA,REGION=0M,DYNAMNBR=256
//STEPLIB  DD DISP=SHR,DSN=<tlib_hlq>.TKANMOD
//KCIFLOW  DD DISP=SHR,DSN=<tlib_hlq>.TKANCUS(KFJOMEGA)
//KCIVARS  DD *                                        
ACTION            CREATE
RTE_NAME          <rte_name>
RTE_PLIB_HILEV    <rte_plib_hilev>
/*

    Replace the placeholders in the example JCL with appropriate values:

    <lpar>
    Run Configuration Manager actions on the LPAR where you will start the runtime environment.
    <tlib_hlq>
    The high-level qualifiers of the target libraries.
    <rte_name>
    Runtime environment name, 1 - 8 characters.

    Configuration Manager uses this name for various purposes, including:

    • MVS member names
    • MVS data set name qualifiers
    • z/OS UNIX System Services directory name, all uppercase
    <rte_plib_hilev>
    The high-level qualifiers of the runtime environment definition library:

    rte_plib_hilev.RTEDEF

    Configuration Manager uses the values of RTE_NAME and RTE_PLIB_HILEV to set the default value of other parameters, such as RTE_HILEV and RTE_VSAM_HILEV, that are used for data set names. To avoid exceeding the z/OS 44-character limit for data set names, the combined length of RTE_NAME and RTE_PLIB_HILEV should not exceed 28 characters. For example, if RTE_NAME is 8 characters, then RTE_PLIB_HILEV should not exceed 20 characters.

    After running the job, check the KCIPRINT sysout data set.
  2. Edit the parameters in the rte_plib_hilev.RTEDEF library to configure an OMEGAMON AI for JVM agent.

    In the RTEDEF(rte_name) member, set the following parameters to Y:

    CONFIGURE_TEMS_KDS
    Configures a monitoring server (Tivoli® Enterprise Monitoring Server, or TEMS)
    CONFIGURE_E3270UI_KOB
    Configures an enhanced 3270 user interface address space
    CONFIGURE_JVM_KJJ
    Configures an OMEGAMON AI for JVM monitoring agent

    Set all of the other parameters to N.

    RTE_NAME                         <rte_name>
RTE_PLIB_HILEV                   <rte_plib_hilev>
RTE_SECURITY_USER_LOGON          NONE
RTE_SECURITY_FOLD_PASSWORD_FLAG  Y
RTE_SECURITY_CLASS               ""
RTE_X_SECURITY_EXIT_LIB          <rte_plib_hilev>.<rte_name>.SECEXITS                 
RTE_TEMS_NAME_NODEID             <rte_name>:TEMS
RTE_TEMS_TRANSPORT_MODE          HTTPS
RTE_COMM_PROTOCOLn               IPPIPE
RTE_TCP_HOST                     <sysiphostname> 
RTE_TCP_PORT_NUM                 1918
RTE_VTAM_APPLID_PREFIX           OM<sysclone>
RTE_STC_PREFIX                   OMEG
RTE_USS_RTEDIR                   "/var/rtehome"
CONFIGURE_TEMS_KDS               Y  * TEMS
CONFIGURE_E3270UI_KOB            Y  * Enhanced 3270                
CONFIGURE_CICS_KC5               N  * CICS TS                      
CONFIGURE_CICS_TG_KGW            N  * CICS TG                      
CONFIGURE_DB2_AGENT_KD5          N  * Db2                          
CONFIGURE_IMS_KI5                N  * IMS                          
CONFIGURE_JVM_KJJ                Y  * JVM                          
CONFIGURE_ZOS_KM5                N  * z/OS                         
CONFIGURE_MESSAGING_KMQ          N  * MQ                           
CONFIGURE_MESSAGING_KQI          N  * Integration Bus              
CONFIGURE_NETVIEW_KNA            N  * Netview                      
CONFIGURE_MFN_KN3                N  * Network                      
CONFIGURE_STORAGE_KS3            N  * Storage                      
CONFIGURE_OMEGAVIEW_KWO          N  * Integration Monitor          
CONFIGURE_ITCAMAD_KYN            N  * ITCAM for Applications       
CONFIGURE_ACM_KRN                N  * Advanced Catalog Mgmt        
CONFIGURE_ARD_KRH                N  * Advanced Rpt and Mgmt        
CONFIGURE_AAD_KRG                N  * Advanced Audit               
CONFIGURE_AAM_KRJ                N  * Advanced Alloc Mgmt     
CONFIGURE_ATAM_KRK               N  * Automated Tape Alloc    
CONFIGURE_ABR_KRV                N  * Advanced Backup and Rec 
CONFIGURE_ODP_KAY                N  * Data Provider

    Also in the RTEDEF(rte_name) member, set the following parameters to match your site-specific standards:

    RTE_STC_PREFIX
    1- to 4-character prefix of the started task names for this runtime environment. The value in the initial set of parameters is OMEG.
    RTE_VTAM_APPLID_PREFIX
    Prefix of the VTAM® applids in this runtime environment. For this minimal runtime environment, there is only one VTAM application: the enhanced 3270 user interface.

    Each VTAM application in a runtime environment has a corresponding parameter for the VTAM applid. The default values of these parameters are the value of RTE_VTAM_APPLID_PREFIX followed by an application-specific suffix.

    In the initial set of parameters created by the CREATE action, the value of RTE_VTAM_APPLID_PREFIX is OMxx, where xx is the value of the z/OS® static system symbol SYSCLONE. SYSCLONE is a 1- or 2-character shorthand notation for the system (LPAR) name. This value is one example of why you need to run Configuration Manager actions on the LPAR where you will start the runtime environment.

    If you use these values, then the default VTAM applid for the enhanced 3270 user interface is OMxxOBAP. For example, if the system (LPAR) name is ZOS1, then the VTAM applid is OMS1OBAP.

    RTE_USS_RTEDIR
    The path of the z/OS UNIX directory where you want Configuration Manager to write runtime files required by the started tasks.

    The TSO user ID that runs Configuration Manager jobs must have permission to write to this directory, otherwise the GENERATE action will fail.

    RTE_TCP_PORT_NUM
    The TCP/IP port number on which the monitoring server will listen.
    Tip: Later steps in this procedure describe how to activate VTAM resources and APF-authorize libraries. If you insert the parameter RTE_X_STC_INAPF_INCLUDE_FLAG Y in the RTEDEF(rte_name) member, then the started tasks include a member that performs these steps for you.
    In the RTEDEF(GBL$PARM) member, set the following parameters:
    GBL_USS_TKANJAR_PATH
    The z/OS UNIX path that the SMP/E installation jobs define using the ddname TKANJAR. This parameter is required when the runtime environment configures OMEGAMON AI for JVM.
    GBL_HFS_JAVA_DIR1
    The z/OS UNIX path of the Java™ home directory.
    GBL_DSN_CSF_SCSFMOD0
    This parameter is explicitly added in the GBL$PARM member that is generated after the CREATE action, as it is relevant for several security-related aspects of the product configuration (such as password encryption). If your installation does not use the Integrated Cryptographic Service Facility (ICSF), you can remove or comment out this parameter in your RTEDEF(GBL$PARM) or RTEDEF(GBL$lpar).
  3. Convert the hub monitoring server to a remote monitoring server.
    Edit the RTEDEF(KDS$PARM) or RTEDEF(KDS$lpar) member for the runtime environment.

    Set the following parameters:

    KDS_TEMS_TYPE
    Change from HUB to REMOTE.
    KDS_HUB_TEMS_NAME_NODEID
    Set to the value of RTE_TEMS_NAME_NODEID in the central hub runtime environment.
    KDS_HUB_TCP_PIPE_PORT_NUM
    Set to the value of RTE_TCP_PORT_NUM in the central hub runtime environment.
    KDS_HUB_TCP_HOST
    Set to the host name of the LPAR for the central hub runtime environment.
  4. Submit a job that performs the GENERATE action.
    The GENERATE action generates the runtime members for the runtime environment, including the started tasks.
    //UID#ZMCM JOB ,CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID
/*JOBPARM SYSAFF=<lpar>
//S1       EXEC PGM=KCIOMEGA,REGION=0M,DYNAMNBR=256   
//STEPLIB  DD DISP=SHR,DSN=<tlib_hlq>.TKANMOD
//KCIFLOW  DD DISP=SHR,DSN=<tlib_hlq>.TKANCUS(KFJOMEGA)
//KCIVARS  DD *                                        
ACTION            GENERATE   
RTE_NAME          <rte_name>
RTE_PLIB_HILEV    <rte_plib_hilev>
/*
    You have completed the steps that involve the configuration software. The remaining steps complete the configuration of the runtime environment outside of the configuration software.