Uniqueness test within a domain (SUMMARY with COUNT)

You can write a compliance report on the level of a SUMMARY of the underlying basic report type (as opposed to the record level) by adding a SUMMARY statement on the DOMAIN statement. In the associated records in TYPE=COMPLIANCE, the CLASS will contain the first field name used in the summary key, and RESOURCE will contain the fields value. The COUNT summary statistic will then become available, and if you use it you can write a GOAL on the number of objects in the domain as type relation number.

The controls implemented in SCKRCARL member C2RHF090 include an example of the use of a COUNT summary statistic on a DOMAIN level that allows testing for existence.

DOMAIN FTPD_no_exit_mod,
  DESC("FTP server user exit modules not defined"),
  SELECT(r_ac1),
  SUMMARY(r_ac1(system complex ver count_FTP_modules(<1)))
                                                                        
RULE FTPD_no_exit_modules,
  DOMAIN(FTPD_no_exit_mod),
  DESC("FTP server user exits, when in use, must be securely implemented
    by the z/OS systems programmer, and must be approved by an Information
    Security System Manager (ISSM)."),
  CAPTION("No FTPD user exits")
  GOAL No_FTPD_exit_modules r_ac1=0,
   DESC("No FTP server user exit modules found.")
ENDRULE