How to: Use a shared procedure for multiple monitoring servers

Edit online

You can configure your environment to use the same started task procedure for multiple monitoring servers across different systems in the sysplex. This topic explains how to perform this task using either Configuration Manager or PARMGEN.

Before you begin

A Tivoli Enterprise Monitoring Server (monitoring server) can be configured as one of several types: hub, high-availability hub, remote. By default, the started task procedure for each monitoring server is created to be run as a separate task. The generated procedure is different for each monitoring server by type; for example, the name of the runtime environment, the data set names, and the required DD statements can all vary by monitoring server type.

This default configuration is not suitable for some sites that might have any of the following requirements:

The SYS1.PROCLIB (or equivalent procedure library) must be shared across all the systems in the sysplex.
Only a single, specific agent procedure is allowed (that is, only one procedure per agent).

To satisfy such requirements, you must use a procedure that is the same for all monitoring servers across all systems; it must have the same name, the same contents, and reference the same data sets. To accomplish this setup, you can configure your environment to generate a shared procedure.

This topic explains how to generate a shared procedure for use with multiple monitoring servers using either Configuration Manager or PARMGEN.

About this task

This task requires the use of the following parameter:

KDS_TEMS_PROC_SHARED: This flag specifies if the monitoring server procedure can be shared among different systems in the sysplex. When the flag is set to Y, the same procedure is generated for a hub monitoring server or a remote monitoring server, and the procedure can be copied to a shared SYS1.PROCLIB. The default value for this parameter is N.

The use of system variables is also required.

Use the following steps to create a shared procedure for use with multiple monitoring servers.

Procedure

Set the flag parameter that enables the generation of a monitoring server procedure that can be shared:
- Using Configuration Manager: Add parameter KDS_TEMS_PROC_SHARED set to Y to RTEDEF(KDS$PARM) or RTEDEF(KDS$lpar), and then run the GENERATE action.
- Using PARMGEN: In WCONFIG(rte_name), set parameter KDS_TEMS_PROC_SHARED to Y, and then run the $PARSE job.
  Note: For more information about making these changes using PARMGEN, see Scenario SMPE03: Applying SMP/E maintenance with new configuration changes to an existing RTE and overriding the IBM-supplied configuration defaults.
Review the generated procedure, and proceed as appropriate:
- If you use system variables in your runtime environment configuration, including a system variable for RTE_NAME, the generated procedure is ready to be shared.
- If you do not use system variables in your runtime environment configuration, you can use the generated procedure as a shared procedure if there is a variable in your PARMLIB system symbol list that corresponds to your RTE_NAME values across all the LPARs in the sysplex. To enable the procedure to be shared, update the following lines:
```
//TEMS PROC RGN=0M,TIM=1440,MEMLIM=NOLIMIT,          
//          SYS=&SYSNAME.,                                   
```
  In this example, &SYSNAME. resolves to an RTE_NAME on each system where it is started.
Copy the shared started task procedure to your system library.