FIX TAG 946
CollInquiryResult
Definition
Result returned in response to Collateral Inquiry 4000+ Reserved and available for bi-laterally agreed upon user-defined values
Compare versions
Differences between the selected source snapshots, including wording and errata; not a migration guide.
FIX 4.4 FIX 5.0 SP2
Value text or deprecation changed 3
| Value | FIX 4.4 | FIX 5.0 SP2 |
|---|---|---|
0 | Successful (Default) | Successful (default) |
3 | Invalid parties | Invalid Parties |
8 | Collateral Inquiry type not supported | Collateral inquiry type not supported |
Values 11
| Value | Meaning |
|---|---|
0 | Successful (default) |
1 | Invalid or unknown instrument |
2 | Invalid or unknown collateral type |
3 | Invalid Parties |
4 | Invalid Transport Type requested |
5 | Invalid Destination requested |
6 | No collateral found for the trade specified |
7 | No collateral found for the order specified |
8 | Collateral inquiry type not supported |
9 | Unauthorized for collateral inquiry |
99 | Other (further information in Text (58) field) |
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"). Examples: 723 in field 21 would be mapped int as |21=723|. -723 in field 12 would be mapped int as |12=-723| The following data types are based on int.
Used in messages 1
Includes nested components and repeating groups. Open a location to see its surrounding requirements.
35=BGCollateralInquiryAckMessage body