Using dynamic job descriptor entries (djdes) – Xerox 4112-4127 Enterprise Printing System-192 User Manual
Page 355
Using LCDS Print Description Language
5-1
5.
Using Dynamic Job Descriptor
Entries (DJDEs)
Dynamic Job Descriptor Entries, unlike the PDL commands
described in the Input Processing, Print Format, and Logical
Processing sections, are not coded in JSLs. They are coded in
the data stream to make changes during printing to what was
specified in the JSL. DJDEs are coded slightly differently from
JSL statements.
Using the IDEN command to enable DJDEs
To invoke DJDE processing in a job, you must code an IDEN
command in the JDL. The DJDE record(s) are interspersed
among the data records in the input data stream. Each DJDE
record contains an identification field (which matches the search
criteria specified in the active JDE) and a series of parameters
that describe the actual JDE changes to be applied to the report.
The IDEN command notifies the system that DJDE records may
be part of the input data stream. IDEN also describes the
characteristics of the DJDE records and the search criteria for
locating and identifying them.
Example
Following is an example of a coded IDEN command:
The PREFIX parameter defines the character string that must
appear in the identification part of each DJDE record in the input
data stream. When the system recognizes this character string
(in this example, it is the EBCDIC string 'RTEST'), it examines
the rest of the record for DJDE parameters. The OFFSET and
SKIP parameters define the starting positions of the prefix string
and DJDE parameters within the record.
IDEN
PREFIX='RTEST', SKIP=9, OFFSET=3,
OPRINFO=YES;