Running the examples on z/OS

This documentation describes how to run this example on z/OS.

About this task

Be aware of the following points when these files are used on z/OS operating systems:

  • When ported to z/OS, every map, schema, and file that is ported to z/OS must have a unique eight character DDNAME in the JCL.
  • After you build the maps for the z/OS operating system, you must rename the resulting *.mvs compiled map to a unique eight character name.
  • The compiled map file must be uploaded as a PDS member that contains maps. The schemas can either be uploaded as a traditional MVS data set to be referenced in a DSN option, or in a z/OS UNIX file, such as a Hierarchical File System (zFS or HFS) environment to be referenced in a PATH option. Both maps and schemas must be uploaded as binary.
Note: Throughout this documentation, <install_dir> is the installation location of the Pack for Financial Payments, and n.n.n.n is the current version of the Pack for Financial Payments.

Procedure

  1. Create a copy of the <install_dir>/packs/financial_payments_vn.n.n.n/fix directory to hold the z/OS modified files.
  2. Review the FIX to FIXML conversion maps. The conversion maps are in the <install_dir>/packs/financial_payments_vn.n.n.n/fix/examples/fixFML<msg>/maps directory.
    Where <msg> is any of the FIX messages listed under the FIX component examples section.

    Resolve the input card for FIX to FIXML.

    For example:

    fxfm0001_email_fix_to_fixml from map source fixfml_50_email.mms.

    The map uses one input card, called fix_50. The fix_50 card contains file email_50.inp. This file is in the <install_dir>/packs/financial_payments_vn.n.n.n/fix/examples/fixFMLemail/data directory.

    The file resolves to DD:fix#50 as the default DD name. This default DD name can be overridden through use of the execution command.

    For example:

    MAPDDS /IF1 FIX50IN /OF1 FIXML5OT /TIO /AE

    The values FIX50IN and FIXML5OT are z/OS DD overrides for the input and output cards that are defined for the map.

  3. Review the FIXML to FIX conversion maps. The conversion maps are in <install_dir>/packs/financial_payments_vn.n.n.n/fix/examples/fixFML<msg>/maps directory.
    Where <msg> is any of the FIX messages listed under the FIX component examples section.

    Resolve the input cards for FIXML to FIX map.

    For example:

    fmfx0001_email_fixml_to_fix from map source fmlfix_50_email.mms.

    The map uses one input card called fixml_50. The fixml_50 card contains the file fixml_email_50.xml. This file is in <install_dir>/packs/financial_payments_vn.n.n.n/fix/examples/fixFMLemail/data directory.

    The file resolves to DD:fixml#50 as the default DD name. This default DD name can be overridden through the execution command.

    For example:

    MAPDDS /IF1 FXML50IN /OF6 FIX50OUT /TIO /AE

    The values FXML50IN and FIX50OUT are z/OS DD overrides for the input and output cards that are defined for the map.

    Note: Running any of the FIXML to FIX example maps requires the FIX checksum utility RUN maps to be referenced within JCL.

    For example:

    • //FIXCHKSM1 DD DSN=&CHKSM1,DISP=SHR

      where

      &CHKSM1 refers to compiled map fxchksm1_utility

    • //FIXCHKSM3 DD DSN=&CHKSM3,DISP=SHR

      where

      &CHKSM3 refers to compiled map fxchksm3_compute

  4. The example conversion maps references metadata values that specify the FIXML schemas. There are two options about how to reference the schemas within a JCL.