Example assumptions

The following assumptions are made regarding FIX mapping from and to FIXML examples.

The following assumptions are made when the FIX to FIXML maps are run:

• The example FIX input files are validated, for example, fix_email_50.inp, which is in the <install_dir>/packs/financial_payments_vn.n.n.n/fix/examples/fixFMLemail/data directory.
• The input file is validated against the corresponding FIX type trees, for example, fix_50.mtt, which is in the <install_dir>/packs/financial_payments_vn.n.n.n/fix/examples/fixFMLemail/trees directory.
• The input file FIX checksum in tag 10, is validated by calling one of the FIX checksum utility maps, for example, fxchksm2_validate.mmc.

The following assumptions are made when the FIXML to FIX maps are run:

• The example input file is validated, for example, fixml_email_50.xml, which is in the <install_dir>/packs/financial_payments_vn.n.n.n/fix/examples/fixFMLemail/data directory.
• The input file is validated against the FIXML type trees, for example, fixml_50.mtt, that is in the <install_dir>/packs/financial_payments_vn.n.n.n/fix/examples/fixFMLemail/trees directory.
  Note: The FIX 5.0 SP2 and FIX 5.0 SPE EP messages work directly with schemas without the need for a corresponding type tree.
• The FIXML input file message is a well-formed XML message and conforms against the FIXML schema called, for example, fixml-main-5-0.xsd, in the <install_dir>/packs/financial_payments_vn.n.n.n/fix/examples/fixFML<msg>/schemas directory.

  Where <msg> is any of the FIX messages listed under the FIX component examples section.

• Output file FIX checksum in tag 10, is populated by calling one of the FIX checksum utility maps, for example, fxchksm3_compute.mmc.