Coding Other System Level Commands - Xerox DocuPrint 100 Software Manual

PDL principles and procedures
Specifying formats
(PDEs)
Using copy
modification
entries
Defining character
code translation
tables
1-24
There are many standard formats or print description entries
(PDEs) available for your JSL. These formats are listed in the
"PDE command" section of the "Specifying print format
parameters" chapter. PDEs, like VFUs, require identification; for
example:
PDE1: PDE BEGIN=(0.18IN,0.66IN),
FONT=(L0112B,L01BOA),
PMODE=LANDSCAPE;
PDE2: PDE BEGIN=(1.03,.51),
BEGIN=(6.30,.51),
FONTS=P1012A, PMODE=PORTRAIT;
Copy modification entries (CMEs) allow you to change certain
parts of static data in report output and to change fonts within
variable data. Below are some sample CMEs:
CME1: CME LINE=(9,–), POS=1, FONT=1;
CME2: CME LINE=3, POS=59,
CONSTANT='FIRST QUARTER';
CODE commands define character translation tables used to
convert input job data into printed characters. For example:
C1: CODE DEFAULT= EBCDIC;
ASSIGN= ('\', '/');

Coding other system level commands

System level commands without identifiers should be indented
under the commands with identifiers. One exception is the JDL
name command, which precedes the identifier commands and is
not indented.
The following sections discuss several other commands that are
usually coded at system level and that do not require identifiers.
Using LCDS Print Description Language