PDFlib binary distribution for IBM eServer zSeries / MVS
========================================================

Please observe the notes in the PDFlib manual regarding expected
file formats (EBCDIC text vs. ASCII text vs. binary) for several
items related to PDFlib usage. These rules must strictly be observed
in order to successfully use PDFlib on EBCDIC-based platforms.


How to use PDFlib on MVS
------------------------

The PDFlib binaries have been built with the IBM compiler. Note that
the PDFlib DLL for MVS will not work with programs built with the SAS C
compiler since the IBM and SAS compilers do not produce binary-compatible
output. However, PDFlib can alternatively be built with the SAS C compiler.

The PDFlib load & compiler sidedeck module are in a TSO XMIT format. You must 
do the appropriate TSO RECEIVE to extract them onto your system.

- Place LIBPDF.XMIT to hlq.PDFLIB.LOAD

- Place LIBPDF.DEFSD.XMIT to hlq.PDFLIB.SIDEDECK

- Place the other files into the approriate datasets;
  The directories of the distribution correspond to 
  this sample dataset layout:

    Allocated as FB 80:

     hlq.PDFLIB.BIND.C.SRC         << .C source files
     hlq.PDFLIB.CNTL               << JCL
     hlq.PDFLIB.BIND.C.H           << .H source files
     hlq.PDFLIB.BIND.OBJ           << object modules
     hlq.PDFLIB.SIDEDECK           << definition sidedeck

    The sample source is located in \bind\c\src and \bind\c\h

    Allocated as MVS load module format:

     hlq.PDFLIB.LOAD               << PDFlib load module

    Allocated as MVS PDSE load module format:

     hlq.PDFLIB.BIND.LOAD          << PDFlib sample load modules

    Allocated as VBM 32756:

     hlq.PDFLIB.BIND.DATA.JPG,GIF,TIF   << image data
     hlq.PDFLIB.BIND.DATA.PDF           << PDF import data, ..
     hlq.PDFLIB.BIND.DATA.AFM           << font specific data
     hlq.PDFLIB.BIND.DATA.PFA           << font specific data

See CCBIND, CHELLODL, RUNBIND in \bind\c\jcl for sample JCL
to compile, link, and run the PDFlib sample applications.


New with the 5.0.1 release is a COBOL binding.  See \bind\cobol\source
for COBOL versions of the standard PDFlib samples. JCL to compile & link
the samples is located in \bind\cobol\jcl.

The PDFlib COBOL binding OBJ XMIT file is located in \bind\cobol\obj.
The PDFlib COBOL wrapper DLL XMIT file is located in \bind\cobol\load.

Note:  With the 7.0.2p1 release, the COBOL binding object file has been
compiled as REENTRANT (RENT).  This requires that the binder output
of any COBOL program linked to it reside in a PDSE, rather than a 
traditoinal PDS.


How to use PDFlib with CICS
---------------------------

The PDFlib binary for MVS can be used with CICS. Due to restrictions
imposed by the CICS environment the following must be observed when
using PDFlib with CICS:

- The license file can not be used. Instead, the license key must be
  supplied via a call to PDF_set_parameter().

- The PDF output must be created in memory by supplying an empty file
  name to PDF_open_file(), and the resulting PDF data fetched with
  PDF_get_buffer().

- External import files (PDFs, fonts, images, etc.) can not be used.
  Instead, virtual PVF files must be created by supplying the relevant
  data to PDF_create_pvf(). The virtual file names used with this call
  can later be used with other PDFlib API calls (see chapter 3.1.5
  in the PDFlib reference manual for more information on virtual files).

- The UPR resource file can not be used. Instead, resources must be
  configured via PDF_set_parameter() or a virtual UPR file.



PDFlib source code distribution for IBM eServer iSeries and zSeries
===================================================================

PDFlib for IBM eServer iSeries and zSeries platforms (and compatible
platforms) is only available under the terms of a commercial license.
PDFlib source code for these platforms is available under a separate
license.

