Db2 Tools for z/OS

OMEGAMON XE for Db2 PE: Set up just got easier! by Matthias Tschaffler

By CALENE JANACEK posted Wed February 03, 2021 01:07 PM


OMEAGMON XE for Db2 PE has streamlined the process for configuring the runtime environment. In September 2020, IBM delivered this enhancement for the Z Monitoring Suite.  The ISPF-driven configuration process that still exists, is called PARMGEN. The new feature, Configuration Manager, is a batch job driven process that uses standard JCL and various parameters to achieve the same results, faster and easier.  What may have taken many hours and steps with PARMGEN can now be achieved in minutes using Configuration Manager.  Initially, this feature was only available in the IBM Z Monitoring Suite.  But now, Configuration Manager is also available in the standalone OMPE XE for Db2 PE product. 

Configuration Manager versus PARMGEN

Configuration Manager evolved from PARMGEN so if you understand PARMGEN, then understanding Configuration Manager should not be an issue at all.  It is your choice to use either Configuration Manager or PARMGEN to configure runtime environments for OMEGAMON.  Both processes use the same parameters. 

A runtime environment (RTE) consists of different z/OS datasets, started tasks as well as z/OS UNIX files.  These are the files that are required to monitor different subsystems on a z/OS LPAR and these related members are collectively known as runtime members.  The main purpose of Configuration Manager is to generate runtime members using different OMEGAMON parameters.  This process is known as the GENERATE action.

Generating runtime members for a runtime environment involves modifying a set of parameters, then running one single Configuration Manager batch job.  The parameters that you use for this job are all stored in plain text.

Using Configuration Manager during Configuration

When using Configuration Manager there are no ISPF panels to navigate, this installation is a batch job only process.  The installation uses the same JCL for all actions that need to be performed.  Here is an example of the JCL:

There are three different ACTIONs that need to be performed to complete a configuration, CREATE, DISCOVER and GENERATE. To generate runtime members from parameters, you submit only one single job. To generate runtime members, you submit the same single job in all situations. 

Migrating Legacy PARMGEN Configurations

You can also use the MIGRATE action that allows a user to import legacy configurations into the Configuration Manager RTE definition dataset. 

MIGRATE supports legacy PARMGEN RTE’s with and without system variables, customized security exits,  as well as embed override members. 

The MIGRATE action supports the migration of one single RTE at a time.  It does not support migrating multiple legacy PARMGEN RTE’s into a single RTE definition dataset configuration. 

This new action is still driven in simple JCL like the original CREATE, DISCOVER and GENERATE. 

For more details and information: