Additional validation
In addition to enforcing message structure and syntax, the type trees also enforce a number of other rules.
Additional validation rules are defined in the following table.
| Rule | Description |
|---|---|
| Restriction list verification | Verifies the code list on FIX tags: examples are country codes, currency codes, exchange, and language data types. |
| FIX tags numeric data types | Enforces allowable numeric ranges for the following data types: int, float, Qty, Price, PriceOffset, Amt and Percentage. |
| Body length verification | Validates that the actual body length is consistent with the value specified in tag number 9 of the FIX message. |
| Message specific cross tag checking | Validates the presence or absence of certain tags that depend on certain values of other tags within the same message. |
| FIX tags without values verification | Verifies the FIX tags that have actual values specified. FIX tags without values fail the FIX type tree validation. |
Checksum digit validation is no longer being enforced within the FIX type trees. See Checksum integrity check.
The structure of the FIX tags allow restriction lists and numeric ranges to be
implemented consistently across message types. These FIX fields are defined as "Group"
class in the FIX type trees consisting of a common data type "Item" class. The data type
items introduced in the FIX type trees are re-used in other FIX fields having the same
data types. Maps built using FIX type trees from previous versions of the WebSphere
Transformation Extender Pack for FIX require re-mapping of the FIX fields, specifically
those fields that belong to the following data types:
- Country
- Currency
- Exchange
- Float (this includes data types, that is: Qty, Price, PriceOffset, Amt, and Percentage