Overview of configuration parameters

The OMEGAMON monitoring agents use parameters for setting and storing configuration values. The value of these parameters can be set using the new PARMGEN configuration method.

The PARMGEN configuration method uses a runtime environment based approach to configuration. With PARMGEN, you edit a comprehensive list of parameters to configure all the installed products and components in a runtime environment. You then submit a series of jobs to create a complete runtime environment with the parameter values you specified. You can also use the PARMGEN workflow generator, which steps you through the configuration process.

If you have used only the Configuration Tool (ICAT) to configure OMEGAMON agents, you must migrate your Configuration Tool settings to PARMGEN. To generate the batch parameter deck needed for migration, see the PGN05 scenario in the Scenarios and How tos section in the IBM Tivoli OMEGAMON and Tivoli Management Services on z/OS Shared Documentation.

Some parameters, such as those used by runtime environments and the Tivoli® Enterprise Monitoring Server, are common to all the OMEGAMON agents. Other parameters are specific to a particular agent. This section is a reference for parameters specific to the OMEGAMON for z/OS monitoring agent. It provides the following information for each parameter:
  • A description of the parameter
  • Whether the parameter is required or optional
  • Where the value for the parameter is stored in the runtime libraries, the name of the parameter in the libraries, and its default and permissible values
  • Related parameters.
The parameter descriptions in this reference are organized alphabetically, by the parameter names used in the PARMGEN configuration method. For a list of the parameters as organized in the PARMGEN configuration profile, see Table 1.
Note: Some parameters described in this reference include n or nn in their names. These are not the actual names of these parameters as you will see them in the configuration profile. The n or nn means that you can have multiple instances of this parameter in your configuration profile. For example, you will most likely have multiple instances of the KM2_HIST_DSTOR_STORCLASn because you can have up to 7 SMS storage classes. Likewise, you would have multiple instances of the KM2_NONSTDn_DSN, KM2_NONSTDn_MBR, KM2_NONSTDn_PARM values if you defined several nonstandard parameters. If you cannot find a parameter by searching on its full name, try searching on a part of the name, omitting the numbers that define that instance.

This reference information is intended to be used in connection with the Configuring section in the IBM Tivoli OMEGAMON and Tivoli Management Services on z/OS Shared Documentation, in which the PARMGEN configuration method is described. Descriptions of the parameters that define a runtime environment and configure the shared Tivoli Management Services components in the runtime environment are found in the the Reference section in the IBM Tivoli OMEGAMON and Tivoli Management Services on z/OS Shared Documentation.