GOOD/BAD COUNTER HANDLING.

An effective method to handle good/bad counters for reporting error conditions is described. Many devices count how many good and bad operations take place during the activation of a hardware device. There has been no effective way of using these counters to determine when a condition occurs that should be logged as an error condition and/or requires operator intervention/notification. The problem is to define threshold logging criteria. Defining a ratio (%) between good/bad does not protect good count runaway nor provide protection from premature logging. An example of good count runaway is illustrated.