...
Expand | ||
---|---|---|
| ||
I2I is part of EagleML, we don't have a separate version for I2I. EagleML/I2I have the same version. To determine which EagleML version you have in your environment, open Message Center Editor and open the following file: /eagle_ml-2-0_cm/w_config.inc. In the top line of this file, you will find information about the installed EagleML version. For example: <!-BR-EAGLEML_PRD_20151007.1-> In this example, you see BR-EAGLEML_PRD_20151007.1. This indicates that this environment contains the September 2015 monthend release. The date for the monthend release is typically the first Wednesday after the first Tuesday of the following month. For example, September 2015 EagleML monthend package was released on October 7th 2015. Refer to the related wiki page: http://eagle.helpdocsonline.com/checking-your-eagleml-version. You can find detailed information about each EagleML release in the EagleML Release Notes section. |
Filter Questions
...
Security Master File (SMF) Filters Questions
...
Expand | ||
---|---|---|
| ||
Yes, if you don't specify any filters for SMF, then all SMF will be extracted. There are no default filters, with one exception: maxrows (count of max returned records in the extract file). The default value of this parameter is 100,000 records (refer to Available Filters wiki page). But, on the level of I2I processes, there is also the EntityList filter which can be considered default if it is set in the spoke map. The spoke can also use one of the available Sources from the Sources List to filter SMFs – this is defined in the spoke map. |
Held Security Filters Questions
...
Expand | ||
---|---|---|
|
...
|
...
If Held Position Source parameter is empty, the Held Position SQL query will not be executed. This means that the extract looks thru all positions sources (doesn't filter them). |
Expand | ||
---|---|---|
| ||
If Held Position Source parameter is set (for example: heldpositionsources = STARDIRECT), then all positions with source = STARDIRECT will be extracted. |
Expand | ||
---|---|---|
| ||
This is also true for for Held Cash Activity Source. If Held Cash Activity Source is empty, then the Held Cash Activity SQL query will not be executed. If Held Cash Activity Source parameter is set (for example: |
...
heldcashsources = |
...
CASHTEST), then |
...
all cash activities with source = |
...
CASHTEST will be extracted. |
...
Held Corporate Action Source is not used. |
Date Filters Questions
Expand | ||
---|---|---|
| ||
Yes, they can be used in SMF extracts. But, the date filters are different for Date filters without Held Mode and Date filters with Held Mode. |
Expand | ||
---|---|---|
|
...
Date filters without Held Mode:
This means that all SMF records from the history table with EFFECTIVE_DATE value greater than or equal to the effective date filter value will be extracted.
This means that all SMF records from the composite or history table with the UPDATE_DATE value greater than or equal to the update date filter value will be extracted. Date filters with Held Mode: |
...
|
...
|
...
entityselectiontype / entityselectionvalue
|
...
|
...
|
...
|
...
Expand | ||
---|---|---|
| ||
If "effectivedate" filter is not set, then filtering by EFFECITVE_DATE field will not be used, there is no default filter value. In general |
...
, "effectivedate" filter is not used in Held Mode. |
Expand | ||
---|---|---|
| ||
Need to use "heldeffectivedate" filter and do not use ProcessCenter parameter in RTR. |
Expand | ||
---|---|---|
|
...
For Date filters without Held Mode: "fromeffectivedate" and "toeffectivedate" filters work as usual:
|
...
|
...
|
...
|
...
For "Date filters with Held Mode": "fromeffectivedate" and "toeffectivedate" filters |
...
aren't available. |
Expand | ||
---|---|---|
| ||
"effectivedate", "fromeffectivedate" and "toeffectivedate" filters are available only for SMF history extract and not available in Held Mode as follows: |
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
Planned Enhancements and Resolved Issues
...
Expand | ||
---|---|---|
|
...
This was a problem in the EagleML code, we have fixed it. It works correctly if we use the HeldEffectiveDate parameter instead of EffectiveDate in the Date filter. EffectiveDate in the Date filter is not used in the Held mode. However, current version of I2I doesn't support error descriptions in the final TSR, it shows only Status (SUCCESS, ERROR, NO_DATA). We are working on it right now and in one of the following EagleML updates, we will add this new feature. |
...
Expand | ||
---|---|---|
|
...
Yes, this was a problem and we have fixed it. |
...
Expand | ||
---|---|---|
|
...
Yes, it is possible. We are working on it right now. In one of the following EagleML and EJM Monitoring Tool updates, we will add this new feature. |
...