Parameters of rule checking

If a rules set is configured, Rules Validation Engine (RVE) rule checking will only be performed if the command is issued through the RVE Business Logic Tier (BLT).

When control displays (CNTL_ANALOG, CNTL_STATUS, and CNTL_MULTISTATE) are used to command a point, rule checking will be performed; whereas RVE rule checking will be bypassed on function puts issued from the command line.

Tag checking occurs before RVE rule checking. Prohibitive tags such as "no commands" cause a command to abort. However, if a warning tag is encountered, you can override it to enable rule checking to proceed. If a Command Test Override tag is encountered, you will be given an opportunity to override any lower priority prohibitive tags to enable rule checking to proceed without interruption from these tags.

As rule checking occurs, you will be notified of any rule violations. However, rule violations can be overridden if you wish to proceed with the command.

The following logs exist for RVE:

• log\RVEcommand.log

• log\RVEbltcaller.log

• log\BLTHost.RVE.log