DOC1 Programmer's Guide

Running PCE
A PCE job uses the following resources:
Script file
Mandatory – this is the program code that describes
what PCE is to do when a job is run. Refer to
“Programming PCE” on page 15 for details.
Initialization file
Mandatory – this provides information about the
PCE environment including regional and system
settings.
Output datastream(s)
The file(s) to be manipulated by PCE. Files that are
input to PCE must have been produced by DOC1
Generate. During a typical PCE process, pages from
the datastreams are read to memory, manipulated as
required and then output to a new file. Both input
and output files are identified using an open
command in the PCE script itself.
Journal files
Many DOC1 applications create one or more
journal files to act as an index into the pages created
in the output datastream. PCE can use these to
locate and extract specific pages. It can also write
new or updated journal information if required.
Journal files are identified using an open command in
the PCE script itself.
HIP file
This is the file containing the instructions and
resources for a DOC1 application as created by the
DOC1 Work Centre. If you intend to add new
presentation objects to pages you will need to
identify the HIP file that was used when the output
datastream was initially created by DOC1 Generate.
This is specified in the section of the
initialization file.
Translation tables file
Mandatory – this contains tables that are used when
PCE converts text data. A standard translation tables
file is provided with DOC1 distribution material.
Custom files may be supplied in some
circumstances. The file to be used is referenced in the
section of the initialization file.
Messages file
Mandatory – this contains the text of the diagnostic
messages that may be issued by PCE and is supplied
with DOC1 distribution material. It must be
referenced in the section of the initialization
file.
User exit control file
If you need to call functions from external programs
as part of the PCE process you will need create this
file to identify the modules required and specify the
type of each function to be called. The control file
itself is referenced in the section of the
initialization file.
Text substitution file
If you want to use the PCE mapp command this file
provides the text strings to be returned according to
the parameter used. It is referenced in the
section of the initialization file. See “mapp” on
page 51 for more information.
Exception dictionary
If you want to use the PCE mixc command this file
includes the correct casing for non-standard text
strings. It is referenced in the section of the
initialization file. See “mixc” on page 52 for more
information.
99