Print Server version 6.
Xerox Corporation Global Knowledge & Language Services 800 Phillips Road Bldg. 845-17S Webster, NY 14580 Copyright © 2007 Xerox Corporation. All rights reserved. Copyright protection claimed includes all forms and matters of copyrighted material and information now allowed by statutory or judicial law or hereinafter granted, including without limitation, material generated from the software programs that are displayed on the screen such as styles, templates, icons, screen displays, looks, etc.
Table of contents Laser safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii Ozone information: U. S. only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii Operation safety: U. S. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii Operation safety: Europe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix Warning markings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of contents Ending a JSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29 Sample completed JSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30 Before creating a JSL: considerations and decisions . . . . . . . . 1-31 Input data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-32 Output specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-32 Special features . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of contents Packed data formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9 Record formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9 Record structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10 Multivolume processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10 Input processing command descriptions . . . . . . . . . . . . . . . . . . . . . . . 2-11 BLOCK command . . . . . . . . . . .
Table of contents PCC DEFAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCC INITIAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCC MASK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCC command: points to note . . . . . . . . . . . . . . . . . . . . PCC command example . . . . . . . . . . . . . . . . . . . . . . . . RECORD command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Record command parameters . . . . . . . . . . .
Table of contents VOLUME MAXLAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . VOLUME MINLAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VOLUME OPTIMIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . VOLUME OSCHN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VOLUME OSHDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VOLUME OSTLP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VOLUME RMULT . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of contents BSELECT and BDELETE commands: points to note . . Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LMODIFY command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LMODIFY command parameters . . . . . . . . . . . . . . . . . . LMODIFY INK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of contents RSTACK DELIMITER . . . . . . . . . . . . . . . . . . . . . . . . . . RSTACK HRPTNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . RSTACK PRINT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RSTACK TEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RSTACK command: points to note . . . . . . . . . . . . . . . . RSTACK command example . . . . . . . . . . . . . . . . . . . . . 3-56 3-56 3-57 3-58 3-58 3-59 4. Specifying print format parameters . . . . .
Table of contents LINE FONTINDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LINE GDATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LINE INKINDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LINE LPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LINE MARGIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LINE OVERPRINT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LINE PCC . . . . . . . . . . . . . . .
Table of contents OUTPUT SF1FUNCTION . . . . . . . . . . . . . . . . . . . . . . . 4-77 OUTPUT SF2FUNCTION . . . . . . . . . . . . . . . . . . . . . . . 4-78 OUTPUT SHIFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-78 OUTPUT SIZING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-79 OUTPUT STAPLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-81 OUTPUT STOCKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-82 OUTPUT SYSPPR . . . . . . . . . . . . . . .
Table of contents Considerations and cautions for using DJDEs . . . . . . . . . . . . . . . . . . . 5-8 Types of DJDEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10 DJDE descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14 ALTER DJDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14 ALTER DJDE: point to note . . . . . . . . . . . . . . . . . . . . . . 5-15 Examples of ALTER DJDE . . . . . . .
Table of contents FORM[S] DJDE: point to note . . . . . . . . . . . . . . . . . . . . GDATA DJDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GRAPHIC DJDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GRAPHIC DJDE: points to note . . . . . . . . . . . . . . . . . . ICATALOG DJDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ICATALOG DJDE example . . . . . . . . . . . . . . . . . . . . . . IDFAULT DJDE . . . . . . . . . . . . .
Table of contents SAVE DJDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAVE DJDE: point to note . . . . . . . . . . . . . . . . . . . . . . . SEFMAP DJDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SEFMAP DJDE: points to note . . . . . . . . . . . . . . . . . . . SEFMAP DJDE examples . . . . . . . . . . . . . . . . . . . . . . . SF1FUNCTION DJDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SF2FUNCTION DJDE . . . . . . . . . . .
Table of contents Input unpacking examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Valid host computer and label specifications . . . . . . . . . . . . . . . . . . . . Host system JDLs on system software CD . . . . . . . . . . . . . . . . . . . . . . LPS tape label format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1 D-2 D-4 D-5 Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of contents xvi Using LCDS Print Description Language
Laser safety WARNING Adjustments, use of controls, or performance of procedures other than those specified herein may result in hazardous light exposure. Xerox FreeFlow Print Server-based printers are certified to comply with the performance standards of the U.S. Department of Health, Education, and Welfare for Class 1 laser products. Class 1 laser products do not emit hazardous radiation.
Operation safety: U. S. Your Xerox equipment and supplies have been designed and tested to meet strict safety requirements. They have been approved by safety agencies, and they comply with environmental standards. Please observe the following precautions to ensure your continued safety. WARNING Improper connection of the equipment grounding conductor may result in risk of electrical shock. • Always connect equipment to a properly grounded electrical outlet.
1-800-828-6571 For customers outside the United States, contact your local Xerox representative or operating company. Operation safety: Europe This Xerox product and supplies are manufactured, tested and certified to strict safety regulations, electromagnetic regulations and established environmental standards. Any unauthorized alteration, which may include the addition of new functions or connection of external devices, may impact the product certification.
WARNING This product must be connected to a protective earth circuit. This product is supplied with a plug that has a protective earth pin. This plug fits only into an earthed electrical outlet. This is a safety feature. Always connect equipment to a properly grounded electrical outlet. If in doubt, have the outlet checked by a qualified electrician. To disconnect all electrical power to the product, the disconnect device is the power cord. Remove the plug from the electrical outlet.
Maintenance Any operator product maintenance procedures are described in the user documentation supplied with the product. Do not carry out any maintenance on the product which is not described in the customer documentation. Before cleaning your product Before cleaning this product, unplug the product from the electrical outlet. Always use materials specifically designated for this product; the use of other materials may result in poor performance and may create a hazardous situation.
This is a Class A product. In a domestic environment this product may cause radio frequency interference, in which case the user may be required to take adequate measures. Shielded interface cables must be used with this product to maintain compliance with Council Directive 89/36/EEC.
Introduction Using LCDS Print Description Language provides information on how to use PDL to program LCDS job descriptions that can be used on any Xerox FreeFlow Print Server-based printing system featuring LCDS. Examples of these systems include, but are not limited to: the Xerox DocuPrint 75/90 and 100/115/135/155/180 Enterprise Printing Systems, the DocuPrint 75 MX, the Xerox DocuTech 128/155/180 HighLight Color Printing System, and the Xerox Nuvera 100/120 family of printing systems.
Introduction Xerox 180, 180MX, 96, and 96MX Laser Printing Systems The following families of printing systems support subsets of the PDL commands that can be used.
Introduction – WARNINGS: Printed in bold red • Angle brackets: Angle brackets surrounding a word indicate the word is the name of a key on the print server keyboard. Key names start with a capital letter. (Example: Press .) • Square brackets: Square brackets around words or phrases indicate the names of buttons to click or menu options to select on a screen., Square brackets also indicate the names of fields and text boxes on screens. (Example: In the [Folders] field, select [resources].
Introduction xxvi Using LCDS Print Description Language
1. PDL principles and procedures The Xerox LCDS Print Description Language (PDL) is a set of commands you give to the printing system to define properties such as the appearance, output destination, and paper feed source for your LCDS print job. You can use LCDS PDL to do all of the following in your print jobs: • Change and mix font types on a page to page, line to line, or character to character basis.
PDL principles and procedures Enabling PDL features and functions To enable these functions, you enter PDL commands to enable the following for your print job: • Describe the input (type, format, characteristics, and source) • Define any logical or special processing functions to be performed on selected text, pages, or copies • Describe the output (type, format, font selection, accounting options, and destination) Each command has a set of parameters and parameter options used to define the above ch
PDL principles and procedures Refer to the “Specifying DJDE records” section of the “Using Dynamic Job Descriptor Entries (DJDEs)” chapter for information on how to include DJDEs in the data stream. PDL command structure and components In order for the system to recognize and respond correctly to your PDL commands, you must construct and enter them correctly. Some components of PDL commands must be specified every time, while others are optional. There are some rules for constructing commands.
PDL principles and procedures • Comments (if appropriate) These components are shown in the following figure. Figure 1-1. Diagram of PDL command components 1. Command statement 2. Identifier 3. Command keyword 4. Parameter keyword 5. Parameter option 6. Additional parameter keywords and options In the example above, the identifier, parameter keyword, and parameter options are part of the VFU command, which is represented by the required command keyword VFU.
PDL principles and procedures Command identifier Some PDL commands require identifiers to precede their command keywords. By coding an identifier before a command, you associate the identifier with the command. This allows the command to be referenced (by its identifier) by other commands within the JSL. Some identifiers also determine the names of the files that the Xerox Job Descriptor Compiler creates. Different syntax rules apply to identifiers, depending on the command being coded.
PDL principles and procedures Refer to Appendix A, “PDL command and DJDE summary,” for a list of all available command keywords. Parameters Parameter options and right part components Each command keyword is followed by parameters. Parameters give precise specifications for the print job or application. • In commands that comprise a JSL, each parameter consists of a left part and a right part, separated by an equal (=) sign. (Spaces before and after the equal sign are optional.
PDL principles and procedures Example: • ABNORMAL ERROR=CONTINUE, OTEXT=(... WAIT); ACCT USER=BOTH; Variable references In creating your JSLs, you will often include variable references, which may be either file names of resources stored on the system disk (forms, CMEs, PDEs, stocksets, and so on) or identifiers for commands coded previously in the JSL.
PDL principles and procedures • • • EBCDIC Octal Kanji – Using the # character (case toggle) Within a text string, the # character may be used as a case toggle. In other words, when a text string is encountered, it is assumed that characters are inserted into the print line as they appear in the text string (usually in uppercase). If the system encounters a #, it interprets the characters as lowercase mode.
PDL principles and procedures Table 1-2. Types of string constants Constant Definition Example Hexadecimal Normally used as string constants, but they may also be used as value constants. Each pair of hexadecimal characters results in one byte. A hexadecimal constant must immediately be preceded by the characters X apostrophe (X’), then followed by another apostrophe, to indicate to the PDL compiler that the expression that follows is in hexadecimal.
PDL principles and procedures Table 1-2. Types of string constants (Continued) Constant Definition Example 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.
PDL principles and procedures Table 1-2. Types of string constants (Continued) Constant Definition Example H2 and H6 H2 and H6 constants generate H2000 BCD and H6000 BCD codes, respectively. Use of H2 and H6 is identical to use of E and A prefixes described in the previous sections of this table. Since H2000 and H6000 BCD are defined as 6-bit codes, no specification greater than X’3F’ generates a legal character.
PDL principles and procedures Command syntax For the system to read and process any command you put in your JSL, you must place all elements in the proper order and use the correct symbol or amount of space to separate them. Syntax rules When you enter your PDL commands at the print server, workstation, or host keyboard, you must follow these syntax rules in order for the system to recognize the commands.
PDL principles and procedures END; END; • Multiple part options: Use parentheses to enclose multiple parts of a parameter option. Example: CRITERIA CONSTANT=(0,120,EQ,T1); • Order of right part components: If you want to specify more than one component of a parameter right part, enter the components in the order they are shown in the command description and separated by commas. Example: The MESSAGE OTEXT parameter has two alternative options, one of which has four components enclosed in parentheses.
PDL principles and procedures NOTE: Commas and blanks cannot be used interchangeably. Many commands require commas to separate the parameters, and blanks are not valid delimiters. The syntax diagram in each command and parameter description shows which delimiters to use. • Command example Uppercase text: Use UPPERCASE letters when coding PDL commands. Comments, however, need not be in uppercase. The following LINE command example contains three parameters.
PDL principles and procedures Sample PDL commands The following table lists a set of commands in the order that they might appear in a JSL. It shows the components of PDL commands and a variety of right part options. The commands are displayed below in table form so you can more easily distinguish their components. When coding a JSL, you may want to use tabs to separate these parts. You may also prefer to place all parameters for a command on the same line with the command keyword. Table 1-5.
PDL principles and procedures Table 1-5.
PDL principles and procedures The Job Source Library (JSL) The PDL commands that you issue to the printing system must be entered together in a file called a “job source library” (JSL). The JSL file is then compiled to convert it to an object file called a “job descriptor library” (JDL), which the system can read. The printing system then responds to the commands contained in the JDL file and prints the job the way you want it to appear.
PDL principles and procedures What does a JSL specify? A JSL is a set (“library”) of commands that specify various aspects of a print job, including: • What portion of the variable and fixed data to use • Placement, font, and point size for the variable and fixed data • Which fonts, forms, images, signatures, and logos to use • What paper stocks to use for the job • Page layout • Banner page recognition and processing • How many copies to print • Messages to the operator • Use of black or c
PDL principles and procedures Refer to “Coding a JSL” in this chapter for the procedure for creating a Job Source Library. PDL commands are organized within a JSL in groupings called “command levels.” • JDL or system level commands • Catalog level commands • Job or JDE level commands You may code commands within these levels following the JDL command, which identifies the start of the system level. The system level must have at least the SYSTEM or JDL command.
PDL principles and procedures The following table illustrates a sample JSL file format and provides examples. Note that comments are used to designate the beginning of each level. Table 1-7.
PDL principles and procedures JDL name Begin your JSL by deciding on a name for the compiled JDL and entering the “JDL” command on the first line of the JSL. The JDLNAME is a 1 to 6 character alphanumeric identifier specifying the name of the JDL to be created. Select a name that is related to the function of the JDL and identifies the type of jobs you are creating. For example, if your site has several input sources, you might want to name the JDL for an online job “JDLONL: JDL;.
PDL principles and procedures The VFU (vertical format unit) commands in the JSL illustration shown in table 1-7 are examples of commands with identifiers. (In this JSL, the VFU command identifiers are called “VFU1” and “VFU9.”) The types of commands described in the following sections are usually coded first at the system level (following the JDL command) because: • They require identifiers. • They typically apply to all jobs within a JSL.
PDL principles and procedures Specifying VFUs The VFU (vertical format unit) command specifies the vertical tabbing for the print job. There can be more than one VFU identified. Each VFU command requires an identifier.
PDL principles and procedures Specifying formats (PDEs) Using copy modification entries There are many standard formats or print description entries (PDEs) available for your JSL. These formats are listed in the “PDE command” section of the “Specifying print format parameters” in Chapter 4. PDEs, like VFUs, require identification; for example: PDE1: PDE BEGIN=(0.18IN,0.66IN), FONT=(L0112B,L01BOA), PMODE=LANDSCAPE; PDE2: PDE BEGIN=(1.03,.51), BEGIN=(6.30,.
PDL principles and procedures Setting up input parameters You may want to start by specifying 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.
PDL principles and procedures Catalog level commands The catalog level allows the coding of commands common to several JDEs. A catalog can then be referenced in an INCLUDE parameter in any following JDE commands. A catalog section of a JSL begins with the CATALOG command and ends with the appearance of another CATALOG command or a JOB command. CATALOG commands may contain the same commands that appear in the JOB command.
PDL principles and procedures Examples of JOB commands Following are some examples of job commands. JOB2: JDE; JOB3: JDE INCLUDE=CAT2; JOB4: JDE; LINE VFU=VFU2; OUTPUT FORMS=AY2F; A JOB or JDE command remains in effect until another JOB or JDE command or an END command is encountered. The identifier in a JOB or JDE command, as in JOB2, JOB3, or JOB4 in the previous example, is used with the identifier on the JDL or SYSTEM command to initiate a print job.
PDL principles and procedures Here is a sample STOCKSET command: SSML: STOCKSET Specifying output requirements ASSIGN=('WHITE',CVR), ASSIGN=('YELLOW',BLL), ASSIGN=('GREEN',SUM), INIFEED=CVR, SYSPAGE=SUM; 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 them of special circumstances.
PDL principles and procedures Comments Comments are optional statements you may include in the source file to identify sections of the JSL, describe selected PDL commands and their functions, or provide messages for anyone who modifies the JSL later. The system does not perceive these comments as commands and ignores them. Comments may appear anywhere within the JSL and may consist of multiple records.
PDL principles and procedures CMEs, PDEs, TSTs, and STOCKSETs: Following an END; command for a JSL, you may code one or more CMEs (CME command), PDEs (FORMAT command), TSTs (ROUTE command), or stocksets (STOCKSET command). If the CME, PDE, TST, or stockset that you are coding will be used by more than one JSL file or is referenced by a DJDE, compile and catalog it as a separate file (not part of any JSL). Refer to “Compiling a JSL,” later in this chapter, for the procedure.
PDL principles and procedures SSML: LINE DATA=(1,132), PCCTYPE=IBM3211, VFU=VFU1; ACCT USER=TRAY; IDEN PREFIX='C9700', SKIP=7, OFFSET=1; STOCKSET ASSIGN=('WHITE', CVR), ASSIGN=('YELLOW', BLL), ASSIGN=('GREEN', SUM), INIFEED=CVR, SYSPAGE=SUM; MESSAGE OTEXT=('ALL FORMS DUPLEX ONLY!!!', 1, WAIT); /* Job level commands*/ JOB1: JDE; OUTPUT JOB2: DUPLEX=YES, SHIFT=YES, FORM=SMPLE, MODIFY=CME1, FORMAT=PDE1,COPIES=10, OFFSET=FIRST, PURGE=NO; JDE; LINE VFU=VFU2UP; OUTPUT FORMAT=PDE2, FORMS=SPL2, C
PDL principles and procedures Input data Before starting to develop the JSL for your application, you should know the following information about the input data.
PDL principles and procedures • Will the output be delivered face up, N to 1 (last page first), and collated? • Will the data be printed on one side of the page (simplex) or on both sides (duplex)? • Will graphics be used? • What types of applications will be printed? For example: – Forms – Reports – Letters – Billing statements using variable data, that is, information that varies from customer to customer.
PDL principles and procedures Interactions between JSLs, catalogs, and jobs Before starting to develop the JSL for your application, consider the interactions, similarities, and differences between various JSLs, catalogs, and jobs. Remember: although a printing system can have only one JOB or JDE in effect at a time, you can still create JSLs with multiple JOBs or JDEs, and switch between the JDEs by using DJDEs in the data stream.
PDL principles and procedures Logical page A “logical page” is a user defined page image that is bordered by Top of Form and Bottom of Form and left and right margin specifications. Up to 63 logical pages can be defined on a physical page. NOTE: You are not able to specify right margins on logical pages. The right margin size is determined by the left margin and the line length.
PDL principles and procedures Figure 1-2. Vertical and horizontal positions in portrait mode 1. Left margin (horizontal position or hpos) 2. Character cell 3. Top margin (vertical position or vpos) Figure 1-3. Horizontal and vertical positions in landscape mode 1. Left margin (hpos) 2. Character cell 3.
PDL principles and procedures Portrait orientation The following figure shows portrait orientation dimensions for a document using FMT6 (the standard portrait format for impact printer output). Figure 1-4. Page layout for FMT6: Impact printer format, 8.
PDL principles and procedures Landscape orientation The following figure shows landscape orientation dimensions for a document using FMT1 (the standard landscape format for impact printer output). Figure 1-5. Page layout for FMT1: Equivalent impact printer format, 8.1 lines per inch Fonts A font is a character set that has a unique type style, type size, and orientation. Both fixed pitch and proportionally spaced fonts are available for use on your printing system.
PDL principles and procedures Figure 1-6. Fixed pitch and proportional font character spacing 1. Fixed pitch character cell 2. Proportionally spaced character cell Because the length of a line printed with a proportional font is relatively unpredictable, fixed pitch fonts are used for variable data on a report to avoid overprinting of forms by variable data. Proportional fonts are normally used for form data such as titles and headings.
PDL principles and procedures In addition to typeface, style, and size, a font can be defined by its orientation: • Landscape • Portrait • Inverse landscape • Inverse portrait Custom fonts, signatures, and logos may be ordered from Xerox through your sales representative. Overriding PDL commands The system default values are listed in the “PDL command and DJDE summary” in Appendix A. The printing system uses the defaults for parameters you do not specify in the JSL.
PDL principles and procedures Figure 1-8. Command override sequence User interface window overrides Setting late binding attributes Some PDL commands and DJDEs that are specified in the JSL can be overridden by queue properties that have been selected on user interface queue management windows. • Quantity: The highest priority override is the Quantity (copy count) specification that can be set on the Queue Manager or the Online Manager window. This parameter must be set before the job is decomposed.
PDL principles and procedures Figure 1. Print Services window with Queue Manager selected 2. On the queue list, double-click the name of the queue to which your job will be sent. The Properties window for the selected queue opens. 3. On the Properties window, click the tab that contains the attributes for which you want to specify an override.
PDL principles and procedures – The FreeFlow Print Server on the DP EPS supports unlimited stock media to be assigned to a tray. – The FreeFlow Print Server on the Nuvera 1xx MX DPS supports up to 15 different media to be assigned to a tray.
PDL principles and procedures Figure 2. Output tab on Queue Properties window with [Override] options selected NOTE: The [Initial Form] selection that appears on some of the user interface windows functions differently from the other options that can override JDL commands. [Initial Form] is overridden by DJDEs, even if its [Override] option is selected. 5. Click [OK]. The Properties window closes, and the properties for which you selected [Override] are implemented for the next job.
PDL principles and procedures Specifying overrides while a job is printing If you want to specify late binding overrides that will immediately take effect on a job that is currently printing, do the following: 1. Click [Pause Printing] on the Print Services window to halt printing. 2. Follow the procedure for specifying late binding attributes, described in the previous section.
PDL principles and procedures NOTE: This JSL contains some highlight color commands and parameters: IDR, ILIST, ICATALOG, and IDEFAULT. These commands are processed, but most have no effect on the output if the JSL is used to print on the FreeFlow Print Server LCDS systems. However, if the JSL is used on a highlight color printing system such as the Xerox 4890 LPS, the commands are followed.
PDL principles and procedures Table 1-8. Sample JSL (Continued) /*Catalog level commands*/ CATPOW: CATGRP: CATALOG; VOLUME HOST=IBMONL, CODE=EBCDIC; RECORD LENGTH=135, STRUCTURE=VB, PREAMBLE=2, ADJUST=3; CATALOG; VOLUME HOST=IBMONL, CODE=EBCDIC; RECORD LENGTH=135, STRUCTURE=VB, PREAMBLE=1, LTHFLD=1, FORMAT=BIN, OFFSET=0, ADJUST=2; /*Job or JDE level commands*/ 1: JDE; 2: 3: DFLT: OUTPUT IDR=IDR1, NUMBER=(1, 1, 0, 1,’BLACK’), FORMAT=PDE1, LOGO=(SIG1,1.5 IN,6.
PDL principles and procedures System defaults can be used for all other specifications, although typically each application has its own specific characteristics. • Use tab spacing to create columns for the command identifiers, commands, and parameters in your JSLs. While not required by the system, this organization makes it much easier to identify command sets, their commands, and the parameters of each command quickly, reducing the chance of error.
PDL principles and procedures • After deciding on the command levels you will use, make a test run of the job to see the output and to make any necessary adjustments. • Design forms to accommodate placement of data on the page. NOTE: It is best to start with the standard formats (print description entries or PDEs) that are predefined on the system. Each of these formats (FMT1 through FMT11) matches standard form layouts.
PDL principles and procedures Before you start Before you start to code your JSL, be sure you have done the following: 1. Identify the source media and data format. 2. Design the layout of your print job. 3. Build forms for the job, if necessary. 4. Identify logical processing requirements. 5. Determine whether you will use catalogs. Short JSL coding procedure The fastest and easiest way to create a JSL is to build it from an existing one, such as the default JSL (named DFAULT.
PDL principles and procedures Figure 1-9.
PDL principles and procedures c. From the Programs menu, select [Text Editor]. A Text Editor window opens. Figure 1-10. Text Editor window 2. Bring the default JSL (stored in the “lcds” folder on the system disk) into the Text Editor, using the following procedure. a. From the File menu on the Text Editor menu bar, select [Include...]. The Text Editor – Include a File window opens.
PDL principles and procedures Figure 1-11. Text Editor – Include a File window b. In the [Enter path or folder name:] text field at the top of the Include a File window, enter one of the following directory paths and press . /opt/XRXnps/resources/lcds/ or /var/spool/XRXnps/resources/lcds/ NOTE: The file and folder names are case–sensitive. Be sure to enter the directory path exactly as it is shown above, with regard to uppercase and lowercase letters.
PDL principles and procedures d. Click the file name DFAULT.JSL, then click [OK]. The default JSL is displayed in the Text Editor window. 3. Using the default JSL as a base, enter any changes, additional commands or parameters, and deletions that you need to make in order to construct your new JSL. NOTE: You should consider carefully the ID name that you enter in the JDL or SYSTEM command (the first line of the JSL), because this identifier determines the name of the JDL file when your new JSL is compiled.
PDL principles and procedures 5. In the [Enter path or folder name:] text field, enter one of the following paths to the “lcds” folder: /opt/XRXnps/resources/lcds/ or /var/spool/XRXnps/resources/lcds/ NOTE: The file and folder names are case–sensitive. Be sure to enter the directory path exactly as it is shown above, with regard to uppercase and lowercase letters. Remember to include the slashes (/) at the beginning and end. The “lcds” folder, where the DFAULT.
PDL principles and procedures Full JSL coding procedure If you do not want to use an existing JSL as a pattern and you prefer to build the entire JSL yourself, follow these steps. 1. Open a Text Editor window by following these steps: a. On the print server screen, right-click in the background to display the Workspace menu. b. From the Workspace menu, select [Programs]. The Programs pull-down menu opens beside the Workspace menu. Figure 1-13. Workspace and Programs menus c.
PDL principles and procedures Figure 1-14. Text Editor window 2. In the Text Editor window, code the JDL name, starting at the left edge of the window workspace. 3. Code the system or JDL level ID commands with their identifiers. Recommended: • Before beginning your system level commands, code a comment line stating that the following entries are system level commands. • For each command, at the beginning of the line, enter the identifier, followed by a colon (:) and the command keyword.
PDL principles and procedures 4. Code the rest of your system level commands (those not requiring identifiers), to specify your input processing commands. Refer to the “Specifying input parameters” chapter for information on coding these commands. Recommended: For each of these commands, tab or space over about 10 character spaces to enter the command keyword. Then tab or space over until the cursor is about 20 spaces from the left edge of your Text Editor workspace to begin entering the parameter keywords.
PDL principles and procedures Recommended: Do the following when you are coding catalog commands. • Place a comment on the line above the first CATALOG command line, indicating that the following commands are catalog level. • Place the catalog identifier, followed by a colon (:) and the CATALOG keyword, at the left margin, aligned with the system level identifiers.
PDL principles and procedures Figure 1-16. Text Editor – Save As window 13. In the [Enter path or folder name:] text field, enter one of the following paths to the “lcds” folder: /opt/XRXnps/resources/lcds/ or /var/spool/XRXnps/resources/lcds/ The “lcds” folder, where the DFAULT.JSL and all other system LCDS resource files are stored, is the recommended folder for storing your JSLs. You have write access to this folder, which means you can add files and create new folders within it. 14.
PDL principles and procedures CAUTION Be sure to give a new name to the JSL file you have created. Otherwise, your new JSL may overwrite the default JSL in the “lcds” folder. (Overwriting can occur if you access the default JSL by selecting [Open} from the File menu on the Text Editor window instead of [Include]. • The name must end with the .JSL file extension. • The name must be one to six characters in length (not including the .JSL extension). 15. Click [OK].
PDL principles and procedures Table 1-10.
PDL principles and procedures Sample offline JSL The following figure shows an example of an offline JSL. Note how comments are used to explain and identify parts of the JSL. NOTE: This JSL contains some highlight color commands. These commands are processed by the FreeFlow Print Server, but all printing is in monochrome. Table 1-11.
PDL principles and procedures Table 1-11.
PDL principles and procedures Compiling a JSL The second part of creating the JSL is compiling it. Each JSL file must be compiled (converted) into an object file (Job Descriptor Library or JDL) before it can be read by the system to print a job. The Xerox Job Description Compiler (XJDC) software on your print server performs this conversion. The process is diagrammed below. Figure 1-17. PDL compilation 1. JSL 2. XJDC (PDL compiler) 3. CME file (Copy Modification Entry) 4.
PDL principles and procedures • Do not omit any slashes (/). These symbols separate different directory levels of folders in the UNIX file system. The slash at the beginning of the command is actually the identifier or “name” of the parent (root) directory of the file system. • Enter all command text in lowercase letters. NOTE: This rule does not apply to UNIX file and folder names that contain uppercase letters. Be sure to enter any file or folder names exactly the way they appear in the directory.
PDL principles and procedures Figure 1-19. Terminal window with % prompt displayed 2. Move the pointer onto the Terminal window. A blinking cursor should be visible next to the prompt (a % sign, sometimes preceded by the name of your system). 3. At the % prompt, enter the following command to compile the JSL (be sure to leave spaces where they are indicated). /opt/XRXnps/bin/xjdc options /opt/XRXnps/resources/lcds/JSLNAME.
PDL principles and procedures Table 1-12. xjdc command options 1-68 Option Definition COMpile Compiles the JSL with printed sheets. SCAn Scans the JSL only. PRInt Generates a printed JSL. NOPrint Generates a printed JSL only when it contains errors. REPlace Specifies that an existing JDL file may be replaced by a new output file of the same name. This is the default.
PDL principles and procedures If the JSL compiles correctly with no errors, the JDL object file is created from the JSL, and a message is displayed in the Terminal window, indicating that the compilation was successful. The system places the newly created JDL file (along with the .LST and .RSC files that are created at the same time) in the “lcds” resources folder where your JSL is located. 4. If the JSL does not compile correctly, correct any errors in the JSL and recompile it.
PDL principles and procedures Correcting errors in a JSL If errors are encountered in a JSL while it is being compiled, the following message appears in the Terminal window: **********JSL CONTAINS ERROR(S)********** Figure 1-20. Terminal window displaying compiling messages for a JSL with errors The system does not create a .JDL file in the “lcds” folder, but it does create a .LST file, which shows where the errors are. 1. Open and inspect the .
PDL principles and procedures Figure 1-21. Text Editor – Open a File window c. In the Folders field, double-click the name of each of the folders that comprise the path to the “lcds” folder, in the order shown below: /opt/XRXnps/resources/lcds d. In the Files field of the Open a File window, click the name of the .LST file for the JSL you attempted to compile; or In the Files text field on the Open a File window, enter the name of your .LST file. The name syntax is as follows: JSLNAME.LST e.
PDL principles and procedures Figure 1-22. A .LST file for a JSL containing errors 2. Open another Text Editor window and display your JSL in this new window. (The procedure for displaying the JSL is described under “Opening a file in the Text Editor,” above.) 3. Enter the indicated corrections to your JSL, referring to the .LST file in the other Text Editor window as needed. 4. On the Terminal window, recompile the corrected JSL, using the compiling procedure that is described earlier in this section.
PDL principles and procedures Dynamic job descriptor entries (DJDEs) Dynamic job descriptor entries (DJDEs) are parameters embedded within the input data stream. DJDEs modify the printing environment established by a job descriptor entry (JDE) as the job is printing. Dynamic job descriptor entry processing allows certain JDE parameters to be changed for individual pages or records.
PDL principles and procedures Dumps The dump feature is a troubleshooting tool for print jobs. It allows you to generate a hardcopy of the command and data transmission between the host computer or the magnetic tape and the printing system while a job is being transmitted and printed. Online dump The online dump provides a printout of all the command and data transmission taking place between the host computer and the printing system.
PDL principles and procedures Table 1-13. Print format command usage for online dump Field Definition HOST COMMAND The English translation of the host command in hexadecimal. END STATUS One byte of status in hexadecimal transmitted to the host. SEQ# Incremental count in decimal of the host commands received during a dump session. The maximum number is 999,999. LENGTH Length in decimal of the data transmitted. DATE and TIME Date and time when the host command was received by the dump processor.
PDL principles and procedures Offline dump The offline tape dump feature is a troubleshooting tool for tape jobs. It allows you to generate a hardcopy printout of all the characters, carriage control information, channel status, tape labels, and other information in the data stream, while a job is being transmitted and printed. Starting and ending tape dump sessions To print a dump of an offline job you wish to troubleshoot, follow these steps: 1.
PDL principles and procedures The tape data stream dump contains the following information for each block that is dumped: • Block number • Block length • The decimal number of the starting byte in each printed line of data • The data printed in hexadecimal • The data printed using the translation code table that is defined in the VOLUME CODE command.
PDL principles and procedures Table 1-14. Software version compatibility V3A: 4635 VM10: DP180 LPS DP180 MX DocuSP 3.7: DP EPS DP 75 MX DP 100/115/ 135/155/180 MX 1 1 1 9 2 3, 5 1 1 9 4 2 1 4 4 4, 9 6 1 2 1 4 4 4, 9 1 2 2 1 2 1 1 9 2 4, 7, 8 6, 7, 8 4, 7, 8 2 1 4, 8 4 4, 9 Compiled in V3A 2 2 2 2 2 2 1 1 9 Compiled in XJDC 4.0 2 2 2 2 2 2 1 1 9 V3.9: 9790 8790 V4.0 & 5.0: 4850 4890 DP92C 1 1 2 3, 5 4 1 2 4 Compiled in V3.
PDL principles and procedures Printing highlight color applications on FreeFlow Print Server LCDS systems If you have a Xerox 4850, 4890, or DP92C HighLight Color LPS, or the FreeFlow Print Server-based Xerox DT128/155/180 HLC Printing System, your applications probably include the use of highlight color (one color plus black). The JDLs used to print these applications contain commands and parameters that specify the location and the color ink to be used.
PDL principles and procedures Table 1-15. Highlight color commands (Continued) Command Color parameter DJDE available? IRESULT Yes LOGO Yes NUMBER Yes XMP Yes For detailed information on the syntax and use of these PDL commands and DJDEs, refer to the Print Description Language Reference for your 4850/4890 or DP92 HighLight Color LPS. Downloading highlight color JDLs to your FreeFlow Print Server You can download color JDLs to your FreeFlow Print Server LCDS systems.
PDL principles and procedures • Downloading to the FreeFlow Print Server LCDS systems colored forms that were created with host or third party vendor software packages. Refer to the Forms Creation Guide for the 4850/4890 or DP92C HighLight Color LPS for detailed information on creating and using highlight color forms. Points to note for colored forms: • Light tints with isolated pixels of color that print on the Xerox 4850, 4890, or DP92C LPS may not be visible on the FreeFlow Print Server LCDS system.
PDL principles and procedures 1-82 Using LCDS Print Description Language
2. 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 online from a host attached channel interface or a remote communication, and offline from magnetic tape via the Tape Client. Input data streams The FreeFlow Print Server LCDS systems receive data online, over a channel or through Ethernet using TCP/IP.
Specifying input parameters Input processing functions The following functions are part of input processing on the FreeFlow Print Server LCDS systems. Input processing online For online printing, the LCDS data is transmitted from a host computer either directly or through a protocol converter. The FreeFlow Print Server LCDS systems receive print data either over a channel through bus and tag cables, or through the Socket Gateway or lpr using TCP/IP protocol.
Specifying input parameters Report separation The two logical processing commands that can control report separation online are BANNER and RSTACK. The BANNER command specifies the detection criteria for traditional spooler banner pages and their associated report boundaries. The RSTACK command is used to detect other types of report boundary indicator records called RSTACK records. NOTE: After reports are processed they are managed and printed as jobs.
Specifying input parameters In the event of a power failure, the system notifies you if you need to retransmit any data, and which records to resend. Downloading resource files from the host to the printer You can download resource files such as forms, fonts, JSLs, and so forth, by using the FILE DJDE. The FILE dynamic job descriptor entry (DJDE) transfers files while normal printing activity is taking place.
Specifying input parameters Forms control buffer (FCB) and vertical format control processing The 3211 and 4245 forms control buffer (FCB) defines channel positions and forms length. You may restrict the forms control buffer information by accepting or suppressing the normal processing of host transmitted FCB input. To suppress processing of FCB input, specify FCB=IGNORE in the LINE command.
Specifying input parameters • When the system is operating online in 3211 or 4245 emulation mode, forms control buffers (FCBs) are received from the host to redefine channel-to-line number assignments and to set margins based on the print position indexing byte. • If the print position indexing (PPI) byte of the FCB is enabled, it is not suppressed by FCB=IGNORE.
Specifying input parameters Table 2-2.
Specifying input parameters Input processing offline 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. Offline printing is handled by the Tape Client software, which is an optional part of the FreeFlow Print Server system software. To submit a tape job, you set up the job on the Tape Client window on the print server and click [START]. The job is submitted to the printer through the Socket or LPR gateway.
Specifying input parameters Tape codes Tape codes that are recognized by the FreeFlow Print Server LCDS systems are EBCDIC, ASCII, and several versions of BCD. If these codes are not sufficient for a particular tape, you may create a new code translation table or modify (customize) an existing code translation table. Tables that show the correspondence between standard recording codes and printed characters are in Appendix C, “Character code assignment tables,” in this manual.
Specifying input parameters Record structure A record is arbitrarily divided into two portions: operating system and user. • The operating system portion of the record contains information that is supplied by the host operating or spooling system. • The user portion of the record contains information that is provided by the application or the program that is running on the host system.
Specifying input parameters As before, volume 1 is the start-of-job, and the volume specified by n is the volume that contains data for the last page that was written to the print file before the system rollover. Input processing command descriptions The basic PDL commands to control input processing are CODE, PCC, RECORD, SEFFNT, TCODE, and VOLUME, which are defined here.
Specifying input parameters BLOCK command The BLOCK command defines block length characteristics and recording modes for offline data sources. BLOCK command parameters The following table summarizes the BLOCK command parameters. Table 2-4. Summary of BLOCK command parameters Parameter Specifies Offline Online DJDE BLOCK ADJUST Specifies the adjustment value that is added to or subtracted from the content of the block length field.
Specifying input parameters BLOCK ADJUST Specifies a block adjustment value that is added to, or subtracted from, the contents of the block length field to determine the true block length. Refer to the “BLOCK LENGTH” parameter section for further information. Syntax BLOCK ADJUST = value Options Table 2-5. BLOCK ADJUST parameter options and definitions Option Definition value Specifies the block adjustment length.
Specifying input parameters BLOCK FORMAT Specifies the recording mode of the block length field. Syntax BLOCK FORMAT = type Options Table 2-7. BLOCK FORMAT parameter options and definitions Option Definition type Type of recording mode of the block length field. The following types are available: • BIN (binary) • DEC (decimal) • PACK (packed with no sign) • PKSG (packed with sign) BLOCK LENGTH Specifies the longest physical block that is being processed.
Specifying input parameters • If a block length is specified that is less than the minimum block length that is found on the tape, the system 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. However, specifying the maximum block length in the JSL may slow performance.
Specifying input parameters Default 1 BLOCK LTHFLD: point to note • If the 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 the tape is the actual physical block length. • The LTHFLD parameter may be overridden if RECORD STRUCTURE is changed through tape label processing. BLOCK OFFSET Specifies the location of the block length field. Syntax BLOCK OFFSET = value Options Table 2-11.
Specifying input parameters BLOCK POSTAMBLE parameter: points to note • If the block delimiter string constant is specified, the block postamble is ignored. • The POSTAMBLE parameter may be overridden if RECORD STRUCTURE is changed through tape label processing. BLOCK PREAMBLE 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. Syntax BLOCK PREAMBLE = length Options Table 2-13.
Specifying input parameters BLOCK command: points to note Note the following when using the BLOCK command: • The values for LTHFLD, OFFSET, FORMAT, and PREAMBLE may be overridden if RECORD STRUCTURE is changed as the result of ANSI or IBM OS/Standard label processing. • The length of the block delimiter constant should not be coded as the BLOCK POSTAMBLE. Both lengths are subtracted from the end of the block.
Specifying input parameters Figure 2-1. Sample BLOCK command diagram CODE command Defines a character code translation table. When you require a user defined character code translation table, you define the character translation using this command, then reference the CODE command using the VOLUME CODE parameter. As an alternative, you can use the USER option of the VOLUME CODE parameter to reference the CODE command for which no identifier was provided.
Specifying input parameters The following sections describe the syntax of the CODE command parameters and explain the parameter options. CODE ASSIGN Defines user character code assignments. Syntax ac: CODE ASSIGN = {(input, output) | (input, (output1 [, output2] [,...]))} Options Table 2-16. CODE ASSIGN parameter options and definitions Option Definition input Defines the input code.
Specifying input parameters Options Table 2-17. CODE DEFAULT parameter options and definitions Option Definition codetype Can be one the following: • ASCII • BCD • EBCDIC • PEBCDIC • H2BCD • H6BCD • IBMBCD value A one byte hexadecimal, octal, or alpha constant. If a value is specified, all inputs are coded to that value. Default CODE DEFAULT parameter: points to note Codetype: EBCDIC • The DEFAULT parameter must be coded before any ASSIGN parameter for the assignment exceptions to become active.
Specifying input parameters Example 2 In this example, consecutive input codes, such as X’5B’ and X’5C’, need not be specified to accomplish code modification. CODE2: CODE DEFAULT=EBCDIC, ASSIGN=(X'5A',(X'40',X'40', X’40’)); CODE SPACECODE Defines the blank (space) character code for the single-byte character set. Syntax ac: CODE SPACECODE = spacecode, Options Table 2-18.
Specifying input parameters ac identifier A command identifier of the type ac is optional for the first DBCODE command within a JDE. Thereafter, each additional DBCODE command must include the identifier. The ac identifier consists of 1 to 6 alphanumeric characters (A through Z and 0 through 9). One of the characters must be alphabetic. DBCODE command parameters The following table summarizes the DBCODE command parameters. Table 2-19.
Specifying input parameters DBCODE DEFAULT Specifies a base code from which you can make double-byte character code assignment exceptions. The base code is specified by a codetype; the exceptions are specified in the ASSIGN parameter. Syntax ac: DBCODE DEFAULT = codetype Options Table 2-21.
Specifying input parameters IDEN command parameters Table 2-22. Summary of IDEN command parameters Parameter Specifies Online Offline DJDE IDEN DJPCC Specifies processing of carriage control for DJDE records. Y Y N IDEN OFFSET Specifies the starting position of the prefix string. Y Y N IDEN OPRINFO Specifies whether the DJDE record is printed and delivered to the stacker. Y Y N IDEN PREFIX Specifies a character string that appears in the DJDE record identification part.
Specifying input parameters IDEN OFFSET Specifies the number of bytes (beginning at 0) from the beginning of the user portion of the record to the beginning of the prefix string constant of the DJDE record. The number may be negative. Syntax IDEN OFFSET = value Options Table 2-24.
Specifying input parameters IDEN PREFIX Defines the character string that must appear in the identification part of each DJDE record in the input data stream. When the system recognizes this character string, it examines the rest of the record for DJDE commands. Syntax IDEN PREFIX = sc Options Table 2-26. IDEN PREFIX parameter options and definitions Option Definition sc string constant. Specifies the search criterion for recognizing DJDE records.
Specifying input parameters IDEN command example IDEN PREFIX=’RTEST’, SKIP=9, OFFSET=3, OPRINFO=YES, DJPCC=IGNORE; KCODE command Defines a double-byte character code translation table. When you require a user defined translation table of double-byte character codes, you define the double-byte character translation using the KCODE command, then reference this command using the VOLUME KCODE parameter.
Specifying input parameters KCODE ASSIGN Defines double-byte character code assignment exceptions or an entire user character translation table. Syntax ac: KCODE ASSIGN = {(input, output) | (input, (output1 [, output2] [,...])} Options Table 2-29. KCODE ASSIGN parameter options and definitions Option Definition input A numeric constant that defines the input double-byte code.
Specifying input parameters KCODE command: point to note The DBCODE command can be used in the same manner as KCODE. PCC command Enables you to create a table (or modify an existing standard table) of one-byte printer carriage control codes and define their action. NOTE: This command is ignored by the FreeFlow Print Server LCDS systems for both channel and TCP/IP processing.
Specifying input parameters Table 2-31. Summary of PCC command parameters (Continued) Parameter Specifies Online Offline DJDE LTHFLD Length of field containing record length Y N N OFFSET Location of record length field Y N N POSTAMBLE Length of extraneous data at end of record Y N N STRUCTURE Input record structure Y N N The following sections describe the syntax of the command parameters and explain their options.
Specifying input parameters Syntax [ac:] PCC ASSIGN = {(byte, ccln) | (byte, (ccln1 [, ccln2] [, ...])} Syntax for ccln definition: {field1[, field2 [, field3]] | (field1 [, field2 [, field3]] [, {TOF | OVR | IGN}])} Options Table 2-33. PCC ASSIGN parameter options and definitions Option Definition byte The printer carriage control byte that is being defined. Its value is in the range 0 to 255 (X00 to XFF). ccln carriage control line number.
Specifying input parameters PCC ASSIGN parameter: points to note • You need not specify consecutive byte values. For example, you can code the following command as a single command: ASSIGN=(X’60’, SP1), ASSIGN=(X’61’, SP2), ASSIGN=(X’62’, SP3); The single command is: ASSIGN=(X’60’, SP1, SP2, SP3)); • If byte translation is specified under the PCC LINE parameter (that is, the LINE PCC parameter TRAN option is specified), the PCC control byte is translated into standard EBCDIC before being applied.
Specifying input parameters Table 2-34. PCC DEFAULT parameter options and definitions (Continued) Option Definition PCCtype Parameters and the tables that can be modified are: • ANSI • B2500 • B2700 • B3700 • B4700 • B6700 • H2000 • H6000 • IBM1401 • IBM1403 • IGN • OVR • TOF • US70 • XEROX • NONE Default PCC DEFAULT parameter: point to note A table of PSP1 (Print and Space 1) codes The DEFAULT parameter must precede any ASSIGN parameter.
Specifying input parameters PCC MASK Makes inaccessible any unnecessary bits from the printer carriage control byte. Syntax [ac:] PCC MASK = value Options Table 2-36. PCC MASK parameter options and definitions Option Definition value Specifies an 8 bit value that will be used in a bit wise “AND” operation with the printer carriage control byte being processed. AND occurs after translation, if any.
Specifying input parameters In the previous example, these codes were added to the standard IBM1403 carriage control code table: X’40’ (Space 1 Line And Print), X’F1’ (Skip to Channel 1 And Print), and X’F8’ (Print And Skip to Channel 8). RECORD command Specifies the structure of the print record. (For online printing, only the LENGTH parameter of this command is used. For offline printing, the RECORD command has several additional parameters that define the record structure.
Specifying input parameters Options Table 2-38. RECORD ADJUST parameter options and definitions Option Definition value A constant integer that is 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 the record length. The first character may be plus (+) or minus (-). Default 0 RECORD CONSTANT Specifies a constant string used to signal the end of a record.
Specifying input parameters Options Table 2-40. RECORD FORMAT parameter options and definitions Default Option Definition type The following types are available for the record format: • BIN (binary) • DEC (decimal) • PACK (packed with no sign) • PKSG (packed with sign) BIN RECORD LENGTH Specifies the length of the longest record. Syntax RECORD LENGTH = value Options Table 2-41.
Specifying input parameters • The tape label contents can override a record length value. If a defined record length is larger than the default block length (1330), you must specify a block length that is large enough to hold the record. If a large enough record length is not specified, data may be lost. • The RECORD LENGTH parameter may be overridden by ANSI or IBM OS/Standard labels that specify record length.
Specifying input parameters RECORD OFFSET Specifies the location of the record length field. Syntax RECORD OFFSET = value Options Table 2-44. RECORD OFFSET parameter options and definitions Option Definition value Specifies the number of bytes that the block length field is offset from the first byte of the record. The value is an integer in the range 0 to LENGTH-LTHFLD – 1.
Specifying input parameters Options Table 2-46. RECORD PREAMBLE parameter options and definitions Option Definition length An integer in the range of 0 to the record length that specifies the number of bytes from the first byte of the tape record to the first byte of the first logical record Default 0 RECORD STRUCTURE Specifies the general record structure of the input data. Syntax RECORD STRUCTURE = structure-type Options Table 2-47.
Specifying input parameters 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. • LINE DATA parameter and RECORD 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.
Specifying input parameters Figure 2-3.
Specifying input parameters SEFFNT command When you print a job on large sized paper (such as 11 by 17 inch or A3), the paper must feed with its short edge as the leading edge. This is called “short edge feed” (SEF). The SEFFNT command enables or disables the short edge feed font mapping feature. SEFFNT creates customized mapping files (of the type .LIB) and triggers the system to invoke short edge feed font mapping. It is used in conjunction with the PDE currently in effect.
Specifying input parameters SEFFNT command parameters The following table summarizes the use of the SEFFNT command parameters. Table 2-48. Summary of SEFFNT command parameters Parameter Specifies Online Offline DJDE label Specifies the name of the font mapping file or the identifier of a font mapping table that will be created. If the label does not exist, the SEFFNT command either creates a table in the JDL or uses an existing mapping file if MAP is specified.
Specifying input parameters Table 2-49. SEFFNT SEFMAP parameter options and definitions (Continued) Option Definition REP REPLACE Indicates that the specified font pairs create a new mapping table to replace the current one. Default SEFFNT SEFMAP parameter: points to note No default • When specified without a label preceding the SEFFNT command, SEFMAP puts all font mapping definitions within the JDL, rather than creating a separate mapping file.
Specifying input parameters Options Table 2-50. SEFFNT MAP parameter options and definitions Option Definition filename References a font mapping file. The file is accessed when the JDL is used for printing. label References the label of a labeled SEFFNT command that is defined in the current JSL. Default No default SEFFNT command: points to note Note the following when using the SEFFNT command: • The system does not assume any mappings for fonts. You must always provide the mapping.
Specifying input parameters • If you want to use 11 by 17 inch paper or any size that requires SEF, be aware that form source libraries (.FSL) files, form (.FRM) files, logo (.LGO) files, and image (.IMG) files are not automatically scaled or rotated. You may need to alter the FSL text file to specify that the form should be rotated. SEFFNT command examples Following are a few examples of how to use the SEFFNT command. Example 1 A FNTMAP.LIB file is created on the system disk.
Specifying input parameters Example 5 Job 4 overrides the system level SEFFNT mapping with a job level definition. JOB4: JOB; SEFFNT SEFMAP=(L01BOB,P0812A); TCODE command The TCODE command defines a set of input–character–to–type assignments that will be used for the masked string comparisons in a report. You must use TCODE whenever you need to modify one of the standard sets of default type assignments.
Specifying input parameters • The printing system accepts lowercase characters expressed literally or symbolically; that is, preceded by the pound sign (#) functioning as a switch case operator. The following table gives some examples of how the TCODE command may be coded to specify the following types of character sets. Table 2-51. Specifying various types of character sets Type Interpretation 1 Defines numeric characters (0 through 9) by default.
Specifying input parameters TCODE DEFAULT Specifies an initial set of character type assignments for use with masked comparisons. You may specify default assignments for any standard character set by coding the appropriate keyword. Syntax ac: TCODE DEFAULT = {tcode Type | value} Options Table 2-53. TCODE DEFAULT parameter options and definitions Option Definition tcode Type Available tcode type keyword parameters are: • ASCII • BCD • EBCDIC • PEBCDIC • IBMBCD value An integer from 0 to 7.
Specifying input parameters Options Table 2-54. TCODE TASSIGN parameter options and definitions Option Definition typespec A typespec may be coded as a single integer, n. When coded as a single integer, the value must be in the range of 0 to 7. When coded as a series of integers, the values must be within the range of 1 through 7. NUMERIC may be used instead of 1; ALPHA may be used instead of 2. inputspec An inputspec may be coded as a single character, char, as a series of characters, (char [,...
Specifying input parameters Options Table 2-55. TCODE TRESET parameter options and definitions Option Definition typespec A typespec may be coded as a single integer, n, within the range of 1 through 7. NUMERIC may be used instead of 1; ALPHA may be used instead of 2. inputspec An inputspec for this parameter is the same as defined for TASSIGN parameter, or it can be ALL, which specifies that all characters in the code table are disassociated from the specified types.
Specifying input parameters Example 4 The basic character set is EBCDIC. The editor that was used to edit the JSL file is limited to uppercase only: T4: TCODE DEFAULT=EBCDIC, TASSIGN=(3,('A',–,'I'),('J',–,'R'),('S',–,'Z')), TASSIGN=(4,('#A',–,'#I'),('#J',–,'#R'),('#S',–,'#Z')); VOLUME command The VOLUME command specifies input medium and data characteristics. VOLUME command parameters The following table summarizes the parameters of the VOLUME command. Table 2-56.
Specifying input parameters Table 2-56. Summary of VOLUME command parameters (Continued) Parameter Specifies Online Offline DJDE VOLUME KANJI Specifies double-byte character printing mode and allows printing of data streams of intermixed single-byte and double-byte characters. Y N N VOLUME KCODE Specifies the double-byte character code translation table that the system will use to interpret the input data. Y N N VOLUME LABEL Specifies the type of label on the input tape.
Specifying input parameters VOLUME BMULT Specifies a multiplication factor that you can use to determine the true block length. Syntax VOLUME BMULT = value Options Table 2-57. VOLUME BMULT parameter options and definitions Option Definition value An integer from 1 to 15 that you extract from the tape label and apply as a multiplication factor to the block length to determine the true block length Default 1 VOLUME CODE Specifies which code translation table the system uses to interpret the input data.
Specifying input parameters Default VOLUME CODE parameter: points to note EBCDIC • When you run a CODE=NONE job with DUPLEX=YES and SHIFT=YES, you must specify MARGIN in inches. • Input data is translated according to the CODE selected on the VOLUME command. Any character that is translated into an ASCII X’20’ is truncated after the last significant (nonASCII X’20’) character in the print record. • On the FreeFlow Print Server LCDS systems, trailing spaces are deleted for the current code set only.
Specifying input parameters VOLUME DBCS Specifies the double-byte character printing mode. Allows printing of data streams of intermixed single-byte and doublebyte characters. Syntax VOLUME DBCS = {YES | NO} Options Table 2-60. VOLUME DBCS parameter options and definitions Option Definition YES Allows printing of a data stream of intermixed single-byte and double-byte characters. NO Allows printing only of single-byte characters.
Specifying input parameters VOLUME EOV Specifies the action the system takes when it encounters an end of volume (EOV) on the input data tape. Syntax VOLUME EOV = ([PAUSE | NOPAUSE], [EOF | NOEOF]) Options Table 2-62. VOLUME EOV parameter options and definitions Option Definition 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.
Specifying input parameters Options Table 2-63. VOLUME EXPAGE parameter options and definitions Option Definition YES If a character is not included in the font file, the error is flagged on the summary page. NO No unprintable character reporting is done. Default YES VOLUME HOST Specifies the computer or host operating system that generated the input data file. Syntax VOLUME HOST = host type Options Table 2-64.
Specifying input parameters Default Offline printing: IBMOS Online printing: No default VOLUME HOST parameter: points to note • For HOST=DUMP, two tape marks at the end of the tape are required to dump the data tape using DUMP.JSL. • If a selected HOST type is inconsistent with a selected LABEL type, the PDL issues an error message and automatically substitutes a valid label. Do not code the LABEL parameter of the VOLUME command in cases where it is not appropriate for a particular HOST type.
Specifying input parameters • If the host application program uses ANSI carriage control commands, the host operating system converts each command to a valid 3211 or 4245 channel command before sending it to the printer for online printing. The printing system online interface (as well as the 3211 and 4245) rejects any commands other than those processed. Therefore, the only appropriate PCCTYPE for an online JSL file is IBM3211, which is the online default.
Specifying input parameters VOLUME KCODE Specifies which double-byte character code translation table the system will use to interpret the input data. Syntax VOLUME KCODE = {keyword | id } Options Table 2-66. VOLUME KCODE parameter options and definitions Option Definition keyword Specifies a specific, standard, system defined double-byte code translation table.
Specifying input parameters VOLUME LCODE Specifies the code translation table that will be used in interpreting the tape label. Syntax VOLUME LCODE = {keyword | id | NONE} Options Table 2-68. VOLUME LCODE parameter options and definitions Option Definition keyword Specifies a specific, standard, system-defined code translation table.
Specifying input parameters Options Table 2-69. VOLUME LPACK parameter options and definitions Option Definition NO Indicates that no unpacking operation will be performed. YES Indicates that the labels are packed. If YES is specified, the UNPACK parameters specify the required unpacking method for both the labels and the input data. If the data in a report is packed, the labels may be either packed or unpacked.
Specifying input parameters Options Table 2-71. VOLUME MINLAB parameter options and definitions Option Definition 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. Default 80 VOLUME OPTIMIZE Enhances the performance of the data stream. NOTE: This parameter is supported only partially by the FreeFlow Print Server LCDS systems.
Specifying input parameters VOLUME OSCHN Specifies the channel that the system uses to signal the end of a report that is generated by an IBM OS writer. Syntax VOLUME OSCHN = value Options Table 2-73. VOLUME OSCHN parameter options and definitions Option Definition value Specifies the vertical format unit (VFU) channel that the system uses to signal the end of a report.
Specifying input parameters Options Table 2-75. VOLUME OSTLP parameter options and definitions Default Option Definition value Specifies the number of trailer pages that follow the report. 0 VOLUME RMULT Specifies a multiplication factor that the record length uses to determine the true record length. Syntax VOLUME RMULT = value Options Table 2-76.
Specifying input parameters Options Table 2-77. VOLUME TCODE parameter options and definitions Option Definition tcode Type Specifies one of the following standard character sets for which type assignments are defined by default: • ASCII • BCD • EBCDIC • H2BCD • H6BCD • IBMCD • PEBCDIC By coding any one of the keywords, you are furnished with a set of character to type assignments. label Specifies an identified label of a TCODE parameter that defines a set of type assignments.
Specifying input parameters VOLUME VCODE Specifies a table of character type codes to use with the CRITERIA command, VALUE parameter. This parameter accommodates the different presentations of numbers used in different countries, thereby ensuring accurate comparisons of numeric values. Syntax VOLUME VCODE = (translation type, keyword) Options Table 2-79. VOLUME VCODE parameter options and definitions Option Definition translation type Specifies a standard code translation set.
Specifying input parameters There are eight unique character Type codes in a character code translation set, as defined in the following “Unique character Type codes” table. Table 2-81.
Specifying input parameters Offline: 2-72 VOLUME HOST=UNIVAC, LABEL=STANDARD, UNPACK=T4X3, CODE=ASCII, LCODE=ASCII; VOLUME HOST=IBMOS; VOLUME HOST=B6700, LABEL=ANSI, BMULT=6, RMULT=6; VOLUME HOST=OCTDUMP, CODE=H6BCD, UNPACK=T4X3; Using LCDS Print Description Language
3. Using logical processing Logical, or special, processing enables you to specify logical functions that will be performed on a record or a set of records. During job processing, the system tests the value of a specified test expression and directs the flow of processing based on the result of the test.
Using logical processing Test expressions To define a logical processing command fully, you must specify one or two fields in the record that will be tested. In general, a logical processing command has the following format: parameter command-keyword = options, ..., command-keyword TEST = testexp, ...; The testexp parameter of a logical processing command defines a test that will be performed on either one or two specified fields and their associated contents. The test result is a TRUE or FALSE value.
Using logical processing • A specific print line range is specified by the LINENUM parameter, and the line or lines that are being tested contain no record (that is, the lines have been skipped or spaced over). If the test specifies a change mode function, the CRITERIA command fails because no change has occurred. However, the value for the LAST option of the CHANGE parameter remains unchanged for comparison with the next record.
Using logical processing Logical processing commands that have TEST parameters The logical processing commands with TEST parameters are listed below. Each individual command should be specified only once per job descriptor entry. If any one command is specified more than once, the last occurrence is used without notification of any error.
Using logical processing Each constant that is included in a referenced 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. NOTE: The TABLE command must precede any CRITERIA command that references it. This command requires an identifier of the type ac (at least one alpha character required). TABLE command parameters The following table summarizes the TABLE command parameters. Table 3-2.
Using logical processing TABLE MASK Defines mask characters used within string constants (specified by CONSTANT parameter). Also indicates which characters denote special type testing and what that type is. Syntax ac: TABLE MASK = (ignorechar [, charspec1 [, charspec2 [,...]]]) Options Table 3-4. TABLE MASK parameter options and definitions Option Definition ignorechar Specifies a character that appears in positions that will not be compared within a string constant.
Using logical processing TABLE command: points to note • In an unmasked comparison (using only the CONSTANT parameter of the TABLE command), characters in the string constant that correspond positionally to those in the input data string are tested for absolute equality, one character at a time.
Using logical processing The characters used in the MASK parameter occupy numbered positions, beginning with 0 and separated by commas. These position numbers in the MASK parameter are used as type numbers. Therefore, the associations of mask characters to type that are listed in the following table are made for the above TABLE command. Table 3-5.
Using logical processing Example 4 The TABLE command below sets up the character to type associations shown in the following table. T2: TABLE MASK=('*',':','!'), CONSTANT=('DATE ::/::/:: ID!!!'); Table 3-6.
Using logical processing Constant mode In Constant mode (that is, when the CRITERIA CONSTANT parameter has been specified), you must specify the location, length, and contents of a fixed field within a record. Each record is examined at the specified location to determine if the constant is present (the identifier tabid defines the table containing the constant).
Using logical processing The criid1 and criid2 are the identifiers for two CRITERIA commands. The parentheses in this format are required.
Using logical processing – Compare the character in that position for absolute equality. – Ignore the character in that position (consider the character, whatever it is, to compare as equal). – Compare the character in that position for type, for example, alphabetic, numeric, or some specially defined type. Character types An attribute called type may be associated with any character or characters in a character set. The possible types are identified by the integers 1 through 7.
Using logical processing Masked comparisons using nondefault type assignments Performing masked comparisons using either a nonstandard character set or a standard set for which the default type assignments are not suitable requires coding the following: • TCODE command: This command is used either to modify a set of standard default type assignments or to define a completely new set (shown in processing sequence 3 in the following figure).
Using logical processing CRITERIA command parameters A CRITERIA command may contain only one specification of one of these parameters: CONSTANT, CHANGE, or VALUE. In addition, it may optionally contain the LINENUM parameter. Thus, one or two parameters must be provided in the CRITERIA command. The following table summarizes the CRITERIA command parameters and gives their uses and functions. Table 3-7.
Using logical processing Options Table 3-8. CRITERIA CHANGE parameter options and definitions Option Definition offset The offset in bytes (relative to zero) from the start of the user portion of the record to the control field within the record. length The length in bytes of the control field. Its range is 1 to 255. NE Indicates “not equal to.” LAST Indicates that the control field of the current record is being compared to the control field of the previous (last encountered) record.
Using logical processing – If the LINENUM parameter is used, lines within the specified range are processed normally, and lines outside the range are not evaluated. Thus, Change mode comparison strings are not saved from lines outside of a LINENUM range. Refer to the “CRITERIA LINENUM” parameter section in this chapter for information on using this parameter of the CRITERIA command.
Using logical processing Options Table 3-9. CRITERIA CONSTANT parameter options and definitions Option Definition offset The offset in bytes (relative to zero) from the start of the user portion of the record to the field in the record being compared. length The length in bytes of the test field. Its range is 1 to 255. EQ Indicates the operation EQUAL TO. NE Indicates “not equal to.” tabid table identifier.
Using logical processing Options Table 3-10. CRITERIA LINENUM parameter options and definitions Option Definition init initial line An integer specifying the number, on each logical page, of the beginning line for which the CRITERIA command is evaluated. count An integer specifying the consecutive number of lines (starting with the initial line) for which the CRITERIA command is evaluated.
Using logical processing Table 3-11. CRITERIA VALUE parameter options and definitions Option Definition GE Indicates the operation “greater than or equal.” tabid table identifier. The identifier of a table, specified in the TABLE command, containing the numeric value to which the test field is compared.
Using logical processing – Non-numeric characters, such as currency symbols, positive and negative number designators, and alphabetic text may only precede, follow, or enclose the numeric character string. Valid character strings would include the following if the appropriate VCODE table is specified: ‘$(1,500.00)’, ‘–1.500,00 DM’, and ‘kr–1.
Using logical processing – If the operator is NE, LT, GT, LE, or GE, the system tests the variable data against only the first value in the TABLE CONSTANT statement. Performance considerations with the CRITERIA VALUE parameter CRITERIA VALUE affects system performance in relation to the number of characters per page involved. This is a function of the number of tests performed, the number of character columns in each test, and the number of lines in which the criteria is evaluated.
Using logical processing Logical processing command descriptions Logical processing commands cause the system to test input data records in the job against specified criteria. If the criteria are satisfied, the system performs specific actions. The commands described in the following sections provide logical processing functions. The following table summarizes the logical processing commands and the functions that are associated with them. Table 3-12.
Using logical processing The system recognizes the end of a report when enough banner pages have been printed to satisfy the “end of report” test criteria. BANNER command parameters The following table summarizes the BANNER command parameters. Table 3-13. Summary of BANNER command parameters Parameter Specifies Online Offline DJDE BANNER HCOUNT Specifies the total number of consecutive header pages that are recognized at Start of Report.
Using logical processing Options Table 3-14. BANNER HCOUNT parameter options and definitions Option Definition value Maximum number of consecutive header pages that will be recognized at the start of the report Default BANNER HCOUNT parameter: point to note 0 The FreeFlow Print Server LCDS systems do not recognize header banner pages if an HCOUNT value of 0 is specified.
Using logical processing Options Table 3-16. BANNER HRPTNA parameter options and definitions Option Definition offset Amount of space, specified in bytes (relative to zero), from the start of the user portion of the record to the subfield within the record. length The number of bytes in the subfield (1 to 16). NONE Specifies that no report name is to be selected.
Using logical processing Options Table 3-18. BANNER TEST parameter options and definitions Options Definitions testexp test expression Refer to “Coding a test expression” earlier in this chapter for the format and syntax of a testexp. If a test expression is satisfied, the page containing the record tested is considered a banner page. Default No default BANNER TYPE Specifies the use of selected data pages as banner pages when reports do not contain this information.
Using logical processing BANNER command: points to note • Field content captured via HJOBNO and HRPTNA is translated using the CODE table in effect when the record containing them is processed. • The following table shows the effect of the TCOUNT and HCOUNT parameters of the BANNER command under the conditions listed, and the results of each. Table 3-20.
Using logical processing Example 2 If a job stream has two trailer pages with the character string DATE=mm/dd/yy appearing on line 10 or 11 and beginning in print position 20, the BANNER criteria could be coded as follows: T2: TABLE CONSTANT=('DATE=::/::/::'), MASK=(':'); C2: CRITERIA CONSTANT=(19,13,EQ,T2), LINENUM=(10,2); BANNER TEST=C2, HCOUNT=0, TCOUNT=2; The MASK parameter specifies a masking character.
Using logical processing Options Table 3-21. TEST parameter options and definitions Option Definition testexp test expression. Defines a test expression for a block that will be selected for printing (BSELECT) or deleted (BDELETE). Refer to “Coding a test expression” earlier in this chapter for the format and syntax of a testexp.
Using logical processing The contents of the first byte of each tape block (offset=0, length=1) is examined for the character constant 'P'. When a 'P' is detected, the entire block is selected (BSELECT) for printing. When the first byte of any block does not contain a 'P', that block is bypassed and not printed. In this example, only block 1 is printed. The following figure shows a sample of how BSELECT and BDELETE commands are used. Figure 3-2.
Using logical processing LMODIFY command Enables you to select one or more text strings to which highlight color will be added under specified conditions. NOTE: The FreeFlow Print Server LCDS monochrome systems ignore this command. However, JSLs that contain the LMODIFY command may be created and transferred to a highlight color laser printing system, such as the DT 128/155/180 HLC, for use with highlight color jobs.
Using logical processing LMODIFY SELECT Specifies the part of the print line that will be printed in the specified ink. Syntax LMODIFY SELECT= {LINE | (offset, length)} Options Table 3-24. LMODIFY SELECT parameter options and definitions Option Definition LINE Prints the entire line using the specified ink. offset Specifies in bytes (relative to zero) the amount of space from the beginning of the print line to the beginning of the portion of the line that will be printed in the specified ink.
Using logical processing Points to note: LMODIFY command • The LMODIFY command acts upon individual print lines. The offset values in all of the test criteria are measured from the beginning of the print line to the beginning of the test field. The print data offset (pdo value) in the LINE DATA parameter can affect the relationship between the beginning of the input data record and the beginning of the print line.
Using logical processing RAUX TEST parameter Specifies the test expression for selection of paper from the auxiliary tray. Syntax RAUX TEST = testexp Options Table 3-26. RAUX TEST parameter options and definitions Option Definition testexp test expression. Describes the criteria that, when detected by the system, will cause a page to be fed from the tray identified for the AUX stock. Refer to “Coding a test expression” earlier in this chapter for the format and syntax of a testexp.
Using logical processing Figure 3-3. Data record showing offset specified in RAUX command The data record, when processed as part of the input data stream, causes the page it is a part of to be printed on a sheet of paper fed from the auxiliary tray. The Xs are depicted in the above example only to illustrate the specified offset of 20 character positions.
Using logical processing Options Table 3-27. RDELETE and RSELECT TEST parameter options and definitions Option Definition testexp • Default For RSELECT: Specifies the test criteria that, if met, will cause the record to be selected for printing. • For RDELETE: Specifies the test criteria that, if met, will cause the record to be deleted from the printed output. Refer to “Coding a test expression” earlier in this chapter for the format and syntax of a testexp.
Using logical processing Figure 3-4. Illustration of RDELETE command usage 1. Tape mark, followed by interblock gap (IBG) 2. Block 1, followed by interblock gap (IBG) 3. Block 2, followed by interblock gap (IBG) 4. Tape mark 5. Record length field (in preamble) 6. Printer carriage control (PCC) byte (at start of user portion of record) 7. Print line 8. 103 bytes of data RFEED command The logical processing RFEED command allows you to change stock names on a page by page basis without using DJDEs.
Using logical processing Options Table 3-28. RFEED TEST parameter options and definitions Option Definition testexp References a criteria table to be used to test for conditions that will cause the stock defined by the stock parameter option to feed for the next page. Refer to “Coding a test expression” earlier in this chapter for the format and syntax of a testexp. stock Defines the stock whose assigned tray(s) will be used for the page, (either a stock name or a stock reference).
Using logical processing PAPERSTK: STOCKSET ASSIGN=('RED',REDPPR), ASSIGN=('BLUE',BLUPPR), ASSIGN=('GREEN',GRNPPR); T1: TABLE CONSTANT=('ABC'); T2: TABLE CONSTANT=('DEF'); T3: TABLE CONSTANT=('GHI'); C1: CRITERIA CONSTANT=(4,3,EQ,T1); C2: CRITERIA CONSTANT=(4,3,EQ,T2); C3: CRITERIA CONSTANT= (15,3,EQ,T3); RFEED TEST=((C1,'RED'), (C2,'BLUE'), C3, 'GREEN')); In this example, the system checks C1, C2, and then C3.
Using logical processing ROFFSET can also force an offset on either all copies of the report or only the first copy. In conjunction with job offset control (OFFSET parameter of the OUTPUT command), you can exert extensive control over the offsetting function to build tailored, job controlled stacks of output in your printer stacker tray. ROFFSET command parameters The following table summarizes the ROFFSET command parameters. Table 3-29.
Using logical processing ROFFSET TEST Specifies the test expression for offsetting pages in the stacker bin. Syntax ROFFSET TEST = testexp Options Table 3-31. ROFFSET TEST parameter options and definitions Option Definition testexp test expression. Specifies the criteria test that, if satisfied, causes the output to be offset in the stacker tray. Refer to “Coding a test expression” earlier in this chapter for the format and syntax of a testexp.
Using logical processing ROFFSET command example In the following example, a file has multiple reports without any delimiter records separating the reports. Each page of the report has a page number as part of the heading. Each report causes renumbering of the pages, starting with PAGE...1. With the ROFFSET command coded below, an offset occurs for all passes of the reports.
Using logical processing RPAGE command The RPAGE command allows you to reposition the current (or next) logical page on the physical page. RPAGE command parameters The following table summarizes the RPAGE command parameters. Table 3-32. Summary of RPAGE command parameters Parameter Specifies Online Offline DJDE RPAGE SIDE Specifies the side of the physical page on which to reposition the logical page. Y Y Y RPAGE TEST Defines the test expression for detecting an RPAGE record.
Using logical processing Options Table 3-33. RPAGE SIDE parameter options and definitions Option Definition sideopt In duplex (with no BFORM), sideopt produces the following results: NUFRONT The specified logical page is positioned as the first logical page on a new sheet. BACK The specified logical page is positioned as the first logical page of the next available back. NUBACK The specified logical page is positioned as the first logical page on the back of a new sheet.
Using logical processing RPAGE TEST Defines the test expression for detection of an RPAGE record that will cause the logical page to be repositioned on a physical page. Syntax RPAGE TEST = testexp Options Table 3-34. RPAGE TEST parameter options and definitions Option Definition testexp test expression. Specifies the criteria test that, if met, will reposition the logical page. The logical page on which this record normally appears is called the “current logical page.
Using logical processing RPAGE command: points to note Note the following when using the RPAGE command. • If a record intended to satisfy the criteria for RPAGE is suspended by RSUSPEND, that record is not checked for the RPAGE criteria. Note that the RPAGE criteria takes effect when printing is resumed. • Record selection or deletion is performed prior to RPAGE processing.
Using logical processing Figure 3-6.
Using logical processing Figure 3-7.
Using logical processing RRESUME and RSUSPEND commands The print suppression logical processing function permits you 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 and resumption are invoked by the use of two separate commands: RSUSPEND and RRESUME. The tests for each command are independent and must be described separately.
Using logical processing Options Table 3-37. RSUSPEND and RRESUME BEGIN parameter options and definitions Option Definition CURRENT Specifies that printing will stop or resume on the current record. • If CURRENT is coded for RSUSPEND, the record satisfying testexp does not print. • If CURRENT is coded for RRESUME, the record is printed. NEXT Specifies that printing will stop or resume with the next record.
Using logical processing • Interaction with RSTACK – A record that satisfies the RSTACK criteria is detected, and it terminates the report and record suspension, regardless of whether or not the printing of records was suspended at the time. DJDE records are not processed if record printing has been suspended. Refer to the “Using Dynamic Job Descriptor Entries (DJDEs)” chapter for further information.
Using logical processing • DJDE records are processed, not ignored, even when detected after an RSUSPEND record and before the corresponding RRESUME record. RSUSPEND and RRESUME example Following is an example of the RSUSPEND and RRESUME commands.
Using logical processing RSTACK command The stacked reports feature enables you to define a series of reports in a single file. This is accomplished by specifying the end of the report in the coded logical processing commands. The printer stacks reports in a file if more than one report is included in a single file (or a single spooled host file identified by the banner pages).
Using logical processing In this mode, you can use the PRINT parameter to print the delimiter (or the delimiter packet) and to select the output destination of this delimiter page: BIN, TRAY, or BOTH. The option BOTH delivers the page to the sample tray and to the output tray. The delimiter page, when printed, is output as part of the subsequent report.
Using logical processing RSTACK command parameters The following table summarizes the parameters of the RSTACK command. Table 3-39. Summary of RSTACK command parameters Parameter Specifies Online Offline DJDE RSTACK ACCTINFO Prints a subfield of the first record on the accounting page. Y Y N RSTACK DELIMITER Specifies whether RSTACK records are treated as special (delimiter) records, or as the first data record of the next report.
Using logical processing RSTACK DELIMITER Specifies whether or not RSTACK records are treated as data records. Syntax RSTACK DELIMITER = {YES | NO} Options Table 3-41. RSTACK DELIMITER parameter options and definitions Option Definition YES Specifies that all consecutive records that satisfy the TEST criteria are treated as a delimiter packet and not as data records. NO Specifies that this single record separates one report from another and is treated as a data record.
Using logical processing Options Table 3-42. RSTACK HRPTNA parameter options and definitions Option Definition offset The amount of space, specified in bytes (relative to zero), from the start of the user portion of the record to the subfield within the record. length The number of bytes in the subfield (1 to 16). NONE Specifies no report name is selected.
Using logical processing RSTACK TEST Defines the test expression for the “end of report” conditions for either Change mode or Constant mode criteria. Syntax RSTACK TEST = testexp Options Table 3-44. TEST parameter options and definitions Option Definition testexp Defines test criteria that, if satisfied, signals the end of the report for either Change Mode or Constant Mode criteria. Refer to “Coding a test expression” earlier in this chapter for the format and syntax of a testexp.
Using logical processing • Detection of RSTACK immediately following report separation is ignored. This prevents null reports. If RSTACK is specified in a selected JDE or JDL, that is, a JDE or JDL invoked in a DJDE), the following restrictions apply to online systems: – If RSTACK is not specified in the JDE or JDL that is identified in the Initial JDE or JDL field on the user interface window, the DELIMITER=NO parameter should be specified in the selected JDE or JDL.
Using logical processing The following figure illustrates a sample RSTACK command usage. Figure 3-8.
4. Specifying print format parameters To specify the physical characteristics of a print job, define the placement of data on the page, identify system responses to error conditions, and other functions related to the printed output, you use the PDL print format commands. These commands are described in the following sections. Print format command descriptions The following table lists these print format commands and summarizes their functions.
Specifying print format parameters ABNORMAL command The ABNORMAL command allows you to restrict certain operator functions and to define system responses to error conditions. ABNORMAL command parameters The following table summarizes the ABNORMAL command parameters. Table 4-2. Summary of ABNORMAL command parameters Parameter Specifies Online Offline DJDE ABNORMAL ACCTFEED Specifies the stock from which an error sheet will be fed when an error occurs during the accounting report processing.
Specifying print format parameters Syntax ABNORMAL ACCTFEED = {AUX | OPR} Options Table 4-3. ABNORMAL ACCTFEED parameter options and definitions Option Definition AUX Specifies that the error sheet will feed from the stock that was identified as AUX. OPR (Not currently supported) Specifies the medium that is defined in the Virtual Printer. Default AUX ABNORMAL CODE Specifies the handling of illegal function codes in the data stream.
Specifying print format parameters Options Table 4-5. ABNORMAL ERROR parameter options and definitions Option Definition 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 resuming or canceling the job.
Specifying print format parameters ABNORMAL IMISMATCH Specifies the action for a highlight color printer to take when a specified ink requires a primary ink color that is not currently loaded. NOTE: IMISMATCH is a highlight color parameter that is recognized by printers such as the Xerox 4850 and 4890, as well as the Xerox DT 128/155/180 HighLight Color Printing Systems. It may be included in JSLs that are created on the FreeFlow Print Server LCDS systems for highlight color printing.
Specifying print format parameters FreeFlow Print Server-based LCDS printers contain queue default settings and a queue override setting. The default setting will be to Use Loaded Color. The LCDS datastream overrides queue default settings; however, a queue override setting will override the LCDS datastream. The FreeFlow Print Server Mismatch Action will include operator intervention (change ink), cancel the job, or use loaded color.
Specifying print format parameters ABNORMAL ISUBSTITUTE Specifies whether or not the operator of a highlight color printer may initiate ink substitution. NOTE: ISUBSTITUTE is a highlight color parameter that is recognized by printers such as the Xerox 4850 and 4890, as well as the Xerox DT 128/155/180 HighLight Color Printing Systems. It may be included in JSLs that are created on the FreeFlow Print Server LCDS systems for highlight color printing.
Specifying print format parameters Options Table 4-8. ABNORMAL OTEXT parameter options and definitions Option Definition WAIT Displays a message and stops printing until the operator resumes it (by pressing the printer Continue button or selecting Resume from the print server screen). Stopping printing allows the operator to verify the output report in the near vicinity of the marker page. NOWAIT Displays a message, but printing does not stop.
Specifying print format parameters ABNORMAL SECURITY Restricts certain operations or administrative functions. Syntax ABNORMAL SECURITY = {YES | NO} Options Table 4-10. ABNORMAL SECURITY parameter options and definitions Option Definition YES Restricts use of the following functions for the duration of the startup JDE or JDL: • Obtaining a sample print from the current job • Skipping over output pages. NO Specifies that no restrictions will be imposed.
Specifying print format parameters ACCT command The ACCT command enables a printout of an accounting summary to be included with each report printed. This summary consists of a single page of information containing job setup information and counts of processing events. The system automatically saves on disk certain processing information on each report that is printed. The status file accumulates this information on an individual report basis, in the order that it is processed.
Specifying print format parameters Default ACCT DEPT parameter: point to note Built from the JDL name by adding “.JDL” to the name. The department name (sc) is printed on the accounting sheet, and is entered into the accounting log for the report. ACCT USER Specifies the delivery destination of the one-page accounting summary for each report. This page is always printed in the same mode (duplex or simplex) as the report. Syntax ACCT USER = {BIN | TRAY | BOTH | NONE} Options Table 4-13.
Specifying print format parameters CME command Copy modification entries (CMEs) allow certain parts of the printed data in a report to be replaced with predefined static data, and/or specify the changing of fonts within the variable data. (The copy modification function is also referred to as “spot carbon.”) CMEs define a rectangular space on the printed page within which printed data is replaced with a substitution string or a changed font. More than one CME may be applied to a job.
Specifying print format parameters Refer to “Importing LCDS resources” in the “PDL principles and procedures” chapter for the procedure for copying resources to the /opt/XRXnps/resources/lcds/ folder from elsewhere within the Unix file system. NOTE: When you modify a CME source file, you must recompile it with the xjdc command. It is not necessary to recompile the associated JDLs.
Specifying print format parameters CME CONSTANT Specifies a character string to print. Syntax [ac:] CME CONSTANT = sc Options Table 4-15. CME CONSTANT parameter options and definitions Option Definition sc string constant. Represents the character string to be printed. The width of the copy modification rectangle is determined by the number of characters specified by sc. More than one string constant is allowed.
Specifying print format parameters Default CME FONT parameter: points to note No default • A font specification applies to input variable data as well as to static CME data. If a line number (LINE) and character position (POSITION) but no insertion text (CONSTANT) are specified, the font change that is called out applies to input variable data at the specified position. • Fonts may be specified at any point. The last font that is specified remains in effect until another font is specified.
Specifying print format parameters CME INK parameter: points to note • If 0 is specified (or defaulted) for the INK parameter, the ink for the variable data and the CME text reverts to the ink that was specified in the IDFAULT parameter of the OUTPUT command. • An inkindex value greater than the ILIST size causes an “out of range” message to be displayed. The operator has the option to continue printing the job using black ink or to abort the job.
Specifying print format parameters CME POSITION Specifies the initial character position at which to begin to apply the CME in the print line. Syntax [ac:] CME POSITION = n Options Table 4-19. CME POSITION parameter option and definition Option Definition n An integer value in the range of 1 (the first position of the print line) and the value specified by the length option of the LINE DATA parameter.
Specifying print format parameters There also may be multiple text specifications following a column specification. These are combined to form a single text string. • String position: 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.
Specifying print format parameters CME command examples This section shows two examples of uses of the CME command. Example 1 CME parameters specified in standard form: CME12: CME LINE=47, POS=1, FONT=5, CONSTANT=(5)'*', LINE=48, POSITION=1, FONT=1, LINE=49, POS=10, CONSTANT='ABCD'; CME parameters specified in short form: CME12: CME L47,P1,F5,(5)'*',L48,P1,F1,L49,P10,C'ABCD'; or CME12: CME Example 2 L47P1F5(5)'*'L48P1F1L49P10C'ABCD'; The following is an example of copy sensitive CMEs.
Specifying print format parameters IDR command Allows you to define default ink catalogs, palettes, and inks. ac identifier You must specify an ac identifier when defining an IDR. This identifier is referenced by the OUTPUT IDR parameter or the IDR DJDE. If a JSL contains an IDR command, but does not specify an IDR name, the following message appears when the JSL is compiled: IDR FILE WILL BE USED DURING PRINTING.
Specifying print format parameters If no IDFAULT is specified, the first element of the ILIST is used as the default. If no ILIST is specified, the system default is used. IDR command parameters The following table summarizes the IDR command parameters. Table 4-20. Summary of IDR command parameters Parameter Specifies Online Offline DJDE IDR ICATALOG Specifies a default ink catalog that will be used when there is no specific catalog reference.
Specifying print format parameters IDR ILIST This parameter provides a list of all the inks which may be referenced by indexing in printing variable input data or CME data. Syntax ac:IDR ILIST = {‘inkname’ | (‘inkname1’ [‘inkname2’] [, ...])} Options Table 4-22. IDR ILIST parameter options and definitions Option Definition ’inkname’ Name of an ink that may be referenced by ink indexing during printing. Can be a solid primary color only.
Specifying print format parameters IDR PALETTE Establishes a default inks palette that will be used in ink references when there is no specific palette reference. Syntax ac:IDR PALETTE = ‘palette’ Options Table 4-23. IDR PALETTE parameter options and definitions Option Definition ‘palette‘ Name of the default palette that will be used in ink references in the absence of a specific palette reference.
Specifying print format parameters Table 4-24. Summary of LINE command parameters (Continued) Parameter Specifies Online Offline DJDE LINE FDATA Specifies starting and ending points of the file data within a record. Y Y N LINE FONTINDEX Specifies that a field within the user portion of the record defines the index to a specific font to be used for that line. Y Y Y LINE GDATA Specifies starting and ending points of graphic data within a record.
Specifying print format parameters Options Table 4-25. LINE BASELINE parameter options and definitions Option Definition TOP Determines the baseline position from the top of each line by using the BASELINE parameter of the first font in the PDE font list. CENTER Positions all of the characters so that their center lines match. BOTTOM Determines the baseline from the bottom of each line by using the BASELINE parameter of the first font in the PDE font list.
Specifying print format parameters LINE DATA Specifies the location and length of the print line data within an input data record. Syntax LINE DATA = (pdo, length) Options Table 4-27. LINE DATA parameter options and definitions Option Definition pdo print data offset. Number of bytes between the start of the user portion of the record and the first character of the record to be printed. length Maximum length of printable data within each logical record.
Specifying print format parameters LINE FCB parameter: points to note • If you specify FCB=PROCESS, an FCB load causes positioning to TOF. If the system is already at TOF, page eject does not occur. However, if the line number before the FCB load is greater than TOF, a page eject occurs. • If you specify FCB=PROCESS and an FCB is sent from the host, the later FCB overrides the previous FCB or VFU. Its length replaces the previous BOF. Furthermore, its contents and length are saved on the disk.
Specifying print format parameters LINE FONTINDEX Specifies that a field within the user portion of a record defines the index to a specific font to be used for that line. If FONTINDEX is not specified, no index is used. Syntax LINE FONTINDEX = {offset | (offset [, initval [, bitopt]]) | NONE} Options Table 4-30. LINE FONTINDEX parameter options and definitions Option Definition offset Specifies the byte offset in the data record where the character that is to be used as a font index number is located.
Specifying print format parameters LINE FONTINDEX parameter: points to note • When the bitopt option is specified, the initval must also be specified. • If the initval 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 128). 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).
Specifying print format parameters Options Table 4-31. LINE GDATA parameter options and definitions Option Definition offset The starting point of the graphic data. termination The terminating byte of the record. The options are: • DEFAULT – If online, a single terminating byte exists. – If offline, no terminating byte exists.
Specifying print format parameters LINE INKINDEX parameter: points to note • The FreeFlow Print Server LCDS systems support only the offset option for the LINE INKINDEX parameter. • When the bitopt option is specified, the initval must also be specified. • The printer permits an entire line or a portion of a line to be printed in highlight color. You can specify highlight color for variable data on a form. (This is analogous to the output capability of font switching.
Specifying print format parameters Default LINE LPI parameter: points to note No default • If the LARGE[ST] is specified for the LINE BASELINE parameter, the LPI parameter is ignored. • The line spacing value is not based on the maximum LPI font of the line. Instead, it is based on the value that is specified in the command: LINE LPI = LINESPACING LINE MARGIN Specifies the left printing margin within each logical page. Syntax LINE MARGIN = {value | (value, valuetype)} Options Table 4-34.
Specifying print format parameters Options Table 4-35. LINE OVERPRINT parameter options and definitions Option Definition overopt overprint option. This option has the following choices: • PRINT: Specifies that all overprint lines are 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.
Specifying print format parameters LINE OVERPRINT parameter example Following is an example of the LINE OVERPRINT parameter. LINE OVERPRINT=(MERGE,NODISP), VFU=V1, DATA=(1,132), PCCTYPE=ANSI, PCC=(0,NOTRAN); LINE PCC Specifies the position (and possible translation) of the printer carriage control field. NOTE: The PCC parameter is ignored in online printing by the FreeFlow Print Server LCDS systems, because online carriage control is derived from commands that are sent using the online channel protocol.
Specifying print format parameters LINE PCCTYPE Specifies a set of printer carriage control codes that will be used in printing a job. Syntax LINE PCCTYPE = {PCCname | PCCid | USER} Options Table 4-37. LINE PCCTYPE parameter options and definitions Option Definition PCCname printer carriage control name.
Specifying print format parameters LINE PCCTYPE parameter: points to note • For the FreeFlow Print Server LCDS systems, this parameter is treated as if the system were an IBM 3211. Note that there is no functional difference between IBM3211 and IBM4245 for PCC types. • Creation of a user defined PCC table, which may be referenced by either an identifier id or the keyword USER, is specified using the PCC command. Refer to “PCC command” section of the “Specifying input parameters” chapter.
Specifying print format parameters LINE command: points to note • Line spacing with multiple fonts: The vertical spacing of a line is the line spacing of 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.
Specifying print format parameters LINE command examples Here are some examples of use of the LINE command. Example 1 The LINE command below defines the characteristics of the following record structure shown in the following figure. LINE DATA=(1,132), PCC=(0,NOTRAN), PCCTYPE=IBM1403, FONTINDEX=133; Figure 4-1.
Specifying print format parameters Figure 4-2. Sample data record structure Example 3 LINE PCCTYPE=NONE, DATA=(1,57), VFU=V1; MESSAGE command The MESSAGE command permits you to inform the operator of special conditions by displaying user defined text on the screen. • All MESSAGE command parameters must be specified in a single command. If multiple message commands are specified, the parameters in the final command are applied.
Specifying print format parameters MESSAGE command parameters The following table summarizes the MESSAGE command parameters. Table 4-39. Summary of MESSAGE command parameters Parameter Specifies Online Offline DJDE MESSAGE ITEXT Specifies that a message to the operator will be displayed during input processing. Y Y Y MESSAGE OTEXT Specifies that a message to the operator will be displayed during printing.
Specifying print format parameters MESSAGE ITEXT parameter: points to note • If EBCDIC or hexadecimal strings or hex defined bytes using “!” in a character string are used in a MESSAGE command, they are interpreted as standard EBCDIC and are translated to extended ASCII. • You can use the # sign as a case toggle to switch between upper- and lowercase when entering the messages. • ITEXT messages for more copies than one are ignored. No error message is displayed.
Specifying print format parameters MESSAGE OTEXT: points to note • Multiple line messages may be specified for a single copy by one of the following methods: – Specifying the copy number more than once in different OTEXT parameters – Specifying a list of string constants contained in a second level of parentheses. • A maximum of 395 messages is permitted per report.
Specifying print format parameters OUTPUT command The OUTPUT command controls the organization and format of a report, including 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. For further information on graphics features, refer to the “Using PDL commands for graphics” chapter. OUTPUT command parameters The following table summarizes the OUTPUT command parameters. Table 4-42.
Specifying print format parameters Table 4-42. Summary of OUTPUT command parameters (Continued) Parameter Specifies Online Offline DJDE OUTPUT GRAPHICS Specifies if and how graphics are used in the job. Y Y N OUTPUT IDFAULT Specifies the default ink that will be used for parameters in which no ink is specified. Y Y Y OUTPUT IDR Specifies the name of an ink descriptor (IDR) that will be used for the job.
Specifying print format parameters Table 4-42. Summary of OUTPUT command parameters (Continued) Parameter Specifies Online Offline DJDE OUTPUT STAPLE Places a wire stitch in copied sets of output. Y Y N OUTPUT STOCKS Specifies a STOCKSET for use in the report. Y Y Y OUTPUT SYSPPR Specifies the system page paper size for a job. Y Y N OUTPUT TMODE Specifies a maximum paper width in order to improve throughput efficiency when mixed paper sizes are used.
Specifying print format parameters Table 4-43. BFORM parameter options and definitions (Continued) Option Definition NONE Specifies that no form is to be added to the associated report page of variable data. inkref Ink reference. Identifies the inks that override the corresponding inks that are specified in the ink list of the form. If a form does not contain an ink list, the form is printed in black. Default NONE OUTPUT BINDING Specifies printing for long edge or short edge binding.
Specifying print format parameters Figure 4-3. Two-hole drilled output from a long edge feed job, with short edge binding The following figure shows the results of different specifications.
Specifying print format parameters Figure 4-4.
Specifying print format parameters OUTPUT COLLATE Specifies whether pages will be printed collated (in ordered sets) or uncollated. Syntax OUTPUT COLLATE = {YES | NO} Options Table 4-45. OUTPUT COLLATE parameter options and definitions Default OUTPUT COLLATE parameter: points to note Option Definition YES Specifies that the output pages are collated. NO Specifies that the output is not collated.
Specifying print format parameters OUTPUT COVER Specifies that cover sheets are to be fed from the AUX stock. These cover sheets may be placed at the front or back of each copy of a report. Syntax OUTPUT COVER = {(FRONT [, SEP]) | BACK | (BOTH [, SEP]) | NONE} Options Table 4-47. OUTPUT COVER parameter options and definitions Option Definition NONE Specifies that no cover sheets are to be fed. FRONT Specifies that a cover sheet will be fed as the first page of each report copy.
Specifying print format parameters Options Table 4-48. OUTPUT CYCLEFORMS parameter options and definitions Option Definition NONE Specifies that no form will be added to the associated report page of variable data. formid Specifies a 1 to 6 character form file name (may be numeric, alpha, or alphanumeric), which exists on the system disk. INKS Specifies that the inks that follow will be used for the forms.
Specifying print format parameters OUTPUT DENSITY Specifies how the system will respond to a scan line density error. This parameter is obsolete and is listed for compatibility purposes only. It is, however, recognized by the XJDC (PDL) compiler. You would use it if your JSL will be used for printing on a system that is running an early version of operating system software. Syntax OUTPUT DENSITY = {FIX | NOFIX | DEFAULT} Options Table 4-49.
Specifying print format parameters Options Table 4-50. OUTPUT DESTINATION parameter options and definitions Option Definition BIN Specifies that the currently selected bin is used. TRAY Sends output to the sample tray. Transparencies should always be sent to this tray. NOTE: Use caution when selecting the TRAY option because of the limited capacity of the sample tray (100 sheets). EXPORT Specifies that sheets be sent to the bypass transport to be fed into a finishing device.
Specifying print format parameters Options Table 4-52. OUTPUT FACEUP parameter options and definitions Default OUTPUT FACEUP parameter: point to note Option Definition YES Specifies that the printed sheets are delivered to the stacker face up. NO Specifies that the printed sheets are delivered to the stacker face down. NO Specify FACEUP=YES when printing on label stock. Delivering label sheets face up prevents delamination when the sheets are stacked.
Specifying print format parameters OUTPUT FEED parameter: points to note • “FEED = stockreference” must refer to a stock assigned to a stockname by the STOCKSET command that has been specified for the report. • The MAIN stock is the default for system generated pages and is used if no SYSPAGE stock is specified. • The FreeFlow Print Server LCDS software comes with MAIN, AUX, and AUTO stocks defined.
Specifying print format parameters OUTPUT FORMS 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 in the same OUTPUT command. Syntax OUTPUT FORMS = {NONE | formid | (formid [, init [, copies]]) [, (INKS, inkref1 [,inkref2] ...)])} NOTE: To ensure readability, enter the entire FORMS parameter. Do not abbreviate to “FOR,” because the system interprets “FOR” as FORMAT. Options Table 4-55.
Specifying print format parameters OUTPUT FORMS parameter: points to note • CYCLEFORMS and FORMS parameters: Both may be used within a report; however, only the last parameter specified is in effect at any given time. If a multicopy report specifies CYCLEFORMS, a FORMS DJDE that is encountered within the report overrides the CYCLEFORMS parameter from that point in every copy.
Specifying print format parameters Table 4-56. OUTPUT GRAPHICS parameter options and definitions (Continued) Option Definition Unused options: The following options are ignored by the FreeFlow Print Server LCDS systems. They are included here for compatibility. MOVE Specifies that all referenced graphic disk files will be copied into the print file. (On the FreeFlow Print Server LCDS systems, YES is used instead.
Specifying print format parameters Options Table 4-57. OUTPUT IDFAULT parameter options and definitions Option Definition ‘inkref’’ ink reference The default ink that will be used for all subsequent parameters that do not specify a colored ink. Default OUTPUT IDFAULT parameter example The first ink that is referenced in the IDR ILIST parameter in effect at the start of the page. If no IDR is specified, the default ink is BLACK.
Specifying print format parameters OUTPUT IMAGE This parameter is for Batch mode processing only, and specifies the initial graphic imaging parameters to be used. Syntax OUTPUT IMAGE = (vpos [units], hpos [units] [, n [/d]] [, (INKS, inkref1 [, inkref2])]) Options Table 4-59. OUTPUT IMAGE parameter options and definitions 4-60 Option Definition vpos vertical position.
Specifying print format parameters Default OUTPUT IMAGE parameter: points to note Top left corner of the portrait or landscape oriented page, scaled at 1/1 • To put an image on a page, use a form with the image, or use the IMAGE DJDE. • If the UN option is used to define positioning, the UNITS parameter must precede this command. • The IMAGE parameter must follow the GRAPHICS=BATCH parameter, as these two parameters are order dependent.
Specifying print format parameters Table 4-60. OUTPUT INVERT parameter options and definitions (Continued) Default Option Definition BOTH Specifies page inversion on front and back sides. NONE Turns page inversion off. NONE OUTPUT IRESULT Specifies what the result will be when objects that are imaged with different inks overlap. Syntax OUTPUT IRESULT = {BLACK | COLOR} Options Table 4-61.
Specifying print format parameters OUTPUT LOGO Allows you to specify a logo for imaging on all pages of a report, unless it is canceled by a CANCEL DJDE. Up to 128 logos can be specified on a page. Syntax OUTPUT LOGO = (name, vpos units, hpos units [, INKS, inkindex1 [, inkindex2])]) Options Table 4-62.
Specifying print format parameters OUTPUT LOGO parameter: points to note • The number of logos that are allowed on a page varies depending on the structure of the logo and the amount of available dynamic memory space. If there is not enough dynamic memory available for the number of logos specified for a given page, an error message is generated. • Existing .LGO (logo) files and restricted RES format .
Specifying print format parameters OUTPUT MODIFY parameter: points to note • A CME may be coded within a JSL or coded and catalogued separately for use by several JSLs. Any CME invoked by a DJDE must be catalogued separately. Refer to the “CME command” section earlier in this chapter for further information. • If the CME is within the JSL, it must precede a reference to its identifier by the MODIFY parameter.
Specifying print format parameters Table 4-64. OUTPUT NTO1 parameter options and definitions Option Definition n number. The NTO1 threshold, which specifies the maximum number of pages a report may have in order for it to be printed n to 1. If the threshold count is exceeded before the end of the report, the system prints the entire report 1 to n. The default value of n is 50 physical sheets, but n may range from 1 to 32767. When a value is greater than 100, the system generates a warning message.
Specifying print format parameters • NTO1 and OSTK: When printing ordered stock in NTO1 sequence using the OSTK parameter, note the following: The ordered stock must be reverse collated in the feeder so that the first sheet of the set is on the bottom, the second sheet next to the bottom, and so on, with the last sheet of the set on top to be fed first. If the report is larger than the N to 1 threshold, it prints in 1 to N order, and the reverse collated stock is then inappropriate.
Specifying print format parameters Table 4-65. OUTPUT NUMBER parameter options and definitions (Continued) 4-68 Option Definition findex font index. An index into the list of fonts specified in the currently active FONTS parameter of the PDE command, or of a recent DJDE. The index is an integer, starting with 1 for the first font. If a font index is not specified, the first font in the list is used.
Specifying print format parameters Table 4-65. OUTPUT NUMBER parameter options and definitions (Continued) Option Definition inkref ink reference. Specifies the reference number for the ink with which the page number will be printed. NO Specifies that no page numbering is to be performed.
Specifying print format parameters OUTPUT OFFSET parameter: point to note The OFFSET control of FIRST, ALL, or NONE may be modified by the ROFFSET command. Refer to the “ROFFSET” command section in the “Using logical processing” chapter. If OUTPUT OFFSET=FIRST (or ALL) was specified, and the ROFFSET criteria is satisfied on the first page of a report, the normal offset from the preceding report occurs. OUTPUT OSTK Specifies that ordered stocks are used for printing the job.
Specifying print format parameters Table 4-67. OUTPUT OSTK parameter options and definitions (Continued) Option Definition L or P Landscape or Portrait. Indicates at which edge of the paper the tab is located. If L, it is located at the right edge of the landscape oriented page. If it is P, it is located at the right edge of the portrait oriented page. The default is P. Defaults OUTPUT OSTK parameter: points to note • mod and pos: 1 • RES • no tabs • size: 0.
Specifying print format parameters – Tab widths: When running a tab stock job, you must not include the width of the tab when specifying the PAPERSIZE command. However, you must include the width of the tab when specifying the stock size on the print server user interface windows or on the printer control console.
Specifying print format parameters However, if the OSTK command is specified, the system allows a tolerance of n inches (where n is the width of the tab specified in the OSTK command) when validity checks are being performed on BEGIN values and graphic positioning. In addition, the FEED=tab stock DJDE must precede any printable text data that is placed on the tab. – When running tab stock jobs, dedicate one tray for tab stock. – Avoid using tab stock with two-sided printing.
Specifying print format parameters – Specify TABS in the ordered stock statement so that dynamic width checking is disabled. – You may define the ordered stock statement at the job or the system level of a JSL. If you define it at the job level, you must ensure that the ordered stock command defined from the initial JDE and JDL to a selected JDE and JDL are exactly alike.
Specifying print format parameters What to do: In order to run the job in succession, you must code the JSL with MOD=5 and POS=1 for Job 1 and MOD=5 and POS=5 for Job 2. The system keeps track of the last tab position in tray 2 at the end of Job 1. Upon starting Job 2, printer purges Tab 3 and Tab 4 because Job 2 starts with POS=5 and Job 1 used Tab 1 and Tab 2. • You can improve performance by ordering application dependent tab stock.
Specifying print format parameters • PAPERSIZE=B4 and PAPERSIZE=(10.12,14.33) produce identical results because they indicate long edge feed, as opposed to short edge feed format. Refer to the “SEFFNT command” section in the “Specifying input parameters” chapter for detailed information on short and long edge feed. • To print on B5 and 7 by 10 inch paper sizes, the printer requires the 7 by 10 inch enablement kit (a hardware option) to be installed.
Specifying print format parameters Options Table 4-69. OUTPUT PURGE parameter options and definitions Option Definition NO Specifies that graphic disk files should not be deleted. YES Specifies that all .IMG graphics files that were created or replaced by document interleaved graphic processing for this report should be deleted at the end of the report printing. Default OUTPUT PURGE parameter: point to note YES You can use the SAVE DJDE to override the purging of specific files.
Specifying print format parameters OUTPUT SF2FUNCTION Specifies to the third party finisher whether or not it should perform the user-defined SF2 operation on the current report. This parameter provides control over third party finishing devices that conform to the DFA standard. You use it to invoke Finishing Function SF2 through the DFA channel C7. The user must specify what function SF2 will have.
Specifying print format parameters Options Table 4-72. OUTPUT SHIFT parameter options and definitions Option Definition v1 value 1. An integer value in dots for the amount of shift on the simplex page or the odd (front) side of the duplex page. (Each dot is 1/300 of an inch.) The range for v1 is –75 to 75. v2 value 2. A value in dots for the amount of shift on the even (back) side of a duplex page. The range for v2 is –75 to 75. YES Specifies that a shift occurs.
Specifying print format parameters Options Table 4-73. OUTPUT SIZING parameter options and definitions Option Definition SEMIAUTO (Standard mode of operation.) Causes the printer to stop printing when there is a paper size mismatch. For the printer to resume printing, the operator must do one of the following: • Resume printing to print the job on the next larger size paper. • Change the paper or the effective stock. • Cancel the job.
Specifying print format parameters • If the stock is not an exact paper size match, but is larger than the specified size, selecting SEMIAUTO (or BEST) causes the printer to stop and wait for operator confirmation to continue printing, using the larger paper. Further mismatches of this type are ignored until: – The STOCKS parameter changes – End Of Report and no STOCKS parameter is in effect – End Of Job – The printer stops printing.
Specifying print format parameters Default OUTPUT STAPLE parameter: points to note NO • The STAPLE command must be specified in the initial JDL/ JDE, or the JDL/JDE DJDE record must be the first record processed. If there is a banner page in front of the JDL/JDE DJDE record, the STAPLE command is ignored. • If the NTO1=YES and STAPLE=YES parameters are specified, the system overrides NTO1=YES with NTO1=NO and places an error message in the listing file when the JSL is compiled.
Specifying print format parameters OUTPUT STOCKS parameter: points to note • If the stocksetname does not reference a STOCKSET command coded earlier in the same JDL, the system assumes that the stockset exists as a .STK file in the “lcds” folder, which is read at print time. In this case, XJDC inserts a message in the listing file when the JSL is compiled, indicating that a .STK file will be used at print time.
Specifying print format parameters OUTPUT SYSPPR parameter: points to note • PAPERSIZE=B4 and PAPERSIZE= (10.12, 14.33) produce identical results in that they indicate long edge feed, as opposed to short-edge feed format. Refer to the “SEFFNT command” section in the “Specifying input parameters” chapter for detailed information on short and long-edge feed.
Specifying print format parameters OUTPUT TMODE Specifies a maximum paper width in order to improve throughput efficiency when mixed paper sizes are used. Refer to “Paper sizing and print speed” in your printer operator guide for an explanation of the relationship between paper widths and throughput speed. Syntax OUTPUT TMODE = {width | (width [,widthunit])} Options Table 4-77.
Specifying print format parameters • Pitch modes and throughput performance: The printing system can operate in several different pitch modes: 3, 4, 5, 6, and 7. The following table shows the minimum and maximum boundary values for each pitch mode and the default paper sizes that can be specified with the TMODE parameter. The table shows these default scan values in inches (IN), centimeters (CM), DOTS, and XDOTS (dots at 600 dpi), along with their associated print speeds in pages per minute (ppm).
Specifying print format parameters – For any paper size wider than 15.32 inches / 389 mm, the system automatically switches to 3 pitch mode, in which it prints up to 77 pages per minute. – For very large papers, such as 11 by 17 inches or A3, paper is fed short edge first, so the 11-inch edge leads through the printer.
Specifying print format parameters Example: Assuming that your application calls for 8.5 by 11-inch paper, you could use 5 pitch mode. However, by selecting 4 pitch, which reduces the pages per minute on the DP180 EPS from 180 to 77, you make the printer speed more closely match your finishing device capabilities and you reduce the potential for paper jams. Problem: Your application uses four paper sizes, ranging from 8.5 by 11 inches for the first few pages to 11 by 17 inches for the last several pages.
Specifying print format parameters OUTPUT TRANS Specifies whether or not transparencies are used in the print job. Syntax OUTPUT TRANS = {YES | NO} Options Table 4-79. OUTPUT TRANS parameter options and definitions Default OUTPUT TRANS parameter: points to note Option Definition YES Indicates that transparencies will be used in the job. NO Indicates that transparencies will not be used in the job.
Specifying print format parameters Options Table 4-80. OUTPUT UNITS parameter options and definitions Option Definition size An integer value constant that defines the number of dots in a user defined unit (UN). When used to compute the position of a graphic, the result is rounded to the nearest dot.
Specifying print format parameters OUTPUT XSHIFT parameter example Following is an example of the OUTPUT XSHIFT parameter. INVPDE: PDE PMODE=PORTRAIT, BEGIN=(1.3,.37), FONTS=P0612A; INVJDE: JDE; OUTPUT INVERT=BACK, SHIFT=YES, XSHIFT=40, FORMAT=INVPDE,PAPERSIZE=(8.5,11); OUTPUT command: point to note Certain parameters of the OUTPUT command interact with each other or with other commands.
Specifying print format parameters Example 3 The commands in the following figure illustrate use of the offsetting features of the OUTPUT command. The parameter ALL offsets all copies of all reports; FIRST offsets just the first copy of each report and NONE inhibits offsetting. Figure 4-5.
Specifying print format parameters Figure 4-6. Illustration of use of OUTPUT CYCLEFORMS parameter in a multicopy report PDE command The PDE command specifies a page descriptor entry (PDE), which defines the formatting 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.
Specifying print format parameters Table 4-82. Standard print formats (PDEs) PDE id No. of lines No. of columns lines per inch char. per inch Approx. point size Page size and orientation* BEGIN values Default font id 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,.
Specifying print format parameters PDE command parameters The following table summarizes the PDE command parameters. Table 4-83. Summary of PDE command parameters Parameter Specifies Online Offline DJDE PDE BEGIN Specifies the location of the first print line on the page. Y Y Y PDE FONTS Specifies the fonts to be used to print CME and variable data. Y Y Y PDE PMODE Specifies whether the job will print with landscape or portrait orientation.
Specifying print format parameters Options Table 4-84. PDE BEGIN parameter options and definitions Option Definition vpos vertical position Specifies the vertical position of the first character of the first print line of the logical page relative to the top edge of the physical sheet. It must be a decimal number with up to four digits to the right of the decimal point; for example, 0.5634 or 2.35. The default vertical position is .18.
Specifying print format parameters • RTEXT is imaged on a separate physical sheet. The line and column specifications for positioning the text refer to the first logical page specified in the PDE. • RAUX criteria that is found on any logical page on the physical page causes that sheet to be fed from the tray containing the stock identified as the AUX stock. • Accounting statistics are accumulated on the basis of physical pages.
Specifying print format parameters • The placement of the values of the BEGIN parameter on the FreeFlow Print Server LCDS systems, 4850 LPS, 4890 LPS, and DP92C LPS is relative to the top edge of the physical sheet for all paper sizes. On the 4635 and DP180 LPS, however, an A4 paper size specification causes the image to shift approximately 1/8 inch (3 mm) downward.
Specifying print format parameters PDE FONTS parameter: points to note • If different fonts are used on the same print line, character heights of all fonts used in the print line are compared to find the largest font in the line. (The line spacing value that was defined, or specified as an override, for that font is used to determine the position of the next print line.) • The maximum number of fonts that may be used in printing a given page or a given job varies depending on a number of factors.
Specifying print format parameters PDE command: points to note • You may code PDEs as part of the JSL or create them as separate files so that they may be referenced by one or more JDLs or by DJDEs. PDEs are invoked by the OUTPUT FORMAT parameter or by the FORMAT DJDE. A PDE must have been previously compiled for a DJDE to access it. • You can create a PDE as a separate disk file and use it as if it were part of the JDL that references it.
Specifying print format parameters Example 2 The following is an example of multiple BEGINs. Two logical pages are defined on one physical page. 2UP: PDE Example 3 BEGIN=(.5 IN,.5 IN), BEGIN=(6.5IN,.5 IN), PMODE=PORTRAIT, FONTS=P1012B; This is an example of a PDE that may be compiled separately from a JDL. The compilation process creates a .PDE object file, which may be referenced from within a JDL or by a DJDE. The name of the object file for this PDE is PDE99.
Specifying print format parameters ROUTE RFORM Specifies a form to be printed with all RTEXT pages. Syntax ROUTE RFORM = {formid | NONE} Options Table 4-88. ROUTE RFORM parameter options and definitions Option Definition formid form identifier. Name of the form that will be used with all RTEXT pages. This identifier references a previously created form file (formid.FRM). NONE Specifies that no form will be printed on RTEXT pages.
Specifying print format parameters Options Table 4-89. ROUTE RTEXT parameter options and definitions Option Definition sc string constant. Specifies the message to be printed (a string of 1 to 132 characters). It is printed with the first font specified in the FONTS parameter of the PDE command. Refer to the fontindex option in this table. passnum pass number. An integer specifying the single copy (pass) to which the text applies.
Specifying print format parameters • If a proportional pitch font is used, the starting column number for printing the RTEXT is determined by using the character spacing value for the space character in the character font. • If RTEXT is specified along with COVER=(FRONT, SEP) or (BOTH, SEP), the RTEXT pages are printed on the covers. Front covers are picked only on copies for which there is RTEXT. If RTEXT is specified in noncollate mode, only the routing page for copy one is printed.
Specifying print format parameters After the above commands are compiled by PDL, a .TST file is created. In the example above, the file would be named “ROUTE1.TST.” You can then access this file by name with the ROUTE command (RTEXT= rtextid) from a JDL or with a DJDE. For this example, the RTEXT parameter would be coded as follows: RTEXT=ROUTE1, You must specify RFORM, if it is needed, along with the reference to the RTEXT file (RFORM is never catalogued with RTEXT).
Specifying print format parameters STOCKSET command parameters The following table summarizes the STOCKSET command parameters. Table 4-90. Summary of STOCKSET command parameters Parameter Specifies Online Offline DJDE STOCKSET ASSIGN Lists stock names and associates them with stock references. Y Y N STOCKSET INIFEED Specifies which stock to use in the absence of any designation in the OUTPUT FEED parameter.
Specifying print format parameters STOCKSET INIFEED Specifies which stock to use in the absence of any OUTPUT FEED parameter or FEED DJDE. If no stock is specified, the INIFEED parameter defaults to the first stock name specified in the ASSIGN parameter. Syntax [ac:] STOCKSET INIFEED = {‘stockname’ | stockreference} Options Table 4-92.
Specifying print format parameters Table 4-93. STOCKSET SYSPAGE parameter options and definitions Option Definition MAIN Specifies that system pages feed from the tray containing the stock identified as MAIN. AUX Specifies that system pages will feed from the tray containing the stock identified as AUX. Default STOCKSET SYSPAGE parameter: points to note MAIN • Paper size mismatch on system pages: Pages generated by the system via such commands as IDEN OPRINFO are formatted for 8.
Specifying print format parameters • The MAIN and AUX stocks and their preferred trays have already been defined in the operating system software when the printing system is delivered. However, you can change their specifications at the user interface, using the Stock Manager windows. (You cannot, however, delete them.) STOCKSET command example The STOCKSET command is similar to the PDE and CME commands, because it produces a file you can compile separately from the JDL.
Specifying print format parameters VFU command The VFU command assigns output line numbers to printer carriage control channels. These Line to Channel assignments perform the same function as the printer carriage control tape on a conventional line printer. The VFU command also assigns line numbers to the top of the form (TOF parameter) and the bottom of the form (BOF parameter). TOF and BOF are used for prejob page alignment and for page overflow processing.
Specifying print format parameters Options Table 4-95. VFU ASSIGN parameter options and definitions Option Definition channo channel number. The number of the channel being assigned. It is an integer in the range 0 to 15. lineno line number. The number of the output print line that you are assigning to a particular channel. It is an integer in the range TOF to BOF. Default No default VFU BOF Specifies the Bottom Of Form line number. Syntax [ac:] VFU BOF = value Options Table 4-96.
Specifying print format parameters Options Table 4-97. VFU TOF parameter options and definitions Option Definition value Specifies the number of lines from the top of the logical page to the first print line (top of form). The TOF specification is independent of channel assignments. It should be greater than or equal to 1, and less than or equal to the smallest line number assigned to a channel.
Specifying print format parameters VFU command 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 assigned 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; Assume the printing system is printing a report and the current line number is 11.
Specifying print format parameters 4-114 Using LCDS Print Description Language
5. Using Dynamic Job Descriptor Entries (DJDEs) Dynamic Job Descriptor Entries, unlike the PDL commands described in the Input Processing, Print Format, and Logical Processing sections, are not coded in JSLs. They are coded in the data stream to make changes during printing to what was specified in the JSL. DJDEs are coded slightly differently from JSL statements. Using the IDEN command to enable DJDEs To invoke DJDE processing in a job, you must code an IDEN command in the JDL.
Using Dynamic Job Descriptor Entries (DJDEs) Example Here is another example: IDEN PREFIX=E'DJDE', SKIP=7, OFFSET=2, OPRINFO=YES; For information on coding the IDEN command and explanations of its parameters and options, refer to the “IDEN command” description in the “Specifying input parameters” chapter. Specifying DJDE records DJDE records are part of the data stream. The system looks for them only if there is an IDEN PREFIX command within the JDE used to process the job.
Using Dynamic Job Descriptor Entries (DJDEs) • DJDE records need not be consecutive because none of the parameters are applied until the system encounters END. However, it is recommended that DJDE records be consecutive, especially when used with delimiter records. • A page oriented DJDE that is positioned before any print record on a page takes effect on the current page.
Using Dynamic Job Descriptor Entries (DJDEs) The following figure shows the usage of a single record DJDE and the IDEN command. Figure 5-1. Single record DJDE diagram and IDEN command The following is an example of a multiple record DJDE.
Using Dynamic Job Descriptor Entries (DJDEs) DJDE operator information pages The specification OPRINFO=YES in the JDE specifies that the DJDE records will be printed and sent to the output bin at the next page transition after an END command. The DJDE records are printed on a separate page from the report data. However, no page formatting occurs and DJDEs in long records are truncated at the end of the physical page boundary.
Using Dynamic Job Descriptor Entries (DJDEs) Restrictions on job parameter modification To process a DJDE, the system must process data up to the recognition and interpretation of the DJDE itself. This sequence requires that the basic description of the input source must be correct before the application of the DJDE. Therefore, you must not change the description of the input source with DJDEs, either by accident or by intent.
Using Dynamic Job Descriptor Entries (DJDEs) Parameters that can be changed through a JDE DJDE The parameters that can be changed through a JDE that you specify in a JDE DJDE are listed in the following table. Table 5-2.
Using Dynamic Job Descriptor Entries (DJDEs) Considerations and cautions for using DJDEs Remember the following points and cautions when coding and applying DJDEs. Page transition issue If you use the JDE DJDE to reassign the channel that caused the page transition (generally channel 1), when the DJDE printer carriage control (PCC) byte is processed the first page may be incorrectly positioned after the page transition occurs.
Using Dynamic Job Descriptor Entries (DJDEs) Effect of multiple logical pages • JDE • JDL • DUPLEX=NO • FEED If you use multiple PDE BEGIN commands to define multiple logical pages on one physical page (as described in the PDE command description in the “Specifying print format parameters” chapter), consider the following: • With the exception of DEPT and SHIFT, all page oriented DJDEs are applied at a logical page boundary.
Using Dynamic Job Descriptor Entries (DJDEs) Printer carriage control and DJDEs Printer carriage control processing may differ if it is associated with DJDEs. Use of certain PCC parameters in conjunction with DJDEs affects what those parameters do. The following table shows what to expect from those PCC parameters when DJDEs are present. Table 5-3.
Using Dynamic Job Descriptor Entries (DJDEs) • If DJDEs are located at the start of a report, they invoke changes beginning with the first page of the report (or report copy). Table 5-4. Page oriented DJDEs DJDE Function BEGIN Specifies the location of the starting print line of each logical page. BFORM Specifies that a form will be printed on the back side of each printed page.
Using Dynamic Job Descriptor Entries (DJDEs) Table 5-4. Page oriented DJDEs (Continued) 5-12 DJDE Function ITEXT Specifies a text message that will be displayed to operators during processing. JDE Specifies the JDE to be used within the selected JDL at the next page boundary. JDL Specifies the name of the JDL to be invoked at the next page boundary. MAP References a previously created font mapping file. MARGIN Specifies the left printing margin within each logical page.
Using Dynamic Job Descriptor Entries (DJDEs) Record oriented DJDEs Record oriented DJDEs take effect immediately at the next record following the last record of the packet (set) of DJDE records of which they are a part. After an END parameter, a compiled record oriented DJDE takes effect immediately. NOTE: The exception is the OVERPRINT DJDE, which takes effect at the next logical page boundary if FONTINDEX has been invoked in a JDE or DJDE.
Using Dynamic Job Descriptor Entries (DJDEs) The following table lists record oriented DJDEs that are used with graphics. Table 5-6. Record oriented DJDEs for graphics DJDE Function ALTER Specifies the new imaging parameters for graphics. BATCH Delimits Batch mode graphic data to permit normal processing of online banner pages for Batch mode jobs. CANCEL Cancels the hold specified by the H parameter in a GRAPHIC or IMAGE DJDE.
Using Dynamic Job Descriptor Entries (DJDEs) Options Table 5-7. ALTER DJDE options and definitions Option Definition name Identifies a previously specified graphic that is currently subject to the HOLD parameter of the command that specifies it. Refer to the “IMAGE DJDE” section later in this chapter. vpos vertical position.
Using Dynamic Job Descriptor Entries (DJDEs) ASSIGN DJDE Specifies an assignment of a VFU channel number to a page line number or set of line numbers. Type Syntax Record oriented ASSIGN= (channo, lineno) or ASSIGN = (channo, (lineno1 [, lineno2] [, ...])) Options Table 5-8. ASSIGN DJDE options and definitions Option Definition channo channel number. The number of the channel being assigned. It is an integer in the range 0 to 12. lineno line number.
Using Dynamic Job Descriptor Entries (DJDEs) Syntax BATCH = {START | END} Options Table 5-9. BATCH DJDE options and definitions Option Definition START Marks the beginning of online Batch mode data. END Marks the end of online Batch mode data. BATCH DJDE: points to note • The BATCH DJDE is supported for online Batch mode jobs only. • This DJDE must be used precisely to mark the beginning and ending of online Batch mode data.
Using Dynamic Job Descriptor Entries (DJDEs) Options Table 5-10. BEGIN DJDE options and definitions Option Definition vpos Specifies the vertical position of the first character of the first print line on the logical page. hpos Specifies the horizontal position of the first character of the first print line on the logical page. units Unit measure for the horizontal and vertical positions. It may be specified in inches (IN), centimeters (CM), or DOTS. The default is IN.
Using Dynamic Job Descriptor Entries (DJDEs) Options Table 5-11. BFORM DJDE options and definitions Option Definition NONE Specifies that no form will be added to the associated report page of variable data. When NONE is specified in combination with other BFORM options, it takes precedence over the other BFORM options, so that no forms are printed. formid form identifier Specifies a filename for a form that exists on disk.
Using Dynamic Job Descriptor Entries (DJDEs) BOF DJDE Specifies the Bottom Of Form (BOF) line number. It takes effect at the next record following an END DJDE. Type Syntax Record oriented BOF = value Options Table 5-12. BOF DJDE options and definitions Option Definition value Specifies the number of lines from the top of the output page to the last print line on the page (Bottom Of Form).
Using Dynamic Job Descriptor Entries (DJDEs) Options Table 5-13. C (text) DJDE options and definitions Option Definition text The actual text of the comment C (text) DJDE: points to note • When you are coding the C text DJDE, the C must be followed by a space (not by an equal sign). • Any text following the keyword up to a semicolon (unless the semicolon is enclosed in parentheses) or the End Of Record is treated as commentary.
Using Dynamic Job Descriptor Entries (DJDEs) COLLATE DJDE Specifies Collated or Uncollated mode for printing. Type Syntax Page oriented COLLATE = {YES | NO} Options Table 5-15. COLLATE DJDE options and definitions Option Definition YES Specifies that report copies are to be printed in Collated Mode. (Copies are printed in complete, ordered sets.) NO Specifies that report copies are to be printed in Uncollated Mode.
Using Dynamic Job Descriptor Entries (DJDEs) COPIES DJDE: points to note • In duplex processing, if COPIES appears before the back side of a duplex page, a blank back sheet is output, and the print data continues on the next front page. • If COPIES=0 is specified for a page, that page is not printed. • If number is set to zero, this copy count remains in effect until a new copy count or End Of Report is encountered. DJDEs encountered while number is set to zero are processed normally.
Using Dynamic Job Descriptor Entries (DJDEs) DEPT DJDE Defines the name under which accounting statistics will be accumulated for this report. Type Syntax Page oriented DEPT = sc Options Table 5-18. DEPT DJDE options and definitions Option Definition sc string constant. Represents a department code or name under which accounting information is maintained. May be up to 31 characters.
Using Dynamic Job Descriptor Entries (DJDEs) Options Table 5-19. DESTINATION DJDE options and definitions Option Definition BIN Specifies delivery to the currently active output bin. TRAY Specifies delivery to the sample tray. NOTE: Use caution when selecting the sample tray because of its limited capacity. EXPORT Specifies that sheets will be sent to the bypass transport. DESTINATION DJDE: points to note • Transparencies should be sent only to the sample tray.
Using Dynamic Job Descriptor Entries (DJDEs) END DJDE Specifies the end of a DJDE packet. When an END DJDE is encountered, the system applies all DJDE information specified to the current printing environment at the next page or record boundary. Type Syntax Record oriented END; END DJDE: points to note • After the system detects an END parameter, record oriented DJDEs take effect immediately. Page oriented DJDEs take effect at the current page if no data has been printed.
Using Dynamic Job Descriptor Entries (DJDEs) FEED DJDE Controls the stock on which the page is printed. “FEED=stockreference” must refer to a stock assigned to a ‘stockname’ by the STOCKSET command in effect at the time the page is printed. Type Syntax Page oriented FEED = {MAIN | AUX | OPR | ‘stockname’ | stockreference} Options Table 5-21. FEED DJDE options and definitions Option Definition AUX Specifies that the page will feed from the tray(s) assigned to the AUX stock.
Using Dynamic Job Descriptor Entries (DJDEs) Options Table 5-22. GDATA DJDE options and definitions Option Definition offset The starting point within the record of the file data that will be downloaded. termination The terminating byte of the record. The options are: • DEFAULT – If online, a single terminating byte exists. – If offline, no terminating byte exists. • n: The number of terminating bytes that exist FILE DJDE Enables you to load files to the system disks while a print job is in progress.
Using Dynamic Job Descriptor Entries (DJDEs) Table 5-23. FILE DJDE options and definitions (Continued) Option Definition n Rounded up to a multiple of 6, specifies the maximum number of card images to be processed for this file. The default number is 120. NOTE: This option is ignored by DP 2000 Series EPS systems, which do not support card image files.
Using Dynamic Job Descriptor Entries (DJDEs) Files that are transferred with a D (delete) option are deleted as soon as the report is processed, and therefore must not be referenced in a subsequent report. NOTE: The FILE DJDE does not allow a file to be replaced if the file is a system permanent file. System permanent files have a $ in their names. Card image file processing When card image files are transferred, the following occurs: 1.
Using Dynamic Job Descriptor Entries (DJDEs) Records with a length greater than 80 bytes are truncated to 80 bytes; records with a length less than 80 bytes are padded with ASCII blanks to 80 bytes. Character translation may be performed, depending on the JDE in effect. 4. The system terminates record processing for the card image being downloaded when another DJDE record is encountered.
Using Dynamic Job Descriptor Entries (DJDEs) • If the first record does not meet the requirements for a label record, the preceding DJDE packet is printed on an OPRINFO page with an error message indicating that no label record was found. The system then proceeds to process the data as variable text data.
Using Dynamic Job Descriptor Entries (DJDEs) If the nonblank character that is appended at the end of the records is not consistently present throughout the file, the preceding DJDE packet is printed on an OPRINFO page with an error message indicating that processing for the file “FILENAME” is being aborted due to a data error. The system then deletes the partial file that was created and proceeds to process the data as variable text data.
Using Dynamic Job Descriptor Entries (DJDEs) Options Table 5-24. FONTINDEX DJDE options and definitions Option Definition offset Indicates the byte offset in the data record where the font index number is located. Refer to the “LINE OVERPRINT” parameter section in the “Specifying print format parameters” chapter for a discussion of FONTINDEX usage with overprint lines and maximum number of fonts. initval initial value.
Using Dynamic Job Descriptor Entries (DJDEs) 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.
Using Dynamic Job Descriptor Entries (DJDEs) Table 5-25. FONTS DJDE options and definitions (Continued) Option Definition K or DB Indicate a double byte font. A Indicates a 1/2 or 1/4 sized double byte font. *hn Specifies the factor (an integer value from 1 through 16) by which the font will be magnified horizontally. Default: 1 *vn Specifies the factor (an integer value from 1 through 16) by which the font will be magnified vertically. Default: 1 s spacing.
Using Dynamic Job Descriptor Entries (DJDEs) • Because there is ambiguity between the abbreviated forms of the FONTINDEX and the FONTS DJDEs, if either is abbreviated to the first three letters, DJDE processing presumes FONTINDEX. • If there are more than 128 fonts in a DJDE packet, a syntax error occurs, and the FONTS DJDE is ignored. • If any font in the font list is missing, a syntax error occurs and the FONTS DJDE is ignored.
Using Dynamic Job Descriptor Entries (DJDEs) FORM[S] DJDE Specifies the form to be merged onto the printed pages. It takes effect on the next page boundary. The form specified is invoked beginning with the specified starting copy number. Multiple FORMS DJDEs may be used to associate different forms with different copy plies. Type Syntax Page oriented FORM[S] = {NONE | formid | (formid [, init [, copies]]) [, (INKS, inkref1 [, inkref2] ...
Using Dynamic Job Descriptor Entries (DJDEs) GDATA DJDE Specifies the starting point of the graphic data from the beginning of the user portion of a data record. Type Syntax Record oriented GDATA = offset, termination Options Table 5-28. GDATA DJDE options and definitions Option Definition offset The starting point within the record of the graphic data that will be downloaded. termination The terminating byte of the record. The options are: • DEFAULT – If online, a single terminating byte exists.
Using Dynamic Job Descriptor Entries (DJDEs) Options Table 5-29. GRAPHIC DJDE options and definitions 5-40 Option Definition name Identifies the graphic. If document interleaved, it becomes the file name with which the .IMG file is written. If page interleaved, it is used to associate the graphic with other DJDE references. vpos vertical position. Specifies the amount of vertical spacing of the top edge of the graphic from 0,0 on the physical page. hpos horizontal position.
Using Dynamic Job Descriptor Entries (DJDEs) GRAPHIC DJDE: points to note • Other than name, none of the parameters may be used if the specified graphic is document interleaved, nor should name normally be used if the graphic is referenced by an IMAGE DJDE. If the graphic is page interleaved, the remaining parameters may be used exactly as on the IMAGE DJDE (except for the T parameter).
Using Dynamic Job Descriptor Entries (DJDEs) • If inks are used: – If one inkref in the list is omitted, commas must be used as place holders to maintain the relative positioning of the remaining ink references. – If more than two ink references are specified, the additional ink references are ignored. ICATALOG DJDE Specifies an ink catalog that contains palettes and inks for subsequent pages. Type Syntax Page oriented ICATALOG = ‘ink catalog name’ Options Table 5-30.
Using Dynamic Job Descriptor Entries (DJDEs) Options Table 5-31. IDFAULT DJDE options and definitions Option Definition ‘inkref’’ ink reference The default ink that will be used for all objects that do not specify an ink. IDFAULT DJDE: point to note Only saturated primary colors can be specified by this DJDE. IDR DJDE Specifies the ink descriptor entry that will be used for subsequent pages.
Using Dynamic Job Descriptor Entries (DJDEs) Options Table 5-33. ILIST DJDE options and definitions Option Definition ‘inkname’ Specifies an ink name that will be part of the ILIST that is defined for the page. Note that the ink name is specified within single quotes. ILIST DJDE example ILIST = (‘BLACK’, ‘XEROX.RED’) IMAGE DJDE In Batch mode, this DJDE defines new imaging parameters for subsequent graphics. In all other modes, it defines imaging parameters for the named graphic.
Using Dynamic Job Descriptor Entries (DJDEs) Table 5-34. IMAGE DJDE options and definitions (Continued) Option Definition hpos horizontal position. Specifies the horizontal position of the left edge of the graphic, as a rightward offset, relative to 0,0 on the current physical page. Specified as a decimal number with up to three digits to the right of the decimal point and may be followed by a space and the units indicator. NOTE: The default value for the hpos parameter is 0.
Using Dynamic Job Descriptor Entries (DJDEs) Syntax INKINDEX = {offset, [ZERO | ONE] [, bitopt] | NONE} Options Table 5-35. INKINDEX DJDE options and definitions Option Definition offset Indicates the byte offset in the data record where the ink index number is located. ZERO Specifies that the first ink in the list is referenced with an index value of 0. ONE Specifies that the first ink in the list is referenced with an index value of 1.
Using Dynamic Job Descriptor Entries (DJDEs) Options Table 5-36. INVERT DJDE options and definitions Option Definition FRONT Specifies page inversion on front sides. BACK Specifies page inversion on back sides. BOTH Specifies page inversion on both front and back sides. NONE Specifies no page inversion. IRESULT DJDE Specifies what the result will be when objects that are imaged with different inks overlap. Type Syntax Page oriented IRESULT = {DEFAULT | BLACK | COLOR} Options Table 5-37.
Using Dynamic Job Descriptor Entries (DJDEs) • If more than one IRESULT is specified on a page, the last instance takes precedence. • The FreeFlow Print Server-based DT 128/155/180 HighLight Color Printing Systems have queue settings for this option; the default setting is Black. ITEXT DJDE Specifies a text message to be displayed to the operator during input processing. Type Syntax Page oriented ITEXT = {NONE | sc} Options Table 5-38.
Using Dynamic Job Descriptor Entries (DJDEs) Options Table 5-39. JDE DJDE options and definitions Option Definition JDEid Job Descriptor Entry identifier. Name of the JDE that will be used within the current or selected JDL at the next page boundary. This is called the “selected JDE.” JDE DJDE: points to note • The new JDE that is specified in the JDE DJDE JDEid parameter is the “selected JDE.
Using Dynamic Job Descriptor Entries (DJDEs) JDL DJDE: points to note • The JDLid.JDL file must exist on the print server disk. • If there is no delimiter between the JDL DJDE and the JDL identifier (JDLid), a syntax error is displayed. • If only a JDL DJDE (no JDE DJDE) is specified in the DJDE packet, the system uses the JDE most recently specified in a DJDE in this report. If no JDE was specified in any DJDE, the system uses the JDE that is specified on the LCDS Setup window.
Using Dynamic Job Descriptor Entries (DJDEs) Table 5-41. LOGO DJDE options and definitions (Continued) Option Definition units Specifies the unit of measure for the vertical and horizontal positions of the logo on the page. Available units are: • DOTS • CM (centimeters) • IN (inches) • UN (user defined unit) • XDOTS (DOTS at 600 spi) If UN is specified, the user defined positioning unit must be previously defined by the OUTPUT UNITS command in the current JDE or JDL. The default positioning unit is IN.
Using Dynamic Job Descriptor Entries (DJDEs) LOGO DJDE: points to note • Any logos specified in a selected JDE (the JDE that was specified in the JDE DJDE) replace those from the original JDE. If none are specified in the selected JDE, logos from the original JDE are canceled. • If the logo that is specified in the Initial JDE is not found, the job aborts and an error message is displayed.
Using Dynamic Job Descriptor Entries (DJDEs) Table 5-42. LPI DJDE options and definitions (Continued) Option Definition lineno line number Specifies the line number or numbers over which the line spacing will be applied. The options are: • n Number of the line to which the specified linespacing will be applied • n– Number of the line from which the specified linespacing will be applied through BOF (bottom of form). • n–m The specified linespacing will be applied from line n through line m.
Using Dynamic Job Descriptor Entries (DJDEs) Options Table 5-44. MARGIN DJDE options and definitions Option Definition value Specifies the distance from the left edge of the logical page (as indicated by the BEGIN value currently in effect) to the left margin. Has the format nnn.mm (a positive decimal number with up to 2 digits to the right of the decimal point). valuetype Unit of measure for the margin value.
Using Dynamic Job Descriptor Entries (DJDEs) Table 5-45. MODIFY DJDE options and definitions (Continued) Option Definition copies Specifies the number of plies (passes) on which to apply the CME. If copies is not specified, then the CME applies to all copies beginning with the copy number specified by init. NONE Specifies that no CMEs will be applied; data is processed without modification. MODIFY DJDE: points to note • Any CME invoked by a DJDE must be catalogued separately.
Using Dynamic Job Descriptor Entries (DJDEs) Options Table 5-46. NUMBER DJDE options and definitions Option Definition pnum page number An integer that specifies the starting page number. The maximum page number that can be printed is 2,147,483,647.
Using Dynamic Job Descriptor Entries (DJDEs) Figure 5-2.
Using Dynamic Job Descriptor Entries (DJDEs) • The options for the NUMBER DJDE are the same as for the NUMBER parameter of the OUTPUT JSL command. NUMBER DJDE example NUMBER=(1,1,40,1), END; OTEXT DJDE Specifies a text message to be output to the operator during job printing. It takes effect on the next page boundary. Type Syntax Page oriented OTEXT = {(sc [, {passnum | END}] [,WAIT]]) | NONE} or OTEXT = sc Options Table 5-47.
Using Dynamic Job Descriptor Entries (DJDEs) OTEXT DJDE: point to note The DJDE parameters are the same as for the MESSAGE OTEXT command. OVERPRINT DJDE Specifies how overprint lines are handled. (Overprint lines are print lines whose carriage control specifies printing with no line spacing because the last printed line.) Type Syntax Record oriented OVERPRINT = (overopt, disp) Options Table 5-48. OVERPRINT DJDE options and definitions Option Definition overopt overprint option.
Using Dynamic Job Descriptor Entries (DJDEs) OVERPRINT DJDE: points to note • The OVERPRINT DJDE normally takes effect on the next record following an END DJDE. If FONTINDEX has been invoked in a JDE or DJDE, OVERPRINT takes effect at the next logical page boundary. • OVERPRINT options are the same as for the LINE OVERPRINT parameter.
Using Dynamic Job Descriptor Entries (DJDEs) PALETTE DJDE example PALETTE = ’SIMPLE’ PMODE DJDE Specifies the text orientation for each page. Type Syntax Page oriented PMODE = {LANDSCAPE | PORTRAIT} Options Table 5-50. PMODE DJDE options and definitions Option Definition LANDSCAPE Indicates that print lines will be parallel to the long edge of the paper (for paper loaded with its short edge facing the feed direction). Print lines on 11 by 17 inch paper are parallel to the short edge.
Using Dynamic Job Descriptor Entries (DJDEs) Options Table 5-51. RFORM DJDE options and definitions Option Definition formid form identifier. Name of the form to be printed with all RTEXT pages. References a previously created form file (FILENAME.FRM). NONE Specifies that no form will be printed with RTEXT pages. INKS Specifies that the inks that follow will be used for the forms. inkref Identifies the inks that override the corresponding inks that are specified in the ink list of the form.
Using Dynamic Job Descriptor Entries (DJDEs) Syntax RTEXT = {NONE | sc | (sc [, {passnum | ALL} [, line [, col [, fontindex]]]]) | rtextid} Options Table 5-52. RTEXT DJDE options and definitions Option Definition sc string constant Specifies the message to be printed (a string of 1 to 132 characters). It is printed with the first font specified in the FONTS parameter of the PDE command. Refer to the fontindex option in this table.
Using Dynamic Job Descriptor Entries (DJDEs) SAVE DJDE Specifies that image (.IMG) files that were updated during the current report will not be purged when processing of the report is completed. For specific files, this DJDE overrides automatic file deletions that are specified by the OUTPUT PURGE=YES parameter within the JDE. Type Syntax Record oriented SAVE = {filename | (filename [, ...]) | ALL} Options Table 5-53. SAVE DJDE options and definitions Option Definition filename Name of an .
Using Dynamic Job Descriptor Entries (DJDEs) Options Table 5-54. SEFMAP DJDE options and definitions Option Definition (font1, font2) Font pair, where font2 is the SEF mapping for font1. (fontm, fontn) Font pair, where fontn is the SEF mapping for fontm. UPD UPDATE Indicates that the specified font pairs change existing font mappings or appending new mappings to the current font mapping table. REP REPLACE Indicates that the specified font pairs create a new mapping table to replace the current one.
Using Dynamic Job Descriptor Entries (DJDEs) Example 2: SEFMAP=((font1,font7), (font5,font6),REP); Before the above SEF DJDE was processed, the contents of the memory font mapping table were: ((font1,font2), (font3,font4)) After this SEFMAP DJDE is processed, the contents of the memory font mapping table are: ((font1,font7), (font5,font6)) SF1FUNCTION DJDE Specifies to the third party finisher whether or not it should perform the user defined SF1 operation on the current sheet.
Using Dynamic Job Descriptor Entries (DJDEs) SF2FUNCTION DJDE Specifies to the third party finisher whether or not it should perform the user defined SF2 operation on the current sheet. SF2FUNCTION invokes the C7 signal of the electronic interface between printing system and a third party finishing device. Refer to your finishing equipment vendor device documentation for more detailed information. Type Page oriented Syntax SF2FUNCTION = {YES | NO} Options Table 5-56.
Using Dynamic Job Descriptor Entries (DJDEs) Options Table 5-57. SHIFT DJDE options and definitions Option Definition v1 value 1 An integer value in dots for the amount of shift on the simplex page or the odd (front) side of the duplex page. (Each dot is 1/300 of an inch.) The range for v1 is –75 to 75. v2 value 2 A value in dots for the amount of shift on the even (back) side of a duplex page. The range for v2 is –75 to 75. YES Specifies that a shift occurs.
Using Dynamic Job Descriptor Entries (DJDEs) Options Table 5-58. SIDE DJDE options and definitions Option Definition sideopt side option. In duplex (with no BFORM): The four sideopt options produce the following results: NUFRONT The specified logical page is positioned as the first logical page on a new sheet. BACK The specified logical page is positioned as the first logical page of the next available back.
Using Dynamic Job Descriptor Entries (DJDEs) STOCKS DJDE Identifies the stock set and its associated stock(s) to be used in a report. This stockset file (STOCKSETNAME.STK) must already have been created by a compiled JSL and must currently reside in the “lcds” resource folder on the system disk. Type Syntax Page oriented STOCKS = stocksetname Options Table 5-59. STOCKS DJDE options and definitions Option Definition stocksetname Name of the STOCKSET used in a report.
Using Dynamic Job Descriptor Entries (DJDEs) Options Table 5-60. TMODE DJDE options and definitions Option Definition width The process direction measurement that will be used to determine the pitch mode. • For normal (long edge) feeding, this is usually a measure of the short edge of the widest paper being used in the report. • For short edge feeding (SEF) this measures the long edge. Width values can range from the 7 inch equivalent to the 17 inch equivalent.
Using Dynamic Job Descriptor Entries (DJDEs) For example, if the initial TOF and BOF values are 2 for every job, a page transition occurs every time a data record is processed because the TOF and BOF have the same value. If a TOF DJDE specifying a value of 1 is processed and the page transition has already occurred, the TOF DJDE value is too late and does not take effect until the next page transition.
Using Dynamic Job Descriptor Entries (DJDEs) • When simplex mode is put into effect, as is done by use of the TRANS DJDE, the system ensures that the first simplex page printed after the DJDE is on an odd numbered page. To accomplish this, the system forces a blank back side for the last duplex page. However, if you specify TRANS=NO and DUPLEX=YES, the system ensures that the first duplex page is printed on an odd numbered page.
Using Dynamic Job Descriptor Entries (DJDEs) XSHIFT DJDE Specifies whether the image of the form and data on a page is to be shifted, and if so, by what values. This DJDE shifts the data downward (in the x direction) for short edge binding, because a long edge feed page is viewed in portrait mode. It is typically used to accommodate top drilled paper, binding, finishing, and edgemarking. Type Syntax Page oriented XSHIFT = {YES | NO | (v1, v2)} Options Table 5-64.
6. Using PDL commands for graphics Several PDL parameters are available for graphics handling. These include four OUTPUT command parameters (specified in the JDE) and six DJDEs. The following tables summarize those parameters. Table 6-1. OUTPUT command parameters and functions for graphics Option Definition OUTPUT GRAPHICS Specifies if and how graphics will be processed in current job. OUTPUT IMAGE Specifies initial scaling and positioning parameters for graphics in Batch mode.
Using PDL commands for graphics Graphics DJDEs are record oriented because they take effect immediately. For example, ALTER, CANCEL, and IMAGE may appear anywhere on the page and are applied to the page on which they occur. Page oriented DJDEs to be applied to the next page must not precede Batch mode or page interleaved graphics to be applied to the current page. Refer to the “Using Dynamic Job Descriptor Entries (DJDEs)” chapter for more information.
Using PDL commands for graphics Error handling for graphics Use the ABNORMAL ERROR parameter to specify how the system will handle error conditions involving graphics. If you specified ABNORMAL ERROR=STOP in the JSL, the DP 2000 Series EPS systems do the following when they encounter an image that is off the page: • Display an error message. • Partially print the image. • Give the operator the option to abort the job or to continue printing and have the error added to the log.
Using PDL commands for graphics Batch mode In Batch mode, the input stream contains graphics that will be imaged, one per page, with either default or specified imaging options. Batch mode graphics are processed the same as Block mode graphics. In Batch mode, only one graphic is imaged on each page (for example, forms may not be invoked in Batch mode). This feature may be invoked by the GRAPHICS parameter of the OUTPUT command.
Using PDL commands for graphics • Use of block and record constants in an appropriately structured file (type F, FB, V, or VB) containing interleaved graphics is supported. However, the actual delimiter searching is suspended while an .IMG file is being read. – For record delimiters, this means that delimiter searching is suspended from the first record of graphic data until the entire graphic has been read. Extraneous bytes at the end of the last record are ignored.
Using PDL commands for graphics Except for the graphics themselves, the input stream may contain only optional IMAGE DJDE records. When the system encounters an IMAGE DJDE record, that DJDE defines the scaling and positioning parameters for subsequent graphics. Impact of graphics on system performance Incorporating graphics in a job can have an impact on system performance at different points in the printing process. The effect varies according to the mode of graphics transfer.
Using PDL commands for graphics • No online banner page (neither header nor trailer) may include graphic references. • A JDE that is selected with the JDE DJDE or JDL DJDE may not specify GRAPHICS=NO if the current report has already processed at least one graphic. (The GRAPHICS=NO specification is ignored.) • In online Batch mode, PCC commands are ignored beginning with the BATCH=START DJDE until the BATCH=END DJDE is processed.
Using PDL commands for graphics 6-8 Using LCDS Print Description Language
A. PDL command and DJDE summary This section contains all the PDL commands, parameters, and DJDEs available for all the Xerox laser printing systems, including the FreeFlow Print Server LCDS systems. This document may be used as a quick reference for information about PDL command syntax and parameters. The following definitions describe the conventions used in this appendix. Conventions The following symbols are used in the command syntax: Table A-1.
PDL command and DJDE summary • Printing system column: Indicates the laser printing systems to which the command or parameter applies. “ALL” means that the command is applicable to all laser printing systems operating with version 3 software or higher. • Online and Offline columns: Specify the input data stream modes of operation for the printing system. A “Y” for a particular parameter means the parameter is available for that processing mode. An “N” means the parameter is not available for that mode.
PDL command and DJDE summary Table A-2.
PDL command and DJDE summary Table A-2.
PDL command and DJDE summary Table A-2.
PDL command and DJDE summary Table A-2.
PDL command and DJDE summary Table A-2.
PDL command and DJDE summary Table A-2.
PDL command and DJDE summary Table A-2.
PDL command and DJDE summary Table A-2. PDL commands and DJDEs (Continued) Offline Online DJDE orientation Command Parameters Default Printing system OUTPUT (continued) IDFAULT First ink in ILIST parameter 4850, 4890, DP92C LPS, DP EPS (prints black), DT128/155/ 180 HLC Y Y Page IDR DFIDR.
PDL command and DJDE summary Table A-2.
PDL command and DJDE summary Table A-2. PDL commands and DJDEs (Continued) Online DJDE orientation Command Parameters Default Printing system Offline ac:PCC ADVTAPE YES All Y N — ASSIGN — All Y N — DEFAULT DEFAULT All Y N — INITIAL TOF All Y N — MASK X’FF’ All Y N — BEGIN .18 IN, .
PDL command and DJDE summary Table A-2.
PDL command and DJDE summary Table A-2.
PDL command and DJDE summary Table A-2.
PDL command and DJDE summary A-16 Using LCDS Print Description Language
B. PDL command quick reference This section provides a quick reference for PDL commands, in the form of structure diagrams. The commands shown here are supported on some or all of the following laser printing systems: DP180 LPS, DP96 LPS, 4050 LPS, 4090 LPS, 4135 LPS, 4635 LPS, 4850 LPS, 4890 LPS, DP92C LPS, 8790 LPS, 9790 LPS, and DP 2000 Series EPS. Refer to Appendix A, “PDL command and DJDE summary,” for information on which printing systems support each command and parameter.
PDL command quick reference • Syntax column: Beside each command in the Command column, lists the command parameters in alphabetical order and gives the syntax for each parameter. • Default column: Gives the default option for each parameter. PDL command Quick Reference table Table B-2.
PDL command quick reference Table B-2.
PDL command quick reference Table B-2.
PDL command quick reference Table B-2.
PDL command quick reference Table B-2. PDL command quick reference table (Continued) Command Syntax Default OUTPUT OUTPUT BFORM = {formid | (formid [, init | [, copies]] [, INK[S], inkref1 [, inkref2] ...)} NONE OUTPUT BINDING = {LONG | SHORT} LONG OUTPUT COLLATE = {YES | NO} YES OUTPUT COPIES = number 1 OUTPUT COVER = coveropt NONE OUTPUT CYCLEFORMS = {formid [, formid],...) | (formid [,(INK[S], inkref [, inkref],...)]) | ([, formid[INK[S], inkref [, inkref] [,...
PDL command quick reference Table B-2.
PDL command quick reference Table B-2. PDL command quick reference table (Continued) Command Syntax Default ac:PDE ac:PDE BEGIN = (vpos, hpos) .18 IN, .66 IN ac:PDE FONTS = {(f1 [,f2] [, ...]) | ((f1, s1) [, (f2, s2)] [, ...]) | ((f1, s1 [{lpi | XDOTS | DOTS}]) [, (f2, s2 ) [{lpi | XDOTS | DOTS}])] [,...
PDL command quick reference Table B-2. PDL command quick reference table (Continued) Command Syntax Default RSTACK RSTACK ACCTINFO = (offset, length) — RSTACK DELIMITER = {YES | NO} NO RSTACK HRPTNA = {(offset, length) | NONE} NONE RSTACK PRINT = {BIN | BOTH | TRAY | NONE} NONE RSTACK TEST = testexp — RSUSPEND BEGIN = {CURRENT | NEXT} NEXT RSUSPEND TEST = testexp — SAVE (DJDE only) SAVE = {(filename [, ...
PDL command quick reference Table B-2.
C.
Character code assignments IBM BCD code set Table C-1. IBM BCD code set Most significant bits Octal (columns) 0 1 2 3 4 5 6 7 (rows) Binary 000 001 010 011 100 101 110 111 0 000 Y – Q & H 1 001 1 9 / Z J R A I 2 010 2 0 $ B & 3 011 3 # T , L $ C . 4 100 4 @ U % M * D < 5 101 5 ‘ V _ N ) E ( 6 110 6 = W > O ; F + 7 111 7 X ? P 8 K G Honeywell/Bull 200 and 2000 BCD code set Table C-2.
Character code assignments Honeywell/Bull 6000 BCD code set Table C-3. Honeywell/Bull 6000 BCD code set Most significant bits Octal (columns) 0 1 2 3 4 5 6 7 (rows) Binary 000 001 010 011 100 101 110 111 0 000 0 8 space H ¬|^ Q + Y 1 001 1 9 A I J R / Z 2 010 2 [ B & K - S _ 3 011 3 # C .
Character code assignments UNIVAC ASCII character set Table C-5. UNIVAC ASCII character set Octal Character Octal Character Octal Character 040 blank 100 @ 140 \ 041 ! 101 A 141 a 042 “ 102 B 142 b 043 # 103 C 143 c 044 $ 104 D 144 d 045 % 105 E 145 e 046 & 106 F 146 f 047 / 107 G 147 g 050 ( 110 H 150 h 051 ) 111 I 151 i 052 * 112 J 152 j 053 + 113 K 153 k 054 , 114 L 154 l 055 - 115 M 155 m 056 .
Character code assignments Table C-5. UNIVAC ASCII character set Octal Character Octal Character Octal Character 074 < 134 \ 174 | 075 = 135 } 175 { 076 > 136 ^ 176 ~ 077 ? 137 _ 177 null Standard ASCII character set Table C-6.
Character code assignments Standard EBCDIC character set Table C-7.
Character code assignments Xerox EBCDIC to extended ASCII hexadecimal translation values Table C-8.
Character code assignments C-8 Using LCDS Print Description Language
D. Offline specifications This appendix provides specifications for tapes for offline printing. Input unpacking examples The following figure shows several input unpacking examples. Figure D-1.
Offline specifications Valid host computer and label specifications Table D-1. Valid host computer and label specifications Label specifications Host type Unlabeled ANSI ACOS4 x ANSI X Standard Burroughs medium systems: B2500 X X X B2700 X X X X X X X X X X X X B3700 B4700 Burroughs large system: B6700 DUMP FUJITSU System print COBOL Undef . Label specification is ignored. X FXEWTR GRASP POWER POWERVS Label specification is ignored.
Offline specifications Table D-1. Valid host computer and label specifications Label specifications Host type Unlabeled ANSI NEC NCR System print COBOL Undef . X X X OLDUMP Label specification is ignored. OSWTR X OCTDUMP RSX11 Standard X Label specification is ignored. X STDOUT Undef. X UNIVAC X X X US70 X X X XEROX X X X Each shaded area of this table shows the label that is substituted by PDL when an invalid host/label pair is specified.
Offline specifications Host system JDLs on system software CD Job description library (JDL) source files that are supplied on the FreeFlow Print Server software CD are summarized in the following table. Table D-2.
Offline specifications LPS tape label format LCDS resources (such as JDLs) that reside on LPS formatted tapes may be downloaded to the printing system disk from a host mainframe computer by means of . The format of the tapes that may contain these resources is shown in the following diagram. In this diagram, each rectangle represents a record that contains one or more bytes of data. The table that follows it lists the pieces of information that are contained within each record.
Offline specifications Figure D-2.
Offline specifications Table D-3. Content of tape records Byte range Information contained in record Additional information 00–02 File name If not used, must be zero. 04 File type (RAD–50) 06 File size in 512–byte blocks 10 First free byte 12 Date (DOS format) Not used 14 Record size in bytes 80 for text; otherwise, 512 16 Tape block size in bytes 20 Reserved for future use 22–32 ASCII file name (9 characters).
Offline specifications D-8 Using LCDS Print Description Language
Glossary A3 Paper size measuring 297 by 420 mm. A4 Paper size measuring 210 by 297 mm. ACT Advanced Customer Training AFP Advanced Function Printing AIM Ancillary IOT message processor. System task that initializes the client layer between the printer and the print server. It also displays the Fault, Hint, and information messages. algorithm Computational procedure that can be repeated any number of times.
Glossary background job Low-priority job, usually batched, that is executed automatically as system resources become available. batch processing Allows for repetitive operations to be performed sequentially on batched data without much involvement of the computer operator. BCD binary coded decimal binary Numbering system based on 2 that uses only the symbols 0 and 1. Binary is used in computers and related devices since information can be represented with electric pulses (0=off, 1=on).
Glossary bps bits per second. In serial communication, the instantaneous bit speed with which a device or channel transmits a character. BSC binary synchronous communication. 1. Communication using binary synchronous line discipline. 2. Uniform procedure using a standardized set of control characters and control character sequences for synchronous transmission of binary-coded data between stations. buffer Compartment of memory in which this data is stored during transfer from one device to another.
Glossary CME collate compiler copy modification entry. Entry modifying the output printing characteristics of a report on a copy-to-copy basis. To arrange or assemble into ordered sets. Software that translates instructions written in high-level language into machine language for execution by a system. concatenate To connect or link in a series, as when files are grouped together for faster processing. See also job concatenation mode.
Glossary dry ink Minute dry particles of resin and carbon black used to create images. Dry ink can accept an electrical charge.
Glossary fixed pitch Font set in which every character cell has the same width. In reference to character sets, this term describes typefaces in which all character cells are of equal width; monospaced as opposed to proportional spaced. fixed spacing Arrangement of characters on a line so that all characters occupy the same amount of horizontal space. floating accent Nonspacing accent characters that can be combined with characters and printed as a composite. form format form feed 1.
Glossary HCS high-capacity stacker. Stacker bin capable of holding 2500 sheets of 20 pound/75 gsm paper. In the LPS, the high-capacity stacker bins are located in the top half of the feeder/stacker modules. hexadecimal Numbering system with a base of 16. In this system, 10 through 15 are represented by A through F, respectively.
Glossary Interpress master I/O File written according to the Interpress standard. input/output IOM image output module IOT input output terminal, also referred to as “printer” IPD Interpress decomposer IPFONTS Interpress fonts IPL initial program load. For the optional open-reel tape drive, the internal initialization sequence whereby certain functions are loaded into random access memory (RAM).
Glossary leading 1. Vertical distance between lines (also called line space), measured from a baseline of one line to the baseline of the next. 2. Extra spacing between lines of type. 3. In typography, spacing between lines and paragraphs. LED light emitting diode. Solid substance that glows when a current is passed through it. Often used for indicator lights on disk drives or modems, as well as for displays on other electronic equipment. LEF long-edge feed.
Glossary metacode MHz MICR module MTU Same as “native mode.” Method of speaking to and controlling the image generator. These controls are used by the character dispatcher to generate scan line information. This information is sent in the form of character specifications to the image generator, which uses it to compose the bit stream that modulates the laser. megahertz. 1. Unit of cycling speed (one million cycles per second) for an electromagnetic wave (in particular, a radio wave). 2.
Glossary output overprinting 1. Material produced by a peripheral device of a computer, such as a printout or a magnetic tape. 2. Result of completed operations. Printing more than one character at the same position. overprint ratio Maximum number of variable data and form characters that may be intersected by a single scan line. page 1. In computer programming, a block of instruction, data, or both that can be located in main or auxiliary storage. 2.
Glossary ppm pages per minute PQA print quality adjustment PROM programmable read-only memory proportional font Font containing characters that vary in width. See also fixed font. proportional spacing Text in which each alphanumeric character is given a weighted amount of space. Such output has print-like appearance.
Glossary scale To adjust font or image size according to given proportions. SCSI small computer system interface. Accepted standard for connecting peripheral devices to computers. SDLC SEF sequential set simplex printing synchronous data link control short-edge feed. The movement of paper through the printer in the direction of the paper width (the shorter side of a sheet of paper). In numeric sequence, usually in ascending order.
Glossary synchronous sysgen syntax system controller Efficient encoding of data suitable for high-speed, block-oriented data transmission by using equal time elements. system generation Rules governing the structure of expressions in a programming language. Part of the system that provides interfacing capability, data handling, formatting, buffering, and operator control for the system.
Glossary TXC total xerographic convergence UCS Universal Character Set. Printer feature that permits the use of a variety of character UCSB UI UNIX Text Editor utility program validation value constants variable text VM virtual page vpos VS WAN weight x axis x dot x height Universal Character Set Buffer user interface Editing window on a UNIX workstation print server, used to code PDL commands in a JSL.
Glossary XMP xerographic mode persistence XMS xerographic mode switching XPAF, XPF Xerox Printer Access Facility XPMF-VMS Xerox Print Management Facility - VMS Version XPPI Xerox Pen Plotter Interface XPS Xerox Publishing System y axis Glossary-16 Vertical axis on a forms grid Using LCDS Print Description Language
Index Symbols # sign changing case, 1-8 Numerics 2-sided printing see duplex printing 3211, IBM emulation, 2-2 4245, IBM emulation, 2-2 A abbreviations in command syntax, 1-12 ABNORMAL command, 4-2–4-9 ACCTFEED parameter, 4-2 CODE parameter, 4-3 ERROR parameter, 4-3, 6-3 IMISMATCH parameter, 4-5 ISUBSTITUTE parameter, 4-7 OTEXT parameter, 4-7 REP parameter, 4-8 SECURITY parameter, 4-9 ac identifier, 1-5, 2-19, 2-49 accounting error sheet, 4-2 printing sheet, 4-10 specifying department, 5-24 accounting page
INDEX ADJUST parameter, 2-13 CONSTANT parameter, 2-13 FORMAT parameter, 2-14 LENGTH parameter, 2-14 LMULT parameter, 2-15 LTHFLD parameter, 2-15 OFFSET parameter, 2-16 POSTAMBLE parameter, 2-16 PREAMBLE parameter, 2-17 ZERO parameter, 2-17 Block mode (graphics), 6-3 BMULT parameter, VOLUME command, 2-56 BOF, 4-110, 4-111 BOF DJDE, 5-20 BOF parameter VFU command, 4-111 Bottom of Form see BOF, 4-110 braces, 1-14 brackets, square, 1-14 BSELECT command, 3-28–3-31 TEST parameter, 3-28 C C DJDE, 5-20 CANCEL DJDE,
INDEX abbreviations, 1-12 blank spaces, 1-12 system level identifiers, 1-21 variables, 1-7 comments, 1-29 in DJDEs, 5-20 compatibility between systems, 1-77–1-81 compiling a JSL, 1-65–1-72 constant mode, CRITERIA command, 3-10 CONSTANT parameter BLOCK command, 2-13 CME command, 4-14 CRITERIA command, 3-16–3-17 RECORD command, 2-37 TABLE command, 3-5 constants string, 1-7 value, 1-7 conventions, document, xxiv COPIES DJDE, 5-22 COPIES parameter OUTPUT command, 4-49 copy modification entries see CMEs correcti
INDEX END DJDE, 5-26 ending a DJDE, 5-2, 5-26 ending a JSL, 1-29–1-30 EOF DJDE, 5-26 EOV parameter, VOLUME command, 2-59 ERROR parameter ABNORMAL command, 4-3, 6-3 errors in JSL, correcting, 1-70–1-72 EXPAGE parameter, VOLUME command, 2-59 F FACEUP parameter OUTPUT command, 4-53 FCB interaction with VFU, 2-5 FCB parameter LINE command, 4-26 FDATA DJDE, 5-27 FDATA parameter LINE command, 4-27 FEED DJDE, 5-27 FEED parameter OUTPUT command, 4-54 feeding stock, 3-37 AUX tray, 3-33 FILE DJDE, 2-4, 5-28–5-33 fini
INDEX commands, 1-79 IDR, 4-20–4-23 commands on monochrome systems, 1-18 DJDEs, 5-42, 5-43, 5-45, 5-47, 5-60, 5-73 downloading JDLs, 1-80 forms, 1-80 parameters, 4-5, 4-7, 4-15, 4-21–4-23, 4-30, 4-58, 4-59, 4-62 highlight color jobs, 1-79–1-81 HJOBNO parameter BANNER command, 3-24, 3-27 HOST parameter VOLUME command, 2-3, 2-60 HRPTNA parameter BANNER command, 3-24, 3-27 RSTACK command, 3-56 I IBM 3211 emulation, 2-2 4245 emulation, 2-2 ICATALOG DJDE, 5-42 ICATALOG parameter IDR command, 4-21 IDEN command, 1
INDEX job recovery online, 2-3 JSL coding, 1-49–1-61 full procedure, 1-56–1-61 short procedure, 1-50–1-55 command levels, 1-18–1-28 compiling, 1-65–1-72 correcting errors, 1-70–1-72 creating hints and tips, 1-47–1-49 default, 1-53 definition, 1-2 ending, 1-12, 1-29–1-30 from other monochrome printers, 1-81 information specified in, 1-18 required elements, 1-47 sample, 1-30–1-31, 1-46, 1-48 offline, 1-63 online, 1-61, 2-6 saving a new, 1-54, 1-59 what to know before creating, 1-31–1-40 K KANJI parameter, VOL
INDEX measure, unit of defining, 4-89 MESSAGE command, 4-39–4-42 ITEXT parameter, 4-40 OTEXT parameter, 4-41 messages error, 5-5 operator, 4-7, 4-39–4-42 DJDEs, 5-5, 5-48, 5-58 MINLAB parameter, VOLUME command, 2-65 modes, CRITERIA command, 3-9–3-10 change mode, 3-10 constant mode, 3-10 value mode, 3-10 MODIFY DJDE, 5-54 MODIFY parameter OUTPUT command, 4-64 Move mode see Random mode (graphics) multiple begins, 5-9 multivolume processing, 2-10 N N to 1 printing, 4-65 name, JDL, 1-21 NTO1 parameter OUTPUT co
INDEX TRANS parameter, 4-89 UNITS parameter, 4-89 XSHIFT parameter, 4-90 output command descriptions see print format command descriptions output parameters, specifying, 1-28 OVERPRINT DJDE, 5-59 OVERPRINT parameter LINE command, 4-32 overrides specifying during printing, 1-45 overriding commands, 1-40–1-47 ozone, xvii P packed data formats, 2-9 Page Interleaved format, 6-5 page numbers specifying, 4-67, 5-55 page-oriented DJDEs, 5-10–5-12 pages logical, 1-35 physical, 1-34 system, 1-34 PALETTE DJDE, 5-60 P
INDEX multivolume reports, 2-10 online, 2-3 REP parameter ABNORMAL command, 4-8 repeat count, indicating, 1-8 report separation, 2-3 required elements of JSLs, 1-47 resources downloading, 2-4 restricting functions, 4-9 restrictions parameter changes by DJDE, 5-6 RFEED command, 3-37–3-39 TEST parameter, 3-37 RFORM DJDE, 5-61 RFORM parameter ROUTE command, 4-102 RMULT parameter, VOLUME command, 2-68 ROFFSET command, 3-39–3-42 PASSES parameter, 3-40 TEST parameter, 3-41 rollover, system multivolume reports, 2-
INDEX mismatch response, 4-79 specifying, 4-54 DJDE, 5-27 specifying size, 4-75 STOCKS DJDE, 5-70 STOCKS parameter OUTPUT command, 4-82 stockset specifying, 4-82 STOCKSET command, 1-27, 4-105–4-109 ASSIGN parameter, 4-106 INIFEED parameter, 4-107 SYSPAGE parameter, 4-107 string comparisons, 3-11 string constants, 1-7–1-10 types, 1-8 STRUCTURE parameter RECORD command, 2-41 syntax, command, 1-12–1-14 conventions, 1-14 SYSPAGE parameter STOCKSET command, 4-107 SYSPPR parameter OUTPUT command, 4-83 system leve
INDEX variables, 1-7, 1-14 VCODE parameter VOLUME command, 2-70–2-72 vertical formatting See VFU command VFU interaction with FCB, 2-5 VFU command, 1-23, 4-110–4-113 ASSIGN parameter, 4-110 BOF parameter, 4-111 TOF parameter, 4-111 VFU parameter LINE command, 4-36 VFUs specifying, 1-23, 4-110–4-113 VOLUME command, 2-54–2-72 BMULT parameter, 2-56 CODE parameter, 2-56 DBCODE parameter, 2-57 DBCS parameter, 2-58 EMTYPE parameter, 2-58 EOV parameter, 2-59 EXPAGE parameter, 2-59 HOST parameter, 2-3, 2-60 KANJI p
INDEX INDEX-12 Using LCDS Print Description Language
