1.7 Job Source Library (JSL) Structure ................12 1.7.1 Command levels....................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 .............
Page 6
Contents 1.15Page Orientation......................27 1.15.1Landscape orientation ..................27 1.15.2Portrait orientation ................... 27 1.16Fonts.......................... 28 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..............
Page 7
Contents 3.13.2Example ......................133 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 ........
Page 8
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 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).
LCDS-Module Components and Overview Overview 1.2 LCDS-Module Components and Overview Before discussing XDL commands in detail, a general understanding of LCDS-Module components and functions is helpful. The following sections provide such a general over- view. 1.3 Preparing for a Print Job...
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: •...
Hierarchy of replacement 1.6.1 Purpose of XDL For a job to be printed on a LCDS-Module, it is necessary to create a file of XDL commands to define the format of the input media, processing requirements, and the format of the print- ed output.
Page 13
TABLE, CRITERIA, CME, PDE, and so on. A command keyword is required for each XDL command statement. Parameter Each command keyword is followed by parameters used to select its processing parame- ters. The parameters for an XDL command keyword consist of a left and right part separat- ed by an equal sign (=). A29247-X4-X-8-7672...
Page 14
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 (*/).
Page 15
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).
Page 16
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);...
Page 17
Normally used as string constants, each pair of hexadecimal characters results in one byte. A hexadecimal constant must immediately be preceded by the characters X apostrophe (X') to indicate to the XDL compiler that the following expression is in hexadecimal. For exam- ple: IDEN PREFIX=X'C1C2C3C4';...
Page 18
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'...
Page 19
Overview Xerox Print Description Language (XDL) • 'ink-catalog-name.palette-name.inkname' • 'ink-catalog-name..inkname' When ink-catalog-name or palette-name are missing the appropriate IDR command para- meters will be used. (Refer to the IDR command description.) In JSL files basically only primary colour specifications are allowed, no shaded colours.
Job Source Library (JSL) Structure Overview 1.7 Job Source Library (JSL) Structure To simplify JSL coding, XDL commands are grouped into command levels. The use and syntax of command levels, along with the required END command, are defined in the fol- lowing sections: •...
Page 21
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;...
Page 22
Job Source Library (JSL) Structure Overview System or JDL level A system or JDL command set establishes installation-dependent requirements and default values for job descriptor entries. At the system level, JDL may be used interchangeably with SYSTEM. At the system level, commands are specified which apply to all job descriptor en- tries (JDEs) identified within a job source library (JSL).
Page 23
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:...
Page 24
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: ASSIGN=(1,5),ASSIGN=(2,10),ASSIGN=(3,15),...
According to the job or JDE command levels, for jobs one and three, the recording code of the input data is Printable EBCDIC (PEBCDIC). The XDL command: VOLUME CODE=PE- BCDIC overrides both catalog and system (or JDL) command level definitions.
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.
Page 27
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 •...
Page 28
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.
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 •...
Keep in mind that the specifications to select in your JSL can be changed easily. By using the IDEN command you can allow DJDEs to override XDL commands on a page- by-page or record-by-record basis. Also, certain operator commands can alter the print job in such areas as the number of copies to be printed, the sequencing of reports, and paper feed specifications.
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.
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 com- mand must be specified in the JSL to advise the system where to look for them in the input data stream.
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.
Page Considerations Overview 1.13.10 Ending a JSL When you are finished constructing your JSL, you must let the system know you are fin- ished 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: •...
Overview Page Orientation 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.
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-Mod- ule. Each font character occupies an area called a character cell. All character cells in a fixed font are the same width.
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"...
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.
Page 39
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.
Page 40
Summary of BLOCK Command Parameters Input Processing Parameter Definition(s) Offline Online DJDE LTHFLD= value value Specifies the length in bytes of the field containing the block LENGTH specified above. The size is an inte- ger 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 ac- tual block length.
Page 41
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.
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.
Page 43
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.
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-to- channel, and printing actions are all defined through this parameter.
Page 45
Input Processing Summary of PCC Command Parameters Parameter Definition(s) Offline Online DJDE ASSIGN= This option has the following components: (byte,(ccln, byte [ccln][,...]) The printer carriage control byte being defined. Its value is in the range 0 to 255 (X’00’ to X’FF’). Possi- ble codings are: Character, ASCII, EBCDIC, HEX, OCT.
Page 46
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: Space m lines before printing. Skip-to-channel-n before printing.
Page 47
Input Processing Summary of PCC Command Parameters Parameter Definition(s) Offline Online DJDE DEFAULT= pcctype: pcctype can have one of the following values: ANSI B2500 B2700 B3500 B3700 B4700 B6700 IBM1401 IBM1403 IBM3211 IBM4245 UNISYS US70 XEROX NONE additonally the following ccln are supported: SP1 [PIN] [PIN] SP1 SK1 [PIN]...
Page 48
Summary of PCC Command Parameters Input Processing • Multiple user-defined PCC tables are allowed, but only one may be used without a com- mand identifier. The corresponding PCCTYPE parameter on the LINE command refer- ences each table through a command identifier. The keyword USER can be used to ref- erence any user-defined PCC table for which no command identifier is coded.
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.
Page 50
Summary of RECORD Command Parameters Input Processing Parameter Definition(s) Offline Online DJDE LENGTH= value value An integer in the range 1 to 310 for offline (133 is the default) or 150, the online default. For offline sys- tems, 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...
Page 51
Input Processing Summary of RECORD Command Parameters Parameter Definition(s) Offline Online DJDE STRUCTURE= structure-type 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.
Page 52
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; Data (Block-LENGTH minus Block-PREAMBLE minus Block-POSTAMBLE) divided by Record LENGTH must be a whole number. 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.
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. This parameter specifies the action the system takes when it encounters an end-of-volume (EOV) on the input data tape.
Page 55
Input Processing Summary of VOLUME Command Parameters Parameter Definition(s) Offline Online DJDE BMULT= value 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 val- ue is an integer and can range from 1 (default) to The default is 1.
Page 56
Summary of VOLUME Command Parameters Input Processing Parameter Definition(s) Offline Online DJDE EOV= This option has the following components: ([PAUSE | PAUSE NOPAUSE], Displays a message when EOV is encountered. [EOF | A CONTINUE response by the operator causes NOEOF]) the tape to rewind and the normal volume change sequence to proceed.
Page 57
Input Processing Summary of VOLUME Command Parameters Parameter Definition(s) Offline Online DJDE HOST= host-type label host-type 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...
Page 58
Summary of VOLUME Command Parameters Input Processing Parameter Definition(s) Offline Online DJDE LCODE= keyword keyword Specifies a specific, standard, system-defined code translation table for label blocks. The avail- able options are: EBCDIC ASCII NONE USER USER refers to the single unlabeled CODE com- mand allowed within the JDE or JDL.
Page 59
Input Processing Summary of VOLUME Command Parameters Parameter Definition(s) Offline Online DJDE MINLAB= value 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 ex- ceed the BLOCK LENGTH.
Page 60
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,...
Page 61
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...
Page 62
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 op- erating system converts each command to a valid 3211 command before sending it to the printer.
Page 63
Input Processing Summary of VOLUME Command Parameters may be successfully printed with only one transmission by using copy-sensitive forms. Re- fer to the FORMS parameter of the OUTPUT command in the "Specifying output parame- ters" chapter. Report separation Report separation is defined in terms of banner page detection or other user-defined pro- cessing criteria.
Page 64
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.
Page 65
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 char- acteristics - 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.
Page 66
Summary of VOLUME Command Parameters Input Processing 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...
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 sys- tem responses to error conditions. ERROR This parameter specifies the required system response to abnormal conditions detected in input processing or compiling DJDEs.
Page 69
Print Processing Summary of ABNORMAL Command Parameters Parameter Definition(s) Offline Online DJDE IMISMATCH= STOP STOP Stops processing the current report or job and waits for the operator to respond with the ABORT command or to load the requested pri- mary colour followed by the CONTINUE com- mand.
Page 70
Summary of ABNORMAL Command Parameters Print Processing Parameter Definition(s) Offline Online DJDE Hint: This option is to be seen in context with IMIS- MATCH. In this version of the LCDS-Module doesn't exist a SUBSTITUDE command, be- cause it is meaningless with IMISMATCH=CON- TINUE.
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.
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.
Page 73
Print Processing Summary of ac:CME Command Parameters Parameter Definition(s) Offline Online DJDE CONSTANT= Represents the string constant to be printed for defi- nition of string constants). The width of the copy mod- ification rectangle is determined by the number of characters specified by sc.
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.
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-spac- ing value that is computed as dots per line, and rounding is done on that value.
Page 76
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'; A29247-X4-X-8-7672...
'XEROX1' | name. 'SDFLT$' The XEROX1 entry is gracefully ignored while com- piling the XDL but rejected during print data process- ing. SDFLT$ is gracefully ignored. For restricted implementation see 6.2.3. PALETTE= palette palette Specifies the default ink-palette.
Page 78
Summary of IDR Command Parameters Print Processing Parameter Definition(s) Offline Online DJDE ILIST= ink-name ink-name | Specifies a list of ink-names. One of those inks in this (ink-name ink-list is used when an ink-reference consists of a [, ink-name] numerical ink-index which points into the ink-list. [, ink-name][, Only primary colours are allowed in this list.
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.
Page 80
Summary of LINE Command Parameters Print Processing Parameter Definition(s) Offline Online DJDE FCB= PROCESS PROCESS FCB in 3211 Format processed FONTINDEX= Allows the user to specify a certain location in the in- {offset | (offset put record where an index to the font to be used is [,init-val][,bit- stored.
Page 81
Print Processing Summary of LINE Command Parameters Parameter Definition(s) Offline Online DJDE INKINDEX= Allows the user to specify a certain location in the in- offset | put record where an index to the ink to be used is (offset[, init-val] stored.
Page 82
Summary of LINE Command Parameters Print Processing Parameter Definition(s) Offline Online DJDE MARGIN= This option has the following components: {value | value (value,value- The form nnn.mm (a positive decimal number with up type)} to 2 digits to the right of the decimal point) which is the distance from the left margin.
Page 83
Print Processing Summary of LINE Command Parameters Parameter Definition(s) Offline Online DJDE PCC= This option has the following components: (offset,trans- offset type) Specifies the byte offset of the user portion of the record within each logical record to the printer car- riage control (PCC) field.
Page 84
Summary of LINE Command Parameters Print Processing Parameter Definition(s) Offline Online DJDE PCCTYPE= pcc-name pcc-name Options are: ANSI B2500 B2700 B3500 B3700 B4700 B6700 IBM1401 IBM1403 IBM3211 IBM4245 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.
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-id The command identifier of the VFU table, which must precede this reference to it.
Page 86
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 switch- es 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 par- ticular line is determined by the largest font in use in the previous line.
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 param- eters, 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 de- fault to the carriage control parameter of print-and-space-1-line.
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.
Page 89
Print Processing Summary of MESSAGE Command Parameters Parameter Definition(s) Offline Online DJDE OTEXT= WAIT WAIT Specifies that after the text is displayed, printing is suspended until the operator has responded with a CONTINUE parameter. OTEXT= Specifies that the text is displayed after the last copy of the report is printed.
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 con- trols 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.
Page 91
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 para- meter is given. 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.
Page 92
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...
Page 93
Print Processing Summary of OUTPUT Command Parameters Parameter Definition(s) Offline Online DJDE BFORM= NONE NONE Specifies that no form is to be added to the associat- ed report page of variable data. A init parameter specifies the beginning ply (pass) number to which a specified form applies.
Page 94
Summary of OUTPUT Command Parameters Print Processing Parameter Definition(s) Offline Online DJDE COVER= Specifies that both front and back cover pages are to (BOTH, SEP) be printed and that no data is to be printed on the front cover. The system generates additional blank pages for be- gin and end report.
Page 95
Print Processing Summary of OUTPUT Command Parameters Parameter Definition(s) Offline Online DJDE FACE- This parameter specifies faceup delivery of pages. UP=YES|NO The default is NO. Note: This parameter is generally ignored in PRISMApro- duction (LCDS) which means, that the default-value (NO) is processed, independently if YES or NO is de- fined.
Page 96
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 de- fault is FMT1.
Print Processing Summary of OUTPUT Command Parameters 3.8.1 Standard Print Description Entry PDE id No. of No. of Approx. Page size and BEGIN Default lines columns point orientation values font id size FMT1 13.6 11 by 8.5 (.18,.66) L0112B FMT2 11 by 8.5 (.18,.50) L0212A...
Summary of OUTPUT Command Parameters (Continuation) Print Processing 3.9 Summary of OUTPUT Command Parameters (Continuation) Parameter Definition(s) Offline Online DJDE FORMS= This option consists of: (form-id[, init form-id [, copies]] Specifies a 1 to 6 character file name (may be numer- [, (INKS, inkref ic, alpha, or alphanumeric) which exists on disk.
Page 99
Print Processing Summary of OUTPUT Command Parameters (Continuation) Parameter Definition(s) Offline Online DJDE IDFAULT= inkref 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 OUT- PUT command.
Page 100
This command is unsupported as it applies only to hpos units batch mode processing. The command is gracefully [, n[/d]] processed by the XDL compiler and ignored. It is doc- [, (INKS, inkref umented here for completeness only. [, inkref] img_name [, ...])])
Page 101
Print Processing Summary of OUTPUT Command Parameters (Continuation) Parameter Definition(s) Offline Online DJDE If more inkrefs are specified than contained in the in- klist of the image, the extra inkrefs are ignored. Existing images are printed in black unless inkrefs are specified in the INKS parameter.
Page 102
Summary of OUTPUT Command Parameters (Continuation) Print Processing Parameter Definition(s) Offline Online DJDE IRESULT= The IRESULT is gracefully ignored in the LCDS-Mod- COLOUR ule. In case of overprinting one colour the other with the LCDS-Module always both colours are printed. The result has to be checked visually because it de- pends on the geometrical printer characteristics.
Page 103
(n-to-1). NTO1 is the command parameter keyword. The default is NO Note: When NTO1=YES, XDL overrides COL- LATE=NO with COLLATE=YES and notes this action with a warning in the message window. NTO1=YES causes FACEUP=YES to be specified.
Page 104
1TON. The default value of NTO1 is 50 physical sheets, but n may range from 1 to 100000. When the value is greater than 100, XDL generates a warning message into the message win- dow. PLABEL sheets are not counted for the thresh- old.
Page 105
Print Processing Summary of OUTPUT Command Parameters (Continuation) Parameter Definition(s) Offline Online DJDE OFFSET= Results in an offset of each copy of each report. Note: For continuous feed printers the attached post processing system must support this. Otherwise ALL takes no effect. The default is ALL.
Summary of OUTPUT Command Parameters (Continuation) Print Processing 3.9.1 Definitions in Xerox-/Océ printing This paragraph defines a few terms from the point of view of a Xerox-printer or - lets say - a Xerox-user. It is not intended, to redefine Xerox-terms here, on the contrary, it is the in- tention to repeat here Xerox-terms to get a common understanding of definitions in Xerox- /Océ...
Page 107
Print Processing Summary of OUTPUT Command Parameters (Continuation) Coordinate-Systems Now a coordinate-system is laid over a page, where the Y-axis is laid over the leading edge and the X-axis is laid over the left edge with an origin in the upper left corner. The y-values increase from left to right, the X-values increase from top to bottom.
Page 108
Summary of OUTPUT Command Parameters (Continuation) Print Processing That edge, which defines the left/right edge coincides with the X-axis in the coordinate- system. This direction is also defined as ‘slow scan direction’. Attention: the X is an Y Xerox is used in the PAGESIZE-option, Xerox is used in the PGD-structured field) Duplex...
Page 109
Print Processing Summary of OUTPUT Command Parameters (Continuation) Dot-/scan-address The dot-addresses are defined through the Y -axis, start with 0 on the left side and in- Xerox crease to the right. The scan-addresses are defined through the X -axis, start with 0 on top and increase Xerox to bottom.
Page 110
Summary of OUTPUT Command Parameters (Continuation) Print Processing LANDSCAPE / PORTRAIT LANDSCAPE A printout is designated as a landscape-printout, when that line on which the characters are added from left to right for human reading is a parallel to the long edge [1,2,3]. In PMODE=LANDSCAPE the LANDSCAPE-rules are applied.
Page 111
Print Processing Summary of OUTPUT Command Parameters (Continuation) PORTRAIT A printout is designated as a portrait-printout, when that line on which the characters are added from left to right for human reading is a parallel to the short edge [1,2,3]. In PMODE= PORTRAIT the PORTRAIT -rules are applied.
Page 112
Summary of OUTPUT Command Parameters (Continuation) Print Processing vpos/hpos The positioning-coordinates vpos (vertical positioning) and hpos (horizontal positioning) have different meaning in different PMODEs if you refer to a coordinate-system. They have the same meaning if you apply them on a sheet of paper to be printed on. vpos always defines the offset from the top-edge of the page;...
Page 113
Print Processing Summary of OUTPUT Command Parameters (Continuation) SHIFT The SHIFT-option in the OUTPUT-command shifts the print-data (variable data, forms and images) against the physical paper in the ±X-direction, independent of a portrait- or land- scape-print-mode. An increasing positive Shift-value results in an increasing distance of variable data and leading edge, a increasing negative Shift-value results in a decreasing distance of variable data and leading edge.
Page 114
Summary of OUTPUT Command Parameters (Continuation) Print Processing Forms A form can be seen as a regular page for: • coordinate system • dot-/scan-addresses • landscape/portrait. The page-terms • hpos/vpos • duplex • shift are not applicable. During printout the coordinate-system of a form and a page must coincide with their x- and y-axis and their origin.
Page 115
Print Processing Summary of OUTPUT Command Parameters (Continuation) Note: As soon as the X -axis becomes longer than the y-axis, you can divide the X- Xerox axis by 2, so that you get two halves of your original page: an upper and a lower half.
Page 116
Summary of OUTPUT Command Parameters (Continuation) Print Processing AFP-EXAMPLES The following examples demonstrate, how a Xerox-printout is implemented on IPDS-print- ers through means of the LCDS-Module. To demonstrate this, the examples always show a print-example on a Xerox printer and the corresponding printout on an IPDS-printer under the two conditions: small and wide paper.
Page 117
Print Processing Summary of OUTPUT Command Parameters (Continuation) LEF / PORTRAIT This example demonstrates, how a regular portrait-printout is implemented on an IPDS- printer. Xerox-characteristics: IPDS-characteristics: PMODE = PORTRAIT 1.) small paper; one_up PAGESIZE = USLETTER 2.) wide paper; one_up Typical for this example is, that the X 3.) wide paper;...
Page 119
Print Processing Summary of OUTPUT Command Parameters (Continuation) LEF / LANDSCAPE Xerox-characteristics: IPDS-characteristics: PMODE = LANDSCAPE 1.) small paper; one_up PAGESIZE = USLETTER 2.) wide paper; one_up Typical for this example is, that the X 3.) wide paper; two_up Xerox axis is shorter than the Y -axis.
Page 122
Summary of OUTPUT Command Parameters (Continuation) Print Processing SEF / LANDSCAPE Xerox-characteristics: IPDS-characteristics: PMODE = LANDSCAPE 1.) small paper; one_up PAGESIZE = USLEDGER 2.) wide paper; one_up Typical for this testcase is, that the X -axis is Don’t care for long edges or short edges, but take Xerox longer than the Y -axis.
Page 124
Summary of OUTPUT Command Parameters (Continuation) Print Processing SEF / PORTRAIT Xerox-characteristics: IPDS-characteristics: PMODE = PORTRAIT 1.) small paper; one_up PAGESIZE = USLEDGER 2.) wide paper; one_up Typical for this testcase is, that the X -axis is Don’t care for long edges or short edges, but take Xerox longer than the Y -axis.
Page 126
The default is NO. Note: If NTO1=YES and STAPLE=YES, XDL overrides NTO1=YES with NTO1=NO and notes this action with a warning in the message window. When an entire set is delivered to the stitcher compiler tray, output issues a parameter to stitch the set.
Print Processing Summary of OUTPUT Command Parameters (Continuation) Parameter Definition(s) Offline Online DJDE STAPLE=YES Specifies stitching and implies NTO1=NO and COLLATE=YES, but not vice versa. Individual sheets cannot be offset when coded in the JSL. STAPLE=NO Specifies no stitching This is the default-value. STOCKS= No Default stockset-name...
Summary of OUTPUT Command Parameters (Continuation) Print Processing DUPLEX=YES Any job that runs in simplex mode runs in duplex mode except transparencies. COLLATE Once you have specified multiple copies, the value of the COLLATE parameter cannot be changed again within the report. CYCLEFORMS, FORMS Both may be used within a report;...
Page 129
Print Processing Summary of OUTPUT Command Parameters (Continuation) Example 2 OUTPUT COPIES=3, DUPLEX=YES, SHIFT=YES, NUMBER=(1,66,132), COVER=(FRONT, SEP), FORMS=GBAR; Pages printed with this OUTPUT command are in duplex mode with a margin shift of 75 dots. Three copies of the report are made, the first of which is offset; the second and third copies are stacked on top of the first.
Summary of PDE Command Parameters Print Processing 3.10 Summary of PDE Command Parameters The PDE command specifies a page descriptor entry (PDE) which defines formatting infor- mation for each page of a report. This formatting information includes page orientation (landscape or portrait), location of the beginning print line for each logical page, and the fonts to be used.
Page 131
Print Processing Summary of PDE Command Parameters Parameter Definition(s) Offline Online DJDE BEGIN= This option has the following components: (vpos,hpos) vpos Specifies a decimal number with up to three digits to the right of the decimal point, such as 0.563 IN and 2.35 CM, are all legal specifications).
Summary of PDE Command Parameters Print Processing 3.10.1 Examples This section shows examples of using the PDE command. Example 1 PDE1: PDE PMODE=LANDSCAPE,BEGIN=(.861,.7),FONTS=(L0112B,L01BOB); PDE2: PDE PMODE=PORTRAIT,BEGIN=(1.3,.37),FONTS=((P08TYA,6.8),P080AA,6.8); JDE; OUTPUT FORMAT=PDE1; JDE; OUTPUT FORMAT=PDE2; Two PDEs are defined and referenced in separate JDEs. PDE1 specifies a landscape page and two landscape fonts;...
Print Processing Summary of ROUTE Command Parameters 3.11 Summary of ROUTE Command Parameters The ROUTE command allows the user to print identifying information (text and an optional form) on the page preceding a report. The ROUTE command may be coded within a JDL or in a disk file of ROUTE commands.
Page 134
RTEXT= rtext-id rtext-id This option is used to reference a cataloged file of RTEXT parameters previously compiled by XDL. RTEXT= NONE NONE Specifies that no text is to be printed on a separate page.
Page 135
Print Processing Summary of ROUTE Command Parameters Example Following is an example of how to use the ROUTE command: ROUTE RTEXT=('USER 1',1,33,64),RTEXT=('USER 2',2,33,64); The text USER 1 and USER 2 is to be printed in the center of a page preceding the respec- tive copies of a two-copy report.
Summary of VFU Command Parameters Print Processing 3.12 Summary of VFU Command Parameters The VFU command is used to assign output line numbers to printer carriage control chan- nels. These line-to-channel assignments perform the same function as the printer carriage control tape on a conventional line printer.
Page 137
Print Processing Summary of VFU Command Parameters Parameter Definition(s) Offline Online DJDE ASSIGN= This option has the following components: (channo, channo lineno) The number of the channel being assigned. It is an in- teger in the range 0 to 15. The user may end the VFU command with a semicolon and start another VFU command without an id field to continue specification for the same channel or a different channel.
Page 138
Summary of VFU Command Parameters Print Processing Example Following is an example of how to use the VFU command: In the following example, top of form is assigned to line number 5 and bottom of form is as- signed to line number 55. Channels 1, 2, and 12 have been assigned line numbers. V1: VFU ASSIGN=(1,5), ASSIGN=(2,(10,15,20,25,30,35,40,45,50)), ASSIGN=(12,55),TOF=5,BOF=55;...
Print Processing Summary of STOCKSET Statement Command Parameters 3.13 Summary of STOCKSET Statement Command Parameters The STOCKSET statement defines a set of stocks used in a report. Stock reference are used in the DJDE of the Print Data to specify a stock. With the SCT (Stock Configuration tool, see User's Guide), the user can associate stocknames to the stocks of the printer.
Page 140
Summary of STOCKSET Statement Command Parameters Print Processing SYSPAGE= Specifies which stock to use for system-generated stock-name | pages (DJDE OPRINO, PLABEL). stock-refer- ence | MAIN | There is no default. A29247-X4-X-8-7672...
Print Processing Summary of STOCKSET Statement Command Parameters 3.13.1 Points to note System-generated pages (such as PLABEL or OPRINFO) are printed using the STOCK- SET's SYSPAGE command that is in effect. If no STOCKSET is in effect, cluster MAIN is used.
Using Logical Processing Logical Processing Commands 4 Using Logical Processing The logical processing (sometimes referred to as ”conditional processing”) commands en- able the user to specify logical functions performed on either a record, a set of records, or on a block basis. 4.1 Logical Processing Commands To define a logical processing command fully, you must specify one or two fields in the record or block to be tested.
Page 144
CRITERIA Command Using Logical Processing TABLE MASK='?',CONSTANT='HE?DE? PAGE'; CRITERIA CONSTANT=(1,11,EQ,T1), LINENUM=(1,10); TABLE CONSTANT='TRAILER PAGE'; CRITERIA CONSTANT=(0,12,EQ,T2), LINENUM=(1,10); Criteria C1 and C2 are then specified at the job level: HDRP: JOB; BANNER TEST=C1,HCOUNT=2,TCOUNT=0; TRLP: JOB; BANNER TEST=C2,HCOUNT=0,TCOUNT=3; BOTH: JOB; BANNER TEST=(C1 OR C2),HCOUNT=2,TCOUNT=3; Refer to ”Test expressions”...
Page 145
Using Logical Processing CRITERIA Command Parameter Definition(s) CONSTANT= offset (offset,length, The offset in bytes (relative to zero) from the start of the physical tape block to a EQ | NE,tab-id) field within the tape block being compared to a table or string constant. In the case of record processing, it is the offset from the start of the user's portion of the record to the field in the record being compared.
Page 146
CRITERIA Command Using Logical Processing for the TEST to be successful. If OR is coded, then if either CRITERIA command is satisfied for a data record, the TEST is successful. The second and third Test parameters are optional; but if either is specified, the other must also be present.
Page 147
Using Logical Processing CRITERIA Command Constant mode In the constant mode, the user must specify the location, length, and contents of a fixed field within a user's record or block. Each user's record or block is examined at the specified lo- cation to determine if the constant is present (the identifier tab-id defines the table contain- ing the constant).
CRITERIA Command Using Logical Processing If the test specifies a change mode function, the CRITERIA fails because no change has occurred, but the value for LAST option of the CHANGE parameter is unchanged for com- parison with the next record. (See additional information under the ”Criteria parameter func- tions”...
Using Logical Processing CRITERIA Command 4.2.2 Examples This section shows two examples of using the CRITERIA command. Example 1 The following are examples of CRITERIA commands including the TABLE commands they reference. The identifiers C1 and C2 are referenced by a logical processing TEST para- meter.
String comparison Concepts Using Logical Processing 4.3 String comparison Concepts This section focuses on string comparisons, character types, and masked comparisons us- ing default and non-default type assignments. 4.3.1 String comparisons String comparisons for logical processing are specified using the CRITERIA and TABLE commands.
Using Logical Processing String comparison Concepts 4.3.3 Masked comparisons using default type assignments Performing masked comparisons using unmodified standard default type assignments re- quires coding the following: • TCODE command. Used either to modify a set of standard default type assignments or to define a completely new set.
TABLE Command Using Logical Processing 4.4 TABLE Command The TABLE command is used to build a table of constants for use by the logical processing commands. Each constant included in a TABLE command is examined by the system to see if it is equal in value to the input data field specified in the CONSTANT parameter of the CRITERIA command.
Page 153
Using Logical Processing TABLE Command Parameter Definition(s) CONSTANT= [,sc ][,...]) is a string of constants composed of literal characters and masking characters (as defined by the MASK parameter of this command). All string constants must be of the same length in bytes. The number of bytes for all constants in the table (after conversion of any hexadecimal or octal constants) is limited to 255 bytes.
Page 154
TABLE Command Using Logical Processing The characters used in the MASK parameter occupy numbered positions, beginning with 0, separated by commas. These position numbers in the MASK parameter are used as type numbers. Therefore, the mask character to type associations listed are made for the above TABLE command.
Using Logical Processing BANNER Command 4.5 BANNER Command The stacked reports feature enables the online and offline user to define a series of reports in a single file. This is accomplished by specifying an end-of-report condition in the coded logical processing commands RSTACK (online and offline) and BANNER (online use only). End-of-report is that point in processing a report when all of the pages of a copy of a report have been formatted to disk and processing has begun on the next report.
Page 156
BANNER Command Using Logical Processing Parameter Definition(s) Offline Online DJDE HRPTNA= NONE NONE Specifies that no report name is to be selected. The default is NONE. TCOUNT= value value Specifies the total number of consecutive trailer ban- ner pages which must be detected to satisfy the test expression.
Using Logical Processing BANNER Command 4.5.1 Points to note Condition Parameter Result The LCDS-Module posi- If TCOUNT = 0 The page after the first header is positioned at tions to TOF after end-of- If TCOUNT not 0 TOF. report processing The page after the last trailer is positioned at TOF.
BSELECT and BDELETE Commands Using Logical Processing The MASK parameter specifies a masking character. The CONSTANT parameter specifies both the constant data being compared and the character positions which contain variable data which are not being compared. In this example, positions 1 through 5 (DATE=) as well as positions 8 and 11 (the /'s) of the specified character string contain fixed data.
Using Logical Processing BSELECT and BDELETE Commands 4.6.2 Examples This section shows examples of using the BSELECT and BDELETE commands. Example 1 The following commands illustrate the use of BSELECT to process interspersed reports (re- fer to the following figure) on a block basis. TABLE CONSTANT=('P');...
Summary of LMODIFY command parameters Using Logical Processing 4.7 Summary of LMODIFY command parameters This command is completely gracefully ignored by the LCDS-Module. TEST This parameter specifies the expression which is to be evaluated for de- ciding if highlight colour will be applied to the current print line. INKINDEX This parameter specifies the index of the desired ink out of inklist to be used.
This parameter can also be used in combination with the XDL parameter FEED of the OUT- PUT command (refer to the chapter "Print format commands") and the FEED DJDE com- mand (refer to the chapter "Specifying dynamic job descriptor entries (DJDEs)").
Page 162
RAUX Command Using Logical Processing • Since DJDE processing occurs prior to RAUX processing, DJDE records are not checked for satisfying the RAUX criteria (offline only). • If RAUX-condition is met, an (additional) form may be printed on the sheet (see “Con- figuring LCDS-Module Parameters”...
Using Logical Processing RFEED Command 4.9 RFEED Command The logical processing RFEED command allows you to change stock names on a page-by- page basis without using DJDEs. The RFEED command allows you to specify paper fed from different stocks if certain criterias are met on a record basis. RFEED is essentially an extension of the RAUX-command in that it allows you to specify virtually any stock-name or stock-reference without being limited to the AUX input bin.
Page 164
RFEED Command Using Logical Processing TABLE CONSTANT (‚GHI‘); CRITERIA CONSTANT (4,3,EQ,T1); CRITERIA CONSTANT (4,3,EQ,T2); CRITERIA CONSTANT (15,3,EQ,T3); RFEED TEST = (C1,‘RED‘), (C2,‘BLUE‘), (C3, ‚GREEN‘)); In this example, the processing checks C1, C2 and then C3. If C2 and C3 satisfy the spec- ified criteria, the C2-cluster has priority over the C3-cluster due to its position in the JSL.
Using Logical Processing RSELECT and RDELETE Commands 4.10 RSELECT and RDELETE Commands Interspersed records within one report or file may either be deleted from or selected for printing by use of the RDELETE and RSELECT commands. These commands can also se- lectively delete specialized records, for example, control records and offset records that are on the data tape but are not to be printed.
RPAGE Command Using Logical Processing 4.11 RPAGE Command The RPAGE command allows for the repositioning of the current (or next) logical page. Parameter Definition(s) Offline Online DJDE SIDE= side-opt side-opt Available side-opt parameters are: NUFRONT (the default), BACK, NUBACK, NEXT, FRSHEET, BK- SHEET.
Page 167
Using Logical Processing RPAGE Command Parameter Definition(s) Offline Online DJDE WHEN= BOTTOM BOTTOM The logical page following the current logical page is repositioned. WHEN= The current record is repositioned. This record prints at TOF. Any spacing or skipping defined to occur be- fore printing the current record is ignored.
RSTACK Command Using Logical Processing 4.12 RSTACK Command The stacked reports feature enables the online and offline user to define a series of reports in a single file. This is accomplished by specifying an end-of-report condition in the coded logical processing commands RSTACK (online and offline) and BANNER (online use only). End-of-report is that point in processing a report when all of the pages of a copy of a report have been formatted to disk and processing has begun on the next report.
Using Logical Processing RSTACK Command In non-delimiter mode (DELIMITER=NO), a single record separates one report from the next. After satisfying the TEST criteria, this record is considered part of the subsequent re- port. In this mode the delimiter record cannot be printed to the tray, that is, PRINT option not available when DELIMITER=NO.
Page 170
RSTACK Command Using Logical Processing • If ACCTINFO is not specified in the JDE or JDL of the START command, it can be invoked in a selected JDE or JDL. The first record after the selected JDE takes ef- fect is then printed as the ACCTINFO field. The following sections describe the syntax of the command parameters and explanations of the parameter options.
Page 171
Using Logical Processing RSTACK Command Parameter Definition(s) PRINT= NONE NONE Specifies that report delimiters are not to be printed. For DELIMITER=NO, no page is printed. If the report is being printed in duplex mode, report delimiters are printed on a single-sided duplex output page. The parameter BOTH in duplex is treated as BIN.
Page 172
RSTACK Command Using Logical Processing Example Following is an example of using the RSTACK command: T1: TABLE CONSTANT=('XEROX'); C1: CRITERIA CONSTANT=(1,5,EQ,T1); RSTACK TEST=C1,DELIMITER=YES,ACCTINFO=(14,19),HRPTNA=(20, 10); Reports are separated by a record with the characters XEROX in bytes 1 to 5 (relative to 0).
Using Logical Processing RSUSPEND and RRESUME Commands 4.13 RSUSPEND and RRESUME Commands The print suppression logical processing function permits the user to delete from printing groups of records that are distinguishable at the start and end, but whose intermediate records may not be unique or distinguishable. (Print suppression or resumption is invoked by the use of two separate commands—RSUSPEND and RRESUME.) The tests for each command are independent and must be described separately.
Page 174
Make sure that if an RSUSPEND command is coded, an RRESUME command must also be present for the job. A warning is issued by the XDL compiler if one command, but not both, is invoked for a job. However, the JDE is compiled as pro- grammed.
Page 175
Using Logical Processing RSUSPEND and RRESUME Commands Example Following is an example of using the RSUSPEND and RRESUME commands. T1:TABLE CONSTANT=('//JOB ','//EXEC'); T2:TABLE CONSTANT=('EOJ '); T3:TABLE CONSTANT=('//EXEC'); C1:CRITERIA CONSTANT=(1,6,EQ,T1); C2:CRITERIA CONSTANT=(1,4,EQ,T2); C3:CRITERIA CONSTANT=(1,6,EQ,T3); RSUSPEND TEST=(C1,OR,C2), BEGIN=CURRENT; RRESUME TEST=(C3,OR,C2), BEGIN=NEXT; The printing of the input data records in the following sample data is suspended (from record //JOB to //EXEC) by the preceding RSUSPEND command.
Page 176
RSUSPEND and RRESUME Commands Using Logical Processing A29247-X4-X-8-7672...
Dynamic Job Descriptor Entries (DJDEs) Benefits of using DJDEs 5 Dynamic Job Descriptor Entries (DJDEs) Dynamic job descriptor entries (DJDEs) are parameters embedded within the input data stream and are used to modify the printing environment established by a job descriptor en- try (JDE) ”on the fly.”...
IDEN Command Dynamic Job Descriptor Entries (DJDEs) 5.2 IDEN Command To invoke DJDE processing, an IDEN command must be coded in the JDL. This command notifies the system that DJDE records may be part of the input data stream. It also de- scribes the search criteria for locating and identifying DJDE records.
Dynamic Job Descriptor Entries (DJDEs) Page- and Record-oriented DJDEs 5.3 Page- and Record-oriented DJDEs 5.3.1 Page-oriented DJDEs Page-oriented DJDEs change specific pages within a report and can change these pages differently in different copies. Such parameters may be placed within the report itself and take effect at the next page boundary.
Page 180
Page- and Record-oriented DJDEs Dynamic Job Descriptor Entries (DJDEs) DJDE Definition(s) BFORM= NONE NONE Specifies that no form is to be added to the associated report page of variable data. COLLATE= Specifies that report copies are to be printed in collated mode. COLLATE= Specifies that report copies are to be printed in uncollated mode.
Page 181
Dynamic Job Descriptor Entries (DJDEs) Page- and Record-oriented DJDEs DJDE Definition(s) FILE=([name] To process a DJDE FILE=, the DJDE command needs to be of the form. name [[,file type], The optional name parameter contains a one- to six-character alphanumeric [[format], file name to save the file data to.
Page 182
Page- and Record-oriented DJDEs Dynamic Job Descriptor Entries (DJDEs) DJDE Definition(s) storage The optional storage parameter is also a single character used to describe how the printing system should store the file when the report that contains the file is finished printing. A ”D” here indicates that the file should be deleted and a ”P”...
Page 183
Dynamic Job Descriptor Entries (DJDEs) Page- and Record-oriented DJDEs Job Source Library (this file type cannot be used in the current print job. See below) The LCDS-Module supports downloading of files in a similar manner to what Xerox calls ”HOSTCOPY”. A message will be posted to the user when a data stream is processed which contains DJDE FILE=.
Page 184
Page- and Record-oriented DJDEs Dynamic Job Descriptor Entries (DJDEs) DJDE Definition(s) FONTINDEX= Allows the user to specify a certain location in the input record where an index to {offset | (offset the font to be used is stored. It takes effect on the next logical page boundary. [,init-val][,bit-opt]) This option has the following components: | OFF | NONE}...
Page 185
Dynamic Job Descriptor Entries (DJDEs) Page- and Record-oriented DJDEs DJDE Definition(s) FORMS= This option consists of: (form-id[, init form-id [, copies]] Specifies a 1 to 6 character file name (may be numeric, alpha, or alphanumeric) [, (INKS, inkref which exists on disk. [, inkref] init [, ...])])
Page 186
Page- and Record-oriented DJDEs Dynamic Job Descriptor Entries (DJDEs) DJDE Definition(s) INKINDEX= Allows the user to specify a certain location in the input record where an index to offset | the ink to be used is stored. It takes effect on the next logical page boundary. (offset[, init-val] [, bit-opt]) offset...
Page 187
Dynamic Job Descriptor Entries (DJDEs) Page- and Record-oriented DJDEs DJDE Definition(s) MARGIN= This option has the following components: {value | value (value,value- The form nnn.mm (a positive decimal number with up to 2 digits to the right of the type)} decimal point) which is the distance from the left margin.
Page 188
Page- and Record-oriented DJDEs Dynamic Job Descriptor Entries (DJDEs) DJDE Definition(s) NUMBER= pnum (pnum,lnum Page number: specifies the starting number (an integer) for page numbering. The ,cnum [,findex beginning page number may be non-positive. The number is incremented at [, inkref]]) page transitions but not printed until it goes positive.
Page 189
Dynamic Job Descriptor Entries (DJDEs) Page- and Record-oriented DJDEs DJDE Definition(s) PALETTE= palette palette Specifies the default ink-palette. It is used when the actual ink-reference does not supply an ink-palette-name. Restriction: This DJDE is gracefully ignored in this version of the LCDS-Module, so the sys- tem is not able to modify / redefine the PALETTE by DJDE.
Page 190
Identifies the index (starting with 1) of the PDE font with which the text is printed. RTEXT= rtext-id rtext-id This option is used to reference a cataloged file of RTEXT parameters previously compiled by XDL. RTEXT= NONE NONE Specifies that no text is to be printed on a separate page.
Page 191
Dynamic Job Descriptor Entries (DJDEs) Page- and Record-oriented DJDEs DJDE Definition(s) SHIFT= Specifies that a shift occurs. A standard size shift occurs if YES is specified (v1=75 and v2 =-75). SHIFT= Specifies that no shift occurs (v1=0 and v2=0). The default is NO. SIDE= Specifies repositioning of the next logical page to the first logical page as defined (side-opt, offset-...
Page- and Record-oriented DJDEs Dynamic Job Descriptor Entries (DJDEs) 5.3.2 Record-oriented DJDEs Record-oriented DJDEs take effect immediately at the next record following the last record of the set of DJDE records of which they are a part; that is, after an END parameter, a com- piled record-oriented DJDE takes effect immediately.
Page 193
Dynamic Job Descriptor Entries (DJDEs) Page- and Record-oriented DJDEs DJDE Definition(s) 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.
Page 194
Page- and Record-oriented DJDEs Dynamic Job Descriptor Entries (DJDEs) DJDE Definition(s) text text Specifies the comment text. The regular meaning of the DJDE-C is to intersperse the DJDE packets with comments. In the LCDS-Module this meaning is enhanced for putting in naviga- tion information into the output data stream.
Page 195
Dynamic Job Descriptor Entries (DJDEs) Page- and Record-oriented DJDEs DJDE Definition(s) DATA= This option has the following components: (pdo, length) (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.
Page 196
Page- and Record-oriented DJDEs Dynamic Job Descriptor Entries (DJDEs) DJDE Definition(s) GRAPHIC= The DJDE GRAPHIC= sentinel specifies that a document or page interleaved (name, vpos graphic image immediately follows this record. It is this DJDE sentinel which ,units causes the LCDS-Module to be started. ,hpos units If no textural data has been previously encountered, the graphic is document in- [, H]...
Page 197
Dynamic Job Descriptor Entries (DJDEs) Page- and Record-oriented DJDEs DJDE Definition(s) A DJDE IMAGE= may also occur in the DJDE packet containing the DJDE GRAPHIC=. The DJDE IMAGE= must specify the T parameter (to indicate refer- ence to a page-interleaved graphic image) and reference the name specified in the DJDE GRAPHIC=.
Page 198
Page- and Record-oriented DJDEs Dynamic Job Descriptor Entries (DJDEs) DJDE Definition(s) IMAGE= This DJDE sentinel is used to position a graphic image on the page. (img-name, img-name vpos units, Specifies the name of a graphic image file. hpos units vpos [, H] [, T] [, D] Specifies the vertical position (top left corner of page) of the top edge of the [, n[/d]]...
Page 199
Dynamic Job Descriptor Entries (DJDEs) Page- and Record-oriented DJDEs DJDE Definition(s) LOGO= name (name, vpos Specifies the name of the logo. A logo specified through PDL will appear on all units, pages of a record. A logo specified through DJDE will appear only on the current hpos units page unless the hold option is specified.
Page 200
Page- and Record-oriented DJDEs Dynamic Job Descriptor Entries (DJDEs) DJDE Definition(s) LOGO= name (name, HERE Specifies the name of a logo image file. [, (VADJ[, + | - HERE ] tvalue)] Specifies the position of the upper left corner of the logo as the top of the next [, HADJ[, + | printed line, at the currently defined left margin (see the MARGIN parameter of -] tvalue)][, H]...
Page 201
Dynamic Job Descriptor Entries (DJDEs) Page- and Record-oriented DJDEs DJDE Definition(s) OVER- Specifies the manner in which overprint lines are handled. (Overprint lines are PRINT= print lines whose carriage control specifies printing with no line spacing since the PRINT | last printed line.).
Dynamic Job Descriptor Entries (DJDEs) DJDE Record Specification 5.5 DJDE Record Specification DJDE records are created by the user as part of the data stream. The system looks for them only if a DJDE prefix has been specified by an IDEN command within the JDL used to pro- cess the job.
Page 204
DJDE Record Specification Dynamic Job Descriptor Entries (DJDEs) • For change mode stacked reports, the DJDE parameters may be placed within the body of the stacked report, where the DJDE records contain the same change field contents as the report to which the DJDE applies. •...
Dynamic Job Descriptor Entries (DJDEs) Application of DJDEs 5.6 Application of DJDEs The following occurrences should be noted when using DJDE records: The specific parameters included in a DJDE packet are the only ones modified when the DJDE is applied. The only exceptions are the JDE=DJDE and JDL=DJDE, which cause all processing parameters contained in the JDE to be updated except for those listed in the ”Job parameter modification restrictions”...
Job Parameter Modification Restrictions Dynamic Job Descriptor Entries (DJDEs) 5.7 Job Parameter Modification Restrictions To process a DJDE, the system has already been required to process data up to the rec- ognition and interpretation of the DJDE itself. This requires that the basic description of the input source must have been correct prior to the application of the DJDE.
Page 207
Dynamic Job Descriptor Entries (DJDEs) Job Parameter Modification Restrictions Command Parameter(s) ROFFSET All parameters RAUX All parameters RPAGE All parameters RSTACK TEST (online only) VOLUME TCODE CODE If a front cover is invoked in a selected JDE which takes effect after the first page of the report, a cover is printed at the point where the DJDE is applied.
Duplex DJDE Page Printing Dynamic Job Descriptor Entries (DJDEs) 5.8 Duplex DJDE Page Printing When certain DJDEs (listed below) are invoked between an odd-numbered page (front side) and an even-numbered page (back side), the following printing sequence occurs. The odd-numbered page is printed as usual, but with a blank back side. What would have been printed on the back side (the even-numbered page) is printed on the front of the next sheet.
Dynamic Job Descriptor Entries (DJDEs) Effect of Multiple Logical Pages 5.9 Effect of Multiple Logical Pages If multiple BEGINs are being used to define multiple logical pages on one physical page the following points should be considered: With the exception of DEPT and SHIFT, all page-oriented DJDEs are applied at a logical page boundary.
Online DJDE Restrictions Dynamic Job Descriptor Entries (DJDEs) 5.10 Online DJDE Restrictions If an online job has header pages only (no trailers), DJDEs in the first header page of a report are recognized but not applied. Also, if headers only are defined, DJDEs invoked within the current report are applied to the first header page of the following report.
Highlight Color Support General 6 Highlight Color Support 6.1 General Color documents – process color and highlight color or custom tone – are becoming in- creasingly more important. Beginning with PRISMA+LCDS V2.02 the advantage of true color is available in its essen- tials for the first time, even without support of the full LCDS command set.
General Highlight Color Support 6.1.2 Why Use Color? There are a number of excellent reasons for using color applications: Understanding • Makes information easier to read through emphasis • Increases recognition rates • Adds visual clarity to document structure Impact •...
Highlight Color Support Implementation 6.2 Implementation The printing method used by Océ for all printers except the VarioStream 9220 causes a reg- ister deviation, since black and color are printed in two separate but consecutive processes. Fusing after the first pass causes the paper to shrink. This shrinkage – or rather the result- ing register deviation –...
Page 214
Implementation Highlight Color Support Example 1: Shading The following example is designed to demonstrate various kinds of shadings (N.B., not orig- inal print samples). In the bitmap column, "B" represents black pixels and "0" white pixels. % Shading Shading Corresponding Bitmap 0 B B 0 0 0 0 0 0 0 B 0 0 0 0 0...
Page 215
Highlight Color Support Implementation Example 2: Hues The following is designed to demonstrate various hue examples. In the bitmap column, "B" represents black pixels, "C" represents highlight-color pixels, and "0" white pixels. Note that black is not included, which results in pure HC shading. The corresponding LCDS bitmaps are formed according to the following rules: •...
Page 216
Implementation Highlight Color Support % Hue Corresponding Bitmap LCDS Bitmap with HC Element 0 B B 0 0 0 C C 0 C C 0 0 0 C C 0 0 B 0 0 0 C C 0 0 C 0 0 0 C C 5% Black and 0 0 0 0 0 0 C C 0 0 0 0 0 0 C C...
Page 217
Highlight Color Support Implementation Example 3: Highlight color in variable text The following example, designed to increase reader attention, shows a highlight color line controlled by INKINDEX or ..CME...INK=..Company nnn Poing dd.mm.yy ......Invoice ..125.00 Item 1 312.20 Item 2 298.20...
Implementation Highlight Color Support Example 4: Two images combined The following example shows a combined image (right) composed of a highlight-color im- age (left) and a black image (middle). The resulting combination gives the impression of a multi-color image. Image 1: HC-Image Image 2: Black Image Combined Image: "Multi-color”...
Page 219
Highlight Color Support Implementation The two printers filter their respective colors from the print data stream and print them, thus HC simplex printing. HC and duplex printing is accomplished by turning the paper over be- tween the two printers. Recto pages are printed in black and verso in HC, given the data is pre-processed accordingly (e.g., ...
LCDS Language Resources Highlight Color Support 6.3 LCDS Language Resources The Xerox highlight color commands are supported for the first time in PRISMA+LCDS V2.02. It should be noted that due to differing Océ and Xerox print processes a 1:1 representation of Xerox 4850 and 4890 applications is not possible.
The following table briefly outlines which Xerox statements are supported in LCDS and which are subject to restrictions. All color-specific extensions are implemented by the XDL syntax check. The Support column shows the level of support, when processing variable data. Generally all commands and options are completely syntax checked.
Queue Management Highlight Color Support 6.4 Queue Management Because a printer's color capabilities are not monitored, queue management is not an option. Color applications will be printed in B&W if the printer is not equipped with color. B&W applications will be printed B&W even if the printer is equipped with color. 6.4.1 INK Catalogs The current version of the LCDS-Module provides these INK catalogs: •...
Page 225
Highlight Color Support Queue Management Catalogs and Palettes The following table shows the catalogs and their associated palettes. Catalog and palette names correspond to those used in Xerox applications. DFAULT Xerox Xerox1 (not supported) SIMPLE SIMPLE SIMPLE DFAULT DFAULT MONO PICTORIAL PICTORIAL MONO...
Page 226
Queue Management Highlight Color Support SIMPLE Palette The SIMPLE palette contains the available primary colors, each in 100%, but no shadings. The color names are long names. The SIMPLE palette consists of the following colors: Color Océ Color (ALTernate color or blacK) BLACK K100 BLUE...
Page 227
Highlight Color Support Queue Management DFAULT Palette The DFAULT palette contains the primary color BLACK only, but different shadings, cover- ing gradations from black -> white. The color names are alphanumeric (see also PICTORI- AL palette). The DFAULT palette consists of the following colors: Color Océ...
Page 228
Queue Management Highlight Color Support MONO Palette The Mono palette is comparable with the DFAULT Palette in that it contains the primary col- or BLACK only, but covering shading gradations from black -> white. The color names are alphanumeric (see also DFAULT / PICTORIAL Palette). The MONO palette consists of the following colors: Color Océ...
Page 229
Highlight Color Support Queue Management RED Palette The RED palette consists of the following colors: Color Océ Color Color Océ Color (ALTernate color or (ALTernate color or blacK) blacK) ALT100 VIVID RED ALT100 PINKISH WHITE ALT23 PALE PINK ALT23 LIGHT PINK ALT45 MODERATE ALT69...
Page 230
Queue Management Highlight Color Support Color Océ Color Color Océ Color (ALTernate color or (ALTernate color or blacK) blacK) R1K94 R15K67 R2K92 R16K1 ALT23 R3K86 ALT23 R4K72 R17K7 ALT30 R4K80 R17K73 R4K82 R17K75 R6K51 R18K57 R6K61 R21K45 R6K89 R22K1 ALT23 R8K19 R22K37 R8K31...
Page 231
Highlight Color Support Queue Management Color Océ Color Color Océ Color (ALTernate color or (ALTernate color or blacK) blacK) R36K43 R72K13 ALT90 R37K27 ALT69 R73K13 ALT90 R38K18 ALT58 R75K2 ALT82 R40K1 ALT45 ALT82 R40K37 ALT82 R76K13 ALT90 R41K4 ALT45 ALT82 ALT45 ALT90 R43K33...
Page 232
Queue Management Highlight Color Support BLUE Palette The BLUE palette consists of the following colors: Color Océ Color Color Océ Color (ALTernate color or (ALTernate color or blacK) blacK) BLUE ALT100 STRONG BLUE ALT100 BLUISH WHITE ALT12 EXTREMELY ALT23 PALE BLUE VERY PALE ALT38 BLUE...
Page 233
Highlight Color Support Queue Management Color Océ Color Color Océ Color (ALTernate color or (ALTernate color or blacK) blacK) B1K96 B12K83 B2K20 B13K77 B2K93 B15K68 B3K75 B16K1 ALT23 B3K83 B16K4 ALT23 B3K85 B16K77 B3K88 B18K59 B4K65 B18K75 B5K25 B20K45 B5K42 B22K36 B5K50 ALT23...
Page 234
Queue Management Highlight Color Support Color Océ Color Color Océ Color (ALTernate color or (ALTernate color or blacK) blacK) B37K33 ALT73 B76K2 ALT82 ALT38 B76K22 ALT100 B38K17 ALT58 B82K14 ALT100 B38K23 ALT69 ALT90 B39K40 B83K17 ALT100 B42K40 ALT82 B85K1 ALT90 B43K1 ALT45 B87K8...
Page 235
Highlight Color Support Queue Management GREEN Palette The GREEN palette consists of the following colors: Color Océ Color Color Océ Color (ALTernate color or (ALTernate color or blacK) blacK) GREEN ALT100 VIVID GREEN ALT100 GREENISH ALT8 WHITE VERY LIGHT ALT38 GREEN BRILLIANT ALT90...
Page 236
Queue Management Highlight Color Support Color Océ Color Color Océ Color (ALTernate color or (ALTernate color or blacK) blacK) G2K82 K100 K100 G2K85 G2K87 G2K92 G3K35 G3K45 G3K53 G3K66 G3K73 G4K19 G4K24 G4K89 ALT8 G5K5 ALT12 G5K10 G6K66 G6K76 G7K24 G7K50 G8K17 G8K29...
Page 237
Highlight Color Support Queue Management Color Océ Color Color Océ Color (ALTernate color or (ALTernate color or blacK) blacK) G9K77 G27K20 ALT58 G11K1 ALT12 G27K26 ALT58 G11K7 ALT23 G28K37 G12K67 G31K43 G13K60 ALT38 G13K75 G33K1 ALT38 G13K77 G33K2 ALT38 G16K5 ALT23 G33K41 G16K28...
Page 238
Queue Management Highlight Color Support Color Océ Color (ALTernate color or blacK) G62K24 ALT90 G63K1 ALT69 G66K16 ALT82 G67K2 ALT69 ALT73 G73K16 ALT90 G76K9 ALT90 ALT82 G84K7 ALT100 ALT90 G94K2 ALT100 G100 ALT100 XEROX1 Catalog The Xerox1 catalog is not supported in the current version of LCDS. A29247-X4-X-8-7672...
Highlight Color Support Migrating to HC 6.5 Migrating to HC This section provides important information related to migrating current applications to col- or. It is assumed that the user has never used HC and wants to benefit from the advantages of HC printing offered by Océ...
Page 240
Migrating to HC Highlight Color Support A29247-X4-X-8-7672...
Appendix Supported, restricted and not supported XDL/DJDE-commands 7 Appendix 7.1 Supported, restricted and not supported XDL/DJDE-commands Statement Command Off- DJDE Comment line line legend: Y: command allowed N: command not allowed Ign.: command ignored: not processed work default handling. -: DJDE is not allowed...
Page 242
Supported, restricted and not supported XDL/DJDE-commands Appendix Statement Command Off- DJDE Comment line line ACCT DEPT P/ok USER BIN/TRAY -only START-JSL-only ALTER (DJDE only!) R/ok BATCH (DJDE only!) R/ign BANNER HCOUNT HJOBNO HRPTNA TCOUNT TEST TYPE BDELETE TEST BLOCK ADJUST...
Page 243
Appendix Supported, restricted and not supported XDL/DJDE-commands Statement Command Off- DJDE Comment line line POSTAMBLE PREAMBLE ZERO BSELECT TEST C (DJDE only!) R/ok enhanced (see de- tailed descripton) CANCEL (DJDE only!) R/ok ac: CATALOG analysed by XDL- compiler ac: CME...
Page 244
Supported, restricted and not supported XDL/DJDE-commands Appendix Statement Command Off- DJDE Comment line line FILE (DJDE only!) R/ok Parameter D= de- lete not supported GRAPHICS (DJDE only!) R/ok IDEN OFFSET OPRINFO PREFIX SKIP ac: IDR ICATALOG P/ok ILIST P/ok PALETTE...
Page 245
Appendix Supported, restricted and not supported XDL/DJDE-commands Statement Command Off- DJDE Comment line line LINE DATA R/ok Only 3211 FCB- Formats pro- cessed. FONTINDEX P/ok INKINDEX P/ok MARGIN P/ok OVERPRINT R/ok PRINT2 and IG- NORE are treated like PRINT PCCTYPE...
Page 246
Supported, restricted and not supported XDL/DJDE-commands Appendix Statement Command Off- DJDE Comment line line CYCLEFORMS DENSITY like DEFAULT DESTINATION DUPLEX P/ok FACEUP specifies faceup delivery of pages (see FACEUP for details) FEED P/ok FORMAT P/ok FORMS P/ok GRAPHICS GRAPHIC = YES is always as- sumed.
Page 247
Appendix Supported, restricted and not supported XDL/DJDE-commands Statement Command Off- DJDE Comment line line OFFSET like ALL PAPERSIZE PURGE RESOLUTION SHIFT P/ok SIZING always SEMIAU- STAPLE see printer capabil- ity of staple func- tion STOCKS P/ign UNITS R/ign ac: PCC...
Page 248
Supported, restricted and not supported XDL/DJDE-commands Appendix Statement Command Off- DJDE Comment line line RAUX TEST RDELETE TEST at the moment there is no differ- ence between on- and off-line RECORD ADJUST CONSTANT FORMAT LENGTH LMULT LTHFLD OFFSET POSTAMBLE PREAMBLE...
Page 249
Appendix Supported, restricted and not supported XDL/DJDE-commands Statement Command Off- DJDE Comment line line ROFFSET PASSES TEST ac: ROUTE RFORM P/ok RTEXT P/ok RPAGE SIDE P/ok TEST WHEN RRESUME BEGIN TEST RSELECT TEST RSTACK ACCTINFO DELIMITER HRPTNA PRINT TEST RSUSPEND...
Page 250
Supported, restricted and not supported XDL/DJDE-commands Appendix Statement Command Off- DJDE Comment line line ac: STOCKSET ASSIGN INIFED SYSPAGE dd: SYSTEM NO DEFAULT ac: TABLE CONSTANT MASK ac: TCODE DEFAULT restricted to specif- ic names ASCII, EBCDIC TASSIGN TRESET ac: VFU...
Need help?
Do you have a question about the XDL and is the answer not in the manual?
Questions and answers