Scenario QCF02: Configuring a full RTE with a static hub and variables enabled

If your site does not meet the requirements for a high-availability hub monitoring server, and you want to configure a hub on z/OS, configure a static hub. You can configure other products in the same runtime environment (RTE) as a static hub, and you can also enable system variables in the same runtime environment. You can use an IBM-provided model to create the RTE and do minimal customization to get up and running, or create the RTE from scratch and customize to your exact requirements.

Before you begin

If you intend to enable the self-describing agent feature on the monitoring server, or to configure any products that require a z/OS® UNIX System Services file system, make sure that make sure that the required Hierarchical File System (HFS) or z/OS File System has been created or set aside and that it is mounted before you begin configuration. The file system must have access to a Java™ runtime environment running under IBM®'s 31-bit or 64-bit Java SDK Version 5 (or higher) on an HFS or zFS file system.

About this task

This scenario creates a full (RTE) with variables enabled. The RTE comprises a z/OS-based static hub monitoring server, OMEGAMON monitoring agents, and the OMEGAMON enhanced 3270 user interface. For this scenario, you use IBM-provided RTE template $MDLHFV. You can also create the RTE from scratch.

This scenario involves completing five main steps using the configuration software:

  1. Defining the new RTE.
  2. Setting up PARMGEN work environment for the runtime environment
  3. Customizing the configuration profiles
  4. Creating the runtime members and jobs
  5. Submitting batch jobs to complete the RTE setup
After you complete these steps, you complete any configuration steps required outside the configuration software and start the products.