Limitations for the AFP to
PCL transform
This topic lists
the items in the AFP architecture
that the AFP to PCL transform
does not currently support. Unsupported items are either
ignored or error messages are issued. Because the AFP architecture and PSF continue
to be enhanced with new functional capabilities, this list might be
incomplete after the publication date. IBM® suggests
that you test how your AFP applications
print on your non-AFP printers to make sure the output is acceptable.
- DATACK JCL parameter and print-error-reporting job
attribute (for information about an alternative to the DATACK JCL
parameter, see Migration considerations)
- DBCS fonts in XML and record-format line data
- Include Page (IPG)
- Global Resource Identifier (GRID)
- Internal copy groups
- Invoke master environment group (IMG)
- IOCA: ABIC (non-concatenated) image compression
- Map Color Attribute Table (MCA)
- Map Page (MPG)
- Medium Finishing Control (MFC)
- Preprocess Presentation Object (PPO)
- Presentation Fidelity Control (PFC)
Other limitations include:
- The transform might create bar codes that are larger or smaller
than the same bar codes printed on AFP printers.
The transform creates bar codes with a resolution of 300 pels per
inch. Even though the size of bar codes might be different, the bar
codes will scan properly.
- The transform does not check all AFP structured
fields in the AFP documents for
validity. PSF might check additional structured fields for validity
when it prints the AFP documents.
Therefore, do not use the AFP to
PCL transform to determine if PSF can print an AFP document.
|