Linnea
If you know of classes that are used by applications, and they clutter your reports, you could just exclude those classes entirely (or for specific resources using masks), by adding
exclude class=xxxx resource=(aa.bb, aa.cc, bb.**)
If you happen to have an indicator in your current RACF database, stored in profiles that you would want to omit from reports, you could use the SIM_PROFILE capability and implicit lookup in ACCESS newlists to retrieve this indicator, and use it to exclude ACCESS events that would have been covered by the profile.
Note:
One of the SIM_ fields must be referenced in the SORTLIST command.
CSDATA fields are not supported.
For example, if you tag these profiles with string LOG=NONE in the installation data field, you could use this as a filter using
exclude :instdata=:"LOG=NONE"c
------------------------------
Rob van Hoboken
------------------------------