Identifying potential checks

Look for potential checks in the following areas:

System history can provide an insight to potential checks.
Past system outages or conditions that produced an alert usually indicate a situation that could be detected by an appropriate check.
Support call documentation can reveal common configuration problems and values.
Product documentation may reveal settings that you wish to check in real time.
Single and multisystem configuration situations.

Within those areas, look for check routine candidates from the following:

Configuration problems or dynamic installation changes, including common initial setup errors and single points of failure.
Configuration values do not reflect recommended settings. For example, the CNZ_SYSCONS_MSCOPE check ensures that MVS™ system consoles are defined to have local message scope, which is recommended.
Defaults that no longer reflect the current recommendations.
Configuration recommendations that may have changed as a result of new functions introduced.
Installation values approaching configuration limits