Since PTF UJ95574 (APAR OA66051) you may have noticed a new job output DD in IBM Z Monitoring Configuration Manager, called Exclude report - EXCLRPT. In this blog, I’m going to explain what it is, how it works and how you can benefit from it.

Background

When GENERATE action is run, one of the workflows in the background copies prepared runtime members from WK* to RK* libraries. While some members are always copied and replaced, others might contain custom configurations and therefore should not be refreshed. Some members are always excluded by default (using IBM-provided exclude list), others can be added to the exclude list by user. EXCLRPT adds more transparency – with a quick glance, you can easily see what’s been excluded and where.

Use cases

I’m going to review three use cases:

1. GENERATE without user excludes (default)
2. GENERATE with user excludes
3. GENERATE with duplicate excludes

For the examples in this blog, SMP/E environment with all OMEGAMON products is used and all products are configured in the RTE.

The exclude report provides the status of excluded members for the following libraries:

• RKANCMDU
• RKANPARU
• RKANSAMU
• RKD2PAR
• RKD2PRF
• RKD2SAM

At least one excluded member must be found in the RK* data set for the respective section to be included in the report.

Use case 1: GENERATE without user excludes

Let’s imagine we have an existing RTE and we re-run GENERATE action for it. When the job completes, find the job output and use ? to list job output data sets. You will notice EXCLRPT printed out:

This EXCLUDE report prints members in their corresponding data sets that are excluded by default, indicated by “default” note on the right side of the table. That means, if these members were manually edited, they won’t be refreshed when GENERATE action is run. There is also a couple of members that are always regenerated in the process and not impacted by exclude rules, they are marked with **.

Use case 2: GENERATE with user excludes

Let’s add some user excludes and run GENERATE action again. User excludes are added by editing EMBEDS data set member KCI$XW2R:

In this example, I’m going to add members from different data sets (RKANSAMU, RKANPARU, RKD2PRF), using different ways to specify them, and run GENERATE:

EXCLRPT now contains members reported as “user” excludes.

Use case 3: GENERATE with duplicate excludes

In this case I’m going to add an user exclude in KCI$XW2R which already matches with what is excluded by default. Let’s suppose that my RKANPARU library contains a couple of KppTHRSH members and I want to exclude them:

The report informs that both excluded members belong to IBM-provided exclude list, therefore it is recommended not to duplicate it in user exclude member.

We hope that this report will help you quickly assess your exclude member setup and make it easier to keep everything on track.

Related information:

Understanding Configuration Manager Output: REPORT

#OMEGAMON #IBMZ #AIOpsonZ