Supported objects and controls

The AFP to PCL transform supports these objects and controls:

AFP resources

• Page definitions, including conditional processing, record-format page definitions, and XML page definitions
• Form definitions, including basic N_UP processing, enhanced N_UP processing, and offset stacking
• Overlays
• Page segments
• User resource libraries

  The job submitter must have RACF® authorization to read all AFP resource libraries that the transform uses. For more information, see Setting up security for AFP resource libraries.

Line data

• Carriage control (ANSI, machine)
• CHARS
• Mixed line data and AFP records (including IDM, IMM)
• Record-format line data
• Traditional line data
• Table reference characters
• Shift-out/shift-in for DBCS data: SOSI1, SOSI2, SOSI3, and SOSI4 options

MO:DCA-P objects

• Bar Code Object Content Architecture (BCOCA) (see Table 2 for the bar codes that the AFP to PCL transform supports)
• Font Object Content Architecture (FOCA):
  • Single-byte character set (SBCS) fonts:
    • 300-pel raster fonts (fixed and relative metrics)
    • 240-pel raster fonts (fixed and relative metrics)
    • AFP outline fonts
  • Double-byte character set (DBCS) fonts:
    • 300-pel raster fonts (fixed and relative metrics)
    • 240-pel raster fonts (fixed and relative metrics)
    • AFP outline fonts
    • TrueType, OpenType, and WorldType fonts
• Graphic Object Content Architecture (GOCA): All functions
  Note:

  The transform positions GOCA characters like normal text by using the font size in the GOCA data stream. Characters are not scaled, and the cell size in the GOCA data stream is ignored. The printed output will be similar to the output on most newer IBM® AFP printers. This positioning method is likely to produce the most readable output.
• Image (IM): All functions, in single and double dot, in all rotations
• Image Object Content Architecture (IOCA):
  • FS45 tiled, compressed, and uncompressed image objects except: Include Tile parameter, Referencing Tile structure, IOCA Tile Resource structure
  • Uncompressed, compressed MMR, G3, G4, RL4, JPEG baseline and extended
  • IDE 1-8, 24 (lookup table)
• Map Media Type (MMT)
• Object containers for PDF documents and GIF, JFIF, JPEG, and TIFF image objects
• Offset stacking
• Presentation Text Object Content Architecture (PTOCA1, PTOCA2)

XML data

XML data encoded in EBCDIC (code page IBM-1047). The XML data encoding must match the encoding scheme defined in the page definition.

Table 2 lists the bar codes that the AFP to PCL transform supports.