Using SCRIPT example files in the z/OS environment

Edit online

Be aware of the following when using the NCPDP SCRIPT example files in the z/OS environment:
  • When 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.
  • After building maps for a z/OS platform, you must rename the resulting *.mvs compiled map to a unique 8 character name. The compiled map file, which contains maps and schemas, should be uploaded as a PDS member. Both maps and schemas must be uploaded as binary files.
  • Schemas and DTDs should be uploaded to a variable blocked dataset. These files can reside with the maps in a separate PDS or sequential dataset. You must, however, be aware of the ramifications of uploading variable-length data into fixed blocked datasets. The records are padded up to the fixed size with NULL (x'00') characters. Null characters are not valid XML.