KM5 parameters
Use KM5 parameters to define Sysplex-level entities, assign a current runtime environment to a Sysplex, install product-specific data on the Tivoli Enterprise Monitoring Server, and register the monitoring agent in the Tivoli Enterprise Monitoring Server address space.
You can also use KM5 parameters to configure the persistent data store for OMEGAMON AI for z/OS historical data and allocate the data sets to store the Sysplex-level and system-level data. KM5 parameters enable features such as event-forwarding, use of RMF data, and Netview security validation.
The parameter descriptions in this section are presented alphabetically, but Table 1 lists the parameters in the order they appear in the configuration profile ($CFG$IBM, or your rte_name) file.
| PARMLIB classification | Parameters in this group |
|---|---|
| Values that describe the Agent | KM5_AGT_CONFIGURATION_MODE |
| The TEMS name that the Agent is running in | KM5_AGT_TEMS_NAME_NODEID |
| Write Sysplex proxy message to the MVS™ console | KM5_KDS_KOSWTO_FLAG |
| ENQPlex and Sysplex RTE assignment | |
| Sysplex Persistent Datastore high-level qualifier | |
| (Optional) Started task names for MIM support | KM5_MIM_STCn |
| Sysplex RMF™ setting | KM5_RMF_DDS_COLLECTION |
| Use SYSPLEX name in Managed Systems list | KM5_SYSPLEX_KDS_KOSPLEXNAME_FLAG |
| (Optional) Persistent datastore table space allocation overrides | |
| Take Action commands security options | KM5_SECURITY_ACTION_CLASS |
| OMEGAMON AI for z/OS to monitor Cryptographic Services | |
| Additional OMEGAMON AI for z/OS settings | |
| Near-Term History parameters |