Since NT strategy can not detect the account position, I am thinking about using NTDLL to retrieve true account position and orders at the beginning of strategy run so as to sync correctly. For example, it may use specially coded ocoId prefix to identify different strategy instances. Is this a good workaround solution, or I missed something? Why NT does not provide native API calls to retrieve account level position and order arrays since all these can be done using NTDLL?
- Clearpicks

Comment