Defining multiple runtime environments in an RTEDEF library

You can define one runtime environment per RTEDEF library or, as described here, you can define multiple runtime environments in a single RTEDEF library.

About this task

For each runtime environment that you want to define, you create a corresponding RTEDEF(rte_name) member. To cater for LPAR-specific parameter differences between runtime environments, you create LPAR-specific RTEDEF members.

The simple example presented here defines two runtime environments on different LPARs:

• A runtime environment with a hub monitoring server and an enhanced 3270 user interface, but no monitoring agents.
• A runtime environment with a remote monitoring server and a z/OS® monitoring agent.

The following diagram shows the significant RTEDEF members and their parameters for this example:

In the following procedure, replace the example names with names appropriate for your site:

• Replace the host name zos1 with the host name of the LPAR where you will run the hub monitoring server.
• Replace the LPAR names ZOS1 and ZOS2 with the names of LPARs at your site.
• Use RTE names that match your site naming conventions.

1. Use the CREATE action to create an initial set of parameters in a new RTEDEF library.

   Example JCL:

   //UID#ZMCM JOB ,CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID
   /*JOBPARM SYSAFF=ZOS1  1 
   //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          RTEZOS1  2 
   RTE_PLIB_HILEV    TSOUID.MONSUITE
   /*

    1 

   Run this job on the LPAR where you will run the hub monitoring server, ZOS1.

    2 

   Specify the RTE_NAME that you want to use for the runtime environment with the hub monitoring server. For example, RTEZOS1: the prefix RTE, followed by the LPAR name. You are free to use your own naming convention: for example, there is no requirement for the value to begin with RTE or to end with the LPAR name.

2. Edit the RTEDEF(RTEZOS1) member to configure a monitoring server and an enhanced 3270 user interface.

   Set the following parameters to Y:

   • CONFIGURE_TEMS_KDS to configure a monitoring server
   • CONFIGURE_E3270UI_KOB to configure an enhanced 3270 user interface

   Either delete all other CONFIGURE_* parameters or set them to N.

   Review the following parameter values and, if necessary, change them to match your site requirements:

   • RTE_TEMS_NAME_NODEID
   • RTE_TCP_PORT_NUM
3. Create an RTEDEF(KDS$ZOS1) member.

   Set a single parameter in this member:

   • KDS_TEMS_TYPE HUB

   Strictly speaking, this member is unnecessary, because HUB is the default value of KDS_TEMS_TYPE. However, creating this member serves as a reminder that the runtime environment on this LPAR contains a hub monitoring server. You will also need this member if you decide later to further configure the hub: for example, to make it a high-availability hub (KDS_TEMS_HA_TYPE HA).

   You have completed the definition of the runtime environment for the hub.

4. Run another job that performs a CREATE action, this time for the LPAR where you will run the remote monitoring server.

   Example JCL:

   //UID#ZMCM JOB ,CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID
   /*JOBPARM SYSAFF=ZOS2  1 
   //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          RTEZOS2  2 
   RTE_PLIB_HILEV    TSOUID.MONSUITE
   /*

    1 

   Run this job on the LPAR where you will run the remote monitoring server, ZOS2.

    2 

   Specify the RTE_NAME that you want to use for the runtime environment with the remote monitoring server. For example, RTEZOS2.

5. Edit the new RTEDEF(RTEZOS2) member to configure a monitoring server and a z/OS monitoring agent.

   Set the following parameters to Y:

   • CONFIGURE_TEMS_KDS to configure a monitoring server
   • CONFIGURE_ZOS_KM5 to configure a z/OS monitoring agent

   Either delete other CONFIGURE_* parameters or set them to N.

6. Create an RTEDEF(KDS$ZOS2) member.

   Set the following parameters in the member:

   KDS_TEMS_TYPE

   Set to REMOTE.

   KDS_HUB_TEMS_NAME_NODEID

   Set to the value of RTE_TEMS_NAME_NODEID in the hub runtime environment.

   KDS_HUB_TCP_PIPE_PORT_NUM

   Set to the value of RTE_TCP_PORT_NUM in the hub runtime environment.

   KDS_HUB_TCP_HOST

   Set to the host name of the LPAR for the hub runtime environment.

7. Optionally, delete the RTEDEF(KDS$PARM) member.

   The KDS$PARM member created by the CREATE action contains only one parameter, KDS_TEMS_TYPE. The value of KDS_TEMS_TYPE in the LPAR-specific members takes precedence over the value in KDS$PARM. So the KDS$PARM member is, effectively, redundant.

   You have completed the definition of the runtime environment for the remote monitoring server.

8. Use the GENERATE action to create runtime members for the hub runtime environment.

   Example JCL:

   //UID#ZMCM JOB ,CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID
   /*JOBPARM SYSAFF=ZOS1  1 
   //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          RTEZOS1  2 
   RTE_PLIB_HILEV    TSOUID.MONSUITE
   /*

    1 

   Run this job on the LPAR where you will run the hub, ZOS1.

    2 

   Specify an RTE_NAME value to match the RTEDEF(RTEZOS1) member for the hub runtime environment.

9. Use the GENERATE action to create runtime members for the remote monitoring server runtime environment.

   Reuse the JCL from the previous step, with the following changes:

    1 

   Run the job on the LPAR where you will run the remote monitoring server, ZOS2.

    2 

   Specify the corresponding RTE_NAME for that runtime environment, RTEZOS2.