How to: Connect agents on local RTE and agents on remote RTEs to the HUB TEMS

Edit online

Agents on different RTEs can be configured to report to the same HUB TEMS. This topic explains how to perform this task using PARMGEN.

Decide the primary TEMS, regardless if it is a Hub or a Remote TMES, that the agents connect to. If you enable the backup TEMS feature by changing the agent's Kpp_TEMS_BKUP1_* parameters, you must also decide the backup TEMS that the agents connect to.

Refer to the following configuration scenario among 3 RTEs in different LPARs to understand how to connect agents on different RTEs to the HUB TEMS. The LPARs are:

LPAR 1: RTE_NAME = SYSA (&sysname = SYSA; &sysplex = TESTPLEX; &sysiphostname = SYSA)
LPAR 2: RTE_NAME = SYSB (&sysname = SYSB; &sysplex = TESTPLEX; &sysiphostname = SYSB)
LPAR 3: RTE_NAME = SYSC (&sysname = SYSC; &sysplex = TESTPLEX; &sysiphostname = SYSC)

The components and configurations on each RTE are different:

SYSA RTE configures the following products:
- A Hub TEMS (KDS)
- OMEGAMON enhanced 3270 User Interface (KOB)
- OMEGAMON AI for Db2 (KD5)
- OMEGAMON for IMS (KI5)
- OMEGAMON AI for Networks (KN3)
KD5, KI5, and KN3 agents report directly to the local z/OS Hub TEMS via IPPIPE and SNA protocols.
Take the default values in PARMGEN for most of the following parameters in the LPAR RTE profile in WCONFIG. You can define most of these parameter values in option 1 (Set up/Refresh PARMGEN work environment -KCIJPCFG). The backup TEMS feature is not enabled on this RTE.
1. Specify common RTE parameters values during KCIJPCFG setup depending on preferred RTE scenario.
```
RTE_TEMS_CONFIGURED_FLAG     y                                          
RTE_TEMS_NAME_NODEID        "SYSA:CMS"                                  
 
```
2. Specify typical z/OS TEMS common parameters.
  - Specify the TEMS type on this RTE as HUB.
```
KDS_TEMS_TYPE               HUB
```
  - Specify the communication protocols in priority sequence to be used by the local TEMS to communicate with other ITM components such as another TEMS, Agents, TEPS, etc. Valid values are "IPPIPE", "IP", "SNA", "IP6PIPE", "IP6", "IPSPIPE", and "IP6SPIPE".
```
KDS_TEMS_COMM_PROTOCOL1           IPPIPE                                
KDS_TEMS_COMM_PROTOCOL2           SNA
 
```
  - Specify the protocol port number for the HUB TEMS, which must be used across the enterprise. Remote TEMS and Agents connecting to the Hub TEMS must use the same port numbers.
```
KDS_TEMS_TCP_PIPE_PORT_NUM  1918  * IP.PIPE
```
  - Specify the TEMS VTAM information. You can take default values for the KDS_TEMS_VTAM_APPL_GLB_BROKER and KDS_TEMS_VTAM_APPL_LLB_BROKER parameters, or use different values. The value CTDHDSLB is used across this scenario.
```
KDS_TEMS_VTAM_LU62_DLOGMOD        CANCTDCS                              
KDS_TEMS_VTAM_LU62_MODETAB        KDSMTAB1                              
KDS_TEMS_VTAM_NETID               USCACO01    
KDS_TEMS_VTAM_APPL_GLB_BROKER CTDHDSLB                          
KDS_TEMS_VTAM_APPL_LLB_BROKER CTDHDSLB                          
KDS_TEMS_VTAM_APPL_KDS_VTAMID CTDDSDS                           
KDS_TEMS_VTAM_APPL_MQ        CTDDSMQ      
 
```
3. Specify typical common agent parameters. Only OMEGAMON for Db2 (KD5) parameters are listed. Other agents have similar parameters.
  - Specify the communication protocols in priority sequence to be used to communicate with other ITM components such as the TEMS, agents, TEPS, etc. Valid values are "IPPIPE", "IP", "SNA", "IP6PIPE", "IP6", "IPSPIPE", and "IP6SPIPE".
```
KD5_AGT_COMM_PROTOCOL1            IPPIPE                                
KD5_AGT_COMM_PROTOCOL2            SNA      
 
```
  - Specify protocol port numbers for agent to connect to TEMS.
```
KD5_TEMS_TCP_PIPE_PORT_NUM  1918 * IP.PIPE
```
  - Specify values that describe the primary TEMS the agents connect to.
```
KD5_TEMS_LOCAL_CONNECT_FLAG       Y                                     
KD5_TEMS_NAME_NODEID        "SYSA:CMS"                             
 
```
  - Specify primary TEMS TCP/IP information and agent local TCP/IP information.
```
KD5_TEMS_TCP_HOST                 "SYSA"
KD5_AGT_TCP_HOST                  "SYSA" 
```
  - Specify primary TEMS VTAM information and agent's local VTAM and logon information.
```
KD5_TEMS_VTAM_LU62_DLOGMOD        CANCTDCS                              
KD5_TEMS_VTAM_LU62_MODETAB        KDSMTAB1                              
KD5_TEMS_VTAM_NETID               USCACO01                        
KD5_TEMS_VTAM_APPL_LLB_BROKER CTDHDSLB  
KD5_AGT_VTAM_NODE            CTDD5N         
 
```
  - Specify agent's APPLIDs.
```
KD5_AGT_VTAM_APPL_OPERATOR   CTDD5OR                            
KD5_AGT_VTAM_APPL_KD5INVPO   CTDD5VP                            
KD5_AGT_VTAM_APPL_NCS        CTDD5NC                            
KD5_AGT_VTAM_APPL_AA         CTDD5AA            
 
```
  Based on the customizations, the xKANPARU(KppENV) runtime members reflect the KDE_TRANSPORT parameter and CT_CMSLIST parameter based on the specified values, in the preferred order of the protocols, which is IPPIPE first and then try SNA if connection by IP wire is not available.
SYSB RTE configures the following products:
- A local z/OS Remote TEMS (KDS) reporting to the z/OS Hub on SYSA
- OMEGAMON AI for Db2 (KD5)
- OMEGAMON for IMS (KI5)
- OMEGAMON AI for Networks (KN3)
No OMEGAMON enhanced 3270 User Interface (KOB) is configured. KD5, KI5, and KN3 agents report to the local z/OS Remote TEMS via IPPIPE and SNA protocols, not directly to the Hub to reduce the burden on the SYSA Hub TEMS.
Take the default values in PARMGEN for most of the following parameters in the LPAR RTE profile in WCONFIG. You can define most of these parameter values in option 1 (Set up/Refresh PARMGEN work environment -KCIJPCFG).
1. Specify common RTE parameters values during KCIJPCFG set-up depending on preferred RTE scenario.
```
RTE_TEMS_CONFIGURED_FLAG     y                                          
RTE_TEMS_NAME_NODEID        "SYSB:CMS"                                  
 
```
2. Specify typical z/OS TEMS common parameters.
  - Specify the TEMS type on this RTE as REMOTE.
```
KDS_TEMS_TYPE               REMOTE
```
  - Specify the communication protocols in priority sequence to be used by the local TEMS to communicate with other ITM components such as another TEMS, agents, TEPS, etc. Valid values are "IPPIPE", "IP", "SNA", "IP6PIPE", "IP6", "IPSPIPE", and "IP6SPIPE".
```
KDS_TEMS_COMM_PROTOCOL1           IPPIPE                                
KDS_TEMS_COMM_PROTOCOL2           SNA
 
```
  - Specify the protocol port number for the remote TEMS same as the port number that is used by the Hub TEMS.
```
KDS_TEMS_TCP_PIPE_PORT_NUM  1918  * IP.PIPE
```
  - Specify the TEMS VTAM information.
```
KDS_TEMS_VTAM_LU62_DLOGMOD        CANCTDCS                              
KDS_TEMS_VTAM_LU62_MODETAB        KDSMTAB1                              
KDS_TEMS_VTAM_NETID               USCACO01                        
KDS_TEMS_VTAM_APPL_GLB_BROKER CTDHSDLB                          
KDS_TEMS_VTAM_APPL_LLB_BROKER CTDDSLB                           
KDS_TEMS_VTAM_APPL_KDS_VTAMID CTDDSDS                           
KDS_TEMS_VTAM_APPL_MQ        CTDDSMQ               
 
```
  - Specify its Hub TEMS values. These parameters are key settings for the Remote TEMS that tell PARMGEN where the HUB TEMS is and how to set up the RTEMS KDSENV and KDCSSITE runtime members. In this scenario, you must specify the values of the Hub TEMS on RTE SYSA.
```
KDS_HUB_TEMS_NAME_NODEID        "SYSA:CMS"    * Hub RTE_TEMS_NAME_NODEID   
KDS_HUB_TCP_HOST                "SYSA"    * Hub KDS_TEMS_TCP_HOST     
KDS_HUB_TCP_PIPE_PORT_NUM       "1918"    * Hub KDS_TEMS_TCP_PIPE_PORT_NUM 
KDS_HUB_VTAM_APPL_GLB_BROKER    "CTDHDSLB"   * Hub KDS_TEMS_VTAM_APPL_GLB_BROKER
KDS_HUB_VTAM_NETID              "USCACO01"    * Hub KDS_TEMS_VTAM_NETID         
 
```
3. Specify typical common agent parameters. Only OMEGAMON for Db2 (KD5) parameters are listed. Other agents have similar parameters.
  - Specify the communication protocols in priority sequence to be used to communicate with other ITM components such as the TEMS, agents, TEPS, etc. Valid values are "IPPIPE", "IP", "SNA", "IP6PIPE", "IP6", "IPSPIPE", and "IP6SPIPE".
```
KD5_AGT_COMM_PROTOCOL1            IPPIPE                                
KD5_AGT_COMM_PROTOCOL2            SNA      
 
```
  - Specify protocol port numbers for agent to connect to TEMS.
```
KD5_TEMS_TCP_PIPE_PORT_NUM  1918 * IP.PIPE
```
  - Specify values that describe the primary TEMS the agents connect to.
```
KD5_TEMS_LOCAL_CONNECT_FLAG       Y                                     
KD5_TEMS_NAME_NODEID        "SYSB:CMS"                             
 
```
  - Specify primary TEMS TCP/IP information and agent local TCP/IP information.
```
KD5_TEMS_TCP_HOST                 "SYSB"
KD5_AGT_TCP_HOST                  "SYSB" 
```
  - Specify primary TEMS VTAM information and agent's local VTAM and logon information.
```
KD5_TEMS_VTAM_LU62_DLOGMOD        CANCTDCS                              
KD5_TEMS_VTAM_LU62_MODETAB        KDSMTAB1                              
KD5_TEMS_VTAM_NETID               USCACO01                        
KD5_TEMS_VTAM_APPL_LLB_BROKER CTDDSLB         
KD5_AGT_VTAM_NODE            CTDD5N      
 
```
  - Specify agent's APPLIDs.
```
KD5_AGT_VTAM_APPL_OPERATOR   CTDD5OR                            
KD5_AGT_VTAM_APPL_KD5INVPO   CTDD5VP                            
KD5_AGT_VTAM_APPL_NCS        CTDD5NC                            
KD5_AGT_VTAM_APPL_AA         CTDD5AA  
 
```
4. You can enable the backup TEMS feature for the agents to report to the z/OS Hub TEMS on RTE SYSA in case the z/OS RTEMS local on RTE SYSB gets an ABEND. In this scenario, uncomment out the following parameters and specify the values of the Hub TEMS, which become the second entries in CT_CMSLIST for RKANPARU(KD5ENV).
```
KD5_TEMS_BKUP1_NAME_NODEID      "SYSA:CMS"  
KD5_TEMS_BKUP1_TCP_HOST         "SYSA"       
KD5_TEMS_BKUP1_VTAM_LU62_DLOGMOD  CANCTDCS
KD5_TEMS_BKUP1_VTAM_APPL_LLB_BKR  CTDHDSLB
KD5_TEMS_BKUP1_VTAM_NETID         USCACO01
 
```
  Based on the customizations, the xKANPARU(KppENV) runtime members reflect the KDE_TRANSPORT parameter and CT_CMSLIST parameter based on the specified values, in the preferred order of the protocols, which is IPPIPE first and then try SNA if connection by IP wire is not available. The KD5 agent is configured to report to a backup TEMS, which in this scenario is the Hub TEMS on SYSA, if the local RTEMS on SYSB is not running.
SYSC RTE configures the following products:
- OMEGAMON AI for Db2 (KD5)
- OMEGAMON for IMS (KI5)
- OMEGAMON AI for Networks (KN3)
No TEMS (KDS) or OMEGAMON enhanced 3270 User Interface (KOB) is configured. KD5, KI5, and KN3 Agents report to z/OS Hub TEMS configured in the other LPAR (RTE_NAME = SYSA) via IPPIPE and SNA protocols.
Take the default values in PARMGEN for most of the following parameters in the LPAR RTE profile in WCONFIG. You can enable the backup TEMS feature on this RTE to have the agents report to the HUB TEMS on SYSA or the RTEMS on SYSB. However, in this scenario the backup TEMS feature is not enabled.
1. Specify common RTE parameters values during KCIJPCFG set-up depending on preferred RTE scenario. In this scenario, no TEMS is configured in the RTE.
```
RTE_TEMS_CONFIGURED_FLAG     N                                          
RTE_TEMS_NAME_NODEID        ""                            
 
```
  When RTE_TEMS_CONFIGURED_FLAG=N, PARMGEN ignores the KDS_* parameters in the profile.
2. Specify typical common agent parameters. Only OMEGAMON for Db2 (KD5) parameters are listed. Other agents have similar parameters.
  - Specify the communication protocols in priority sequence to be used to communicate with other ITM components such as the TEMS, agents, TEPS, etc. Valid values are "IPPIPE", "IP", "SNA", "IP6PIPE", "IP6", "IPSPIPE", and "IP6SPIPE".
```
KD5_AGT_COMM_PROTOCOL1            IPPIPE                                
KD5_AGT_COMM_PROTOCOL2            SNA      
 
```
  - Specify protocol port numbers for agent to connect to TEMS.
```
KD5_TEMS_TCP_PIPE_PORT_NUM  1918 * IP.PIPE
```
  - Specify values that describe the primary TEMS the agents connect to. If the primary TEMS that this agent connects to is configured on another RTE, or running on a non-z/OS platform, specify 'N' to the KD5_TEMS_LOCAL_CONNECT_FLAG parameter, then customize the KD5_TEMS_* parameters accordingly to point to the non-local primary TEMS.
```
KD5_TEMS_LOCAL_CONNECT_FLAG       N                                     
KD5_TEMS_NAME_NODEID        "SYSA:CMS"                               
 
```
  - Specify primary TEMS TCP/IP information and agent local TCP/IP information.
```
KD5_TEMS_TCP_HOST                 "SYSA"
KD5_AGT_TCP_HOST                  "SYSC" 
```
  - Specify primary TEMS VTAM information and agent's local VTAM and logon information.
```
KD5_TEMS_VTAM_LU62_DLOGMOD        CANCTDCS                              
KD5_TEMS_VTAM_LU62_MODETAB        KDSMTAB1                              
KD5_TEMS_VTAM_NETID               USCACO01                        
KD5_TEMS_VTAM_APPL_LLB_BROKER CTDHDSLB         
KD5_AGT_VTAM_NODE            CTDD5N      
 
```
  - Specify agent's APPLIDs.
```
KD5_AGT_VTAM_APPL_OPERATOR   CTDD5OR                            
KD5_AGT_VTAM_APPL_KD5INVPO   CTDD5VP                            
KD5_AGT_VTAM_APPL_NCS        CTDD5NC                            
KD5_AGT_VTAM_APPL_AA         CTDD5AA     
 
```
  Based on the customizations, the xKANPARU(KppENV) runtime members reflect the KDE_TRANSPORT parameter and CT_CMSLIST parameter based on the specified values, in the preferred order of the protocols, which is IPPIPE first and then try SNA if connection by IP wire is not available.