Running SEPA on z/OS

Before you deploy the SEPA components 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, SEPA, AOS, and EBA STEP2 rules.
• All compiled maps and schemas, and input XML files, must be ported in binary to the z/OS platform. The schemas and maps must reside in the same location, like a library data set.
• A DTD must be ported, in binary, to the z/OS environment, but this DTD does not need to be in the misapprehends subdirectory.
• 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 points to the corresponding schema or DTD.
• After modification of the type trees, the maps must be built and then 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.