Transaction Surveillance rules can be a powerful way to sift through large amounts of transaction data looking for specific groups of transactions on a card or terminal. The trade-off to having that power is that it is relatively easy to write rules that can cause unacceptable performance overheads on the system. Some examples of rules that can cause large resource usage are included later in this section. It can also be difficult to get the rule functioning as intended at the first attempt.
It is recommended that when deploying new rules into a production system that they first be tested using the command line Batch/Test tool, IRTSVTST. This tool allows you to test both the functionality and predicted performance of the new rule in the production environment. See the Transaction Surveillance Rule Test Tool section for more information on how to run this tool.
Transaction Surveillance rules are specified in the IRTSVCOL ini file.
IRTSVCOI on HPE NonStop with the file being located in the Prognosis subvolume, or
IRTSVCOL ini file on other platforms, which is located in the /Prognosis/Server/Configuration folder.