Creating Separate Files For Grouping Xdl Commands; Hierarchy Within A Job Descriptor Library (Jdl) - Oce XDL Reference Manual

Overview

1.8 Creating Separate Files for Grouping XDL 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
shorter 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 instead of after it.

1.9 Hierarchy within a Job Descriptor Library (JDL)

A command to specify the recording code (CODE parameter 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 XDL command: VOLUME CODE=PE-
BCDIC 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 speci-
fied 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 catalog
which, in turn, specifies EBCDIC in the VOLUME command CODE parameter.
Non-JDL hierarchy — START in PJM Window
The next level of command replacement above the JOB or JDE command is the START
command to be defined in the PJM LCDS Data file properties General tab. Values specified
in the START parameter override those in the job command level. LCDS-Module supports
in the START-command the JDE- and JDL-names only.
A29247-X4-X-8-7672
Creating Separate Files for Grouping XDL Commands
17