S550-0435-04

Using extended code pages

Using extended code pages

Extended code pages are code pages that include multiple encodings within a single code page. Traditional code pages include EBCDIC or ASCII encoding only, but extended code pages can contain EBCDIC or ASCII encodings along with the Unicode equivalent value. Each code point can be mapped to one or more Unicode values so a printer can print with TrueType and OpenType fonts. The Code Page Control (CPC) structured field in the code page indicates whether the code page contains Unicode values. If an extended code page contains Unicode values, PSF can send the values to a printer that supports extended code pages. If a printer does not support extended code pages, the Unicode values are removed from the code page before PSF sends it to the printer.

Extended code pages can be stored in partitioned data sets (PDS or PDSE) in user or system font libraries, or in UNIX files (zFS files) in user path or system font path libraries. The recommended file name prefix for extended code pages is T1. When stored in UNIX files, extended code pages must have a .ECP file extension in uppercase format.

PSF uses these methods to access extended code pages:

  • PSF uses z/OS® UNIX System Services to access extended code pages that are installed in user path libraries specified in the USERPATH parameter on the OUTPUT JCL statement or in system font path libraries specified with the FONTPATH parameter on the PRINTDEV statement of the PSF startup procedure.
  • PSF accesses extended code pages that are installed in PDS or PDSE libraries specified in the USERLIB parameter on the OUTPUT JCL statement or with the FONTDD parameter on the PRINTDEV statement of the PSF startup procedure.

To create, modify, or install extended code pages:

  1. If you are using PSF with z/OS V1R13 or earlier, use a resource installer program, such as the InfoPrint AFP Resource Installer (Program Number 5639-EE2) to create, modify, and install extended code pages in UNIX path libraries. The InfoPrint AFP Resource Installer contains extended code pages that are built with Unicode values.
    Notes:
    1. Be sure the resource installer is set up with the correct permissions to access the path libraries.
    2. The resource installer does not create resource access table (RAT) entries for files with a .ECP extension.
    3. You might need PTF IP23012 when you are using extended code pages support in the InfoPrint AFP Resource Installer. See the Ricoh Production Print Solutions web page for PTF IP23012: http://rpp.ricoh-usa.com.
    4. You can obtain the InfoPrint AFP Resource Installer extended code pages at no extra charge from the IBM® Extended Code Pages web page: http://www-01.ibm.com/support/docview.wss?uid=psd1P4000878.
    5. If you are using PSF with z/OS V2R1, a resource installer program is not necessary because the z/OS Font Collection contains prebuilt RATs for TrueType and OpenType fonts that are installed during the z/OS V2R1 installation. For more information about the z/OS Font Collection, see z/OS Font Collection.
  2. To place extended code pages in a PDS or PDSE, transfer the code pages from the UNIX files to the partitioned data set and run the AFRREBLK program. See Using the AFP Reblocking Program.
    Note:
    Do not use file transfer protocol (FTP) to store an extended code page in a partitioned data set. You only use FTP to transfer an extended code page to a UNIX file.
  3. Identify the resource libraries where the extended code pages are found:
    • For code pages in a PDS or PDSE:
      • Identify user libraries with the USERLIB parameter on the OUTPUT JCL statement. See USERLIB.
      • Identify system font libraries in the PSF startup procedure with the FONTDD parameter on the PRINTDEV statement. See PSF for z/OS: Customization.
    • For code pages in UNIX files:
      • Identify user path libraries with the USERPATH parameter on the OUTPUT JCL statement. See USERPATH.
      • Identify the system font path libraries in the PSF startup procedure with the FONTPATH parameter on the PRINTDEV statement.
  4. Use z/OS UNIX System Services to set access permissions to the directories and files in the user path and font path libraries. PSF must have read permissions set for each path directory and file it is accessing. If the permissions for each directory or file are not set correctly, PSF cannot access the path library. For more information about z/OS UNIX System Services, see z/OS UNIX System Services Command Reference.