A High ERUF Value Does Not Mean That Your Transaction Is Invalid

If you design a transaction and calculate an ERUF value of 35, then it is obviously a very complex transaction, but what does this high value of 35 indicate to you?

• That if this transaction is part of a heavily and frequently used application, you should consider simplifying it, because it is too complex for heavy and frequent use on most IBM i.

• That if this application is not used frequently it is probably okay but it could become a "bottleneck" if its usage rates change. Its usage rate can change because it used more often by the same group of users, or because new groups of users start to use it.