Xerox FreeFlow manual Tables, Coding other system level commands

PDL principles and procedures

Specifying formats There are many standard formats or print description entries (PDEs) (PDEs) available for your JSL. These formats are listed in the

“PDE command” section of the “Specifying print format parameters” in Chapter 4. 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;

Using copy Copy modification entries (CMEs) allow you to change certain modification parts of static data in report output and to change fonts within

entries variable data. Below are some sample CMEs:

CME1:	CME	LINE=(9,–), POS=1, FONT=1;
CME2:	CME	LINE=3, POS=59,
		CONSTANT='FIRST QUARTER’;

Defining character CODE commands define character translation tables used to code translation convert input job data into printed characters. For example:

tables

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.

1-24 Using LCDS Print Description Language