PRINT DESCRIPTION LANGUAGE (PDL)
2-16 XEROX DOCUPRINT 180 LPS PDL REFERENCE
Creating separate files for grouping PDL commands
If you have multiple commands of the same type, such as CMEs and
PDEs, you may want to create separate files for them to group like
specifications together and to make your JSLs short er and more
efficient. You can create these types of command files by simply
listing them as you would in a JSL and complete the list with an END;
command before specifying a JSL’s JDL coding identifier in stead of
after it.
Files containing groups of PDE and CME commands may be created
as system or editor files. Because you use the editor to create and
modify your JSLs, it may be more efficient for you to create these
command files in the editor.
Refer to your
DocuPrint 180 LPS Operations Reference
for detailed
information on using system and editor command files.
Hierarchy of replacement
The system default values shown in appendix A are the more
commonly used values in job processing; they can be thought of as
a basic job descriptor entry (JDE). PDL commands need cod ing for
only those parameters that must be changed to process your unique
print jobs. This coding process may be further s pecified by placing
commands common to more than one job in the catalog command
level. When these coding features are properly implemented, it is
possible for the same command to be used in more than one job or
JDE command level within a library. The PDL processor evaluates
user coded commands and applies the highest ord er, error-free
definition to the job for printing. This process, termed the hierarchy of
replacement, is discussed in the subsequent paragraphs and
illustrated in figure 2- 6.

Hierarchy within a job descriptor library (JDL)

Figure 2-4 shows a coded JDL that contains four jo bs or JDEs. A
command to specify the recording code (CODE param eter of the
VOLUME command) of the input data appears in three places:
•According to the system command level (or JDL) command set,
the default recording code of the input data is ASCII (VOLUME
CODE=ASCII).
•According to the catalog command level, the recording code of
the input data is EBCDIC (VOLUME CODE=EBCDIC).
•According to the job or JDE command levels, for jobs one and
three, the recording code of the input data is Printable EBCDIC
(PEBCDIC). The PDL command: VOLUME CODE=PEBCDIC
overrides both catalog and system (or JDL) command level
definitions.
For job descriptor entry 2:JOB;, the recording code of the input data
is EBCDIC, as specified in the CATPOW catalog command. In
4:JOB;, the recording code of the input data is EBCDIC because the
JOB command’s INCLUDE parameter specifies the CATGRP