FIX Protocol Tag 112: TestReqID
Identifier carried in a Test Request. The Heartbeat sent in reply must echo the same value.
- Tag number
- 112
- Data type
- STRING
- FIX versions
- FIX 4.0 to 5.0 SP2 and FIXT 1.1
- Used in
- 2 message types
Practical notes on TestReqID
TestReqID is the identifier in a TestRequest (35=1), which the Heartbeat sent in reply must echo.
- Any string works. A timestamp or a counter makes replies easy to match in logs.
- Only the Heartbeat that answers a TestRequest carries 112. Regular heartbeats leave it out.
Common mistakes
- Answering a TestRequest with a Heartbeat that does not echo the TestReqID; the requester keeps waiting and times out.
See also:Heartbeat timeout
Tag 112 in each FIX version
Values and message usage as defined in a specific version.
Data type
STRING: Text of printable characters. It cannot contain the SOH delimiter.
Example
112=TEST-1
Illustrative value. In a message, fields are separated by the SOH character (0x01), often shown as | or ^ in logs.
Decode a message with this tagMessage types that use tag 112
- Heartbeat 35=0
- Test Request 35=1
Covers every version from FIX 4.0 to 5.0 SP2, including fields reached through components and repeating groups. The version pages above show whether the tag is required in each message.
Field and message data comes from the QuickFIX data dictionaries for FIX 4.0 to 5.0 SP2 and FIXT 1.1, used under the QuickFIX Software License. This product includes software developed by quickfixengine.org (http://www.quickfixengine.org/). Enumerated value names are converted to plain text for reading.