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

Download

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 +49 8121 72-3940 Fax +49 8121 72-3950

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 basis.

• Print two different forms back-to-back (duplex) on one sheet of paper, therefore, reducing paper costs. Additionally, this option offers potential savings in inventory, filing, storage, 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 overview.

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 creates 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 processing.

1.5 Input Data Types

The LCDS-Module can work effectively in many different environments, and it has the capability 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, descriptions, 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-cover 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 output 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 characteristics of the existing job descriptor entry (JDE). DJDEs can take effect on a report-toreport, 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 software package, for example, XPPI, XDGI, or PC-based software through the front-end processor. These systems are often used for electronic publishing and can produce very sophisticated printed documents. Data from these sources come in a form that the LCDSModule 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 printed 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 processing 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 parameters. The parameters for an XDL command keyword consist of a left and right part separated 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 parameter 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 GRAPHICS.

• 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 applications. 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 example:

IDEN PREFIX=X'C1C2C3C4';

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 immediately be preceded and immediately followed by the apostrophe (') character. For example:

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 preceded 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 results 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 parameters 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 following 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 application 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 entries (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 parameter 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 catalog 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][,...])];

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

cat-name or cat-name

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

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 encountered. 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 command is not necessary.

END command

A JDL terminates with the END command. If one JDL is to follow another, the next command 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=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 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 creation:

• 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 customize 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? (Orientation 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 catalog, block or record length, test criteria, DJDEs, error responses, accounting requirements, 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 application 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 parameters quickly. Here is a short example:

SMPLST: V1:

T1: C1:

CME1: JOB1:

JOB2:

JOB3:

END;

JDE;

JDL; VFU

VOLUME

BLOCK RECORD LINE

TABLE CRITERIA

CME

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 defaults 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 specify 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 pageby-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

Overview Steps in creating a JSL

1.13.3 Setting up input parameters

Next, you may want to specify the input data characteristics for the application. The basic input processing commands are BLOCK, CODE, PCC, RECORD, TCODE, and VOLUME. Input processing characteristics vary depending on the data source. For example, if your JSL is for an online application, the BLOCK command is not applicable. Also, parameters within a command may apply to offline only, online only, or both. For example, with the VOLUME command, the parameters CODE and HOST can apply to both online and offline, EOV applies only to offline applications, and OPTIMIZE applies only to online applications.

The following is a sample of typical offline commands:

/*System level commands*/

VOLUME HOST=IBMOS,

LABEL=STANDARD, CODE=EBCDIC;

BLOCK LENGTH=2660,

PREAMBLE=4, LTHFLD=2, FORMAT=BIN;

RECORD LENGTH=136,

PREAMBLE=4, STRUCTURE=VB, LTHFLD=2, OFFSET=0, FORMAT=BIN;

1.13.4 Specifying LINE command parameters

The LINE command references VFUs from the ID level and allows you to instruct the system on which parts of the data in each record are to be printed. For this reason, it typically follows the RECORD command. For example:

LINE DATA=(1,132),

PCCTYPE=ANSI, PCC=(0,NOTRAN), VFU=VFU1;

A29247-X4-X-8-7672 23

Steps in creating a JSL Overview

1.13.5 Specifying use of DJDEs

Most XDL commands can also appear in the form of DJDEs, which allow page-by-page or record-by-record modifications to your applications. In order to use DJDEs, an IDEN command must be specified in the JSL to advise the system where to look for them in the input data stream. For example:

IDEN PREFIX='C9700', SKIP=7,

OFFSET=1;

Refer to the appendix ”Supported XDL/DJDE commands” for information on which XDL commands have DJDE counterparts.

1.13.6 Adding logical processing specifications

Logical processing commands are invoked when the system locates satisfactory test criteria. These test criteria are set up for record or block fields and, if met, allow special processing to take place for such things as banner pages, block selection or deletion, page selection from auxiliary paper trays, and page offsetting. An example of logical processing tests and criteria is provided in this catalog level command set:

/* Catalog level commands*/ TCCS: CATALOG;

T1: TABLE CONSTANT=('PAGE1'); T2: TABLE CONSTANT=('INPUT RECORDS'); T3: TABLE CONSTANT=('JOB'); C1: CRITERIA CONSTANT=(122,11,EQ,T1),

C2: CRITERIA CONSTANT=(14,13,EQ,T2); C3: CRITERIA CONSTANT=(14,3,EQ,T3);

1.13.7 Specifying formats

There are many standard formats available for you to select for your JSL. These formats are listed in the PDE command section of chapter 3, ”Specifying output parameters.” PDEs, like VFUs and IDRs, require identification, for example:

PDE1:PDE BEGIN=(0.18 IN,0.66 IN),

FONT=(LO112B,LO1BOA), PMODE=LANDSCAPE;

PDE2:PDE BEGIN=(1.03, .51),

BEGIN=(6.30, .51), FONTS=P1O12A, PMODE=PORTRAIT;

LINENUM=(1,10);

24 A29247-X4-X-8-7672

Overview Steps in creating a JSL

1.13.8 Using copy modification entries

Copy modification entries (CMEs) allow you to change report output on static data and to change fonts within variable data. Sample CMEs follow:

CME1:CME LINE=(9,-),POS=1,FONT=1; CME2:CME LINE=3,POS=59,

CONSTANT='FIRST QUARTER’;

1.13.9 Specifying output requirements

There are many specifications you can select to define the manner and look of your printed application. You can also have messages displayed to operators to advise or remind them of special circumstances. This is done with the MESSAGE command:

MESSAGE OTEXT=('ALL FORMS DUPLEX ONLY'!!!!!!',1,WAIT),

ITEXT=('COPY 2 WILL NEED BLUE PAPER');

Similarly, the ROUTE command sends printed information preceding the report to operators. Most output specifications are selected from parameters of the OUTPUT command. As with other commands, these can be specified at any command level, but are most often specified at the job level because of the many variations possible. Here are some examples:

/* Job level commands*/

JOB1: JDE;

OUTPUT DUPLEX=YES,

FORM=SMPLE, MODIFY=CME1, FORMAT=PDE1, COPIES=10, BFORM=SMLBK, OFFSET=FIRST;

JOB2: JDE;

LINE VFU=VFU2UP; OUTPUT FORMAT=PDE4,

FORMS=SPL2, COPIES=7;

A29247-X4-X-8-7672 25

Page Considerations Overview

1.13.10 Ending a JSL

When you are finished constructing your JSL, you must let the system know you are finished by entering the END command plus a semicolon (;):

END;

1.14 Page Considerations

Now that you have gone through many of the steps and considerations involved in creating a JSL, the following sections give you information on these page-related topics:

• Paper sizes

• Page orientations

Paper sizes

Paper sizes are considered in terms of page frames, which are boundaries associated with a page as a unit of printing or imaging.

• Physical page

• Logical page

Physical page

The physical page is the size of the paper itself. You may select any page dimensions within a 6- by 6-inch minimum and a 17- by 17-inch maximum.

Logical Page

Description of the frame into which data are to be printed. Using the "2up-Mode" you can place 2 logical pages on one physical page.

26 A29247-X4-X-8-7672

Overview Page Orientatio n

1.15 Page Orientation

There are two types of page orientation:

• Landscape

• Portrait

1.15.1 Landscape orientation

Text elements are placed parallel to the long edge of the logical page. The horizontal edge is longer than the vertical edge.

FMT1: equivalent impact printer format, 6 lines per inch

1.15.2 Portrait orientation

Text elements are placed parallel to the short edge of the logical page. The horizontal edge is shorter than the vertical edge.

FMT6: equivalent impact printer format, 6 lines per inch

A29247-X4-X-8-7672 27

Fonts Overview

1.16 Fonts

A font is a character set which has a unique type style, type size, and orientation. Both fixed and proportionally spaced fonts are available for use on an PRISMAproduction LCDS-Module. Each font character occupies an area called a character cell. All character cells in a fixed font are the same width. Character cells in a proportional font vary in width.

Character spacing

Because the length of a line printed with a proportional font is relatively unpredictable, fixed fonts are used for variable data on a report to avoid overprinting of forms by variable data. Proportional fonts are normally used for forms data, such as titles and headings. A business letter is an example of the use of proportional fonts for variable data.

Character spacing examples

Fonts are available in various families (for example, OCR and Titan), sizes, and faces medium and bold.

In addition to typeface, style, and size, a font can be defined by its orientation:

• Landscape

• Portrait

• Inverse landscape

• Inverse portrait

28 A29247-X4-X-8-7672

Input Processing Summary of Commands associated with Input Processing

2 Input Processing

Specifying input parameters

Input data is processed and temporarily written to disk for subsequent printing under control of user-selected PDL commands. The input processor decodes and formats input data from an offline magnetic tape, a host-attached channel interface, a remote communication, or Ethernet interface. The general functions of input processing are described below.

The basic XDL commands available to control input processing are BLOCK, CODE, PCC, RECORD, TCODE and VOLUME, which are defined in this chapter. The chapter "Using logical processing commands" defines commands enabling you to specify logical functions that may be performed on either a record, block, or page basis.

2.1 Summary of Commands associated with Input Processing

Command Function

BLOCK Input data block characteristics

CODE Input code translation table

PCC Defines printer carriage control code table

RECORD Input data record characteristics

TCODE Masked comparison type assignments

VOLUME Input medium characteristics

A29247-X4-X-8-7672 29

Summary of BLOCK Command Parameters Input Processing

2.2 Summary of BLOCK Command Parameters

ADJUST This parameter specifies a block adjustment value which is added to or

subtracted from the contents of the block length field to determine the true block length.

CONSTANT This parameter specifies that the block delimiter constant sc and all data

following it are ignored until the end of the block is reached.

FORMAT This parameter specifies the recording mode of the block length field.

LENGTH This parameter specifies the longest physical block being processed.

LMULT This parameter specifies a multiplication factor being applied to the con-

tents of the block length field to determine the true block length.

LTHFIELD This parameter specifies the length of the field containing the block length.

OFFSET This parameter specifies the location of the block length field.

POSTAMBLE This parameter specifies the length in bytes of the extraneous data at the

end of each tape block; that is, it is an offset from the end of a block backwards to the end of the last logical record.

PREAMBLE This parameter specifies the length of the operating system portion of the

block, that is, the byte offset from the first byte of a tape block to the first byte of the first logical record.

ZERO This parameter specifies the end of block indicator.

30 A29247-X4-X-8-7672

Input Processing Summary of BLOCK Command Parameters

Parameter Definition(s) Offline Online DJDE

ADJUST= value

value

Specifies the block adjustment length. This length is a constant integer added to or subtracted from the value in the block length field of every tape block. The resulting value is the true block length. The range for a value is

-127 to 127 and must be less than the block length parameter (LENGTH). The character plus (+) or minus (-) may be used to specify a positive or negative adjustment.

The default is 0.

CONSTANT= scsc

is a string (hexadecimal, octal, or character) constant which signals block-end. The length of the constant may be from one to four bytes. There is no default. If not defined, there is no blockend-string.

FORMAT=

type

Specifies how the block length is coded: BIN (binary) DEC (decimal) (=printable) The default is BIN.

YNN

LENGTH=

value

Specifies the length, in bytes, of the longest physical

YNN

block (an integer in the range 12 to 24,576). The default is 1330. For offline processing, the tape label contents may override a coded LENGTH parameter, but this length is still limited by the above maximum value. The default is 1330.

LMULT=

value

Multiplied by the value in the length field (refer to

YNN

LENGTH parameter) to compute the number of bytes in the block. A value is an integer in the range of 1 (the default) to 15. The default is 1.

A29247-X4-X-8-7672 31

Summary of BLOCK Command Parameters Input Processing

Parameter Definition(s) Offline Online DJDE

LTHFLD=

value

OFFSET=

value

POSTAMBLE= value

PREAMBLE=

value

Specifies the length in bytes of the field containing the block LENGTH specified above. The size is an integer in the range of 0 (the default) to 5. If size is set to 0, the block length field is not considered to be part of the block, and the length of a block, on tape, is the actual block length. The default is 0.

value

Specifies the block length field offset. This offset is the number of bytes from the first byte of a block to the block length field. A value is an integer in the range 0 (the default) to LENGTH-LTHFLD-1. The default is 0.

value

is an integer in the range of 0 (the default) to block length. It specifies the number of bytes at the end of the block which do not contain any record. The default is 0.

value

An integer in the range of 0 (the default) to block length. It specifies the number of bytes at the beginning of the block which do not contain any records. The default is 0.

YNN

ZERO= YES

YES Specifies that the end of a tape block is indicated by

YNN

a record length value of 0. Data that follows the record is ignored up through the end of the block.

ZERO= NO

NO Indicates that the end of a tape block is not indicated by a value of 0. The default is NO.

32 A29247-X4-X-8-7672

Input Processing Summary of BLOCK Command Parameters

Points to note:

• The LENGTH parameter may be overridden by ANSI, IBM OS or Standard labels that specify block length.

• The values for LTHFLD, OFFSET, FORMAT, and PREAMBLE may be overridden if RECORD STRUCTURE is changed as the result of ANSI, IBM OS or Standard label processing.

• The search for the block delimiter constant starts after the block preamble and proceeds forward to the first appearance of the constant.

• The maximum block size that may be processed by the input task is 24,576 bytes. The input task is able to allocate at least one input buffer for offline tape jobs when the tapes are written in maximum size blocks.

• If a block length is specified which is less than this minimum block length found on the tape, input processing allocates input buffers, which are sized to the minimum tape block length. It is wise to specify the maximum block length in the JSL, so that input buffers are large enough to handle the largest block. If the actual tape block length is smaller than the JSL block length, then no error message is reported; otherwise, an error is displayed.

• If a block delimiter constant is positioned and is part of a record or block, the user should use caution, since the record or block will be truncated. As a result, the data will not be formatted as specified.

Online versus offline JDLs

An offline JDL statement set that modifies the system default values, specifically in the BLOCK or RECORD commands, may experience incorrect results if running an online job (JDE). In other words, if an online job (JDE) is called out in an offline JDL that has changed the system default values (of the BLOCK and RECORD command parameters), the job may not print correctly. It is best then to separate and run online and offline jobs (JDEs) independently from each other.

A29247-X4-X-8-7672 33

Summary of CODE Command Parameters Input Processing

2.3 Summary of CODE Command Parameters

A CODE command is referenced by the CODE or LCODE parameters of the VOLUME command whenever a user-defined code translation table is required.

An identifier label (ac:) is optional for the first CODE command within a JDE. Thereafter, each additional CODE command within the JDE must be labeled. Therefore, when multiple CODE commands are available within a JDE or JDL, only one can be unlabeled. The syntax is ac:CODE.

ASSIGN This parameter defines user code assignment exceptions, or the entire user char-

acter translation table.

DEFAULT This parameter specifies a base code from which code assignment exceptions can

be made. The base code is specified by a code-type; the exceptions are specified using the ASSIGN parameter.

Parameter Definition(s) Offline Online DJDE

ASSIGN= input, (out-put [,output2] [,...])

DEFAULT=

code-type

input

Defines the input code.

output

This parameter defines one or more entries to a codetranslation table.

The code type can be one of the following EBCDIC ASCII This option defines the basic-volumes of a codetranslation table.

value

A value is a one-byte hexadecimal, octal, or alpha constant. If a value is specified, all inputs are coded to the specified value. The DEFAULT parameter must be coded prior to any ASSIGN parameter for the assignment exceptions to come into effect. A DEFAULT parameter following any defined corresponding ASSIGN input or output parameter options causes this correspondence to be replaced by the DEFAULT parameter. The default is EBCDIC.

YYN

34 A29247-X4-X-8-7672

Input Processing Summary of CODE Command Parameters

Point to note

Multiple user-defined code translation tables are allowed, but only one may be without a command identifier. The corresponding CODE parameters of the VOLUME command are used to reference each user-created code table by a command identifier. The USER option of the CODE parameters of the VOLUME command are used to reference a user-defined code translation table in which no command identifier is coded.

Example

A user's input tape is recorded in EBCDIC. On output, however, codes 5A, 5B and 5C (characters!,$,* respectively), are assigned to the character blank (X'40'). The command to modify the EBCDIC base table is as follows:

CODE DEFAULT=EBCDIC,ASSIGN=(X'5A',X'40'), ASSIGN=(X'5B',X'40'),ASSIGN=(X'5C',X'40');

A29247-X4-X-8-7672 35

Summary of PCC Command Parameters Input Processing

2.4 Summary of PCC Command Parameters

The PCC command enables the user to create a table (or modify an existing standard table) of one-byte printer carriage control codes and define their action. Line spacing, skip-tochannel, and printing actions are all defined through this parameter.

The user specifies an identifier when defining the PCC table and references it in the PCCTYPE parameter of the LINE command.

ADVTAPE This parameter specifies if an advance to a new page is to occur when two

successive channel-skip parameters are issued with no intervening print. For example, on most printers, the actions: PSK1 (print-and-skip-to-channel-1) followed by SK1N (skip-to-channel-1, do not print) would cause a blank page to be output. However, on a 1403 printer, these actions would not cause a blank page to be output.

ASSIGN This parameter specifies printer carriage control exceptions to a default

table (refer to DEFAULT parameter).

DEFAULT This parameter allows selection of a set of printer carriage control codes.

A table may be selected and then specific control codes may be modified with the ASSIGN parameters.

INITIAL This parameter specifies the initial reference point (TOF or BOF) from

which a report performs its first carriage control function.

MASK This parameter specifies an 8-bit value to be ANDed with the printer car-

riage control byte being processed.

Parameter Definition(s) Offline Online DJDE

ADVTAPE= YES

ADVTAPE=NONO

YES Specifies that multiple skips are honored.

Specifies that multiple skips result in only one skip action being taken. Note that SK1P (skip-to-channel-1and-print) followed by a second SK1P results in a page transition since printing occurred on the first page (even if blanks were printed). The default is YES.

YNN

36 A29247-X4-X-8-7672

Input Processing Summary of PCC Command Parameters

Parameter Definition(s) Offline Online DJDE

ASSIGN= (byte,(ccln, [ccln][,...])

This option has the following components:

byte

The printer carriage control byte being defined. Its value is in the range 0 to 255 (X’00’ to X’FF’). Possible codings are: Character, ASCII, EBCDIC, HEX, OCT. The default is EBCDIC.

ccln:

Specifies the action that should be taken when the printer carriage control byte defined in byte is encountered. A ccln may be any of the following definitions: TOF When byte causes the bottom-of-form (BOF) to occur, instructs the printing system to go to the top-ofform (TOF) on the next page and to stop spacing. IGN When byte causes the bottom-of-form (BOF) to occur, instructs the printing system to ignore it to continue spacing through the end of the physical page. The page then transitions to top-of-form and spacing continues. OVR When byte causes the bottom-of-form (BOF) to occur, instructs the printing system to go to the top-ofform (TOF) on the next page and to continue spacing. The default is OVR.

YNN

A29247-X4-X-8-7672 37

Summary of PCC Command Parameters Input Processing

Parameter Definition(s) Offline Online DJDE

Space print parameters This has the following components:

field

Specifies the carriage action to take before printing. An example is the ANSI carriage control: SPm Space m lines before printing. SKn Skip-to-channel-n before printing.

field

Specifies whether printing occurs for this record: P Print the output data at the line number computed after field1 is processed. N No printing occurs for this record (default).

field

Specifies the carriage action to take after printing. An example is the IBM1403 carriage control). SPm Space m lines before printing. SKn Skip-to-channel-n before printing. Each of the three fields is optional; however, you must specify at least one field. The range for the variables m and n is 0 to 15.

DEFAULT=

ccln

Specifies the required action when a code has not

YNN

been specifically assigned. The assignment codes for various actions are described in the ccln option description of the ASSIGN parameter.

38 A29247-X4-X-8-7672

Input Processing Summary of PCC Command Parameters

Parameter Definition(s) Offline Online DJDE

DEFAULT=

pcctype

pcctype:

can have one of the following values: ANSI ASA B2500 B2700 B3500 B3700 B4700 B6700 IBM1401 IBM1403 IBM3211 IBM4245 NCR ICL SNI UNISYS US70 XEROX NONE additonally the following ccln are supported: N P SP1 [PIN] [PIN] SP1 SK1 [PIN] [PIN] SK1 The default is a table of PSP1 codes (print-andspace1).

INITIAL This option indicates the initial position on the first

page of the report from which the first spacing action is to be taken. The parameter may be either BOF (Bottom Of Form) or TOF (Top Of Form).

MASK This option specifies a one byte value which is to be

logically ANDed with the pcc Byte before using the pcc byte to determine the appropriate action.

Points to note

Note the following when using the PCC command:

A29247-X4-X-8-7672 39

YYN

YNN

Summary of PCC Command Parameters Input Processing

• Multiple user-defined PCC tables are allowed, but only one may be used without a command identifier. The corresponding PCCTYPE parameter on the LINE command references each table through a command identifier. The keyword USER can be used to reference any user-defined PCC table for which no command identifier is coded.

• The user may end a PCC command with a semicolon and start another PCC command to continue specification of the carriage control codes. Multiple PCC commands may be used within a single PCC table definition as long as there are no intervening non-PCC commands.

• Consecutive byte values need not be specified. Thus, the commands

ASSIGN=(X'60',SP1),ASSIGN=(X'61',SP2), ASSIGN=(X'62',SP3);

can be coded in the single command

ASSIGN=(X'60',(SP1,SP2,SP3));

• If under the LINE command byte translation is specified (that is, the LINE command PCC parameter TRAN option is specified), the PCC control byte is translated into LCDS-Module standard EBCDIC before being applied. This means that the byte option on the ASSIGN parameter must be specified as an EBCDIC translation of the PCC byte, for example, X'F1' or 1.

• The DEFAULT parameter must precede any ASSIGN parameter.

Example

PCC1: PCC DEFAULT=IBM1403, INITIAL=TOF, ADVTAPE=NO, ASSIGN=(X'40',SP1P), ASSIGN=(X'F1',SK1P), ASSIGN=(X'F8',PSK8);

Added to the standard IBM1403 carriage control code table are: X'40' (space 1 line and print), X'F1' (skip-to-channel-1-and print), and X'F8' (print-and-skip to channel 8).

40 A29247-X4-X-8-7672

Input Processing Summary of RECORD Command Parameters

2.5 Summary of RECORD Command Parameters

ADJUST This parameter specifies an adjustment value added to or subtracted from

the contents of the record length field to determine the true record length.

FORMAT This parameter specifies the format of the record length field.

LENGTH This parameter specifies the length of the longest logical record. A value

specifies the length, in bytes, of the longest logical record.

LMULT This parameter specifies a multiplication factor applied to the contents of

the record length field to determine the true record length.

LTHFLD This parameter specifies the length of the field containing the record

length.

OFFSET This parameter specifies the location of the record length field.

POSTAMBLE This parameter specifies the length of any extraneous data at the end of

the record.

PREAMBLE This parameter specifies the offset to the user portion of the record, that

is, the record preamble length.

STRUCTURE This parameter specifies the general record structure of the input data.

Parameter Definition(s) Offline Online DJDE

ADJUST=

value

FORMAT=

type

value

Specifies the record adjustment length. It is a constant integer added to or subtracted from the value in the length field of every record. The range of a value is -127 to 127 and must be no greater than length. The first character may be plus (+) or minus (-). The default is 0.

type

Available type parameters are: BIN (binary) DEC (decimal) (=printable) The default is BIN.

YNN

A29247-X4-X-8-7672 41

Summary of RECORD Command Parameters Input Processing

Parameter Definition(s) Offline Online DJDE

LENGTH=

value

LMULT=

value

LTHFLD=

size

value

An integer in the range 1 to 310 for offline (133 is the default) or 150, the online default. For offline systems, the tape label contents may override a value. For online systems, if you define a record length larger than the default block length (1330 bytes), you must also define a block length that is big enough to hold the record. If a larger block length is not specified, the default length value is used and the system produces a warning message on the system controller display. The default is 133 offline, and 150 online.

value

Specifies the multiplication factor. The value specified is multiplied by the value in the length field to compute the number of bytes in the record. A value is an integer in the range 1. The default is 1.

size

Specifies, in bytes, the record length field length. It must be an integer in the range 0 to 5. If the size is set equal to zero, record lengths are not contained in the records, and the record length is the maximum length (LENGTH) for each record. The default is 0.

YYN

YNN

OFFSET=

size

Specifies the record length field offset. This offset is

YNN

the byte offset from the first byte of the record to the record length field. A value must be an integer in the range 0 (the default) to LENGTH-LTHFLD-1. The default is 0.

POSTAMBLE=

length

Specifies the length in bytes of an area at the end of

YNN

each record which is not to be processed. The length must be an integer in the range 0 (the default) to record length. The default is 0.

PREAMBLE=

length

The byte offset from the first byte of the record to the

YNN

first byte of the user's portion of the record. The length must be an integer in the range 0 (the default) to record length. The default is 0.

42 A29247-X4-X-8-7672

Input Processing Summary of RECORD Command Parameters

Parameter Definition(s) Offline Online DJDE

STRUCTURE=

structure-type

May be any of the following: FB (fixed length blocked) F (fixed length) V (variable length) VB (variable length blocked) For offline processing, the tape label contents may override this parameter. The default is FB.

YNN

Points to note

Note the following when using the RECORD command:

• LENGTH May be overridden by ANSI or IBM OS/Standard labels that specify record length.

• LTHFLD, OFFSET, FORMAT, and PREAMBLE The values for these may be overridden if STRUCTURE is changed as the result of ANSI or IBM OS/Standard label processing.

• CONSTANT and STRUCTURE

CONSTANT may be enabled as the result of STRUCTURE being changed to U in label processing. However, no definition is assumed for the constant string. The default must be zero, or it must be defined in the job descriptor entry. The LENGTH on a 4 by 3 packed format tape is the number of 6-bit bytes or characters in the record.

• LINE command, DATA parameter, and RECORD command LENGTH parameter When the DATA parameter of the LINE command is changed to a value greater than the default value, the LENGTH parameter of the RECORD command must also be changed accordingly. For online processing, print position indexing must not be used if LENGTH greater than 150 is specified.

• Online versus offline JDLs An offline JDL statement set that modifies the system default values, specifically in the BLOCK or RECORD commands, may experience incorrect results if running an online job (JDE). In other words, if an online job (JDE) is called out in an offline JDL that has changed the system default values (of the BLOCK and RECORD command parameters), the job may not print correctly. It is best, then, to separate and run online and offline jobs (JDEs) independently from each other.

A29247-X4-X-8-7672 43

Summary of RECORD Command Parameters Input Processing

Example

The RECORD command for the sample input record illustrated below would be coded as follows:

RECORD LENGTH=133, OFFSET=2, LTHFLD=2, PREAMBLE=4, ADJUST=4,

FORMAT=BIN;

LLnnPCC Data

(Block-LENGTH minus Block-PREAMBLE minus Block-POSTAMBLE) divided by Record LENGTH must be a whole number.

44 A29247-X4-X-8-7672

Input Processing Summary of TCODE Command Parameters

2.6 Summary of TCODE Command Parameters

The TCODE command defines a set of input-character-to-type assignments to be used for the masked string comparisons in a report. It must be used whenever it is not possible to use one of the standard sets of default type assignments without modification.

DEFAULT This parameter specifies an initial set of character type assignments for

use with masked comparisons. Default assignments for any standard character set may be specified by coding the appropriate keyword. The full set of assignments for any nonstandard (user-defined) character set may be specified by coding a value with an integer number ranging in value from 0 through 7. If a 0 is specified, all the characters are untyped; if a 1 is specified, all the characters are type 1; if a 7 is specified, all the characters are type 7. The initial set of type assignments may be modified by specifying the TASSIGN and TRESET parameters.

Parameter Definition(s) Offline Online DJDE

DEFAULT=

tcode-type

Available tcode-type keyword parameters are: ASCII EBCDIC

value

Initial typecodes are set to allow the following: all numeric characters (0-9) are type 1 characters, and all uppercase and lowercase alphabetic characters (A-Z, a-z) are type 2 characters. All other characters, if any, are untyped characters. There is no default.

YYN

A29247-X4-X-8-7672 45

Summary of VOLUME Command Parameters Input Processing

2.7 Summary of VOLUME Command Parameters

BMULT This parameter specifies a multiplication factor you can use to determine

true block length.

CODE This parameter specifies which code translation table the system uses

to interpret the input data.

EOV This parameter specifies the action the system takes when it encounters

an end-of-volume (EOV) on the input data tape.

HOST This parameter specifies the computer or host operating system gener-

ated the input data file.

INTERPRESS This parameter provides additional control over the interpress environ-

ment.

LABEL This parameter specifies the type of label on the input tape.

LCODE This parameter specifies the code translation table to use when inter-

preting the tape label.

LPACK This parameter specifies whether undefined labels (LABEL=UNDEF)

are packed or unpacked.

MAXLAB This parameter specifies the longest physical block treat as a label for a

undefined labels (LABEL=UNDEF).

MINLAB This parameter specifies the smallest physical block to treat as a label

for undefined labels (LABEL=UNDEF).

PLABEL Specifies whether the tape labels are to be printed.

RMULT This parameter specifies a multiplication factor the record length uses to

determine the true record length.

TCODE This parameter specifies the set of type assignments to use for masked

comparisons.

UNPACK This parameter specifies the unpacking method of the input data when

required.

46 A29247-X4-X-8-7672

Input Processing Summary of VOLUME Command Parameters

Parameter Definition(s) Offline Online DJDE

BMULT=

value

CODE=

keyword

value

Specifies a multiplication factor that you apply to the block length that you extract from the data block to determine the true block length. The value is an integer and can range from 1 (default) to 15 The default is 1.

keyword

Specifies a specific, standard, system-defined code translation table for data blocks. The available options are: ASCII EBCDIC NONE USER USER refers to the single unlabeled CODE command defined within the JDE or JDL. If you specify more than one CODE parameter, use identifiers so that they can be referenced in your JSL. You must then specify the variable identifier (id) to correspond to the identifier label assigned to the defining CODE command. The default is EBCDIC.

YNN

YYN

CODE=

Specifies a variable identifier you use in the CODE command to refer to a specific user-defined code translation table. The identifier id is required when multiple CODE commands are contained within the JDL.

CODE= NONE

NONE Specifies that data is not to be translated by input processing. Selecting CODE=NONE switch on the metacode interpreter. All code between X'00' and X'0F' are interpreted as control codes.

A29247-X4-X-8-7672 47

Summary of VOLUME Command Parameters Input Processing

Parameter Definition(s) Offline Online DJDE

EOV= ([PAUSE | NOPAUSE], [EOF | NOEOF])

This option has the following components: PAUSE Displays a message when EOV is encountered. A CONTINUE response by the operator causes the tape to rewind and the normal volume change sequence to proceed. NOPAUSE Issues a rewind instruction as soon as the EOV label is processed. EOF End-of-file. Specifies that the end-of-volume label is treated as an end-of-file label. When this occurs, the first part of the page spanning the volumes is output as the last page of the job. The second part of the spanned page is printed as the first page when the next volume is started, with possible page format irregularities. To use the EOF parameter effectively, special user-formatting of the multireel tapes is required to avoid these page format problems. NOEOF Specifies normal end-of-volume processing. The default is (NOPAUSE,NOEOF).

YNN

48 A29247-X4-X-8-7672

Input Processing Summary of VOLUME Command Parameters

Parameter Definition(s) Offline Online DJDE

HOST=

host-type

host-type label

Specifies one of the following options: IBMOS ANSI ANSI ANSI/NONE B2500 ANSI/STANDARD B2700 ANSI/STANDARD B3500 ANSI/STANDARD B3700 ANSI/STANDARD B4700 ANSI/STANDARD B6700 ANSI/STANDARD BARRPC NONE BS2000 ANSI/STANDARD IBMDOS NONE/STANDARD IBMONL NONE ICL2900 STANDARD UNDEF NONE EXOTIC NONE NCR STANDARD UNIVAC ANSI/NONE US70 STANDARD/NONE XSD NONE The default is IBMOS

YYN

LABEL=

label type

In the LCDS-Module this parameter is completely ignored

label type

Specifies one of the following options: NONE (the input tape is unlabeled) ANSI STANDARD (see also HOST=)

YYN

YNN

A29247-X4-X-8-7672 49

Summary of VOLUME Command Parameters Input Processing

Parameter Definition(s) Offline Online DJDE

LCODE=

keyword

LCODE=

LCODE= NONE

keyword

Specifies a specific, standard, system-defined code translation table for label blocks. The available options are: EBCDIC ASCII NONE USER USER refers to the single unlabeled CODE command allowed within the JDE or JDL. You must specify the variable identifier id to correspond to the identifier label assigned to the defining CODE command. The default is EBCDIC.

NONE Specifies that data is not to be translated by input processing.

YNN

LPACK= NO

LPACK= YES

MAXLAB=

value

NO Indicates that no unpacking operation is to be performed. If YES is specified, the UNPACK parameters specify the required unpacking method for both the labels and the input data. The labels do not have to be packed even though the data may require unpacking. The default is NO.

YES Indicates that the labels are packed.

value

Specifies in bytes the maximum length of the longest physical block which is to be considered a label. The value can range from 2 to 4096 bytes. The specified value must be greater than the MINLAB value and must not exceed the BLOCK LENGTH. The default is 81.

YNN

50 A29247-X4-X-8-7672

Input Processing Summary of VOLUME Command Parameters

Parameter Definition(s) Offline Online DJDE

MINLAB=

value

PLABEL= YES/NO

RMULT=

value

TCODE=

tcode-type

value

Specifies in bytes the maximum length of the smallest physical block. The value can range from 1 to 4095 bytes. The specified value must be less than the MAXLAB value and must not exceed the BLOCK LENGTH. The default is 80.

Specifies whether the tape labels are to be printed. If YES is specified, all tape labels (except those encountered during a volume change) are printed on an output page and delivered to the sample tray or output bin. Labels are truncated if they exceed the line width limits of the page. If NO is specified, no tape label printing results. The default is NO.

value

An integer from 1 to 15. The default is 1.

tcode-type

Specifies one of the following standard character sets for which type assignments are defined by default: ASCII EBCDIC By coding any one of the keywords, you are furnished with a set of character-to-type assignments.

YNN

YN -

YNN

YYN

TCODE=

tcode-id

Specifies an identified label of a TCODE parameter that defines a set of type assignments

UNPACK= NONE

NONE Does not perform the unpacking operation.

YNN

The default is NONE.

UNPACK= UNIVAC

UNIVAC Specifies an unpacking routine used for UNIVAC tapes, although you can specify any of these routines independent of the HOST type.

Points to note

Note the following when using the VOLUME command:

A29247-X4-X-8-7672 51

Summary of VOLUME Command Parameters Input Processing

Input data is translated according to the CODE parameter option selected on the VOLUME command. Any character which is translated into an ASCII X'20' is truncated after the last significant (non-ASCII X'20') character in the print record.

Examples

The following are sample VOLUME commands for several different host types:

VOLUME HOST=UNIVAC,LABEL=STANDARD,UNPACK=UNIVAC,

CODE=ASCII,LCODE=ASCII; VOLUME HOST=IBMOS; VOLUME HOST=IBMONL,LABEL=NONE,

CODE=EBCDIC; VOLUME HOST=B6700,LABEL=ANSI,BMULT=6,RMULT=6,

PLABEL=YES;

52 A29247-X4-X-8-7672

Input Processing Summary of VOLUME Command Parameters

Input source

Data to be processed by the printing system may originate from several sources. These sources are magnetic tape (offline processing), a host computer (online processing in 3211 and 4245 modes) and harddisks (import over the network via ftp).

Channel-attachment

An electronic printing system equipped with the online interface unit (OLI) may be attached to a byte multiplexer, block multiplexer, or selector channel of an IBM 370, system 300 or 4300 series, and 9370 models, or of an IBM system 390 ES/9000. The channel-attached system operates in one-byte, six-byte, eight-byte, or burst mode. No programming changes to the IBM operating system software are required, provided that an IBM 3211 printer and 3811 printer Control Unit is already supported on the host system.

A channel-attached LCDS-Module can receive input from the host computer in online 3211 mode. In online 3211 mode, the data stream emulates IBM 3211 line printer format, with or without embedded DJDEs.

Online 3211/6262 mode

Basic input processing functions are augmented by the following functions for online 3211 or 4245 mode operations:

• Handling of all interactions with the online interface (OLI) hardware.

• Building of translation tables based on the present contents of the universal character set buffer (UCSB) and the current FOLD or UNFOLD command in effect.

Online-specific commands

This section explains how to create a JDE or JDL, DJDE processing, online optimization and copy-sensitive copy modification entries (CME).

Creating a JDE or JDL

An online job descriptor library (JDL) and its job descriptor entries (JDEs) are created by the user according to the same rules and syntax as other entries. The one PDL command that must be specified for normal online processing is VOLUME HOST=IBMONL.

The HOST parameter of the VOLUME command performs two functions:

• Allows the electronic printing system to accept data from the online channel.

• Allows PDL to use a different set of defaults for the RECORD and LINE commands.

A29247-X4-X-8-7672 53

Summary of VOLUME Command Parameters Input Processing

The defaults which are automatically selected when VOLUME HOST=IBMONL is specified are as follows:

RECORD LENGTH=150; LINE PCCTYPE=IBM3211, (or IBM4245)

DATA=(0,150);

If ANSI carriage control commands are used in the host application program, the host operating system converts each command to a valid 3211 command before sending it to the printer. Any commands other than those listed are rejected by the online interface. Therefore, the only appropriate PCCTYPEs for an online JSL file is IBM3211.

Because the carriage control command is sent prior to - rather than as part of - the data record, offset to fields (such as DJDE prefix and font index) are typically one byte less for online than offline, where the carriage control byte is part of the data record. For the same reason, the online DATA parameter of the LINE command has a default offset of zero rather than one.

DJDE processing

Printing is controlled through parameters from the user-defined JDE file which may be dynamically modified by dynamic job descriptor entries. DJDEs are user created and processed by the electronic printing system as part of the print data from the host machine. The chapter "Specifying dynamic job descriptor entries (DJDEs)" defines their format and the PDL statements necessary to let the system know they are part of the input data.

Print-and-skip carriage control commands which are associated with online DJDE records are treated as skip-immediate carriage control commands. If the electronic printing system is not at the channel specified, a skip occurs; but if it is already there, no skip occurs unless the last command. Print-and-space carriage control commands associated with DJDE records are ignored.

Nonprint files (for example, font files) can be downloaded from the host using the FILE DJDE.

Copy-sensitive copy modification entries (CME)

Copy modification entries (CMEs) which are copy sensitive (that is, a copy range has been specified on the MODIFY parameter of the OUTPUT command) are ignored online since the data is not automatically available multiple times. To produce copy-sensitive output, the user transmits data the number of times the data needs to be modified. Thus, if six copies of a report are desired and one CME applies to copies 1 through 4, and another CME applies to copies 5 and 6, the report should be transmitted from the host system twice. The first transmission contains a copy count of 4 with CME1 specified, and the second transmission contains a copy count of 2 with CME2 specified. As an alternative, the application

54 A29247-X4-X-8-7672

Input Processing Summary of VOLUME Command Parameters

may be successfully printed with only one transmission by using copy-sensitive forms. Refer to the FORMS parameter of the OUTPUT command in the "Specifying output parameters" chapter.

Report separation

Report separation is defined in terms of banner page detection or other user-defined processing criteria. Logically separated reports are physically offset from one another in the output bins (depending on the attached post processing equipment). The two logical processing commands which can be used to control online report separation are BANNER and RSTACK. Refer to the chapter "Using logical processing commands".

Online record length

The default record length supported by the Océ laser printing systems is 150 bytes, the same default as the 3211/4245 printer. However, the you can choose to use larger record lengths with the following restrictions:

• For print record lengths from 151 bytes to 214 bytes, do not use the print position indexing feature that is normally available on the IBM 3211/4245. This feature is invoked only with FCBs; if FCB=IGNORE is invoked, this restriction is not significant.

• For print record lengths from 215 bytes to 512 bytes, the user must not use the OPTIMIZE parameter of the VOLUME command which provides for online buffering for improved performance.

To select a record length longer than 150 bytes, the user must specify the new value as the LENGTH parameter on the RECORD command and must also modify the DATA parameter of the LINE command to print the extended character or record length.

Points to note

• If the data record transmitted from the host exceeds the RECORD LENTH specified, the record is truncated to the specified record length and no warning is provided.

This action is consistent with the IBM 3211/4245 printer.

• The LENGTH parameter in the RECORD command cannot be changed using a DJDE since this would require dynamic re buffering. Therefore, you should consider modifications to the default online JDL to simplify operations in the online environment.

• The OPTIMIZE parameter of the VOLUME command can be changed through the DJDE JDE=subject to the restrictions listed in OPTIMIZE.

A29247-X4-X-8-7672 55

Summary of VOLUME Command Parameters Input Processing

Offline mode

For offline operations, the input medium to the printing system is magnetic tape, which may be recorded in one of a variety of standard vendor formats. As a programmer, you define the tape input deblocking and record format parameters that reduce physical tape blocks first to logical records, then to print lines. Special processing commands can also be selected that facilitate report processing by providing for logical functions to be performed on the input data described later in this chapter.

Before selecting the PDL commands that are to describe a specific job tape, certain tape structure concepts must be understood. These concepts, discussed in this chapter, enable the PDL programmer to define job tape characteristics such as host format, block/record structure, tape translation code, packed data formats, and several other parameters.

Packed data formats

Six-bit characters may be written onto a 9-track tape in a 4-by-3 packed (or compressed) format. That is, four 6-bit data bytes are compressed into three 8-bit data bytes. Two methods of packing these bits together exist. One method is used by Honeywell 6000 users (T4X3), while Honeywell 2000 users employ a slightly different method of packing (T4X3H2). Whenever an unpacking method is included in the JDL, the system unpacks the characters before data processing. Each 6-bit character is extracted, and two high-order zeros are appended. Normally, after data is unpacked, it must be translated. The character code set is defined in the CODE parameter of the VOLUME command. For a 4-by-3 unpacking method, the data is generally encoded in BCD, and one of the three standard BCD CODE parameters (H2BCD, H6BCD, and IBMBCD) can be used.

Record formats

All tape records input to the printing system are either blocked or unblocked with a fixed length, a variable length, or an undefined format. The PDL commands BLOCK and RECORD define the format of the input data. Tape label contents may also describe blocking and record structure and in some cases override BLOCK and RECORD commands specified in the JDL source file.

Record structure

A record is arbitrarily divided into two portions: operating system and user. The operating system portion of the record contains information supplied by the host operating or spooling system. The user's portion of the record contains information provided by the application or user's program running on the host system. The boundary between the two portions of the record is traditionally between the record length and printer carriage control (PCC) field. If

56 A29247-X4-X-8-7672

Input Processing Summary of VOLUME Command Parameters

there is no record length field, there is no operating system portion of the record. The PDL commands that define the components of a record are described in the "Input record characteristics - RECORD command" section of this chapter.

Multivolume processing

All multivolume reports that force input to make multiple passes over the data are handled in the following manner. For each copy requested, a complete pass is made over the group of volumes that make up the current report. The input processor is forced to make multiple passes over the input data for multicopy reports that specify copy-sensitive CMEs, and (optionally) for multicopy reports that exceed the size of the print file. CMEs are discussed in the "Copy modification entries" section in the chapter "Specifying output parameters".

If a multivolume report requires multiple passes, messages appear on the system controller display with instructions on which action must be performed next.

A29247-X4-X-8-7672 57

Summary of VOLUME Command Parameters Input Processing

58 A29247-X4-X-8-7672

Print Processing Summary of Print Format Commands

3 Print Processing

Print format commands serve many different functions, the most common of which specify the physical characteristics of a print job, define the placement of data on the page, and identify system responses to error conditions.

3.1 Summary of Print Format Commands

Command Function

ABNORMAL Specifies operations security and page offset on jam recovery.

ACCT User accounting.

CME Allows certain parts of report output to be replaced on copies with pre-

defined static data or to specify font changes within variable data.

LINE Controls margin, overprinting, carriage control, and so forth.

MESSAGE Sends message to operator during input or output processing.

OUTPUT Controls printing mode, forms, paper size and type, offsetting and out-

put destination.

PDE Defines page format (page orientation, fonts).

ROUTE Sends message and form for a routing page.

STOCKSET Defines a set of stocks used in a report.

VFU Defines vertical format control.

A29247-X4-X-8-7672 59

Summary of ABNORMAL Command Parameters Print Processing

3.2 Summary of ABNORMAL Command Parameters

The ABNORMAL command allows you to restrict certain operator functions and define system responses to error conditions.

ERROR This parameter specifies the required system response to abnormal

conditions detected in input processing or compiling DJDEs.

IMISMATCH This parameter specifies the action to take when a specified ink requires

a primary colour that is not currently loaded. The default is STOP.

ISUBSTITUTE This parameter specifies whether the operator is allowed to do an ink

substitution or not. The default is ANY.

OTEXT This parameter specifies that the system is to stop and display a WAIT

message when the recovery marker page is printed. This delay allows the operator to verify the output report in the near vicinity of the marker page. The default is NOWAIT, which means that the message is still displayed upon printing of the marker page, but printing does not stop.

Parameter Definition(s) Offline Online DJDE

ERROR= CONTINUE

ERROR= ABORT

ERROR= STOP

CONTINUE Displays the normal system message defining the abnormal condition and continues processing the report without applying the offending DJDE parameter and without offering the operator the choice of continuing or aborting the job.

ABORT Displays the message for the abnormal condition and aborts only the report it is processing (not the entire job) without offering the operator the choice of continuing or aborting the job.

STOP The default for this parameter and indicates that the system stop processing the report and wait for the operator to respond with a CONTINUE or ABORT command. The default is STOP.

YYN

60 A29247-X4-X-8-7672

Print Processing Summary of ABNORMAL Command Parameters

Parameter Definition(s) Offline Online DJDE

IMISMATCH= STOP

IMISMATCH= ABORT

IMISMATCH= CONTINUE

STOP Stops processing the current report or job and waits for the operator to respond with the ABORT command or to load the requested primary colour followed by the CONTINUE command. If ISUBSTITUTE = ANY is specified the operator may enter a SUBSTITUTE INK command instead of loading the required colour. Restriction: This option is gracefully ignored and processed like IMISMATCH=CONTINUE. Restricted implementation: see 6.3.2.

ABORT The current report (not the entire job) is aborted without offering the operator the choice of continuing or aborting the job. Restriction: This option is gracefully ignored and processed like IMISMATCH=CONTINUE. Restricted implementation: see 6.3.2.

CONTINUE The currently loaded primary colour is used ignoring the ISUBSTITUTE parameter or the FDL INKS NOSUBSTITUTE parameter.

YYN

ISUBSTITUTE= ANY

ANY The operator is allowed to enter any SUBSTI-

YYN

TUTE INK command. Restriction: This option is gracefully ignored, because The LCDS-Module doesn't offer any SUBSTITUDE command. Therefore this option is processed like ISUBSTITUDE=ANY. Restricted implementation: see 6.3.2.

ISUBSTITUTE= NONE

NONE The operator is not allowed to enter any SUBSTITUTE INK command. The operator may CONTINUE the report without substitution or ABORT the report.

A29247-X4-X-8-7672 61

Summary of ABNORMAL Command Parameters Print Processing

Parameter Definition(s) Offline Online DJDE

Hint: This option is to be seen in context with IMISMATCH. In this version of the LCDS-Module doesn't exist a SUBSTITUDE command, because it is meaningless with IMISMATCH=CONTINUE. Restricted implementation: see 6.3.2.

OTEXT= WAIT

OTEXT= NOWAIT

WAIT Displays an OTEXT message but the WAIT is ignored. WAIT is treated like NOWAIT.

Displays an OTEXT message but printing does not stop. The default is NOWAIT.

YYN

62 A29247-X4-X-8-7672

Print Processing Summary of ACCT command parameters

3.3 Summary of ACCT command parameters

The ACCT command allows the user to print an account page or to omit the printout of an account page at the end of each report. Using this command, different entries in the general PRISMA accounting reports can be updated. For more information on PRISMA accounting reports refer to the Administrator's Guide, chapter "Accounting".

The parameters of the ACCT statement are:

DEPT Accumulation of user accounting statistics.

USER Output destination of accounting pages within a report.

Parameter Definition(s) Offline Online DJDE

DEPT=sc sc

is a string constant of up to 31 characters representing a department code or name under which accounting information will be maintained. sc is stored in account record type 1200 (see Administrator's Guide)

USER= BIN|TRAY| BOTH|NONE

Specifies destination of the one page accounting summary for each report. BIN Directs the accounting page to the output tray. TRAY same as BIN. BOTH same as BIN. NONE works for Start-JSL only. It cannot be changed via DJDE JDL=switch. This restriction is due to the fact, that LCDS account data are printed on the SPS trailer page. Thus the USER parameter switches SPS header & Trailer pages on or off. To use this feature "INFOPagesFix=NO)" has to be set in LCDS Jobs (PrintLCDS).

yyy

A29247-X4-X-8-7672 63

Summary of ac:CME Command Parameters Print Processing

3.4 Summary of ac:CME Command Parameters

The copy modification feature (also referred to as spot-carbon) allows certain parts of report output to be replaced on selected copies with predefined static data or to specify font changes within the variable data.

CMEs define a rectangular space on the printed page within which printed data is replaced with a substitution string or in which a font change occurs. More than one CME may be applied to a job. CMEs may be coded as part of the JDL or created as separate files so that they may be referenced by one or more JDLs. This latter feature is described more fully in the "Cataloged CMEs” section of this chapter.

An identifier (of the type ac) is specified when defining the CME and references it with the MODIFY parameter of the OUTPUT command. The CME must precede the OUTPUT command.

Cataloged CMEs

CMEs need not be part of a user’s JDL. They may be created as separate disk files and used as if they were part of the JDL that references them. This is done by creating a JSL file containing only CMEs and using the PDL processor to compile it. For each CME, PDL creates an object file on disk. The CME identifier is used as the object file name. When a CME source file is modified, it must be recompiled with PDL, but it is not necessary to recompile the associated JDLs.

When the CME is referenced by the OUTPUT command MODIFY parameter in a JDL (Modify=xxxx.CME) and the CME does not exist within the JDL, the system searches the directory for the file type xxxx.CME. It is then loaded into memory for use in processing the report.

The DJDE MODIFY parameter can also be used dynamically to associate a catalogued CME file with report processing. CMEs must be cataloged as separate disk files if they are referenced by a DJDE MODIFY command.

CONSTANT This parameter specifies a string constant to be printed.

FONTS This parameter specifies an index into the font list (PDE command or

DJDE) for font switching on input data or CME data. A PDE command is selected by the FORMAT parameter of the OUTPUT command.

INK This parameter specifies an index into the ink list (IDR command or DJDE)

for ink switching on input data or CME data. An IDR command is selected by the IDR parameter of the OUTPUT command. The default is 0.

LINE This parameter specifies the line range of the CME.

POSITION This parameter specifies the initial character position of the CME in the

print line.

64 A29247-X4-X-8-7672

Print Processing Summary of ac:CME Command Parameters

Parameter Definition(s) Offline Online DJDE

CONSTANT=scsc

Represents the string constant to be printed for definition of string constants). The width of the copy modification rectangle is determined by the number of characters specified by sc. More than one sc is allowed. There is no default.

FONT=

value

May range from 1 to n, where n is the number of different fonts specified by the FONTS parameter of the PDE command. A value of 1 specifies the first font in the FONTS parameter, 2 the second, and so forth. There is no default.

INK=

value

May range from 1 to n, where n is the number of different inks specified by the ILIST parameter of the IDR command. A value of 1 specifies the first ink in the ILIST parameter, 2 the second, and so forth. The default 0 may also be specified, it instructs the system to use the original ink, that is the ink used in the report prior to that modified by the CME. Only a reference to a primary colour is allowed.

LINE= {n | (n,m) | (n,-)}

This option has the following components:

The initial line number of the copy modification rectangle

The number of lines to repeat the information. If not specified, the information applies only to the starting line.

A dash character indicates that information is to apply to all lines on a page beginning with the line indicated by n. There is no default.

YYN

POSITION=

n An integer value between 1 (the first position of the print line) and the value specified by the length rightpart of the DATA= parameter in the LINE command. The default is 1.

A29247-X4-X-8-7672 65

YYN

Summary of ac:CME Command Parameters Print Processing

3.4.1 Points to note

Note the following when using the CME command:

The CME LINE and POSITION parameters are order dependent in that LINE must always precede POSITION.

Data lines

Data lines are not properly aligned if proportional fonts are being used in landscape mode and a switch is made to a larger font in the middle of the line. This restriction is a result of the functioning of the printer imaging hardware.

Multiple copies

If a multicopy is aborted before all the pages are set up in the page log, one copy gets printed if the CMEs are copy-sensitive. Otherwise, all copies of the setup pages are printed.

OVERPRINT, FONTINDEX, and CMEs

CMEs are not applied if OVERPRINT=MERGE and FONTINDEX are both specified.

CME parameters are applied to all lines within the range regardless of whether or not variable data appears on those lines.

Multiple lines and columns

Multiple lines may be specified and multiple columns may be specified for each line. Multiple line specifications must be given in ascending (top to bottom of page) order. Multiple column specifications for a line range must be given in ascending (left to right) order. There also may be multiple text specifications following a column specification. These are combined to form a single text string. Font and ink specifications may be specified at any point. The last font and ink specified remains in effect until another font or ink is specified.

An example for a CME with these characteristics is as follows:

XYZ: CME LINE=(1, 10), POS=40, FONT=2, POS=80, FONT=3, LINE=(11, 20), POS=1, INK=1, FONT=3, POS=40, FONT=1, POS=80, FONT=2, LINE=(31, 50), POS=1, FONT=2, POS=40, FONT=3, INK=2, POS=80, FONT=1;

66 A29247-X4-X-8-7672

Print Processing Summary of ac:CME Command Parameters

Form and variable data

Under certain circumstances, a form and its associated variable data do not align properly, even though it appears that both use the same line spacing. Variable data has a line-spacing value that is computed as dots per line, and rounding is done on that value. In FDL, the rounding takes place only when it is needed to resolve to a dot address and, therefore, might involve more than one line at a time.

CME string constant

Whether a font switch is applied to a CME string constant depends upon the order in which FONT and CONSTANT are specified in the CME. If FONT is specified before CONSTANT, the font switch applies to the string constant. If FONT is specified after CONSTANT, the font switch occurs at the line position immediately after the string constant.

Where a CME string constant is printed on a line depends upon where the POSITION and CONSTANT parameters are specified in the CME. If POSITION is specified before CONSTANT, the string constant is printed at the specified position. If POSITION is specified after CONSTANT, the string constant is printed at the current position (position 1 if no other POSITION or CONSTANT parameter has been specified), and a subsequent CONSTANT or FONT parameter will take effect at the specified POSITION.

3.4.2 Examples

This section shows two examples of using the CME command.

Example 1

The following is an example of copy-sensitive CMEs.

CME1: CME LINE=3, POS=59, CONSTANT=‘FIRST QUARTER’; CME2: CME LINE=(37,3), POS=81, CONSTANT=(6)’*’; CME3: CME LINE=(1,60), POS=5, FONT=2, INK=3, POS=12, FONT=1;

OUTPUT COPIES=3, MODIFY=(CME1,1,1), MODIFY=(CME2,2,1), MODIFY=(CME3,3,1);

For the first copy of the report, line 3 is modified by the text 'FIRST QUARTER'. For the second copy, the character ‘*’ is inserted in lines 37, 38, and 39 for 6 character positions (starting in column 81). For copy 3, fonts are changed for lines 1 to 60 at character positions 5 and 12. These fonts must be defined in the FONTS parameter of the PDE command.

Copy-sensitive CMEs are not supported for online processing or when COLLATE=NO is specified in the OUTPUT command.

A29247-X4-X-8-7672 67

Summary of ac:CME Command Parameters Print Processing

Example 2

CME parameters specified in standard form:

CME12: CME LINE=47, POSITION=1, FONT=5, CONSTANT=(5)'*', LINE=48, POSITION=1, FONT=1; LINE=49, POSITION=10, CONSTANT='ABCD'I2;

CME parameters specified in short form:

CME12: CME L47,P1,F5,(5)'*',L48,P1,F1,I2,L49,P10,C'ABCD';

CME12: CME L47P1F5(5)'*'L48P1I3F1L49P10'ABCD';

68 A29247-X4-X-8-7672

Print Processing Summary of IDR Command Parameters

3.5 Summary of IDR Command Parameters

The IDR command defines a default ink catalog, ink palette and ink list. An IDR may be coded as part of a JDL or in a separate disk file. An identifier label (ac:) has to be applied to the IDR command, so the syntax is: ac: IDR ...

The IDR command is referenced by the IDR parameter of an OUTPUT command or is called by a DJDE.

For the IDR command at least the ILIST parameter has to be specified. When processing an ink-reference the following rules will be valid: If ICATALOG is not specified the ink-catalog named DFAULT will be used. If PALETTE is not specified the palette named DFAULT will be used. In case of using the ink-catalog named XEROX1 an ink-palette has to be specified too, because the ink-catalog XEROX1 does not contain an ink-palette named DFAULT. Refer to chapter 1.8.2.3 (ink-references). For restricted implementation see 6.4.1 INK Catalogs.

ICATALOG This parameter specifies the default ink catalog to be used in ink refer-

ences without a specific catalog reference.

PALETTE This parameter specifies the default ink palette to be used in ink refer-

ences without a specific palette reference.

ILIST This parameter provides a list of all inks which may be referenced by in-

dexing in printing variable data or CME data. Only primary colours are allowed. The maximum number of inks in an ink list is 64.

Parameter Definition(s) Offline Online DJDE

ICATALOG= 'DFAULT' | 'XEROX' | 'XEROX1' | 'SDFLT$'

PALETTE=

palette

ICATALOG Specifies the default ink-catalog. It is used when the actual ink-reference does not supply an ink-catalogname. The XEROX1 entry is gracefully ignored while compiling the XDL but rejected during print data processing. SDFLT$ is gracefully ignored. For restricted implementation see 6.2.3.

palette

Specifies the default ink-palette. It is used when the actual ink-reference does not supply an ink-palettename.

YYY

A29247-X4-X-8-7672 69

Summary of IDR Command Parameters Print Processing

Parameter Definition(s) Offline Online DJDE

ILIST= ink-name | (ink-name [, ink-name] [, ink-name][, ...])

ink-name

Specifies a list of ink-names. One of those inks in this ink-list is used when an ink-reference consists of a numerical ink-index which points into the ink-list. Only primary colours are allowed in this list. Because of the restricted ILIST implementation there exists an extended default processing which results in either 'alternate colour' or 'black'. For restricted implementation see 6.3.1 Inklist.

YYY

70 A29247-X4-X-8-7672

Print Processing Summary of LINE Command Parameters

3.6 Summary of LINE Command Parameters

The LINE command provides parameters which allow the user to define the characteristics of the user portion of the input data record and how it is to be printed.

DATA This parameter specifies the location and length of the print line data with-

in an input data record.

FCB This parameter specifies whether to suppress or accept the processing of

the host transmitted forms control buffer (FCB).

FONTINDEX This parameter specifies that a field within a user data record defines the

index to a specific font to be used for that line. If FONTINDEX is not specified, none is used.

INKINDEX This parameter specifies that a field within a user data record defines the

index to a specific ink to be used for that line. If INKINDEX is not specified, NONE is used.

MARGIN This parameter specifies the left margin on a physical page.

OVERPRINT This parameter specifies the manner in which overprint lines are handled.

(Overprint lines are print lines whose carriage control specifies printing with no line spacing since the last printed line.)

PCC This parameter specifies the position (and possible translation) of the

printer carriage control field.

PCCTYPE This parameter specifies a carriage control set used in printing a job.

VFU This parameter specifies the vertical format buffer.

Parameter Definition(s) Offline Online DJDE

DATA= (pdo, length)

FCB= IGNORE

This option has the following components:

pdo

(Print data offset) is the number of bytes between the start of the user portion of the logical record and the first character of the record to be printed.

length

Specifies the maximum length of printable data within each logical record. For offline systems the default is (1,132). For online systems the default is (0,150). The default is (1,132) offline. The default is (0,150) online.

IGNORE Suppresses the processing of the host transmitted forms control buffer (FCB).

YYY

NYN

A29247-X4-X-8-7672 71

Summary of LINE Command Parameters Print Processing

Parameter Definition(s) Offline Online DJDE

FCB= PROCESS

FONTINDEX= {offset | (offset [,init-val][,bit- opt]) | NONE}

PROCESS FCB in 3211 Format processed

Allows the user to specify a certain location in the input record where an index to the font to be used is stored. It takes effect on the next logical page boundary. This option has the following components:

offset

Indicates the byte offset in the data record where the font index number is to be found.

init-val

Can be one of the following: ONE or ZERO. ONE specifies that an index value of 1 is associated with the first font in the font list. When the bit-opt parameter is used, the init-val ONE parameter must also be used. ZERO specifies that an index value of 0 is associated with the first font in the font list, an index value of 1 is associated with the second font in the font list, and so forth. The default is ONE.

bit-opt

A numeral having a value in the range of 1 through 7, which specifies the number of low-order bits within the font index byte, which, in turn, specifies an index value into the font list of the current PDE. The default value is 4. If init-val is ONE or is not specified, the value of the font index byte in the data record is a number in the range 1 to n, where n is the number of fonts specified in the PDE parameter (1 to 127). If ZERO is specified, the font index is a number in the range 0 to n, where n is the number of fonts specified in the PDE parameter minus one (0 to 127). The font index value must be present in every record. If the FONTINDEX in the data record is greater than the number of fonts specified, the first font in the list is used.

YYY

FONTINDEX=NONE

NONE Specifies that there is no font index. The default is NONE.

72 A29247-X4-X-8-7672

Print Processing Summary of LINE Command Parameters

Parameter Definition(s) Offline Online DJDE

INKINDEX= offset | (offset[, init-val] [, bit-opt])

Allows the user to specify a certain location in the input record where an index to the ink to be used is stored. It takes effect on the next logical page boundary. This option has the following components:

offset

Indicates the byte offset in the data record where the ink index number is to be found.

init-val

Can be one of the following: ONE or ZERO. ONE specifies that an index value of 1 is associated with the first ink in the ink list. When the bit-opt parameter is used, the init-val ONE parameter must also be used. ZERO specifies that an index value of 0 is associated with the first ink in the ink list, an index value of 1 is associated with the second ink in the ink list, and so forth. The default is ONE.

bit-opt

A numeral having a value in the range of 1 through 7, which specifies the number of low-order bits within the ink index byte, which, in turn, specifies an index value into the ink list of the current PDE. The default value is 4. If init-val is ONE or is not specified, the value of the ink index byte in the data record is a number in the range 1 to n, where n is the number of inks specified in the PDE parameter (1 to 127). If ZERO is specified, the ink index is a number in the range 0 to n, where n is the number of inks specified in the PDE parameter minus one (0 to 127). The ink index value must be present in every record. If the INKINDEX in the data record is greater than the number of inks specified, the first ink in the list is used.

YYY

INKINDEX= NONE

NONE Specifies that there is no ink index. The default is NONE.

A29247-X4-X-8-7672 73

Summary of LINE Command Parameters Print Processing

Parameter Definition(s) Offline Online DJDE

MARGIN= {value | (value,value- type)}

OVERPRINT= PRINT | IGNORE | MERGE | PRINT2

This option has the following components:

value

The form nnn.mm (a positive decimal number with up to 2 digits to the right of the decimal point) which is the distance from the left margin.

value-type

Indicates whether a value is specified in inches (IN), centimeters (CM), or character positions (POS). A value must be specified as an integer (nnn), if a value-type is character positions. The default is (1,POS).

Specifies the manner in which overprint lines are handled. (Overprint lines are print lines whose carriage control specifies printing with no line spacing since the last printed line.). PRINT Specifies that all overprint lines are to be printed as they would be on an impact printer; that is, the second line is printed over the top of the first with no regard to the previous data, including character spacing, which may vary between the two lines of data. IGNORE All overprint lines are ignored. MERGE MERGE is the same as PRINT except when used with FONTINDEX or CME processing. PRINT2 Specifies that up to two consecutive lines will be printed per line - one line and one overprint. Other overprints for the line will be ignored. The default is PRINT. PRINT2 & IGNORE are treated as PRINT.

YYY

YYN

74 A29247-X4-X-8-7672

Print Processing Summary of LINE Command Parameters

Parameter Definition(s) Offline Online DJDE

PCC= (offset,trans- type)

This option has the following components:

offset

Specifies the byte offset of the user portion of the record within each logical record to the printer carriage control (PCC) field. 0 is the default.

trans-type

Options NOTRAN/TRAN specify whether or not the printer carriage control byte is to undergo code translation. TRAN indicates that the byte is to be translated into LCDS-Module standard EBCDIC before being applied, using the translation defined in the CODE parameter of the VOLUME command. NOTRAN (the default) prohibits translation. If in the VOLUME statement CODE=EBCDIC is defined, a TRAN is automatically replaced by a NOTRAN by the LCDS compile function. The replacement is documented by an appropriate warning message during compiling the JSL. The default is (0,NOTRAN).

YNN

A29247-X4-X-8-7672 75

Summary of LINE Command Parameters Print Processing

Parameter Definition(s) Offline Online DJDE

PCCTYPE=

pcc-name

Options are: ANSI ASA B2500 B2700 B3500 B3700 B4700 B6700 IBM1401 IBM1403 IBM3211 IBM4245 NCR ICL SNI UNISYS US70 XEROX NONE Creation of a user-defined PCC table referenced by either an identifier id or the keyword USER is defined using the PCC command. Refer to the ”PCC command” section in this chapter. For offline systems the default is ANSI

. For online systems the default is IBM3211. Note that there is no functional difference between IBM3211 and IBM4245 for PCC types. For IBM 4248 or IBM 6262 you can use IBM 3211 PCC tables. The INITIAL parameter for any selected PCCTYPE (except ANSI or USER, and id) is TOF. For ANSI the INITIAL parameter is BOF. For USER or id the INITIAL parameter is set by the user in the PCC command. The ADVTAPE parameter (refer to PCC parameter in this chapter) for any selected PCCTYPE (except IBM1403, IBM3211, USER, and id) is YES. For IBM1403 and IBM3211/IBM4245, ADVTAPE is set to NO. For USER or id the ADVTAPE is set by the user in the PCC parameter.

YYN

76 A29247-X4-X-8-7672

Print Processing Summary of LINE Command Parameters

Parameter Definition(s) Offline Online DJDE

The default is ANSI for offline. With PCCTYPE=XEROX no special page overflow functions are supported. The default is IBM3211/IBM4245 for online.

VFU=

vfu-id

VFU= NONE

3.6.1 Points to note

Note the following when using the LINE command:

FONTINDEX

Although the maximum bit-opt value may be 7 (allowing a maximum font index value of

127), the maximum number of fonts is constrained by font memory size.

FONTINDEX and OVERPRINT

vfu-id

The command identifier of the VFU table, which must precede this reference to it. (Refer to the ”Defining print line positions” section.) The VFU table defines print line positions corresponding to skip-to-channel parameters for the job to be processed.

NONE Indicates that any skip-to-channel parameter is to be replaced by a carriage control of print and space 1. The default is NONE.

YYN

FONTINDEX, used in conjunction with overprinting, is handled as follows: For OVERPRINT=PRINT, the LCDS-Module overprints records analogously to an impact printer if the fonts are the same size. If the fonts differ, records are overprinted without regard to character spacing. For OVERPRINT=MERGE, the LCDS-Module replaces characters in the previous record which are blank. Character spacing values are adjusted; thus proportionally spaced or different size fonts may be used, and the LCDS-Module performs the character placement.

Characters in the previous record which are blank are replaced only when they are represented by an EBCDIC X40 or an ASCII X20. Binary character representations other than an EBCDIC X40 or an ASCII X20, which produce a blank character when printed with a particular font, is not replaced except in the following case. During input processing, when a binary character representation is greater than the highest character in the specified font, a blank (EBCDIC X40 or ASCII X20) is substituted into that print position. (A sample of the specified font shows the highest binary character representation.) In this case, the LCDSModule replaces this character since it is now an EBCDIC X’40’ or an ASCII X’20’ blank.

A29247-X4-X-8-7672 77

Summary of LINE Command Parameters Print Processing

If FONTINDEX and OVERPRINT=MERGE are specified and proportional fonts are being used, data lines are not properly aligned if printing in landscape mode, and the data switches to a larger font in the middle of the line.

Multiple fonts

When multiple fonts of various sizes are used on a single page, the line spacing of any particular line is determined by the largest font in use in the previous line. The current line can also be adjusted downward by the difference in height between the first and the largest font in the current line. The line spacing of the first line in a report is determined by the first font in the PDE, provided the FONTINDEX parameter has not been specified. When FONTINDEX is specified, the line spacing of the first line of a report is determined by the font indicated by the font index value in the first line of the report. If there is no font index value in the record and FONTINDEX is specified, the line spacing for the first line of the report is determined by the first font in the PDE. When the FONTINDEX or CME parameters are specified, the line spacing of the first line of subsequent pages is determined by the line spacing of the font called out by the last font index of the previous page into the current PDL font list. If a PDE DJDE has occurred prior to the page transition, the font used for the line spacing comes from this list.

The height of the last font used determines the initial base line of that first print line.

The FONTINDEX byte, if selected, is processed for every record, DJDEs, RPAGE, and all criteria records. A valid FONTINDEX byte should be present in all records since it controls line spacing and override line spacing at page transitions.

Font index and ink bytes

It is advisable to put the font index byte in the beginning of a variable record to conserve tape space. The byte must be present in every record.

If the offset to the font index value exceeds the logical record size, the first font in the font list is used, except when HOST=UNIVAC is specified. If HOST=UNIVAC is specified, the byte located at the specified font index offset is processed. The font index byte must be located at the beginning of the record if Univac Fielddata and ASCII records are intermixed within the file.

Print line data

When changing the print line data to a value greater than the default value (150), the LENGTH parameter of the RECORD command must also be changed accordingly. (Refer to the "RECORD command” section of the chapter "Specifying input parameters”.)

78 A29247-X4-X-8-7672

Print Processing Summary of LINE Command Parameters

PCCTYPE

The PCCTYPE=IBM3211/IBM4245 is not intended to be used when processing offline jobs. Checks that the LCDS-Module online interface performs, such as for bad or NO-OP parameters, are not done in the offline mode. There is no check for bad or NO-OP parameters, and they are treated as undefined carriage control parameters in the offline mode and default to the carriage control parameter of print-and-space-1-line.

3.6.2 Examples

This section shows examples of using the LINE command.

Example 1

LINE DATA=(1,132),PCC=(0,NOTRAN),PCCTYPE=IBM1403,FONTINDEX=133, INKINDEX=134;

The print-data-offset parameter of the DATA parameter (the number of bytes between the start of the user portion of the record and the first character of the record to be printed) is 1 byte. The print-length parameter (the number of characters in the longest print line in the record) is defined as 132 bytes. The carriage control is defined as IBM1403, and the position of the carriage control character is the first byte within the user portion of the record. The position of the font index (an index value into a font list that indicates which font is to be selected) is byte 133 (relative to 0).

Example 2

LINE PCCTYPE=NONE,DATA=(1,60),VFU=V1;

Example 3

LINE PCCTYPE=NONE,DATA=(1,57),VFU=V1;

A29247-X4-X-8-7672 79

Summary of MESSAGE Command Parameters Print Processing

3.7 Summary of MESSAGE Command Parameters

The MESSAGE and ROUTE commands permit the user to inform the operator of special conditions. The MESSAGE command displays user-defined text to the operator.

ITEXT This parameter specifies a text message to be output to the operator dur-

ing input processing.

OTEXT This parameter specifies a text message to be output to the operator dur-

ing job printing.

Parameter Definition(s) Offline Online DJDE

ITEXT= NONE

ITEXT=

passnum

OTEXT= NONE

OTEXT=

passnum

NONE Specifies that no text message is output to the operator during input processing. The default is NONE.

Specifies a text message of up to 80 characters.

passnum

Specifies the pass (copy ply) to which the message text applies. The message is output to the operator just before processing of the indicated pass (copy ply) is begun. If no pass number is specified, the indicated message is output at the beginning of the first pass.

NONE Specifies that no text message is output to the operator during job printing. The default is NONE.

Specifies a text message of up to 80 characters (maximum of 400 characters per report).

passnum

Specifies the pass (copy ply) to which the text applies. Multiple sc messages, one per pass-num, may be specified in a JSL. The message is output to the operator prior to the beginning of printing the specified report ply. If no pass number is specified, the text is output once at the beginning of printing the entire report.

YYY

80 A29247-X4-X-8-7672

Print Processing Summary of MESSAGE Command Parameters

Parameter Definition(s) Offline Online DJDE

OTEXT= WAIT

OTEXT= END

WAIT Specifies that after the text is displayed, printing is suspended until the operator has responded with a CONTINUE parameter.

END Specifies that the text is displayed after the last copy of the report is printed.

A29247-X4-X-8-7672 81

Summary of OUTPUT Command Parameters Print Processing

3.8 Summary of OUTPUT Command Parameters

The OUTPUT command controls the organization and format of a report. This includes controls of the number of copies of a report, the forms to be printed with the variable data, report offsetting, and the use of simplex or duplex mode. Many graphics features may be invoked with this command.

BFORM This parameter prints a form on the back side of a duplex data page. In

association with the duplex printing mode DUPLEX=YES, a page containing only a form (no variable data can be printed with this page) may be printed on the back side of a user page. This feature can be used to print static data on the back of each page in a report without the use of DJDEs or the repetitive processing of that data. Different forms may be associated with different copies of a report by the use of multiple BFORM left parts on the same OUTPUT command. If BFORM specifications include some, but not all, copies of a report, those copies not included have blank back sides, that is, no form.

COLLATE This parameter specifies whether pages are to be collated or uncollated.

COPIES This parameter specifies the number of report copies to be printed.

COVER This parameter specifies that cover pages are to be picked from the AUX

cluster. These cover pages may be placed at the front or back of each copy of report. The cover will be printed on the normal paper for CFprinters

CYCLEFORMS This parameter specifies a set of forms to be associated with report pag-

es in a cyclical fashion. Refer to the examples at the end of this section.

DUPLEX This parameter specifies whether printing is to occur in duplex (Print on

both sides of a sheet) or simplex (print on a single side).

FACEUP This parameter specifies faceup delivery of pages.

FEED This parameter controls the stock on which the page is printed. For fan-

fold printers there is only one stock, for cutsheet printers different stocks can be selected.

FORMAT This parameter specifies a page descriptor entry (PDE) to be used in for-

matting the printed output, such as location of starting print line for each logical page on the physical page, font usage, and page orientation.

FORMS This parameter specifies forms to be associated with the report copies.

Different forms may be associated with different copies of a report by the use of multiple FORMS left parts on the same OUTPUT command.

GRAPHICS This parameter specifies how graphics are to be processed in a job.

82 A29247-X4-X-8-7672

Print Processing Summary of OUTPUT Command Parameters

IDFAULT This parameter specifies the default ink for objects with no ink specified

by themselves.This parameter is in effect until another IDFAULT parameter is given.

IDR This parameter is a reference to a previously defined IDR command. It

specifies an ink list to be used in conjunction with ink indices specified in the actual OUTPUT command. The first ink in the ILIST parameter of the IDR will be the default ink for the current job unless it is overridden by an IDFAULT parameter.

IMAGE This parameter specifies, for batch mode processing only, the initial

graphic imaging parameters to be used.

INVERT This parameter allows to define the rotation of a page relative to what is

called “Page origin from the users point of view”. A page can effectively be rotated 180° - head-to-head and head-to-toe.

IRESULT This parameter specifies the printing result for pixel areas where two ob-

jects with different colours overlap. BLACK specifies that black is printed, COLOUR specifies that highlight colour is printed. In the LCDS-Module this parameter is ignored. Since our printers have two distinct print systems for black and highlight colour working subsequently overlapping pixel areas will always be printed with both colours.

LOGO This parameter specifies logos to be associated with all pages of a re-

port. Up to 128 logos may be associated per page. This parameter only works on a per-page base, it is not copy-sensitive.

MODIFY This parameter specifies CMEs to be associated with report copies.

NTO1 Specifies, on a report basis, whether all copies of a particular report are

printed last page first (n-to-1)

NUMBER This parameter specifies page numbering on the output pages of a re-

port. The page number character string is placed on the page at the specified line number based on the line spacing of the specified font. If override line spacing is specified for the font, it does not affect where the page number character string is to be printed.

OFFSET This parameter specifies offset control on a report basis.

PAPERSIZE This parameter specifies the paper size to be used for printing the job.

SHIFT Image shift is the shifting of the image data (system page) relative to the

physical page. This shifting is in the scan counting direction (vertical for landscape and horizontal for portrait). The SHIFT parameter specifies whether the image of the form and data on a page is to be shifted, and if so, by what values. This parameter is used to shift the image on the data in the y-direction for three-hole paper, binding, finishing, and edgemarking.

A29247-X4-X-8-7672 83

Summary of OUTPUT Command Parameters Print Processing

STAPLE This parameter specifies if a report should be stitched or not assumed

the printer is capable to stitch.

STOCKS This command defines the STOCKSET and it’s associated stock(s) to

be used in a report.

UNITS Defines the dot size of a unit used for specifying the position of a graphic

when referenced by the IMAGE parameter on the OUTPUT command or an IMAGE, ALTER, or GRAPHIC DJDE parameter.

XMP This parameter relates to the specific Xerox printing hardware. In the

LCDS-Module it is ignored.

Parameter Definition(s) Offline Online DJDE

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

form-id

Specifies a one-to-six character file name (may be numeric, alpha, or alphanumeric) which exists on disk. This file is created by compiling a forms description language source file, which is called an FSL file, with the FDL system task). A form-id may be the keyword NONE.

init

If the copies parameter is not defined, the last (or only) form specified will apply to all copies beginning with copy number init. If the form is not the last one specified, copies defaults to 1. If neither init nor copies are specified, the form applies to all copies of the report. Note that init copies is only valid offline.

copies

Specifies the number of plies (passes) to which a specified form applies.

inkref

Identifies the inks that override the corresponding inks specified in the ink list of the form. If the form does not contain an ink list, the form is printed in black. If one inkref in the ink list is omitted, commas must be used to maintain the relative positioning of the remaining ink references. If more inkrefs are specified than contained in the ink list of the form, the extra inkrefs are ignored. Inkrefs may be entered as ink names or as numeric ink indices using an inklist specified by an IDR ILIST parameter which is referenced by an IDR parameter in the same OUTPUT command. Only references to primary colours are allowed.

YYY

84 A29247-X4-X-8-7672

Print Processing Summary of OUTPUT Command Parameters

Parameter Definition(s) Offline Online DJDE

BFORM= NONE

COLLATE= YES

COLLATE= NO

COPIES=

number

COVER= NONE

NONE Specifies that no form is to be added to the associated report page of variable data. A init parameter specifies the beginning ply (pass) number to which a specified form applies. This defaults to the first or next copy. The default is NONE.

YES Specifies that the output pages are collated The default is YES.

NO Specifies that the output is not collated.

number

An integer value with range 0 to 32767. For the copies DJDE parameter, a value of 0 may be specified for the DJDE COPIES parameter, in which case no copies are printed. The copies parameter on the START command allows an operator to override this parameter when initiating a print job. The default is 1.

NONE Specifies that no cover pages are to be printed. The default is NONE.

YYY

YYN

COVER= FRONT

FRONT Specifies that a cover page is to be printed at the front of each copy and is the first page of the copy.

COVER= (FRONT, SEP)

SEP Specifies that each front cover does not have any data printed on it; also, no report data is printed on the back of a SEP cover. The system generates an additional blank page between reports.

COVER= BACK

BACK Specifies that a cover page is to be printed at the end of each copy. No report data is printed on back covers.

COVER= BOTH

BOTH Specifies that both front and back cover pages are to be printed and the front of each copy is the first page of the copy.

A29247-X4-X-8-7672 85

Summary of OUTPUT Command Parameters Print Processing

Parameter Definition(s) Offline Online DJDE

COVER= (BOTH, SEP)

CYCLEFORMS= (form-id [, (INKS, inkref [, inkref][, ...])] [, form-id [, (INKS, inkref [, inkref][, ...])])

Specifies that both front and back cover pages are to be printed and that no data is to be printed on the front cover. The system generates additional blank pages for begin and end report.

form-id

Specifies a 1 to 6 character file name (may be numeric, alpha, or alphanumeric) which exists on disk. This file is created by compiling a forms description language source file, called an FSL file with the FDL system task.

inkref

YYY

CYCLEFORMS = NONE

NONE Means that no form is to be added to the associated report page of variable data. The default is NONE.,

DUPLEX= YES

DUPLEX= NO

YES Selects duplex printing.

NO Specifies simplex printing.

YYY

The default is NO.

86 A29247-X4-X-8-7672

Print Processing Summary of OUTPUT Command Parameters

Parameter Definition(s) Offline Online DJDE

FACEUP=YES|NO

This parameter specifies faceup delivery of pages. The default is NO. Note: This parameter is generally ignored in PRISMAproduction (LCDS) which means, that the default-value (NO) is processed, independently if YES or NO is defined. However it exists one exception: If NTO1=YES is defined, then always FACEUP=YES is processed, no matter if NO or YES is defined. In case of NTO1=n and n exceeds the limit, the system acts like NTO1=NO.

FACEUP=YES Specifies that the sheets are delivered to the tray/

output-stacker faceup. FACEUP=YES is executed unconditionally if NTO1=YES, no matter if FACEUP=YES or FACEUP=NO

FACEUP=NO Specifies that the sheets are delivered to the tray/

output-stacker facedown. FACEUP=NO is executed unconditionally if NTO1=NO, no matter if FACEUP=YES or FACEUP=NO This is the default-value.

FEED=

stock-reference

(only for Cutsheet !)

stock-reference

Specifies the stock assigned to a stock-name by the STOCKSET command in effect at the time the page is printed. FEED=stock-reference allows users to change stocks associated with a job, without altering the stock references in the data application itself.

YYN

YYY

FEED=

stock-name

(only for Cutsheet !)

stock-name

Bypasses the reference feature, but still requires that the stock-name is specified as present in the current STOCKSET. (FEED=stock-reference should always be used.)

FEED= MAIN,AUX, OPR

(only for Cut-

MAIN,AUX,OPR These options provide compatibility to existing applications. FEED=OPR is equivalent to FEED=MAIN. The default is MAIN.

sheet !)

A29247-X4-X-8-7672 87

Summary of OUTPUT Command Parameters Print Processing

Parameter Definition(s) Offline Online DJDE

Note: Continuous feed printer cannot physically sup-

port multiple stocks within a report. It does, however, logically support the changing of stocks. When a FEED=DJDE is applied which specifies a stock (using a stock-reference, a stock-name, or one of the supported keywords) which is different than the stock currently in effect the next logical page will be printed as the first logical page on the front of the next page. In the LCDS-Module the relation of stock-name and the corresponding input bin of the printer is defined in the stockset-configuration-table. With the parameter PrinterTyp set to CutSheet the stock-names are to be defined as paper names (Media Name) on the printer panel. (see “Configuring LCDS-Module Parameters” and “PrinterTyp” in Administrator’s Guide). Please refer to the User Guide for further information. If FEED switches to AUX-tray, an (additional) form may be printed on the sheet (see “Configuring LCDSModule Parameters” and “AUX_FRONT/ AUX_BACK” in Administrator’s Guide)

FORMAT=

pde-id

References a PDE that must have been defined previously in a JDL or may make reference to a PDE file separately cataloged in the PDE directory on disk. Standard pde-ids are defined below "PDE command" in this chapter, such as FMT1 and FMT2. These standard pde-ids are part of the software and may be used unless a specialized PDE must be defined. An active PDE may subsequently be replaced entirely or modified in part through DJDEs (refer to the chapter "Specifying dynamic job descriptor entries (DJDEs)". Details on the PDE parameter are discussed in the ”Page descriptors” section of this chapter. Creating and compiling PDE files with the XDL processor is discussed in the ”Compiling the JSL” section in the chapter "Creating a job source library (JSL)." The default is FMT1.

YYY

88 A29247-X4-X-8-7672

Print Processing Summary of OUTPUT Command Parameters

3.8.1 Standard Print Description Entry

PDE id No. of

lines

FMT1 66 132 8.1 13.6 9 11 by 8.5 (.18,.66) L0112B

FMT2 66 150 8.1 15 9 11 by 8.5 (.18,.50) L0212A

FMT3 88 132 10.7 13.6 7 11 by 8.5 (.14,.66) L0312A

FMT4 88 150 10.7 15 7 11 by 8.5 (.14,.50) L0412A

FMT5 49 100 6 10 12 11 by 8.5 (.17,.50) L0512A

FMT6 80 100 8.1 13.6 9 8.5 by 11 (.57,.58) P0612A

FMT7 60 90 6 12 12 8.5 by 11 (.50,.50) P07TYA

FMT8 60 75 6 10 12 8.5 by 11 (.50,.50) P0812A

FMT9 80 200 10.0 20.0 7 11 by 8.5 (.25,.25) L0912A

FMT10 132 132 12.5 17.6 6 8.5 by 11 (.22,.51) P1012A

FMT11 132 150 12.5 20.0 6 8.5 by 11 (.22,.50) P1112A

FMT12 66 172 8.1 13.6 9 14 by 8.5 (.18,.66) L0112B

FMT13 104 100 8.1 13.6 9 8.5 by 14 (.57,.58) P0612A

FMT1A 66 132 8.3 12.5 9 11.69 by 8.27 (.18,.57) R112BL

FMT2A 66 150 8.3 14.3 9 11.69 by 8.27 (.18,.60) R212BL

No. of

columns

lpi cpi Approx.

point

size

Page size and

orientation

BEGIN values

Default

font id

FMT3A 88 132 11.1 12.5 7 11.69 by 8.27 (.18,.57) R312BL

FMT4A 88 150 11.1 14.3 7 11.69 by 8.27 (.18,.60) R412BL

FMT5A 48 100 6 10 12 11.69 by 8.27 (.22,.85) R512BL

FMT6A 80 100 8.1 13.6 9 8.27 by 11.69 (.91,.46) R612BP

FMT7A 60 90 6 12 12 8.27 by 11.69 (.85,.39) R7TIBP

FMT8A 60 75 6 10 12 8.27 by 11.69 (.85,.39) R812BP

FMT9A 80 200 10.0 20.0 7 11.69 by 8.27 (.14,.85) R912BL

FMT10A 132 132 12.5 17.6 6 8.27 by 11.69 (.57,.39) RA12BP

FMT11A 132 150 12.5 20.0 6 8.27 by 11.69 (.57,.39) RB12BP

A29247-X4-X-8-7672 89

Summary of OUTPUT Command Parameters (Continuation) Print Processing

3.9 Summary of OUTPUT Command Parameters (Continuation)

Parameter Definition(s) Offline Online DJDE

FORMS= (form-id[, init [, copies]] [, (INKS, inkref [, inkref] [, ...])])

This option consists of:

form-id

Specifies a 1 to 6 character file name (may be numeric, alpha, or alphanumeric) which exists on disk.

init

Specifies the beginning ply (pass) number to which a specified form applies. This defaults to the first or next copy. If the copies parameter is not specified, the last (or only) specified form applies to all copies beginning with copy number init. If the form is not the last one specified, copies defaults to 1. If neither init nor copies is specified, the form applies to all copies of the report.

copies

The number of copies of the report to be printed.

inkref

YYY

FORMS= NONE

GRAPHICS= The options to this command are unsupported. The

NONE Means that no form is added to the associated report page of variable data. The default is NONE.

command is gracefully processed by the compile function. Options are ignored and a warning message is issued. OUTPUT GRAPHICS=YES is always assumed.

90 A29247-X4-X-8-7672

YYN

Print Processing Summary of OUTPUT Command Parameters (Continuation)

Parameter Definition(s) Offline Online DJDE

IDFAULT=

inkref

IDR=

idr-name

inkref

Specifies the default ink to be used in all subsequent parameters that do not explicitly select an ink. The inkref may be entered as ink name or as numeric ink index using an inklist contained by an IDR which is referenced by an IDR parameter in the same OUTPUT command. Only a reference to a primary colour is allowed. For restricted implementation of IDR see IDR command parameters.

idr-name

References an IDR command, that is previously defined in the JDL or defined in a separate file.

YYY

A29247-X4-X-8-7672 91

Summary of OUTPUT Command Parameters (Continuation) Print Processing

Parameter Definition(s) Offline Online DJDE

IMAGE= (img_name,

vpos units, hpos units

[, n[/d]] [, (INKS, inkref [, inkref] [, ...])])

In the LCDS-Module this parameter is completely ignored. This command is unsupported as it applies only to batch mode processing. The command is gracefully processed by the XDL compiler and ignored. It is documented here for completeness only.

img_name

Specifies the name of the graphic image file.

vpos

Specifies the vertical position (top left corner of page) of the top edge of the graphic, as an offset relative to 0,0 on the current physical page (the position that would be specified by a PDE BEGIN of 0,0). This parameter is specified as a decimal number with up to three digits to the right of the decimal point.

hpos

Specifies the horizontal position of the left edge of the graphic, as an offset relative to 0,0 on the current physical page. The units of the specification is the same as for vpos. This parameter is specified as a decimal number with up to three digits to the right of the decimal point. The default for vpos and hpos is the top left corner (default for n/d) scaled 1/1.

units

DOTS (300 dots per inch), XDOTS (600 dots per inch), centimeters (CM), user-defined units (UN) or inches (IN). The default units value is IN.

n/d

Specifies the reference scale factor. Each parameter, n and d, must be an integer in the range of one to eight, thereby allowing a reference scale factor in the range of 1/8 to eight. Scaling can result in performance problems, because scaling is done page by page during printout.

inkref

Specifies which inks in the ILIST parameter of the IDR command override the corresponding inks specified in the inklist of the image. If one inkref in the list is omitted, commas must be used to maintain the relative positioning of the remaining ink references.

YYY

92 A29247-X4-X-8-7672

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

Specifications and Main Features

Frequently Asked Questions

User Manual