Code and Debug AOF Rules › Coding Guidelines › Logic in Automated Applications

Logic in Automated Applications

As you design your automated applications, avoid inefficient logic for triggering rules. Specifically, you want to avoid the triggering of an AOF rule as a result of an action taken by another AOF rule.

For example, do not issue a command in a message event rule (MSG) using the ADDRESS OPER host environment, and then try to have a command event (CMD) trigger on the command created by the ADDRESS OPER command.

Similarly, do not implement logic to trigger a MSG rule by an ADDRESS WTO host environment instruction that is issued by other AOF rules or OPS/REXX programs. Attempting to code logic in rule A that causes rule B to execute, and then having rule C execute on logic performed by rule B is not only confusing to maintain, but may also cause CA OPS/MVS to use process blocks unnecessarily. The process blocks are crucial to AOF processing and other CA OPS/MVS components.

If you have a piece of common logic that needs to be performed by various AOF rules and requires no waiting, then invoke this code as a REXX external subroutine.