FTU Task 4: Configure a monitoring system on z/OS with a hub monitoring server

In this task, you will configure a simple runtime environment (RTE) with a hub monitoring server, one monitoring agent, and the Enhanced 3270 user interface.

Before you begin

Ensure that you have fully completed the following tasks:
  • FTU Task 1 so that you understand the terminology used in this task and subsequent tasks.
  • FTU Task 2 so that the monitoring products are applied in SMP/E target libraries.
  • FTU Task 3 so that the file system for storing SDA data is available on your z/OS® UNIX System Services system and OMEGAMON® programs are authorized.

About this task

The purpose of this first configuration task is to quickly create a working RTE where you can run the monitoring system after finishing this task. To accomplish this task, we will:
  • Use a sharing type of RTE in which SMP/E libraries are concatenated directly in the runtime JCL. Don’t worry if this isn’t the RTE type you want to use in production. We will be changing the RTE type in a subsequent FTU task.
  • Limit this initial configuration to just one monitoring agent even if you installed many more agents than that into your target libraries. Let’s keep it simple for now. We’ll add more agents to the RTE in a subsequent FTU task.
Follow the step-by-step instructions in Scenario QCF10: Configuring a sharing-with-SMP/E runtime environment with a hub monitoring server to configure this RTE. Make the following adjustments as you go through the scenario:
In the Setting up the work environment step
In the Include Products in this PARMGEN RTE panel, all products that were installed into your target libraries are preselected for configuration. We do not want them all at this time. For this initial configuration, we want only the following components:
  • KDS Tivoli® Enterprise Monitoring Server V6.3.0
  • KM5 OMEGAMON for z/OS V5.3.0
  • OMEGAMON Enhanced 3270 User Interface V7.3.0
Remove the slash in front of all other components to deselect them from the configuration.

Our choice for the one agent to configure first in this RTE is OMEGAMON for z/OS (the agent whose product code is KM5). If you did not install KM5 into your SMP/E target libraries, then it won’t be listed here as an available selection.

If you do not have KM5, our next recommendation would be OMEGAMON for CICS (KC5). If you did not install either of these agents, then choose any one of the agents you did install and remember your choice.

Note: This guide assumes you are configuring KM5 as the agent. If that’s not the case, substitute the KM5 product code in the scenarios with the code of the agent you’ve selected. Be aware that you may have to complete some additional prerequisite steps including program authorization and addition post configuration steps for the agent you choose. If you install a different agent, check technote Preinstallation Requirements and Instructions, the Program Directory, and the Planning and Configuration Guide for your agent or agents.
In the Customizing the configuration profiles step
You need to make a few adjustments to customize the profiles for your site.

Pre-populate the parameters in the configuration profiles by running the KCIJPDLn jobs. For more information about the KCIJPDLn jobs, see Preparing the configuration profiles by running the KCIJPDLn jobs, PARMGEN z/OS DLA utility jobs and commands, and The parameters that can be auto-discovered by the KCIJPDLA job.

In the RTE configuration profile, at a minimum you must edit the RTE_USS_RTEDIR parameter to specify the path for the z/OS UNIX directory where the self-describing agent data is stored. Review the Customizing the runtime environment configuration profile to see if you have to make additional changes.

In the global configuration profile, you must provide a site-appropriate value for the GBL_HFS_JAVA_DIR1 parameter. You must also edit the value for load library GBL_DSN_CSF_SCSFMOD0 parameter and any of the product-specific parameters listed in Customizing the global configuration profile as appropriate.

In the Completing the setup of the environment step
Several of the jobs that you submit to complete the setup require authorization, including those that APF-authorize the SMP/E target libraries and those that add the VTAM® definitions for the started tasks to VTAMLST. Make sure that you have the proper authorization to submit these jobs, or have someone with the proper authority submit them.

Additional steps may be required that can’t be completed in the PARMGEN workflow tool. That should not be the case for FTU Task 4 if you installed only the monitoring server, the Enhanced 3270 user interface, and OMEGAMON for z/OS. Still, you should review the topics in Completing the configuration outside the configuration software.