Duplicate Cancel and Cancel Replace Requests

, ,
1

Imported from previous forum

2

The recieving system must have a function that will verify the uniqueness of ClOrdID. Since the system may have several connections uniqueness must be a combination of multiple fields for example sender and clorid. If the recieving system recieves a duplicate clordid in a message type “D” there is a “Duplicate Order” reject reason. However there is no Duplicate Order reject reason if a cancel request is recieved and the recieving system already has the clordid in its’ database. Can the recieving system reject Cancel Requests, Cancel Replace requests with a OrdReject Duplicate order or must it be CancelReject? If so what is the valid CancelRejectReason?

Thanks

3

> The recieving system must have a function that will verify the uniqueness of ClOrdID. Since the system may have several connections uniqueness must be a combination of multiple fields for example sender and clorid. If the recieving system recieves a duplicate clordid in a message type “D” there is a “Duplicate Order” reject reason. However there is no Duplicate Order reject reason if a cancel request is recieved and the recieving system already has the clordid in its’ database. Can the recieving system reject Cancel Requests, Cancel Replace requests with a OrdReject Duplicate order or must it be CancelReject? If so what is the valid CancelRejectReason?
>
> Thanks
>
This will be a cancel reject ,
If CXlREjREason is mandatory for your engine, then you have to put a value like “1” for exemple: Unknown order with add Tag58:text: the reason of why you reject the cancel request (