The Not Applied message is sent when CME detects a sequence gap from the customer.
35=NotApplied
Excerpt |
---|
Tag | Name | Binary Type | Binary Length | Req | Enumeration | Description |
---|
39001 | UUID | uInt64 | 4 | Y |
| Matches Establish.UUID. | 39018 | FromSeqNo | uInt32 | 4 | Y |
| First not applied sequence number. | 39019 | MsgCount | uInt32 | 2 | Y |
| Count of how many messages have not been applied. This is the difference between: the sequence number (tag 9726-SeqNum) of the last business message received OR the last next sequence number (tag 39013-NextSeqNo) in the Establish message from the customer (inclusive) AND the sequence number (tag 9726-SeqNum) of the new business message received OR the new next sequence number (tag 39013-NextSeqNo) in the Establish message from the customer (inclusive) Example | Last Message | New Message | Tag 39019-MsgCount in Not Applied Message | 1 | business message (tag 9726-SeqNum=100) | business message (tag 9726-SeqNum=110) | 10 | 2 | Establish message (tag 39013-NextSeqNo=100) | business message (tag 9726-SeqNum=110) | 11 | 3 | business message (tag 9726-SeqNum=100) | Establish message (tag 39013-NextSeqNo=110) | 10 | 4 | Establish message (tag 39013-NextSeqNo= 100) | Establish message (tag 39013-NextSeqNo= 110) | 11 |
Info |
---|
Although the Establish message does not have its own sequence number, the tag 39013-NextSeqNo value sent in the Establish message is used to calculate the number of messages that have not been applied. |
| 9553 | SplitMsg | SplitMsg | 1 | N | 0=Split Msg Delayed 1=Out of Order Msg Delayed 2=Complete Msg Delayed | Indicates if a message was delayed as a result of: - being split among multiple packets (0)
- TCP re-transmission (1)
- due to a previously submitted split or out of order message (2).
If absent then the message was not delayed, split, or received out of order |
|