• The check routine encounters multiple errors, such as 3 consecutive abends.
• The Init function processing does not complete successfully.
• The installation environment is not appropriate for the check. For example, the check might be looking for sysplex values when the installation is not a sysplex environment or the check may require UNIX System Services at a time when UNIX System Services is down.
• The parameters passed to the check are not valid.
• The check is a global one running on a different system.

You can get IBM Health Checker for z/OS to enable your check by fixing the error causing the check to be disabled and then refreshing the check. If you update the parameters passed to a check, you do not need to refresh the check, because the system will re-enable the check automatically in order to let it see if the parameters are now correct.

Some conditions causing a disabled check may resolve themselves. For example, if a check is disabled because it is a global check that is already running on a system in the sysplex, it will show up as disabled on other systems. Then, when it is no longer running on the original system, the system will enable the check on another system in the sysplex. Or, if a check requires UNIX System Services to run, but UNIX System Services is down, that check will be disabled until UNIX System Services comes up again. At that point, the system will enable the check.