In prior releases, The Eagle ML/CSV streams were loading override data and submitting the event immediately for each override. This was using up all the rule engines and not using the engines efficiently as each override was using up a rule engine.The procedure was changed to load all the overrides, capture SVS stream procedure allows you to use the engines efficiently as all the securities/effective dates are grouped and are not submitted individually.
The procedure loads all the overrides and then captures all the securities/effective dates of those overrides in a table. The system then executes another procedure as an end-of-file process, groups all the securities/effective dates, and then submits all the events as an end-of-file process. This allows you to use the engines efficiently as all the securities/effective dates are grouped and are not submitted individually.
There are two file ways in which RDC overrides can be loaded into the system:
...