You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
ANVIL API (Assent) Developer Thread
- Thread starter ctarmor-et
- Start date
Whoever need anvil subcontractor that already had "fun" with Anvil API internals during long sleepless nights please write directly to alex.kroifer at gmail dot com
Does anyone know how to keep track of an order status? I'm submitting orders using the B_SendOrder method and I keep a pointer to the order. The problem I'm having is when Anvil rejects the order. I was hoping that the messages:
M_POOL_UPDATE_ORDER
M_POOL_ASSIGN_ORDER_ID
M_POOL_EXECUTION
would notify me if the order was rejected but I'm not getting any of these messages when this situation happens.
I've also tried monitoring the different methods within the order like:
IsActive
IsDead
IsCancelConfirmed
and these also don't appear to be updated as I would expect. When I run in debug mode and see that the order was rejected the return of the IsActive method still returns true.
M_POOL_UPDATE_ORDER
M_POOL_ASSIGN_ORDER_ID
M_POOL_EXECUTION
would notify me if the order was rejected but I'm not getting any of these messages when this situation happens.
I've also tried monitoring the different methods within the order like:
IsActive
IsDead
IsCancelConfirmed
and these also don't appear to be updated as I would expect. When I run in debug mode and see that the order was rejected the return of the IsActive method still returns true.
If you are sending smart order try monitoring this message:
M_SMARTORDER_REMOVE
M_SMARTORDER_REMOVE
You will not get msgs on a failed SendOrder()
You need to check it as follow:
check this parameter on return from call:
.., Order** orderSent = NULL, ...
Something like this:
// Error ?
if ( NULL == pCAnvilOrder->m_pOrder )
{
const char* pError = B_GetOrderErrorMessage(error);
STATICLOG4( "SoftErr: PlaceStockOrder: (%u) %s - Dest: %s - %s", error, (pError ? pError : ""), pCAnvilOrder->m_Venue.c_str(), pCAnvilOrder->Verbose() );
}
You need to check it as follow:
check this parameter on return from call:
.., Order** orderSent = NULL, ...
Something like this:
// Error ?
if ( NULL == pCAnvilOrder->m_pOrder )
{
const char* pError = B_GetOrderErrorMessage(error);
STATICLOG4( "SoftErr: PlaceStockOrder: (%u) %s - Dest: %s - %s", error, (pError ? pError : ""), pCAnvilOrder->m_Venue.c_str(), pCAnvilOrder->Verbose() );
}
B_SendOrder will give you a regular order. (i.e. limit, market, or stop also)
The question is, weather Anvil is rejecting your order, or it is getting rejected further on in its travels.
Here is my experience:
- If Anvil rejects your order, you won't see it in your Anvil orders window. However, you will see an error message in the "position manager" window, and you also get a return code from B_SendOrder which is != SO_OK (sometimes it is SO_OK, but your order pointer will be NULL - that's an error too). You will also see the SO_.* error message in your log file just after the Level1 <Symbol> line and the print out of the current state of the box.
- If the order is rejected further down the chain, you do get a M_POOL_UPDATE_ORDER message for the reject. (you will also get a M_REQ_NEW_ORDER message before B_SendOrder returns. This will tell you the order has been created in Anvil) At this point isDead() should be true (provided all your shares have been rejected, I have seen the case where only some shares are rejected out of the total order size, and then your order is still [a]live.
I try not to hold onto the Order pointer returned, because I'm not sure that there is a guarantee/contract that this will be a valid pointer for the lifetime of the order (someone else may have experience with this though). If I need to find the order, I'll ask Anvil to re-find it via the B_ method. Most of the time I don't need it anyway, because the POOL_UPDATE_ORDER (and the other UPDATE messages) will give me a pointer to the order in question anyway.
The question is, weather Anvil is rejecting your order, or it is getting rejected further on in its travels.
Here is my experience:
- If Anvil rejects your order, you won't see it in your Anvil orders window. However, you will see an error message in the "position manager" window, and you also get a return code from B_SendOrder which is != SO_OK (sometimes it is SO_OK, but your order pointer will be NULL - that's an error too). You will also see the SO_.* error message in your log file just after the Level1 <Symbol> line and the print out of the current state of the box.
- If the order is rejected further down the chain, you do get a M_POOL_UPDATE_ORDER message for the reject. (you will also get a M_REQ_NEW_ORDER message before B_SendOrder returns. This will tell you the order has been created in Anvil) At this point isDead() should be true (provided all your shares have been rejected, I have seen the case where only some shares are rejected out of the total order size, and then your order is still [a]live.
I try not to hold onto the Order pointer returned, because I'm not sure that there is a guarantee/contract that this will be a valid pointer for the lifetime of the order (someone else may have experience with this though). If I need to find the order, I'll ask Anvil to re-find it via the B_ method. Most of the time I don't need it anyway, because the POOL_UPDATE_ORDER (and the other UPDATE messages) will give me a pointer to the order in question anyway.
I tried to use a while back but could not get it to work. I was expecting it to cancel/replace the order, but the messages did not come thru.
I found it easier to keep the order pointer and cancel it, then add new one ..
Sorry I could not be of more help ...
I found it easier to keep the order pointer and cancel it, then add new one ..
Sorry I could not be of more help ...
Quote from ctarmor-et:
I tried to use a while back but could not get it to work. I was expecting it to cancel/replace the order, but the messages did not come thru.
I found it easier to keep the order pointer and cancel it, then add new one ..
Sorry I could not be of more help ...
Thanks ctarmor-et!
It does help.