Test Request
8=FIX.4.2
9=66
34=5025
35=1
49=TEST1
52=20160131-16:10:10.614
56=DWFIX01
112=TEST
10=096
8=FIX.4.2
9=52
34=17
35=0
49=DWFIX01
52=20160201-19:35:42
56=TEST1
112=TEST
10=146
What does the Test Request <1>
message do?
Test Request <1>
message do?-
The
Test Request <1>
message forces a heartbeat from the opposing application and checks sequence numbers or verifies communication line status. -
The opposite application responds to the
Test Request <1>
with aHeartbeat <0>
containing theTestReqID <112>
.
What does the TestReqID <112>
message do?
TestReqID <112>
message do?-
The
TestReqID <112>
verifies that the opposite application is generating the heartbeat as the result ofTest Request <1>
and not a normal timeout. -
The opposite application includes the
TestReqID <112>
in the resultingHeartbeat <0>
. Any string can be used as theTestReqID <112>
(one suggestion is to use a timestamp string).
Tag | Tag Description | Example Value | Value Description | Required |
---|---|---|---|---|
8 | BeginString | FIX.4.2 | FIX Version | Yes |
9 | BodyLength | 66 | Length of message | Yes |
34 | MsgSeqNum | 5025 | Message sequence number | Yes |
35 | MsgType | 1 | Test Request Message | Yes |
49 | SenderCompID | TEST1 | Sender ID | Yes |
52 | SendingTime | 20160131-16:10:10.614 | Sending timestamp | Yes |
56 | TargetCompID | DWFIX01 | Target ID | Yes |
112 | TestReqID | TEST | Identifier included this message to be returned in resulting Heartbeat <0> | |
10 | CheckSum | {Checksum} | Checksum of message | Yes |
Updated less than a minute ago