Configuration Manager
IBM Z® Monitoring Configuration
Manager , also known as Monitoring Configuration Manager or Configuration Manager , is a tool that configures an OMEGAMON runtime environment from a set of parameters that you
specify.
PDF
Products supported by Configuration Manager
These products can be configured using Monitoring Configuration Manager , regardless of the product being part of a suite or pack offering or purchased as a standalone point product.
Introduction to Configuration Manager
IBM Z Monitoring Configuration Manager , also known as Monitoring Configuration Manager or Configuration Manager , is a tool that configures an OMEGAMON runtime environment from a set of parameters that you specify.
Comparison with PARMGEN
IBM Z Monitoring Configuration Manager evolved from PARMGEN. If you understand PARMGEN, then a comparison can help you to quickly understand Monitoring Configuration Manager .
Preparing to use Configuration Manager
Review prerequisites and other considerations before you start using Configuration Manager .
Defining the OMEGAMON subsystem to z/OS
Some OMEGAMON monitoring agents depend on the OMEGAMON subsystem. Before starting a runtime environment that contains any of these monitoring agents, you must define the OMEGAMON subsystem to z/OS.
Creating your first, minimal runtime environment
If you are a first-time user of IBM Z Monitoring Configuration Manager , creating a minimal runtime environment is a good place to start. This example consists of a z/OS agent, a monitoring server, and an enhanced 3270 user interface. You can logon to the enhanced 3270 user interface to view data from the z/OS agent.
Creating or updating a runtime environment
To create or update a runtime environment, you edit a set of parameters, and then you submit a job that performs the GENERATE action to generate runtime members from those parameters.
Batch interface
The JCL to run IBM Z Monitoring Configuration Manager is simple and concise. You specify an action, the name of the runtime environment on which you want to perform that action, and the high-level qualifiers of the data sets for that runtime environment.
Parameters
In general, IBM Z Monitoring Configuration Manager and PARMGEN use the same parameters with the same default values. In a few cases, Monitoring Configuration Manager introduces a new parameter or sets a different default value for an existing parameter.
Upgrade scenarios
This section describes how to add a new agent or product to an existing configuration RTEDEF library (that is, upgrade an existing RTEDEF) and mentions how to find more information on the Configuration Manager MIGRATE action to import existing legacy PARMGEN configuration settings.
Runtime environment definition (RTEDEF) library
A runtime environment definition is a set of parameters. Parameters are stored in a runtime environment definition (RTEDEF ) library. The set of parameters for each runtime environment is organized into several RTEDEF members.
Runtime members
The GENERATE action generates runtime members in locations (MVS™ data set names and z/OS UNIX System Services paths) that are specified by parameters.
Communication between monitoring components
In a typical topology, monitoring agents communicate with remote monitoring servers, and remote monitoring servers communicate with a single, central hub monitoring server.
Variables in parameter values
Many parameter values can optionally refer to variables.
Setting up security exits in your runtime environment
Security exits are required for your runtime environment. You can use the CREATE and MIGRATE actions to set up your security exits library, and use the GENERATE action to create the necessary runtime members.
Using override embed members in Configuration Manager
With Monitoring Configuration Manager , you can use override embed members to provide and maintain customization for your runtime environments.
Remote deployment scenario
In a remote deployment scenario, you must create a runtime environment on a specific LPAR (the configuration LPAR ), package the runtime environment data sets using the PACKAGE action, transfer the data sets to the remote target system (target LPAR ), and deploy or restore the packaged runtime environment data sets on the target LPAR using the DEPLOY action.
Using SMP/E target library copies
Use the Configuration Manager target copy feature to create one or more copies of your SMP/E target libraries, from which you can create or update your runtime environments.
Troubleshooting
Use these topics to troubleshoot issues with Monitoring Configuration Manager .
Messages
Use the information in these messages to help you diagnose and solve problems running Monitoring Configuration Manager jobs.