SessionRejectReason = SendingTime Accuracy Problem

, ,
1

Imported from previous forum

2

Hi,

If SendingTime/OriginalSendingTime format is incorrect, what should be the SessionRejectReason?

Is it [6 = Incorrect data format for value] or [10 = SendingTime Accuracy Problem] ?

Example-
If inbound message contains 52=20151240-10:56:14.722, where valid format is “YYYYmmdd-HH:MM:SS.sss” and date (dd) contains value 40.

Thanks.

3

Hi Hansi,
In your example the format is incorrect. As date must be in the range: [01 - 31].

Whilst if you have recieved today @ noon time a message having a timestamp of yesterday’s (or tomorrow’s) noon time, than it is an accuracy problem.

4

When would I use this? How can I differentiate between clock synchronization issues and network congestion problems and would I care even if I could tell one from the other?

5

[ original email was from John Harris - john.harris@bondmart.com ]
Problems might arise that can be explained neither by clock synchronization nor network congestion. For example, the sending time might be quoted as a time in the future, or as a time prior to transact time in the case of an execution report (which would be nonsensical). Inaccurate sending times might be a function of mischief as well.

When would I use this? How can I differentiate between clock synchronization issues and network congestion problems and would I care even if I could tell one from the other?

6

Thanks a lot Yuval.