Set Up Pending Transactions

Set Up Entities

If you plan to set up pending trade rules that enable the Eagle system to identify certain transactions as pending transactions, you must identify the entities for which you plan to create pending trade rules as eligible for pending trade activity before you can process pending transactions for those entities. For each entity eligible for pending transaction activity for which you plan to use pending trade rules, set the Pending Trade Eligible Indicator field (tag 3679) to Yes. This field is available in the Create/Edit Entity panel, the Create Master Fund panel, and the Edit Master Fund/Sector panel. 

When the system receives a transaction from an upstream system for an entity that is eligible for pending transaction activity, and the transaction meets the pending trade rule criteria, the system identifies the transaction as a pending transaction. Otherwise, when the system receives a transaction from an upstream system for an entity that is not eligible for pending transaction activity, and the transaction meets the pending trade rule criteria, the system does not identify the transaction as a pending transaction.

You do not need to set the Pending Trade Eligible Indicator field to Yes in order to process pending transactions for an entity in cases where the system receives a transaction from an upstream system for an entity, and that transaction is already identified as eligible for pending transaction processing. The the Pending Trade Eligible Indicator field enables the use of pending trade rules for an entity. When the system receives a transaction from an upstream system for an entity, if the transaction is already identified as eligible for pending transaction processing because the incoming transaction's Pending Trade Flag field (tag 3695) has a value of Y, the system does not apply pending trade rules and routes the transaction to the PENDING_TRADES table in the TRADES database for further evaluation. If the incoming transaction's Pending Trade Status field (tag 3720) has a value equal to a custom status code value, the system applies the custom status. Otherwise, if no status is provided on the incoming transaction, the system sets the status to Pending.

Set Up Pending Trade Rules

Pending trade rules, previously called flagged position rules, specify the criteria that the system uses to assign a pending status to transactions that require evaluation prior to processing. For detailed information about setting up pending trade rules, see Manage Pending Trade Rules. 

Set Up Threshold Logic in BOOT.INI

You can configure configurable threshold limits in the STAR engine's boot.ini file to reject transactions that may affect a very large position with many lots. This can prevent processing transactions that can have significant impact on system performance. The STAR engine checks certain threshold limits as a pre-processing step. If the limits are exceeded, then the engine does not process the transactions, but routes them to the Workflow Manager for subsequent exception handling.

You can configure the limits based on the amount of records in either the Cost or Cash positions to be acted on by a transaction. You can also configure the limits based on the number of records rolled back by a transaction or the number of loopbacks produced as a result of processing a transaction. If a limit is exceeded, the transaction fails and the system can process the transaction in a dedicated engine so that it does not impact normal processing.

In addition, the database stored procedure and Batch Release Pending Trades panel allow a delay in a batch release. An interval based in seconds can be submitted to the procedure that the system compares to the most recent transaction's time stamp in the Pending Trades table to determine if that most recent transaction was inserted within the time interval. If it was, the procedure waits to the next execution to release the batch. For example, if the interval is ten seconds and the most recent transaction was inserted five seconds prior, then nothing is done. The reason for this is that if many transactions are being loaded into the Pending Trades table, it is best to gather the set and order them to be more optimal when processing in STAR.

The processing thresholds, which are disabled by default, include the following:

• RollbackThreshold. Maximum allowed number of rows to be rolled back. The default value is 25000.
• CostPositionMaxRowThreshold. Maximum allowed number or rows in a Cost position. The default value is 25000.
• CashPositionMaxRowThreshold. Maximum allowed number or rows in a cash position. The default value is 25000.
• LoopbackMaxCountThreshold. Maximum allowed number of loopbacks produced. The default value is 10000.

You can enable the first three thresholds by adding the following parameter to the engine's book.ini file.

ProcessingThresholdsEnabled = 1

You can enable the LoopbackMaxCountThreshold  by adding the following parameter to the engine's book.ini file.

LoopbackMaxCountThresholdEnabled = 1