FIX TAG 373
SessionRejectReason
Definition
Code to identify reason for a session-level Reject message.
Compare versions
Differences between the selected source snapshots, including wording and errata; not a migration guide.
FIX 5.0 SP2 FIX Latest · EP309
No differences in name, type, definition text, deprecation, or enumerated values.
Values 20
| Value | Meaning |
|---|---|
0 | Invalid Tag Number |
1 | Required Tag Missing |
2 | Tag not defined for this message type |
3 | Undefined tag |
4 | Tag specified without a value |
5 | Value is incorrect (out of range) for this tag |
6 | Incorrect data format for value |
7 | Decryption problem |
8 | Signature problem |
9 | CompID problem |
10 | SendingTime Accuracy Problem |
11 | Invalid MsgType |
12 | XML Validation Error |
13 | Tag appears more than once |
14 | Tag specified out of required order |
15 | Repeating group fields out of order |
16 | Incorrect NumInGroup count for repeating group |
17 | Non "Data" value includes field delimiter (<SOH> character) |
18 | Invalid/Unsupported Application Version |
99 | Other |
About the int data type
Sequence of digits without commas or decimals and optional sign character (ASCII characters "-" and "0" - "9" ). The sign character utilizes one byte (i.e. positive int is "99999" while negative int is "-99999"). Note that int values may contain leading zeros (e.g. "00023" = "23").
Used in messages 1
Includes nested components and repeating groups. Open a location to see its surrounding requirements.
35=3RejectMessage body