Oce XDL, DJDE, PRISMAproduction Server V3.10 Reference Manual

Océ | Reference Guide

Océ

Océ PRISMAproduction Server V3.10

LCDS-Module XDL/DJDE

...and Training?

For this product we also offer seminars at
our Training Center in Poing.

Information:
Phone [phone]
Fax [phone]

Océ Printing Systems GmbH
Postfach 1260
85581 Poing
Germany

August 2005 Edition
A29247-X4-X-8-7672

Copyright © Océ Printing Systems GmbH 2001, 2002, 2003, 2004, 2005
All rights reserved, including rights of translation, reprinting, reproduction by copying
or any other method.
Offenders will be liable for damages. All rights, including rights created by patent
grant or registration of a utility model or design, are reserverd.
Delivery subject to availability; right of technical modification reserved.
All hardware and software names used are trademarks of their respective owners.

Overview

Input Processing

Print Processing

Using Logical Processing

Dynamic Job Descriptor Entries

Highlight Color Support

Appendix

A29247-X4-X-8-7672

Contents

1 Overview..................................................................................................................... 1

1.1 XDL Features and Functions ....................................................................................... 1

1.2 LCDS-Module Components and Overview.................................................................. 2

1.3 Preparing for a Print Job.............................................................................................. 2

1.4 Job Flow Process ........................................................................................................ 2

1.5 Input Data Types ......................................................................................................... 2

1.6 Xerox Print Description Language (XDL) .................................................................... 4

1.7 Job Source Library (JSL) Structure ........................................................................... 12

1.8 Creating Separate Files for Grouping XDL Commands ............................................ 17

1.9 Hierarchy within a Job Descriptor Library (JDL) ........................................................ 17

1.10Creating a Job Source Library (JSL) ......................................................................... 18

1.11Decisions to make before creating your JSL ............................................................. 18

1.12Hints and Tips............................................................................................................ 21

1.13Steps in creating a JSL.............................................................................................. 22

1.14Page Considerations ................................................................................................. 26

Contents

1.5.1 Line Data ........................................................................................................... 3

1.5.2 Formatted Data / Metacode Documents ........................................................... 3

1.6.1 Purpose of XDL ................................................................................................. 4

1.6.2 XDL command structure.................................................................................... 4

1.7.1 Command levels.............................................................................................. 12

1.13.1Name the JDL identifier................................................................................... 22

1.13.2Specifying VFUs.............................................................................................. 22

1.13.3Setting up input parameters ............................................................................ 23

1.13.4Specifying LINE command parameters ........................................................... 23

1.13.5Specifying use of DJDEs ................................................................................. 24

1.13.6Adding logical processing specifications ......................................................... 24

1.13.7Specifying formats ........................................................................................... 24

1.13.8Using copy modification entries....................................................................... 25

1.13.9Specifying output requirements....................................................................... 25

1.13.10Ending a JSL ................................................................................................. 26

A29247-X4-X-8-7672

Contents

1.15Page Orientation........................................................................................................ 27

1.15.1Landscape orientation ..................................................................................... 27

1.15.2Portrait orientation ........................................................................................... 27

1.16Fonts.......................................................................................................................... 28

2 Input Processing...................................................................................................... 29

2.1 Summary of Commands associated with Input Processing....................................... 29

2.2 Summary of BLOCK Command Parameters ............................................................. 30

2.3 Summary of CODE Command Parameters............................................................... 34

2.4 Summary of PCC Command Parameters.................................................................. 36

2.5 Summary of RECORD Command Parameters.......................................................... 41

2.6 Summary of TCODE Command Parameters............................................................. 45

2.7 Summary of VOLUME Command Parameters .......................................................... 46

3 Print Processing ...................................................................................................... 59

3.1 Summary of Print Format Commands ....................................................................... 59

3.2 Summary of ABNORMAL Command Parameters ..................................................... 60

3.3 Summary of ACCT command parameters................................................................. 63

3.4 Summary of ac:CME Command Parameters ............................................................ 64

3.4.1 Points to note .................................................................................................. 66

3.4.2 Examples......................................................................................................... 67

3.5 Summary of IDR Command Parameters................................................................... 69

3.6 Summary of LINE Command Parameters ................................................................. 71

3.6.1 Points to note .................................................................................................. 77

3.6.2 Examples......................................................................................................... 79

3.7 Summary of MESSAGE Command Parameters ....................................................... 80

3.8 Summary of OUTPUT Command Parameters .......................................................... 82

3.8.1 Standard Print Description Entry ..................................................................... 89

3.9 Summary of OUTPUT Command Parameters (Continuation)................................... 90

3.9.1 Definitions in Xerox-/Océ printing .................................................................... 98

3.9.2 Points to note ................................................................................................ 119

3.9.3 Examples....................................................................................................... 120

3.10Summary of PDE Command Parameters................................................................ 122

3.10.1Examples....................................................................................................... 124

3.11Summary of ROUTE Command Parameters........................................................... 125

3.12Summary of VFU Command Parameters ................................................................ 128

3.13Summary of STOCKSET Statement Command Parameters .................................. 131

3.13.1Points to note ................................................................................................ 133

A29247-X4-X-8-7672

Contents

3.13.2Example ........................................................................................................ 133

4 Using Logical Processing..................................................................................... 135

4.1 Logical Processing Commands ............................................................................... 135

4.2 CRITERIA Command .............................................................................................. 135

4.2.1 Points to note ................................................................................................ 140

4.2.2 Examples....................................................................................................... 141

4.3 String comparison Concepts ................................................................................... 142

4.3.1 String comparisons........................................................................................ 142

4.3.2 Character types ............................................................................................. 142

4.3.3 Masked comparisons using default type assignments .................................. 143

4.3.4 Masked comparisons using non-default type assignments ........................... 143

4.4 TABLE Command.................................................................................................... 144

4.5 BANNER Command ................................................................................................ 147

4.5.1 Points to note ................................................................................................ 149

4.5.2 Examples....................................................................................................... 149

4.6 BSELECT and BDELETE Commands .................................................................... 150

4.6.1 Points to note ................................................................................................ 150

4.6.2 Examples....................................................................................................... 151

4.7 Summary of LMODIFY command parameters ........................................................ 152

4.8 RAUX Command ..................................................................................................... 153

4.9 RFEED Command ................................................................................................... 155

4.10RSELECT and RDELETE Commands .................................................................... 157

4.11RPAGE Command .................................................................................................. 158

4.12RSTACK Command ................................................................................................ 160

4.12.1RSTACK delimiter modes ............................................................................. 160

4.12.2HJOBNO, HRPTNA display .......................................................................... 161

4.12.3Online RSTACK usage.................................................................................. 161

4.13RSUSPEND and RRESUME Commands ............................................................... 165

5 Dynamic Job Descriptor Entries (DJDEs) ........................................................... 169

5.1 Benefits of using DJDEs .......................................................................................... 169

5.2 IDEN Command ...................................................................................................... 170

5.3 Page- and Record-oriented DJDEs ......................................................................... 171

5.3.1 Page-oriented DJDEs.................................................................................... 171

5.3.2 Record-oriented DJDEs ................................................................................ 184

5.4 General Points to Note ............................................................................................ 194

5.5 DJDE Record Specification ..................................................................................... 195

A29247-X4-X-8-7672

Contents

5.6 Application of DJDEs ............................................................................................... 197

5.7 Job Parameter Modification Restrictions ................................................................. 198

5.8 Duplex DJDE Page Printing..................................................................................... 200

5.9 Effect of Multiple Logical Pages............................................................................... 201

5.9.1 COPIES=processing ..................................................................................... 201

5.10Online DJDE Restrictions ........................................................................................ 202

5.11DJDE Processing Optimization................................................................................ 202

6 Highlight Color Support........................................................................................ 203

6.1 General .................................................................................................................... 203

6.1.1 Definition of Terms ........................................................................................ 203

6.1.2 Why Use Color? ............................................................................................ 204

6.1.3 Available Toner Colors .................................................................................. 204

6.2 Implementation ........................................................................................................ 205

6.2.1 Highlight Color Printers.................................................................................. 210

6.3 LCDS Language Resources .................................................................................... 212

6.3.1 INKLIST ......................................................................................................... 212

6.3.2 Restrictions.................................................................................................... 213

6.4 Queue Management ................................................................................................ 216

6.4.1 INK Catalogs ................................................................................................. 216

6.5 Migrating to HC........................................................................................................ 231

6.5.1 INKINDEX and CME INK............................................................................... 231

6.5.2 Océ Resource Generators............................................................................. 231

7 Appendix ................................................................................................................ 233

7.1 Supported, restricted and not supported XDL/DJDE-commands ............................ 233

Index .............................................................................................................................. 243

A29247-X4-X-8-7672

Overview XDL Features and Functions

1 Overview

1.1 XDL Features and Functions

Print description language (XDL) is used to describe printing jobs to a LCDS-Module.
XDL accomplishes this by:

• Describing the input (type, format, characteristics).

• Describing the processing functions (logical processing).

• Describing the output (type, format, font selection).

Diverse application needs can be met because XDL enables you to:

• Change and mix font types on a page-to-page, line-to-line, or character-to-character
basis. Output can be customized for specific needs, for example, highlighting important
headings by changing font styles and sizes and by using highlight colour.

• Change page orientation and positioning on a page-to-page basis. Characters may be
printed horizontally or vertically with equal ease. The printing system switches instantly
between horizontal and vertical page formats, combining the two styles within a single
report.

• Print a number of previously separate logical pages on the same physical page of a
document.

• Modify documents on a copy-to-copy basis by printing selected portions of data on a
page-to-page basis. You can replace certain portions of text with other data, delete
paragraphs from some copies, or label other copies confidential.

• Merge variable print data with forms stored on the system disk. This eliminates the need
for most preprinted forms.

• Add data, position it on the page, and print it on a variety of forms in one job. Multiple
forms, stored in digital format, are changeable on a page-to-page and copy-to-copy ba­sis.

• Print two different forms back-to-back (duplex) on one sheet of paper, therefore, reduc­ing paper costs. Additionally, this option offers potential savings in inventory, filing, stor­age, and mailing costs for computer-generated material.

A29247-X4-X-8-7672 1

LCDS-Module Components and Overview Overview

1.2 LCDS-Module Components and Overview

Before discussing XDL commands in detail, a general understanding of LCDS-Module
components and functions is helpful. The following sections provide such a general over­view.

1.3 Preparing for a Print Job

Before a print job runs, the system administrator, programmer, operator, and LCDS-Module
work together:

• System administrator loads fonts, logos, forms, and images to the Print Server and cre­ates print job tickets with workflow information.

• System administrator determines the fonts, forms, and images needed by the job.

• Programmer creates the JSL or copies it onto the system and compiles it.

• Operators start print jobs via the Print Job Manager (PJM). Additional parameters (like
2-up, copies) can be handled by the operator.

1.4 Job Flow Process

The job flow process consists of Input processing, Logical processing and Output process­ing.

1.5 Input Data Types

The LCDS-Module can work effectively in many different environments, and it has the ca­pability to handle input from a wide variety of sources.

Whether you are using the LCDS-Module in an offline capacity or connected directly to a
host computer, input data for printing is sent to the printer in one of two forms:

2 A29247-X4-X-8-7672

Overview Input Data Types

1.5.1 Line Data

Line data - that is, raw data from a computer file including PCC-commands.

• The raw data can be sent to the LCDS-Module offline from magnetic tape or online from
a channel-attached host or over the network

If you are using the LCDS-Module to create reports or other documents from unformatted
data, several elements are required to complete the job:

• Variable data. Variable data is the part of the report that changes from page to page.
In the example of an inventory report, the variable data would be the part numbers, de­scriptions, prices, costs, and so forth.

• The variable data can be imported from the magnetic tape system in the offline mode
or from a host through a channel interface or over the network.

• Form data. Form data can include headings, boxes, lines, and graphic image files,
such as signatures or logos. Form data is entered in the form of compiled files.

• Processing data. Processing data is optional and it allows the operator to control the
output of selected reports, or selected copies of a multiple copy report, for cover-to-cov­er print processing on any job. For example, you may wish to specify that an inventory
report has 49 pages. You may also decide that four copies without cost information are
needed for distribution to clients. The three command sets described below provide out­put control:

• JDE. Gives the operator control over the mechanics of a particular print job. JDE

commands specify for example simplex or duplex printing.

• DJDE. Enables you to modify the printing environment dynamically. These com-

mands are inserted into the input data stream to modify the command characteris­tics of the existing job descriptor entry (JDE). DJDEs can take effect on a report-to­report, page-to-page, and record-to-record basis.

• CME. Enables you to replace certain parts of a report with predefined static data on

selected copies or to specify font changes within the variable data.

1.5.2 Formatted Data / Metacode Documents

Formatted data is sent to the LCDS-Module from a host-based document composition soft­ware package, for example, XPPI, XDGI, or PC-based software through the front-end pro­cessor. These systems are often used for electronic publishing and can produce very so­phisticated printed documents. Data from these sources come in a form that the LCDS­Module can already understand.

A29247-X4-X-8-7672 3

Xerox Print Description Language (XDL) Overview

1.6 Xerox Print Description Language (XDL)

This chapter discusses the following XDL topics used to create and control print jobs.

• Purpose of XDL

• XDL command structure

• JSL structure

• Hierarchy of replacement

1.6.1 Purpose of XDL

For a job to be printed on a LCDS-Module, it is necessary to create a file of XDL commands
to define the format of the input media, processing requirements, and the format of the print­ed output. The source or uncompiled file of XDL commands is referred to as a job source
library (JSL) file. All JSL files must be compiled before they can be referenced to print a job.

The object or compiled file is stored as a internal Print parameter description in the System
catalog. To select this Job Description Library use the ’JDL Name’ and ’JDE-Name’ fields
on the ’General’ tab in the PJM ’File properties’ window for LCDS data print files.

Each command has a set of parameters that can be used to define the characteristics of a
print job (input-, output- and logical- processing). XDL commands used in creating a JSL
may be entered at the LCDS-Module Editor.

1.6.2 XDL command structure

The primary element of a JSL is a job. It usually defines one input format, one set of pro­cessing instructions, and one set of output instructions. Each job has a user-defined name
that you invoke to run the job.

To produce a finished job or application, a JSL must be created and then compiled into a
JDL file. To accomplish this, you must use XDL commands and be knowledgeable about
XDL structure, which includes the following topics:

• Command components

• Right-part constants

Command components

The components of an XDL command are:

• Command identifier, if required

4 A29247-X4-X-8-7672

Overview Xerox Print Description Language (XDL)

• Command keyword

• One or more command parameters

• Parameter options

• Comments, if appropriate

In addition, there are syntax rules you must use in order for the system to recognize and
process your JSLs. These rules are described later in this section.

Identifier

If the command is to be referenced by another command, an identifier must precede the
command keyword.

The XDL command below has a command identifier (VFU1), a command keyword (VFU),
and three command parameters (ASSIGN, TOF, BOF):

VFU1: VFU ASSIGN=(1,1),TOF=1,BOF=55;

A command identifier is a label that may consist of one to six characters (A-Z and 0-9). It
must be followed by a colon (:). The identifier VFU1 in the command above could be coded
with any number of blanks following the VFU1 characters, but no blanks within the identifier
name.

Note: A command that requires an identifier must always be defined prior to any reference

to it.

Command keyword

A command keyword is required. For example, CME is the command keyword and VFU,
TABLE, CRITERIA, CME, PDE, and so on. A command keyword is required for each XDL
command statement.

Parameter

Each command keyword is followed by parameters used to select its processing parame­ters. The parameters for an XDL command keyword consist of a left and right part separat­ed by an equal sign (=).

A29247-X4-X-8-7672 5

Xerox Print Description Language (XDL) Overview

Set of typical XDL commands

Identifier Command key-

word (required)

VFU1:
CME4:

VFU
CME

Parameter key-

word

ASSIGN=

LINE =

Parameter op-

tion

(1,1),

(1,60),

Additional parameter

keywords

TOF=1,BOF=55;

POSITION=5,

FONT=2;

Comments

Comments are statements you include in the source file to describe certain XDL commands
and their functions. These comments can act as reminders if you, or someone else modifies
the JSL at a later time.

Comments may appear anywhere within the JSL. They must be preceded by the character
sequence slash and asterisk (/*), and terminated by the character sequence asterisk and
slash (*/).

/*my comment*/

Syntax rules

When entering your JSL records on the system controller keyboard, make sure to follow
these rules:

• Use commas or blanks to separate the options of a command.

• Use parentheses to enclose multiple right parts.

Note: Only single pairs are supported with the following exceptions: DJDE ASSIGN and

DJDE BEGIN.

• List parameter options in the sequence shown in this manual. To specify a particular
option but not the options preceeding it, use commas or blanks as ”place holders” for
the options you do not specify. For example, the OUTPUT command BFORM parame­ter has three options:

BFORM=(form-id,[init][,copies])

• To specify the form name (form-id) and number of copies, but not the initial copy (init)
on which the backside form (BFORM) is printed, enter:

BFORM=(SMLFRM,,2)

• The second comma (,) after SMLFRM tells the system that ”2” specifies the number of
copies on which the form is printed.

• Use blanks anywhere in the JSL except in keywords and constants.

6 A29247-X4-X-8-7672

Overview Xerox Print Description Language (XDL)

• Abbreviate command and parameter keywords to the first three letters or use the full
keyword, for example, POSITION or POS, OUTPUT or OUT. The only exceptions are
FOR, which the system interprets as the parameter FORMAT instead of FORM and
FON, which the system interprets as parameter FONTINDEX instead of FONTS.
Therefore, make sure to use the abbreviation FOR to represent FORMAT only and FON
to represent FONTINDEX only, or avoid the abbreviation entirely to prevent errors.

• Use a semicolon (;) to indicate the end of an element of data for the system. It must be
at the end of every XDL command.

• Enter command parameters such as FONT, FORM, and GRAPHIC in their singular
form as shown, or with an optional plural ”s,” such as FONTS, FORMS, and GRAPH­ICS.

• Enter the END; command to signal the end of a JSL. You may then enter another JSL
into the system if you wish. Use two END; commands to signal the end of all JSLs to be
processed:

END; END;

• Use all UPPERCASE letters in XDL. Comments, however, need not be in uppercase.

Example: LINE VFU=VFU1, DATA=(1,10),

OVERPRINT=(PRINT,DISP);

XDL commands are only accepted in the first 72 characters of each row/line. You may use
the LCDS configuration tool (see the Administrator’s Guide) to use lower case (”CaseMode”
Parameter) or more than 72 characters (”LineMode” Parameter).

This LINE command example contains three left-part command parameters, VFU, DATA,
and OVERPRINT, a right-part reference to an identifier, VFU1, and parameter options
(1,10) and (PRINT,DISP).

Right-part constants

Constants within the right part of a parameter may be either value or string constants. The
syntax of these constants is defined below.

A29247-X4-X-8-7672 7

Xerox Print Description Language (XDL) Overview

Value constants

Value constants are constants that have arithmetic values. They should be expressed as
decimal numbers. They may be expressed as hexadecimal values, octal values, or even
character values, but these expressions are not recommended. Decimal constants may be
signed and in some cases may have fractional digits, for example:

PDE BEGIN=(1.1, .37);
BLOCK LENGTH=1320;
RECORD LENGTH=132;

String constants

String constants are normally used to specify strings of characters or to reference identifier
parameters. String constants may be expressed as any of the following:

•Keyword

• Identifier

• Hexadecimal

• Character

•ASCII

• EBCDIC

Keyword

Keywords are terms that direct the system to perform specific predetermined activities.
Keywords always consist of the same characters and do not vary. For example:

OUTPUT DUPLEX=YES,

FORMS=NONE;

YES and NONE are keywords.

8 A29247-X4-X-8-7672

Overview Xerox Print Description Language (XDL)

Identifier

String constants may be used to specify names of forms, files, fonts, departments, and so
on. In creating your JSLs, you assign names to the forms and files you want to specify. Each
name you assign identifies the unique object you wish the system to act upon for your ap­plications. For example:

OUTPUT FORM=SMPLE,

BFORM=SMPBK,
MODIFY=CME12;

Identifier are limited to a length of 6 characters.

Hexadecimal

Normally used as string constants, each pair of hexadecimal characters results in one byte.
A hexadecimal constant must immediately be preceded by the characters X apostrophe (X')
to indicate to the XDL compiler that the following expression is in hexadecimal. For exam­ple:

IDEN PREFIX=X'C1C2C3C4';

I

Character

Normally used as string constants, but they may also be numeric value constants, each
character, including embedded blanks, results in one byte. A character constant must im­mediately be preceded and immediately followed by the apostrophe (') character. For ex­ample:

IDEN PREFIX='THIS IS A CHARACTER CONSTANT';
CONSTANT='ABCDE';

If the apostrophe character (') is required in a character constant, it must be defined in some
other way, such as consecutive or double apostrophes ("), or the hexadecimal constant
X’7D’. Character constants may be defined as EBCDIC and take their actual values from
the standard EBCDIC table definition.

ASCII

Used as string constants, each character results in one byte. The constants must be pre­ceded by the characters A apostrophe (A') and followed by an apostrophe (') character. For
example:

IDEN PREFIX=A'ABC';

A29247-X4-X-8-7672 9

Xerox Print Description Language (XDL) Overview

The ASCII string type allows hexadecimal representation of characters to be embedded in
a string. This is done by preceding the hexadecimal representation of the character with an
! character. For example:

IDEN PREFIX=A'ABC!44EF'

is equivalent to

IDEN PREFIX=X'414243444546'

The three-character sequence required for a hexadecimal representation of a character re­sults in one byte.

Two successive ! characters (!!) are necessary to represent one actual ! character when
printing. The two-character sequence (!!) results in one byte.

EBCDIC

EBCDIC constants are used for value and string constants. They must be preceded by the
characters E apostrophe (E') and followed by an apostrophe character ('). The EBCDIC
string type allows hexadecimal representation of characters to be embedded in a character
string. This is done by preceding the hexadecimal representation of the character with an !
character.

For example:

IDEN PREFIX=E'ABC!C4EFG'

is equivalent to the hexadecimal

IDEN PREFIX=X'C1C2C3C4C5C6C7'

Each character represented in EBCDIC results in one byte. Each two-character sequence
representing a character hexadecimally results in one byte.

Note that EBCDIC is the default, therefore the E 'xxx' is usually not required.

Ink references

Ink references may occur as one of the following:

• ink index (numerical

•'ink name' (always enclosed into apostrophes)

Ink names may be written in one of the following formats:

•'inkname'

•'palette-name.inkname'

10 A29247-X4-X-8-7672

Overview Xerox Print Description Language (XDL)

•'ink-catalog-name.palette-name.inkname'

•'ink-catalog-name..inkname'

When ink-catalog-name or palette-name are missing the appropriate IDR command para­meters will be used. (Refer to the IDR command description.)

In JSL files basically only primary colour specifications are allowed, no shaded colours.

Sample XDL commands

Identifier Command

keyword

MYJDL: JDL
VFU1: VFU ASSIGN=(1,1),TOF=1,BOF=55;
VFU2: VFU ASSIGN=(1,(4,59)),TOF=4,BOF=127;
CME1: CME LINE=3,POS=59,CONSTANT='FIRST QUARTER';
CME4: CME LINE=(1,60),POSITION=5 FONT=2;
PDE2: PDE PMODE=PORTRAIT, BEGIN=(1.1,.37),

CODTAB: CODE DEFAULT=EBCDIC, ASSIGN=(X'4A',X'B4');

VOLUME LABEL=NONE, HOST=IBMOS, CODE=CODTAB;
BLOCK LENGTH=1320;
RECORD STRUCTURE=FB,LENGTH=132;

MYJOB1: JDE

LINE VFU=VFU1,DATA=(1,10);
OUTPUT FORMS=XER111,FORMAT=PDE2,MODIFY=CME4;
ROUTE RTEXT=('ENGINEERING',2,56,109),RFORM=

RDELETE TEST=(C1 AND C2);
IDEN PREFIX='$DJDE',SKIP=10,OFFSET=1;
END;

Parameter keyword followed by parameter options and
additional parameter keywords

FONTS=(P08TYA, P08SCA);

XERCOV;

A29247-X4-X-8-7672 11

Job Source Library (JSL) Structure Overview

1.7 Job Source Library (JSL) Structure

To simplify JSL coding, XDL commands are grouped into command levels. The use and
syntax of command levels, along with the required END command, are defined in the fol­lowing sections:

• ID level

• System level

• Catalog level

• Job or JDL level

•END command

The command levels are always preceded by the JDL coding, which provides the name of
the compiled JDL.

1.7.1 Command levels

You can place XDL commands in any command level, depending on your particular appli­cation needs.

Command levels and their general purpose

Command level General purpose

ID Typically used to assign output channel numbers to printer car-

riage control channels through the VFU command, but any
command which has an identifier may be used at the ID level,

such as the CODE, PCC, and ROUTE commands.
System or JDL Establishes defaults for this library.
Catalog Groups XDL commands for easy reference at the job level (like

a macro).
Job or JDE Defines how individual print jobs are processed.

12 A29247-X4-X-8-7672

Overview Job Source Library (JSL) Structure

Sample JSL file format

JDLSMP:

VFU1:
VFU9:

CAT1:

JOBCPP:
JOB2:
JOB3:

JDL;
/* THIS SAMPLE JSL SHOWS THE JSL COMMAND LEVELS*/
/* ID LEVEL COMMANDS CODED HERE*/
VFU ASSIGN = (1,1), TOF = 1, BOF = 66;
VFU ASSIGN = (1,9), TOF = 9, BOF = 66;
/* SYSTEM LEVEL COMMANDS CODED HERE*/
VOLUME HOST = IBMOS;
BLOCK LENGTH = 1330;
RECORD LENGTH = 133;
LINE VFU = VFU9, DATA = (1,132);
OUTPUT FORMS = CPPR1, DUPLEX = NO,
COPIES = 2;
/* CATALOG LEVEL COMMANDS CODED HERE IF NEEDED*/
CATALOG;
LINE VFU = VFU1;
OUTPUT FORMS = FORM2;
/* JOB LEVEL COMMANDS CODED HERE*/
JOB;
JOB INCLUDE = CAT1;
JOB INCLUDE = CAT1;
OUTPUT DUPLEX = YES;
END;

ID level

The ID level has commands that require identifiers so that they can be referenced by other
commands in lower command levels. For example, the ID level contains one or more VFU
commands. As with the other command levels any XDL command can be specified at the
ID level. The ID level must be preceded by JDL coding, which names the JSL. For example:

XSML: JDL;
VFU1: VFU ASSIGN=(1,1),TOF=1,BOF=66;

In this example, XSML:JDL is the name of the complete JDL and the VFU command is in
the ID level.

A29247-X4-X-8-7672 13

Job Source Library (JSL) Structure Overview

System or JDL level

A system or JDL command set establishes installation-dependent requirements and default
values for job descriptor entries. At the system level, JDL may be used interchangeably with
SYSTEM. At the system level, commands are specified which apply to all job descriptor en­tries (JDEs) identified within a job source library (JSL). Each SYSTEM command results in
the creation of a JDL when compiled.

The SYSTEM command has the form:

jdl-name:{SYSTEM|JDL;}

jdl-name is a 1 to 6 character alphanumeric identifier specifying the name of the JDL to be
created. It must contain at least one alphabetic character.

For example:

SAMPL: SYSTEM;

This command identifies the start of a SYSTEM command and the beginning of a JDL. The
jdl-name SAMPL corresponds to the name of the JDL to be used when printing a job. When
DFAULT is coded for the jdl-name, the specification of a JDL parameter option in the
START command is not necessary.

Catalog level

The catalog level allows the coding of commands common to several JDEs. A catalog can
then be referenced in an INCLUDE command in each JDE. A catalog command level is
identified by the CATALOG command and ends with the appearance of another CATALOG
command or a JOB command. CATALOG commands may contain the same commands
which appear in the JOB command.

The CATALOG command has the form:

cat-name: CATALOG;

cat-name is a 1 to 6 character alphanumeric identifier of which at least one character must
be alphabetic. The cat-name is referenced by JDEs after the CATALOG command set has
been defined.

For example:

ONLINE:CATALOG;

In this command, ONLINE is the catalog level identifier to be used in the INCLUDE param­eter of a JOB command.

14 A29247-X4-X-8-7672

Overview Job Source Library (JSL) Structure

For example, to reference the catalog named ONLINE in a job, the job level command
would be:

JOB1:JDE INCLUDE=ONLINE;

Job or JDE level

The job or JDE level allows the grouping of individual jobs together. XDL commands coded
within the job command level override the system commands. XDL commands from a cat­alog command level can be incorporated as shown in the command syntax below. For each
job, values not specified in any of the command sets are taken from the XDL defaults as
defined in appendix A. The JOB or JDE command has the following form:

jde-name: {JOB|JDE} [INCLUDE = (cat-name

[,cat-name2][,...])];

1

jde-name is a 1 to 6 character alphanumeric identifier. It specifies the name of the JDE be­ing defined.

cat-name or cat-name

is a 1 to 6 character alphanumeric identifier of a previously defined

n

catalog name.

Examples–JOB command

JOB2: JDE;
JOB3: JOB;
INCLUDE=ONLINE;
JOB4: JDE;
LINE VFU=VFU2;
OUTPUT FORMS=AY2F;

A JOB command continues until another JOB, JDE command or END command is encoun­tered. The catalog identifier in a JOB or JDE command as with JOB3 above, JOB2 is used
along with the identifier on the SYSTEM command set to initiate a print job. When DFLT is
coded for the jde-name, the specification of a JDE parameter option on the START com­mand is not necessary.

END command

A JDL terminates with the END command. If one JDL is to follow another, the next com­mand after the END command should be another SYSTEM command.

The end of all JDLs to be processed is indicated by two consecutive END commands:

END; END;

A29247-X4-X-8-7672 15

Job Source Library (JSL) Structure Overview

Sample off-line job descriptor library

IBMPDL: SYSTEM;
/*THIS JOB DESCRIPTOR LIBRARY CONTAINS JOB DESCRIPTOR ENTRIES FOR
PROCESSING IBM OFFLINE Paper.

THE SYSTEM STATEMENT SET DEFINES CONSTANTS AND PROCESSING PROCEDURES
THAT WILL APPLY TO ALL JOBS PROCESSED USING THIS LIBRARY UNLESS
OVERRIDDEN BY THE CATALOG OR JOB STATEMENT SETS */

VFU001: VFU ASSIGN=(1,5),ASSIGN=(2,10),ASSIGN=(3,15),

ASSIGN=(4,20),ASSIGN=(5,25),ASSIGN=(6,30),
ASSIGN=(7,35),ASSIGN=(8,40),ASSIGN=(9,45),
ASSIGN=(10,50),ASSIGN=(11,55),ASSIGN=(12,60),
TOF=5,BOF=66;

VOLUME HOST=IBMOS,PLABEL=YES;

BLOCK LENGTH=2048;
RECORD LENGTH=136,STRUCTURE=VB,LTHFLD=2,

ADJUST=0,FORMAT=BIN,PREAMBLE=3;

LINE DATA=(1,132),PCCTYPE=IBM1403,PCC=(0,NOTRAN),

OVERPRINT=(PRINT,NODISP),VFU=VFU001;

ACCT USER=(BIN,TRAY);

CATPOW:CATALOG;

VOLUME HOST=IBMOS;
BLOCK LENGTH=2048,PREAMBLE=6,LTHFLD=2,FORMAT=BIN,

OFFSET=4;

RECORD LENGTH=135,STRUCTURE=VB,PREAMBLE=2,LTHFLD=2,

FORMAT=BIN,OFFSET=0,ADJUST=3;

CATGRP:CATALOG

VOLUME HOST=IBMOS;
BLOCK LENGTH=4096,PREAMBLE=0,ZERO=YES;
RECORD LENGTH=135,STRUCTURE=VB,PREAMBLE=1,LTHFLD=1,

FORMAT=BIN,OFFSET=0,ADJUST=2;

1:JOB;

VOLUME HOST=IBMOS;

2:JOB INCLUDE=(CATPOW);

VOLUME HOST=IBMOS;

RECORD LTHFLD=1,PREAMBLE=1,ADJUST=2;
3:JOB INCLUDE=(CATPOW);
4:JOB INCLUDE=(CATGRP);

VOLUME HOST=IBMOS;
END;

16 A29247-X4-X-8-7672

Overview Creating Separate Files for Grouping XDL Commands

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 17

Creating a Job Source Library (JSL) Overview

1.10 Creating a Job Source Library (JSL)

This section presents the following topics to use as a tool in guiding you through JSL cre­ation:

• Decisions to make before creating your JSL

• Review of XDL components and syntax

• Helpful hints

• Steps in creating a JSL

• Compiling your JSL

• Printing the job

• Short explanations of some application-related issues:

• Paper types

• Page orientations

• Registration shift and skew

•Fonts

• Compatibility with the 4050, 4090.

Keep in mind that many of the contents of this chapter are samples and suggestions of what
can be done with XDL to create your desired applications, that there is a multitude of other
possibilities and options available, and that detailed information on each topic is provided
in the other chapters of this manual.

1.11 Decisions to make before creating your JSL

Before starting to develop the JSL for your application, there are some key decisions you
must make, based on your site-specific needs and the design of the application.

Input data

In general, you should know this information about the input data before creating the JSL:

• The input source, such as the following:

• Host supporting the 3211 or 6262 (4245) host interface

• Reel-to-reel tape or cartridges, which are offline devices

• HD files transferred via network (using ftp, etc.)

18 A29247-X4-X-8-7672

Overview Decisions to make before creating your JSL

• Computer on which the data was created

• Block and record lengths and structure

• Code in which the data is encoded, such as ASCII and EBCDIC

• How printer carriage control (PCC) information should be processed

• For tapes or cartridges only, the label format used.

Output specifications

You must also decide on some basic questions about the output:

• Will the page orientation be landscape or portrait?

• What fonts will you use?

• What forms, if any, will you use?

• What paper sizes will be used?

• Should CMEs be used?

• Should highlight colour be used?

• Will the data be printed on one side of the page (simplex) or on both sides (duplex)?

• Will graphics be used?

• What are your site's conventions, if any, for naming forms, JSLs, files, and jobs?

• This information assists you in planning your applications in terms of the type of input
data to specify, the type of application to design, and how much you will need to cus­tomize the application to meet its intended purpose rather than using system defaults.

Type of application to create

When planning the specifications you will indicate in your JSL, you must first decide the type
of application you want by answering the following questions:

• Will you modify an existing application or create a new one?

• Will you use a form? If so, you need to call out only one form, a sequence of forms or
copy related forms.

• Will the application be landscape (horizontal) or portrait (vertical) orientation? (Orienta­tion is discussed later in this chapter.)

A29247-X4-X-8-7672 19

Decisions to make before creating your JSL Overview

Special features

You also want to determine the following:

• Will you include operator information, such as routing sheets or messages displayed?

• Will you select paper trays?

• What structure will appear on the printed page? For example, a letter or a large form
may require an entire page but, if smaller forms are usable, you may want to print two
or even four on a page.

Will you use dynamic job descriptor entries (DJDEs) to change the application on a page
or report basis?

Interactions between JSLs, catalogs, and jobs

You will also want to consider the interactions, similarities, and differences between various
JSLs, catalogs, and jobs:

• What characteristics are used globally, if any, for all of the applications at your site? For
example, do all jobs use the same host, format, paper size, page orientation, ink cata­log, block or record length, test criteria, DJDEs, error responses, accounting require­ments, fonts, or forms?

• What names will you call the JSL and catalogs or individual jobs within the JSL? Use
names that will be meaningful to you and others who may use the application.

20 A29247-X4-X-8-7672

Overview Hints and Tips

1.12 Hints and Tips

The following tips may help you as you create your JSL:

• The only required elements in a JSL are the following:

• A JDL name, which is the name of the entries created by compiling the JSL

•Job names

• END; command at the end of the JSL.

• System defaults could be used for all other specifications, although typically each ap­plication has its own specific characteristics.

• Use tab spacing to create columns for each element of the JSL: command identifiers,
commands, and parameters. While not required by the system, this organization makes
it much easier to identify command sets, their commands, and each command's param­eters quickly. Here is a short example:

SMPLST:
V1:

T1:
C1:

CME1:
JOB1:

JOB2:

JOB3:

END;

JDE;

JDE;

JDE;

JDL;
VFU

VOLUME

BLOCK
RECORD
LINE

TABLE
CRITERIA

CME

OUTPUT

OUTPUT

BANNER

ASSIGN=(1,5), ASSIGN=(2,10),
ASSIGN=(3,15), TOF=5, BOF=66;
HOST=IBMOS, LABEL=STANDARD,
CODE=EBCDIC, PLABEL=NO;
LENGTH=3990;
LENGTH=133, STRUCTURE=FB;
DATA=(1,132),
PCCTYPE=ANSI,
PCC=(0,NOTRAN), VFU=V1;
CONSTANT=(132) '*';
CONSTANT=(2,132,EQ,T1),
LINENUM=(1,5);
LINE=(9,-), POS=1, FONT=1;

DUPLEX=YES, FORMS=BARS, MODIFY=CME1;

FORMS=NONE, DUPLEX=NO, COPIES=2;

TEST=C1, HCOUNT=1, TCOUNT=0;

• If you are not sure which specifications to select, try running a job using the system de­faults and then adjust the JSL to meet your requirements. You can modify an existing
JSL in the same manner.

• Keep the hierarchy of replacement, described earlier in mind. It is much easier to spec­ify generic or global characteristics at the system level, for example, than to call the
same specifications out over and over again for each job or catalog.

A29247-X4-X-8-7672 21

Steps in creating a JSL Overview

• You do not need to use all command levels in a JSL. Many JSLs have only ID, system,
and job-level commands.

• Keep in mind that the specifications to select in your JSL can be changed easily. By
using the IDEN command you can allow DJDEs to override XDL commands on a page­by-page or record-by-record basis. Also, certain operator commands can alter the print
job in such areas as the number of copies to be printed, the sequencing of reports, and
paper feed specifications.

1.13 Steps in creating a JSL

There are many steps in creating a JSL, and many ways in which a JSL can specify your
application's requirements. The following sequence is simply one example of the format
and content of a JSL to help you get ideas on how to set up your own applications.

1.13.1 Name the JDL identifier

The first step in creating a JSL is to give the JDL a name, which can be no longer than six
alphanumeric characters, for example:

XRXSPL: JDL;

1.13.2 Specifying VFUs

The VFU command specifies the vertical tabbing for the print job. There can be more than
one VFU identified. All are typically specified at the ID level, for example:

/* ID level commands*/
VFU1: VFU ASSIGN=(1,11),

VFU2UP: VFU ASSIGN=(1,(11,77)),

VFU3: VFU ASSIGN=(1,1),

ASSIGN=(12,66),
TOF=11,BOF=66;

ASSIGN=(12,(66,132)),
TOF=11, BOF=132;

TOF=1, BOF=132;

22 A29247-X4-X-8-7672