Running the SEPA component on z/OS

Before deploying the SEPA component of the Transformation Extender Pack for Financial Payments on the z/OS® platform, make note of the following factors:

• The SEPA framework consists of a main map and several executable run maps that use several schemas to validate UNIFI and SEPA.
  Note: EBA functionality is deprecated in this version of the Pack for Financial Payments.
• All compiled maps and schemas, as well as input XML files, must be ported in binary to the z/OS platform. The schemas and maps should reside in the same location, like a library dataset.
• The xliff.dtd from the base product directory must be ported in binary to the z/OS environment.
• All of the type trees in the type_trees subdirectory that are related to a schema or DTD must be (manually) modified to include the DDNAME which will point to the corresponding schema or DTD.
• After modification of the type trees, the maps have to be built and then ported to z/OS.
• Every map, schema, and file that is ported to z/OS must have a unique 8-character DDNAME in the JCL.