AIOps: Monitoring and Observability - Group home

IBM Z Monitoring Configuration Manager support for Advanced Storage monitoring agents is here! by Egle Barusauskiene and Matthias Tschaffler

With PTFs UJ09334 (APAR OA63566)  and UJ09749 (APAR OA64006), IBM Z® Monitoring Configuration Manager now supports all Advanced Storage monitoring agents, namely:

    (1) IBM Tivoli Advanced Allocation Management for z/OS 3.3 (parameter prefix KRJ, configuration guide)
    (2) IBM Tivoli Automated Tape Allocation Manager for z/OS 3.3 (KRK, configuration guide available soon, current documentation)
    (3) IBM Tivoli Advanced Backup and Recovery for z/OS 2.4 (KRV, configuration guide)
    (4) IBM Tivoli Advanced Catalog Management for z/OS 2.6 (KRN, configuration guide)
    (5) IBM Tivoli Advanced Reporting and Management for DFSMShsm 2.6 (KRH, configuration guide)
    (6) IBM Tivoli Advanced Audit for DFSMShsm 2.6 (KRG, configuration guide)

As a result of this delivery, Configuration Manager can now be used to configure the same set of products that are currently supported by PARMGEN.

In the following, we will cover a few Configuration Manager ACTIONs for the Advanced Storage monitoring agent configuration in detail.

If you have an SMP/e environment with all Advanced Storage monitoring agent FMIDs installed, and you are creating a new RTE with Configuration Manager, running the CREATE action will create an RTE_NAME member in the RTEDEF library with storage agents' configure flags set to Y:

    CONFIGURE_AAM_KRJ                Y
    CONFIGURE_ATAM_KRK               Y
    CONFIGURE_ABR_KRV                Y
    CONFIGURE_ACM_KRN                Y
    CONFIGURE_ARD_KRH                Y
    CONFIGURE_AAD_KRG                Y

If any of the agents is not installed, then the corresponding flag will be set to N.

Like any other product, all Advanced Storage agents have corresponding configuration members Kpp$PARM or Kpp$lpar (where Kpp stands for KRJ, KRK, KRV, KRN, KRH and KRG) created in the RTEDEF data set, allowing each agent to be customized separately.

When configuring Advanced Storage agents, it is important to enable embed overrides. If you are working with an existing RTE that does not have embed overrides enabled, you would need to rerun the CREATE action with the parameter KFJ_USE_EMBEDS set to Y. This will create the override members for the agents, such as:
KRJ$SSTn, KRK$SSTn, KRV$SSTn, KRN$SSTn, KRH$SSTn, KRG$SSTn (n = 1-3) in a data set rHilev.rteName.EMBEDS. This data set needs to be referenced in the RTEDEF(rte_name) member by adding parameter RTE_X_OVERRIDE_EMBEDS_LIB and setting the value accordingly:


If you are creating a new RTE, then run the CREATE action with embed overrides flag on its first run in KCIVARS DD:


The same EMBEDS data set is created as well as the appropriate entry for RTE_X_OVERRIDE_EMBEDS_LIB in RTEDEF(rte_name); that is, no manual update is needed.

Kpp$SST1 - the most important embed override member - is used to add a STEPLIB DD override for each agent's started task that is generated with the GENERATE action. It adds the respective Advanced Storage base product library reference. For each agent, this base product library is different:


These DD overrides are added automatically, once embed overrides are enabled in general. You can add as many DD statement overrides in Kpp$SST1 as you need. Other standard override members Kpp$SST2 (used for RKANMODL) and Kpp$SST3 (used for additional overrides) are also created in the EMBEDS library and are available for customization.

If you are a current PARMGEN user and have Advanced Storage agents configured on your system, the use of the MIGRATE action fully supports migrating your agent setup from a PARMGEN RTE to a Configuration Manager RTE as well.

Finally, PTFs UJ09334 and UJ09749 also enable PDS V2 for all six agents in both configuration methods - Configuration Manager and PARMGEN. PDS V2 for new RTEs is enabled by default. PDS V2 can be controlled for each agent separately, and its values customized, modifying the following parameters in RTEDEF data set members Kpp$PARM or Kpp$lpar:


In summary, we have shown how configuring Advanced Storage agents complies with the simplicity of Configuration Manager method, requiring only a minimal intervention.