Xerox DocuPrint 180 Laser Printing System Print Description Language Reference April 1998 721P85530
Xerox Corporation 701 S. Aviation Boulevard El Segundo, CA 90245 ©1998 by Xerox Corporation. All rights reserved. Copyright protection claimed includes all forms and matters of copyrightable material and information now allowed by statutory or judicial law or hereinafter granted, including without limitation, material generated from the software programs which are displayed on the screen, such as icons, screen displays, looks, etc. Printed in the United States of America.
Related publications The Xerox DocuPrint 180 Laser Printing System Print Description Language Reference is part of the ten manual reference set for your laser printing system. The entire reference set is listed in the table below. Several other related documents are also listed for your convenience.
iv XEROX DOCUPRINT 180 LPS PDL REFERENCE
Table of Contents Related publications iii Notice iii Introduction 1.
TABLE OF CONTENTS 2.
TABLE OF CONTENTS Review of PDL components and syntax 3-6 Command levels 3-6 Command components 3-6 Command identifiers 3-6 Command keywords 3-7 Command parameters 3-7 Comments 3-7 PDL syntax Hints and tips 3-8 3-9 Steps in creating a JSL 3-10 Using the Editor 3-10 Name the JDL identifier 3-10 Specifying VFUs 3-10 Setting up input parameters 3-11 Specifying LINE command parameters 3-11 Specifying ACCT command parameters 3-11 Specifying use of DJDEs 3-12 Adding logical proces
TABLE OF CONTENTS DocuPrint 180 compatibility with the 4850, 4135, 4635 and 4050/4090/4650 LPS 3-27 Xerox 4850 and 4890 HighLight Color LPS Running 4850/4890 applications on your DocuPrint 180 LPS 3-28 3-28 Downloading 4850/4890 LPS applications to your DocuPrint 180 LPS 3-29 4850/4890 HighLight Color LPS forms 3-29 Points to note 3-30 Xerox 4050/4090/4650/9700F LPS 3-30 Creating DocuPrint 180 LPS applications on a 4050, 4090, 4650, or 9700F LPS 3-30 Running 4050, 4090, 4650, and 9700F jobs on your
TABLE OF CONTENTS RECORD command ADJUST 4-19 CONSTANT 4-20 FORMAT 4-20 LENGTH 4-21 LMULT 4-21 LTHFLD 4-22 OFFSET 4-22 POSTAMBLE 4-23 PREAMBLE 4-23 STRUCTURE 4-24 Points to note 4-24 Example 4-25 SEFFNT command 4-27 Mapping files 4-28 [label:] SEFFNT SEFMAP 4-29 MAP 4-29 Points to note 4-30 Examples 4-31 TCODE command 4-32 DEFAULT 4-33 TASSIGN 4-34 TRESET 4-35 Points to note 4-36 Examples 4-37 VOLUME command XEROX DOCUPRINT 180 LPS PDL REFERENCE 4-19 4-38 B
TABLE OF CONTENTS RSAT 4-50 TCODE 4-51 UNPACK 4-52 Points to note 4-52 Examples 4-53 Input sources 4-54 Online printing systems 4-54 Channel-attached LPS 4-54 Online 3211/4245 mode Online-specific commands 4-55 Creating a JDE or JDL 4-55 DJDE processing 4-57 Online optimization 4-57 Copy-sensitive copy modification entries (CME) 4-57 Report separation 4-57 Universal character set buffers (UCSBs) 4-58 UCSB processing 4-58 Forms control buffer (FCB) 4-59 Vertical format cont
TABLE OF CONTENTS 6.
TABLE OF CONTENTS Example 1 6-22 Example 2 6-22 EXPORT command 6-23 SEPARATORS 6-24 SNUMBER 6-25 SPLIT 6-26 SRECOVER 6-27 STIMING 6-27 Points to note 6-28 Examples 6-29 LINE command 6-30 DATA 6-31 FCB 6-31 FONTINDEX 6-32 MARGIN 6-33 OVERPRINT 6-34 PCC 6-35 PCCTYPE 6-36 UCSB 6-37 VFU 6-37 Points to note 6-38 Examples 6-40 Example 1 6-40 Example 2 6-40 Example 3 6-41 MESSAGE command 6-42 ITEXT 6-43 OTEXT 6-44 BTEXT 6-45 BTEXT parameter rules 6-49 Poi
TABLE OF CONTENTS DENSITY 6-62 DESTINATION 6-62 DUPLEX 6-63 FACEUP 6-63 FEED 6-64 FORMAT 6-65 FORMS 6-66 GRAPHICS 6-67 IMAGE 6-68 INVERT 6-69 MODIFY 6-70 NTO1 6-71 NUMBER 6-72 OFFSET 6-73 OSTK 6-74 PAPERSIZE 6-75 PURGE 6-76 RESOLUTION 6-76 SF1FUNCTION 6-77 SF2FUNCTION 6-77 SHIFT 6-78 SIZING 6-79 STOCKS 6-80 SYSPPR 6-81 TMODE 6-82 TRANS 6-83 UNITS 6-83 XSHIFT 6-84 XMP 6-85 Points to note — OUTPUT command 6-86 Examples 6-96 Example 1 6-96 Exampl
TABLE OF CONTENTS PMODE 6-103 Points to note 6-104 Examples 6-105 Example 1 6-105 Example 2 6-105 Example 3 6-105 ROUTE command 6-106 Cataloged RTEXT files 6-106 RFORM 6-107 RTEXT 6-108 Example 6-109 STOCKSET command 6-110 ASSIGN 6-110 INIFEED 6-111 SYSPAGE 6-111 Points to note 6-112 Example 6-112 VFU 7.
TABLE OF CONTENTS Examples Example 1 7-9 Example 2 7-9 String comparison concepts 7-10 String comparisons 7-10 Character types 7-10 Masked comparisons using default type assignments 7-11 Masked comparisons using non-default type assignments 7-11 BANNER command 7-13 HCOUNT 7-14 HJOBNO 7-14 HRPTNA 7-15 TCOUNT 7-15 TEST 7-16 TYPE 7-16 Points to note 7-17 Examples 7-17 Example 1 7-17 Example 2 7-17 BSELECT and BDELETE commands 7-18 TEST—BSELECT and BDELETE commands 7-18
TABLE OF CONTENTS Points to note 7-27 Example 7-28 RPAGE command 7-29 SIDE 7-30 TEST 7-31 WHEN 7-31 Points to note 7-32 RSTACK command 7-35 RSTACK delimiter modes 7-35 Delimiter display 7-36 Delimiter on accounting page 7-36 Status display 7-36 Online RSTACK usage 7-36 ACCTINFO 7-37 DELIMITER 7-38 HRPTNA 7-38 PRINT 7-39 TEST 7-39 Points to note 7-40 Example 7-40 RSUSPEND and RRESUME commands 7-41 BEGIN 7-42 TEST 7-42 Points to note 7-43 Example 7-44 TABLE co
TABLE OF CONTENTS OPRINFO 8-8 PREFIX 8-8 SKIP 8-9 Points to note 8-9 DJDE record specification 8-10 Application of DJDEs 8-12 DJDE operator information pages 8-14 Job parameter modification restrictions 8-14 Duplex DJDE page printing 8-16 Effect of multiple logical pages 8-17 COPIES=processing 8-17 Online DJDE restrictions 8-18 DJDE processing optimization 8-18 DJDE parameter definitions 8-19 XEROX DOCUPRINT 180 LPS PDL REFERENCE ALTER 8-19 ASSIGN 8-20 BSEQ 8-21 BSKIP 8-
TABLE OF CONTENTS xviii FORMAT 8-42 FORMS 8-42 Points to note 8-43 GRAPHICS 8-44 IMAGE 8-46 INVERT 8-47 ITEXT 8-48 JDE 8-48 JDL 8-49 MAP 8-49 MARGIN 8-50 MODIFY 8-51 NUMBER 8-52 OTEXT 8-53 OVERPRINT 8-54 PMODE 8-55 RFORM 8-55 RTEXT 8-56 SAVE 8-57 SEFMAP 8-58 SEPARATORS 8-59 SF1FUNCTION 8-60 SF2FUNCTION 8-60 SHIFT 8-61 SIDE 8-62 SNUMBER 8-63 SPLIT 8-64 SRECOVER 8-65 STIMING 8-66 STOCKS 8-66 TMODE 8-67 TOF 8-67 TRANS 8-68 XSHIFT 8-68 Points
TABLE OF CONTENTS DJDE FILE parameter 8-72 Points to note 8-73 File effectiveness 8-73 File replacement and deletion 8-73 Card-image file processing 8-74 LPS-labeled file processing 8-75 Delimited records for LPS-labeled files 9.
TABLE OF CONTENTS A. PDL command and DJDE summary A-1 Conventions A-1 B. PDL command quick reference B-1 Conventions B-1 C. Character code assignment C-1 IBM BCD code set C-1 Honeywell 200/2000 BCD code set C-2 Honeywell 6000 BCD code set C-3 Fieldata translation C-4 UNIVAC ASCII character set C-5 Standard ASCII character set C-6 Standard EBCDIC character set C-7 Xerox EBCDIC to extended ASCII hexadecimal translation values C-8 D.
INTRODUCTION Introduction This document is part of a reference set designed to help you receive maximum benefit from your DocuPrint 180 Laser Printing System (LPS). About the reference set To help you select the appropriate document for your needs, the following section identifies the documents in the set and describes the information contained in each.
INTRODUCTION DocuPrint 180 LPS System Generation Guide DocuPrint 180 LPS Operations Reference DocuPrint 180 LPS Forms Creation Guide DocuPrint 180 LPS Operator Command Summary Card DocuPrint 180 LPS Message Guide This reference contains the following information: • • • DocuPrint 180 LPS PC UI Reference OSS software installation, upgrade, and modification • Command syntax for operator and system administrator procedures • • • • • LPS defaults LPS resources Command summaries Communication and grap
INTRODUCTION DocuPrint 180 LPS Product Reference This reference contains the following information: • • • • • Tape Formats Manual Helpful Facts About Paper LPS connections User considerations LPS comparisons Characteristics of different formats File organization Data formats Carriage control conventions This reference contains the following information: • Font naming conventions • • • Listing of standard fonts Data Sheets Glossary of typography terminology This reference contains the following i
INTRODUCTION About this manual The DocuPrint 180 Laser Printing System PDL Reference describes the print description language commands and dynamic job descriptor entries used to control the printing of jobs on the Xerox DocuPrint 180 LPS. The DocuPrint 180 Laser Printing System PDL Reference is divided into the following chapters and appendices: Chapter 1.
INTRODUCTION PDL syntax conventions used in this manual Table 1 lists the syntax conventions and their usage. Table 2. Syntax conventions Syntax convention Explanation inkref or dots Variable names or values are represented in italics. a|b|c Choices are separated by vertical bars. {a | b | c} Required choices are enclosed in braces. [a | b | c] Optional choices are enclosed in brackets. b Default options are underlined. ...
xxvi XEROX DOCUPRINT 180 LPS PDL REFERENCE
1. 1Overview This chapter provides an overview of PDL related information you will need in order to effectively utilize the PDL capabilities. PDL features and functions Print Description Language (PDL) is used to describe printing jobs to a Xerox laser printing system (LPS). PDL accomplishes this by: • • • Describing the input (type, format, characteristics) Describing the processing functions (logical processing) Describing the output (type, format, font selection, accounting options).
OVERVIEW LPS component types LPS components consist of hardware and software. Hardware Hardware refers to all the physical components of the LPS. Examples are the tape drives, the PC UI, the high-capacity feederstacker, and the physical subsystems of the system controller and the printer. Refer to your Xerox DocuPrint 180 LPS Operator Guide for detailed descriptions of the hardware components of your LPS. Software Software refers to all coded instructions (programs) which are executed by the LPS.
OVERVIEW LPS software components The LPS operating system software (OSS), housed in the system controller, runs both background and foreground processing. The major programs or “tasks” run by the system controller are shown in their hierarchical relationships in the list below.
OVERVIEW Figure 1-1 shows the relationships between these operating system software tasks which load or invoke LPS operations. Figure 1-1. Major LPS processing tasks Operating System Executive (OSEXEC) File Control Program (FCP) Operator Communication Subsystem (OSC)) Utilities Editor Diagnostics Font Editor Input FDL Processor PDL Processor Output DJD RPT Host Interface Processor (HIP) Note: DocuPrintServer (formerly XPSM) and XPAF are supported by HIP, but XNS/Enet are not supported.
OVERVIEW PDL related programs and tasks This section lists the programs and tasks most important to PDL. Operating system executive task (OSEXEC) The operating system executive (OSEXEC) task is always running. It interfaces with the LPS hardware and logs hardware errors. In addition, it queues devices, manages resources, establishes priority for software tasks, and schedules processing. File control program (FCP) The file control program (FCP) manages disk resources.
OVERVIEW Report task (RPT) The report task works in connection with the input task. It records the disk addresses of the font, form, and image files to be used for the job. The result is a page buffer and a page log for each page to be printed. The page buffer consists of the variable data and print instructions for the page. The page log consists of tracking information used in processing the page.
OVERVIEW Preparing for a print job Before a print job runs, the system administrator, programmer, operator, and LPS work together: XEROX DOCUPRINT 180 LPS PDL REFERENCE • System administrator loads fonts, logos, and signatures to the printer from tape, floppy, or the host. Refer to the DocuPrint 180 LPS Operations Reference for detailed information. • System administrator determines the fonts, forms, and graphics system parameters needed by the job.
OVERVIEW Job flow process The job flow process consists of OCS processing, Input processing, and Output processing. OCS processing The steps required during OCS processing are summarized below. Step 1. The START command identifies the JDE/JDL created by the programmer for the job. The OCS task reads the START command and notifies the OSEXEC task to load output, input, DJD, and IPD tasks. Step 2. The OCS task then writes a job queue entry (JQE) for the job in the job queue buffer.
OVERVIEW Output processing The steps required during Output processing are summarized below. Step 1. The OCS task sends a message to output indicating that output processing can start. This message includes the address in the PRFIL1.SYS file of the information for the first page to be printed. Step 2. The output task reads the starting page log buffer and builds an entry in its own page tracking buffer.
OVERVIEW Input data types The LPS can work effectively in many different environments, and it has the capability to handle input from a wide variety of sources. Whether you are using the LPS in an offline capacity, connected directly to a host computer, or remotely over phone lines, input data for printing is sent to the printer in one of two forms: • • Unformatted Formatted.
OVERVIEW — DJDE. Enables you to modify the printing environment dynamically. These commands are inserted into the input data stream to modify the command characteristics of the existing job descriptor entry (JDE). DJDEs can take effect on a report-to-report, page-to-page, and record-to-record basis. — CME. Enables you to replace certain parts of a report with predefined static data on selected copies or to specify font changes within the variable data.
OVERVIEW 1-12 XEROX DOCUPRINT 180 LPS PDL REFERENCE
2. 2Print Description Language (PDL) This chapter discusses the following PDL topics used to create and control print jobs. • • • • • Purpose of PDL PDL command structure JSL structure Creating separate command files Hierarchy of replacement Purpose of PDL For a job to be printed on an LPS, it is necessary to create a file of PDL commands to define the format of the input media, processing requirements, and the format of the printed output.
PRINT DESCRIPTION LANGUAGE (PDL) PDL command structure The primary element of a JSL is a job. A job, which is one printing task, is referred to as a job descriptor entry (JDE). (In PDL, the terms “job” and “JDE” are used interchangeably.) It usually defines one input format, one set of processing instructions, and one set of output instructions. Each job has a user-defined name that you invoke to run the job. To produce a finished job or application, a JSL must be created and then compiled into a JDL file.
PRINT DESCRIPTION LANGUAGE (PDL) In addition, there are syntax rules you must use in order for the system to recognize and process your JSLs. These rules are described later in this section. Figure 2-2. Example of PDL command components In this example, the identifier, parameter keyword, and parameter options are all part of the VFU command, which is represented by VFU, the required command keyword. All of these components may be collectively referred to as a command statement.
PRINT DESCRIPTION LANGUAGE (PDL) Parameter Each command keyword is followed by parameters used to select its processing parameters. The parameters for a PDL command keyword consist of a left and right part separated by an equal sign (=). Table 2-1 represents the typical components of a command statement and provides examples. Table 2-1.
PRINT DESCRIPTION LANGUAGE (PDL) Syntax rules When entering your JSL records on the system controller keyboard, make sure to follow these rules: • Use commas or blanks to separate the individual left- and rightpart parameters of a command. • • Use parentheses to enclose multiple right parts. List parameter options in the sequence shown in this manual. To specify a particular option but not the options preceding it, use commas or blanks as “place holders” for the options you do not specify.
PRINT DESCRIPTION LANGUAGE (PDL) Right-part constants Constants within the right part of a left/right-part parameter may be either value or string constants. The syntax of these constants is defined below. Value constants Value constants are constants that have arithmetic values. They should be expressed as decimal numbers. They may be expressed as hexadecimal values, octal values, or even character values, but these expressions are not recommended.
PRINT DESCRIPTION LANGUAGE (PDL) 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) to indicate to the PDL compiler that the following expression is in hexadecimal. For example: IDEN PREFIX=X’C1C2C3C4’; Character Normally used as string constants, but they may also be numeric value constants.
PRINT DESCRIPTION LANGUAGE (PDL) Note that EBCDIC is the default, therefore the E ’xxx’ is usually not required. Octal Octal constants should be used only as string constants because of the control program conversion process. Each octal character results in 3 bits. One word can store 3 characters. Their use as value constants, however, is not prohibited. Each 3-bit octal character is converted to an 8-bit octal character, internally, by prefixing two binary zeros.
PRINT DESCRIPTION LANGUAGE (PDL) Table 2-2 represents a JSL which includes the components of PDL commands and shows a variety of right-part constants. Table 2-2.
PRINT DESCRIPTION LANGUAGE (PDL) Job source library (JSL) structure To simplify JSL coding, PDL commands are grouped into command levels. The use and syntax of command levels, along with the required END command, are defined in the following sections: • • • • • ID level System level Catalog level Job or JDL level END command The command levels are always preceded by the JDL coding, which provides the name of the compiled JDL.
PRINT DESCRIPTION LANGUAGE (PDL) Figure 2-3 illustrates a sample JSL file format and provides examples. Figure 2-3.
PRINT DESCRIPTION LANGUAGE (PDL) ID level The ID level has commands that require identifiers so that they can be referenced by other commands in lower command levels. For example, the ID level contains one or more VFU commands, as shown in table 2-2. As with the other command levels any PDL command can be specified at the ID level. The ID level must be preceded by JDL coding, which names the JSL.
PRINT DESCRIPTION LANGUAGE (PDL) For example, to reference the catalog named POWER in a job, the job level command would be: JOB1:JDE INCLUDE=POWER; Job or JDE level The job or JDE level allows the grouping of individual jobs together. PDL commands coded within the job command level override the system commands. PDL commands from a catalog command level can be incorporated as shown in the command syntax below.
PRINT DESCRIPTION LANGUAGE (PDL) Figure 2-4.
PRINT DESCRIPTION LANGUAGE (PDL) Figure 2-5.
PRINT DESCRIPTION LANGUAGE (PDL) Creating separate files for grouping PDL commands If you have multiple commands of the same type, such as CMEs and PDEs, you may want to create separate files for them to group like specifications together and to make your JSLs shorter and more efficient. You can create these types of command files by simply listing them as you would in a JSL and complete the list with an END; command before specifying a JSL’s JDL coding identifier instead of after it.
PRINT DESCRIPTION LANGUAGE (PDL) catalog which, in turn, specifies EBCDIC in the VOLUME command CODE parameter. Figure 2-6.
PRINT DESCRIPTION LANGUAGE (PDL) • If a specified font or form file fails a validity check during input, the system aborts the job and displays the following messages: OS8852 Invalid font file header OS8855 Invalid form file header • START with parameters does not execute when HIP print jobs are being processed. • You cannot specify a tape device when you have specified DISC or FORM. Table 2-4 lists the START command parameter option(s) and definition(s). Table 2-4.
PRINT DESCRIPTION LANGUAGE (PDL) Example 1 START J12,H2SYS This command starts a print job using the H2SYS job descriptor library and the job descriptor entry J12. It runs in multiple report mode (by default) and prints the number of copies as specified in the J12 job descriptor entry. The job descriptor library, H2SYS, must reside in the JDL directory. After the START command is initiated, several messages display to inform the operator of the print jobs in progress.
PRINT DESCRIPTION LANGUAGE (PDL) Example 5 START ,ONLINE,,,FORM=GBAR This command processes online data according to the DFLT JDE in the online JDL file, using the GBAR form. Final modification can be made to job descriptor parameters through DJDE parameters in the job input data stream. These DJDE parameters are discussed in the “Specifying dynamic job descriptor entries (DJDEs)” chapter.
3. 3Creating a job source library (JSL) There are many commands available to include in your job source libraries (JSLs) and many ways of organizing them. There are relatively few absolute rules and virtually infinite combinations you can use to create applications through the use of Print Description Language (PDL).
CREATING A JOB SOURCE LIBRARY (JSL) What your JSL specified for LPS processing If your document requires forms, you code programs in form source language (FSL). You then code jobs in job source language (JSL). Your JSL files may call FRM files. If your document uses color, the PDL applications you code must include the appropriate Xerox 4850 or 4890 HighLight Color LPS ink specifications.
CREATING A JOB SOURCE LIBRARY (JSL) Decisions to make before creating your JSL Before starting to develop the JSL for your application, there are some key decisions you must make, based on your site-specific needs and the design of the application.
CREATING A JOB SOURCE LIBRARY (JSL) Output specifications You must also decide on some basic questions about the output: • • • • • • • • Will the page orientation be landscape or portrait? • • Will graphics be used? • What fonts will you use? What forms, if any, will you use? Will Segment Management be used? What paper sizes will be used? Should CMEs be used? How will the output be delivered, such as face up or collated? Will the data be printed on one side of the page (simplex) or on both sides (dup
CREATING A JOB SOURCE LIBRARY (JSL) Special features You also want to determine the following: • Will you include operator information, such as routing sheets or messages displayed on the system controller? • • • Will you select paper trays? • Will you use Dynamic Job Descriptor Entries (DJDEs) to change the application on a page or report basis? Will you allow operators to override specifications in the JSL? What structure will appear on the printed page? For example, a letter or a large form may r
CREATING A JOB SOURCE LIBRARY (JSL) Review of PDL components and syntax Before beginning the formatting of your JSL, a quick review of PDL components may be helpful. These are discussed in more detail in the “Print description language components and processes” chapter. Command levels There are four command levels: • ID level, which has commands with identifiers which must be coded in the library before they can be referenced by other commands in the other levels.
CREATING A JOB SOURCE LIBRARY (JSL) Command keywords Command keywords identify the command for which various parameters may be selected. For example, the command keyword “OUTPUT“ may be followed by any number of its parameters, such as the following: OUTPUT GRAPHICS=YES,DUPLEX=NO, FORMAT=PDFLT,FORM=BAR; Command parameters Each command keyword is followed by one or more parameters which give precise specifications for the print job or application.
CREATING A JOB SOURCE LIBRARY (JSL) PDL syntax Keep the following rules in mind when entering your PDL commands and DJDEs: 3-8 • You may abbreviate the first three letters of commands and parameters, for example, POSITION or POS, and CATALOG or CAT. The only exceptions are the OUTPUT command parameters FORMS and FORMAT. Spell these out completely. • Use a semicolon (;) at the end of a command. A comma (,) or blank space may also be used at the end of a line.
CREATING A JOB SOURCE LIBRARY (JSL) Hints and tips The following tips may help you as you create your JSL: • The only required elements in a JSL are the following: — A JDL name, which is the name of the file created by compiling the JSL — Job names — END; command at the end of the JSL. System defaults could be used for all other specifications, although typically each application has its own specific characteristics.
CREATING A JOB SOURCE LIBRARY (JSL) • You do not need to use all command levels in a JSL. Many JSLs have only ID, system, and job-level commands. • Keep in mind that the specifications to select in your JSL can be changed easily. By using the IDEN command (discussed in chapter 9, “Using graphics“) you can allow DJDEs to override PDL commands on a page-by-page or record-by-record basis.
CREATING A JOB SOURCE LIBRARY (JSL) Setting up input parameters Next, you may want to specify the input data characteristics for the application. The basic input processing commands are BLOCK, CODE, PCC, RECORD, TCODE, and VOLUME. Input processing characteristics vary depending on the data source. For example, if your JSL is for an online application, the BLOCK command is not applicable. Also, parameters within a command may apply to offline only, online only, or both.
CREATING A JOB SOURCE LIBRARY (JSL) Specifying use of DJDEs Most PDL commands can also appear in the form of DJDEs, which allow page-by-page or record-by-record modifications to your applications. In order to use DJDEs, an IDEN command must be specified in the JSL to advise the system where to look for them in the input data stream. For example: IDEN PREFIX=’C9700’, SKIP=7, OFFSET=1; Refer to the appendix “PDL/DJDE command summary,” for information on which PDL commands have DJDE counterparts.
CREATING A JOB SOURCE LIBRARY (JSL) Using copy modification entries Copy modification entries (CMEs) allow you to change report output on static data and to change fonts within variable data. Sample CMEs follow: CME1: CME2: CME CME LINE=(9,-),POS=1,FONT=1; LINE=3,POS=59, CONSTANT='FIRST QUARTER’; Defining paper requirements There are several ways of specifying paper stock in PDL. One method is the STOCKSET command, which can be referenced in lower-level commands.
CREATING A JOB SOURCE LIBRARY (JSL) Specifying output requirements There are many specifications you can select to define the manner and look of your printed application. You can also have messages displayed to operators to advise or remind them of special circumstances. This is done with the MESSAGE command: MESSAGE OTEXT=(’ALL FORMS DUPLEX ONLY!!!’,1,WAIT), ITEXT=(’COPY 2 WILL NEED BLUE PAPER’); Similarly, the ROUTE command sends printed information preceding the report to operators.
CREATING A JOB SOURCE LIBRARY (JSL) Finished JSL The following shows the JSL constructed in this section in its entirety: XRXSPL: JDL; /* ID level commands*/ VFU1: VFU VFU2UP: VFU VFU3: VFU ASSIGN=(1,11), ASSIGN=(12,66), TOF=11,BOF=66; ASSIGN=(1,(11,77)), ASSIGN=(12,(66,132)), TOF=11, BOF=132; ASSIGN=(1,1), TOF=1, BOF=132; /*System level commands*/ VOLUME HOST=IBMOS, LABEL=STANDARD, CODE=EBCDIC, PLABEL=YES; BLOCK LENGTH=2660, PREAMBLE=4, LTHFLD=2, FORMAT=BIN; RECORD LENGTH=136, PREAMBLE=4, STRUCTUR
CREATING A JOB SOURCE LIBRARY (JSL) SHIFT=YES, FORM=SMPLE, MODIFY=CME1, FORMAT=PDE1, COPIES=10, BFORM=SMLBK, OFFSET=FIRST, PURGE=NO; JOB2: JDE; LINE OUTPUT VFU=VFU2UP; FORMAT=PDE2, FORMS=SPL2, COPIES=7; END; Compiling the JSL Compiling converts the information from a job source file (JSL) into an object file (JDL). This is the command to enter at the LPS PC User Interface to compile the JSL: PDL [filename [.JDL] ] [,parameters] The file-id is the source file that contains the PDL command.
CREATING A JOB SOURCE LIBRARY (JSL) Parameters may be any combination of the parameters listed in table 3-2. Table 3-2. PDL filename parameter option(s) and definition(s) Option(s) Definition(s) NOPRINT Specifies that only source records that contain errors, the diagnostics that apply to those lines, and the PDL summary reports are printed during compilation. If there are no errors, there is no printout. The default is to print all of the above plus the PDL source records.
CREATING A JOB SOURCE LIBRARY (JSL) Printing the job Once your JDL is compiled successfully, you can have the LPS print the actual application using the START command: START jde-id,jdl-id The START command specifies the job descriptor library (JDL) and the job descriptor entry (JDE), also called the JOB for printing.
CREATING A JOB SOURCE LIBRARY (JSL) Edgemarking Edgemarking is the placement of marks along the edge of the page. These marks consist of graphic elements that bleed off the paper, tabs for section reference, or marks that denote changes made in redline drafts. Refer to your Xerox DocuPrint 180 LPS Operations Reference for detailed information on edgemarking. Non-imaged elements Elements of a page, that is, text and graphics, may begin at the edge of the physical page and may even extend off the page.
CREATING A JOB SOURCE LIBRARY (JSL) Page orientation There are two types of page orientation: • • Landscape Portrait The vertical and horizontal positions for each of these orientations is shown in figure 3-1. Figure 3-1.
CREATING A JOB SOURCE LIBRARY (JSL) Landscape orientation Figure 3-2 shows landscape orientation dimensions. Figure 3-2.
CREATING A JOB SOURCE LIBRARY (JSL) Portrait orientation Figure 3-3 shows portrait orientation dimensions. Figure 3-3.
CREATING A JOB SOURCE LIBRARY (JSL) Registration shift and skew The registration of a printed image can appear shifted or skewed on a page if the sheet of paper is misaligned as it enters the printer. Because of the design of the LPS feeder, the image registration on each page can vary slightly both horizontally and vertically by up to .05 inches/1 mm. The image can also be slanted or skewed slightly by up to .05 inches/1 mm in opposite directions, for a maximum skew of 0.1 inches/2 mm.
CREATING A JOB SOURCE LIBRARY (JSL) Figure 3-5. Portrait orientation shift and skew For best results, when designing preprinted forms, allow approximately .1 inch or 2.0 mm space on all sides of any boxes, or above and below any lines onto which variable data is to be printed, as illustrated in figure 3-6. Figure 3-6. Note: 3-24 Maintaining margins in preprinted boxes to allow for LPS registration and skew variations Enlarged for the purpose of illustration; not to scale.
CREATING A JOB SOURCE LIBRARY (JSL) Fonts A font is a character set which has a unique type style, type size, and orientation. Both fixed and proportionally spaced fonts are available for use on an LPS. Each font character occupies an area called a character cell. All character cells in a fixed font are the same width. Character cells in a proportional font vary in width. Refer to figure 3-7. Figure 3-7.
CREATING A JOB SOURCE LIBRARY (JSL) Custom fonts, signatures, and logos may be ordered from Xerox through your Xerox sales representative. Font and graphic memory The LPS can print up to 128 fonts on a single page. When processing the page data, the controller stores font, as well as graphic information in a special memory cache within the AIS. The amount of memory required to store font data depends on the size of the fonts and the number of different fonts on a single page.
CREATING A JOB SOURCE LIBRARY (JSL) DocuPrint 180 compatibility with the 4850, 4135, 4635 and 4050/4090/4650 LPS Your Xerox DocuPrint 180 LPS allows you to process Xerox 4850 HighLight Color LPS print jobs which contain ink references. The Xerox DocuPrint 180 LPS is also fully compatible with the 4135 and 4635 LPS with respect to JSL commands. The Xerox DocuPrint 180 LPS prints all 4050, 4090, 4650, and 4635 LPS applications successfully.
CREATING A JOB SOURCE LIBRARY (JSL) Xerox 4850 and 4890 HighLight Color LPS This section explains how the DocuPrint 180 LPS runs applications created for the 4850 and 4890 HighLight Color Laser Printing Systems. Running 4850/4890 applications on your DocuPrint 180 LPS If you have a Xerox 4850 or 4890 version 4.0 HighLight Color LPS, your applications probably include the use of blue, red, or green highlight color.
CREATING A JOB SOURCE LIBRARY (JSL) DJDE commands DJDE commands include the following: • • • • • • • • • • • • • • ALTER BFORM FORMS GRAPHIC ICATALOG IDFAULT IDR ILIST IMAGE INKINDEX IRESULT NUMBER PALETTE XMP For detailed information on the syntax and use of these PDL commands and DJDEs, refer to your Xerox 4850/4890 HighLight Color LPS PDL/DJDE Reference. Downloading 4850/4890 LPS applications to your DocuPrint 180 LPS You can also download color JDLs to your Xerox DocuPrint 180 LPS.
CREATING A JOB SOURCE LIBRARY (JSL) that the DocuPrint 180 LPS will not print them. If an FSL were precompiled by a 4850/4890 LPS FDL compiler and its file (FRM) downloaded to a DocuPrint 180 LPS, the form will print. Refer to your Xerox 4850/4890 HighLight Color LPS Forms Creation Guide for detailed information on creating and using highlight color forms.
4. 4Specifying input parameters Input data is processed and temporarily written to disk for subsequent printing under control of user-selected PDL commands. The input processor decodes and formats input data from an offline magnetic tape, a host-attached channel interface, or a remote communication. The general functions of input processing are described below.
SPECIFYING INPUT PARAMETERS BLOCK command Table 4-2 summarizes the BLOCK command parameters. Table 4-2.
SPECIFYING INPUT PARAMETERS CONSTANT This parameter specifies that the block delimiter constant sc and all data following it are ignored until the end of the block is reached. Syntax Options BLOCK CONSTANT = option(s) Table 4-4 lists the parameter option(s) and definition(s). Table 4-4. CONSTANT parameter option(s) and definition(s) Option(s) Definition(s) sc A string (hexadecimal, octal, or character) constant as described in the chapter "Creating a job source library (JSL).
SPECIFYING INPUT PARAMETERS LENGTH This parameter specifies the longest physical block being processed. Syntax Options BLOCK LENGTH = option(s) Table 4-6 lists the parameter option(s) and definition(s). Table 4-6. LENGTH parameter option(s) and definition(s) Option(s) Definition(s) value Specifies the length, in bytes, of the longest physical block (an integer in the range 12 to 24,576). The default is 1330.
SPECIFYING INPUT PARAMETERS LTHFLD This parameter specifies the length of the field containing the block length. Syntax Options BLOCK LTHFLD = option(s) Table 4-8 lists the parameter option(s) and definition(s). Table 4-8. LTHFLD parameter option(s) and definition(s) Option(s) Definition(s) value Specifies the length in bytes of the field containing the block LENGTH specified above. The size is an integer in the range of 0 (the default) to 5.
SPECIFYING INPUT PARAMETERS POSTAMBLE This parameter specifies the length in bytes of the extraneous data at the end of each tape block; that is, it is an offset from the end of a block backwards to the end of the last logical record. Syntax Options BLOCK POSTAMBLE = option(s) Table 4-10 lists the parameter option(s) and definition(s). Table 4-10. POSTAMBLE parameter option(s) and definition(s) Option(s) Definition(s) value An integer in the range of 0 (the default) to block length. The default is 0.
SPECIFYING INPUT PARAMETERS ZERO This parameter specifies the end of block indicator. Syntax Options BLOCK ZERO = option(s) Table 4-12 lists the parameter option(s) and definition(s). Table 4-12. ZERO parameter option(s) and definition(s) Option(s) Definition(s) YES Specifies that the end of a tape block is indicated by a value of 0 in the record length field (before applying the record length adjustment). Data that follows the record is ignored up through the end of the block.
SPECIFYING INPUT PARAMETERS will be truncated. As a result, the data will not be formatted as specified. Online versus offline JDLs An offline JDL statement set that modifies the system default values, specifically in the BLOCK or RECORD commands, may experience incorrect results if running an online job (JDE). In other words, if an online job (JDE) is called out in an offline JDL that has changed the system default values (of the BLOCK and RECORD command parameters), the job may not print correctly.
SPECIFYING INPUT PARAMETERS CODE command A CODE command is referenced by the CODE or LCODE parameters of the VOLUME command whenever a user-defined code translation table is required. An identifier label (ac:) is optional for the first CODE command within a JDE. Thereafter, each additional CODE command within the JDE must be labeled. Therefore, when multiple CODE commands are available within a JDE or JDL, only one can be unlabeled. The syntax is ac:CODE.
SPECIFYING INPUT PARAMETERS DEFAULT This parameter specifies a base code from which code assignment exceptions can be made. The base code is specified by a code-type; the exceptions are specified using the ASSIGN parameter. Syntax Options CODE DEFAULT = option(s) Table 4-15 lists the parameter option(s) and definition(s). Table 4-15.
SPECIFYING INPUT PARAMETERS Examples Following are two examples of how to use the command. Example 1 A user’s input tape is recorded in EBCDIC. On output, however, codes 5A, 5B and 5C (characters !, $, *) respectively), are assigned to the character blank (X’40’).
SPECIFYING INPUT PARAMETERS PCC command The PCC command enables the user to create a table (or modify an existing standard table) of one-byte printer carriage control codes and define their action. Line spacing, skip-to-channel, and printing actions are all defined through this parameter. The user specifies an identifier (of the type ac) when defining the PCC table and references it in the PCCTYPE parameter of the LINE command. Table 4-16 summarizes the use of the PCC command parameters. Table 4-16.
SPECIFYING INPUT PARAMETERS ASSIGN This parameter specifies printer carriage control exceptions to a default table (refer to DEFAULT parameter). Syntax Options XEROX DOCUPRINT 180 LPS PDL REFERENCE ac:PCC ASSIGN = option(s) Table 4-18 lists the parameter option(s) and definition(s).
SPECIFYING INPUT PARAMETERS Table 4-18. ASSIGN parameter option(s) and definition(s) Option(s) Definition(s) (byte,(ccln1, This option has the following components: [ccln2][,...]) • byte The printer carriage control byte being defined. Its value is in the range 0 to 255 (X00 to XFF). • ccln Specifies the action that should be taken when the printer carriage control byte defined in byte is encountered.
SPECIFYING INPUT PARAMETERS Considerations You do not have to 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, when the LINE command byte translation is specified, the PCC control byte is translated into LPS-standard EBCDIC before being applied.
SPECIFYING INPUT PARAMETERS DEFAULT This parameter allows selection of a set of printer carriage control codes. A table may be selected and then specific control codes may be modified with the ASSIGN parameters. Syntax Options ac:PCC DEFAULT = option(s) Table 4-19 lists the parameter option(s) and definition(s). Table 4-19. DEFAULT parameter option(s) and definition(s) Option(s) Definition(s) ccln Specifies the required action when a code has not been specifically assigned.
SPECIFYING INPUT PARAMETERS INITIAL This parameter specifies the initial reference point (TOF or BOF) from which a report performs its first carriage control function. Syntax Options ac:PCC INITIAL = option(s) Table 4-20 lists the parameter option(s) and definition(s). Table 4-20. INITIAL parameter option(s) and definition(s) Option(s) Definition(s) TOF Specifies the control program to perform the first spacing, skipping, or printing action from the top of form. The default is TOF.
SPECIFYING INPUT PARAMETERS Points to note Note the following when using the PCC command: • Multiple user-defined PCC tables are allowed, but only one may be used without a command identifier. The corresponding PCCTYPE parameter on the LINE command references each table through a command identifier. The keyword USER can be used to reference any user-defined PCC table for which no command identifier is coded.
SPECIFYING INPUT PARAMETERS RECORD command Table 4-22 summarizes the use of the RECORD command parameters. Table 4-22.
SPECIFYING INPUT PARAMETERS CONSTANT This parameter specifies a constant string used to signal the end of a record. This record delimiter constant string signals the end of the record, but it is not included in the print line. Syntax Options RECORD CONSTANT = option(s) Table 4-24 lists the parameter option(s) and definition(s). Table 4-24.
SPECIFYING INPUT PARAMETERS LENGTH This parameter specifies the length of the longest logical record. A value specifies the length, in bytes, of the longest logical record. Syntax Options RECORD LENGTH = option(s) Table 4-26 lists the parameter option(s) and definition(s). Table 4-26. LENGTH parameter option(s) and definition(s) Option(s) Definition(s) value An integer in the range 1 to 310 for offline (133 is the default) or 150, the online default.
SPECIFYING INPUT PARAMETERS LTHFLD This parameter specifies the length of the field containing the record length. Syntax Options RECORD LTHFLD = option(s) Table 4-28 lists the parameter option(s) and definition(s). Table 4-28. LTHFLD parameter option(s) and definition(s) Option(s) Definition(s) size Specifies, in bytes, the record length field length. It must be an integer in the range 0 to 5.
SPECIFYING INPUT PARAMETERS POSTAMBLE This parameter specifies the length of any extraneous data at the end of the record. Syntax Options RECORD POSTAMBLE = option(s) Table 4-30 lists the parameter option(s) and definition(s). Table 4-30. POSTAMBLE parameter option(s) and definition(s) Option(s) Definition(s) length Specifies the length in bytes. The length must be an integer in the range 0 (the default) to record length. The default is 0.
SPECIFYING INPUT PARAMETERS STRUCTURE This parameter specifies the general record structure of the input data. Syntax Options RECORD STRUCTURE = option(s) Table 4-32 lists the parameter option(s) and definition(s). Table 4-32.
SPECIFYING INPUT PARAMETERS For online processing, print position indexing must not be used if LENGTH greater than 150 is specified. • Online versus offline JDLs An offline JDL statement set that modifies the system default values, specifically in the BLOCK or RECORD commands, may experience incorrect results if running an online job (JDE).
SPECIFYING INPUT PARAMETERS Figure 4-3.
SPECIFYING INPUT PARAMETERS SEFFNT command Paper is fed from the short edge to allow for printing on large size paper. This is called short-edge feed (SEF). In order to maintain the current definition of landscape and portrait in these jobs, a mapping must be defined in which every landscape font used in a SEF job has a portrait equivalent and vice versa. Table 4-33 summarizes the use of the SEFFNT command parameters. Table 4-33.
SPECIFYING INPUT PARAMETERS Mapping files A font mapping associates one font to another font. A collection of font mappings may be stored in a mapping file. Font files are files having the FNT extension and are stored on disk. The SEFFNT command is used to enable or disable the short-edge feed feature. SEFFNT creates customized mapping files (of type LIB) or triggers the system to invoke short-edge feed processing. It must be used in conjunction with a PDE.
SPECIFYING INPUT PARAMETERS [label:] SEFFNT SEFMAP When coded outside of a standard JSL (either prior to a JDL command or after an END command), a file containing the font mappings by the name of label.LIB is created on a disk for reference within the JSL by other JSLs or through a DJDE. When specified without a label preceding the SEFFNT command, this SEFMAP parameter puts all font mapping definitions within the JSL, rather than creating a separate mapping file.
SPECIFYING INPUT PARAMETERS Points to note Note the following when using the SEFFNT command: • When the system recognizes a SEF job, it scans the PDE font list and substitutes them with font mappings defined in the JSL. If you specify that font mappings are contained in a file, the input task checks to see if this file exists. If the mapping file or the font file does not exist, job processing continues using the font specified in the PDE command.
SPECIFYING INPUT PARAMETERS Examples Following are a few examples of how to use the command. Example 1 FNTMAP:SEFFNT SEFMAP=(L0112B,P0612A); SYS1:SYSTEM; VOLUME `CODE’=ASCII; FNTMAP.LIB is created on system disk. Example 2 SEFFNT SEFMAP=(L0114B,P0614A); PDE1: PDE FONT=L0114B,PMODE=LANDSCAPE, BEGIN=(.50,.50); Example 3 JOB1: JOB; OUTPUT FORMAT=PDE1; Job 1 uses the SEFFNT command in example 2 because there is no override specified.
SPECIFYING INPUT PARAMETERS TCODE command The TCODE command defines a set of input-character-to-type assignments to be used for the masked string comparisons in a report. It must be used whenever it is not possible to use one of the standard sets of default type assignments without modification. Table 4-37 summarizes the use of the TCODE command parameters. Table 4-37.
SPECIFYING INPUT PARAMETERS DEFAULT This parameter specifies an initial set of character type assignments for use with masked comparisons. Default assignments for any standard character set may be specified by coding the appropriate keyword. Syntax Options TCODE DEFAULT = option(s) Table 4-38 lists the parameter option(s) and definition(s). Table 4-38.
SPECIFYING INPUT PARAMETERS TASSIGN This parameter associates one or more specified characters with one or more specified typecodes. This parameter may also be used to disassociate one or more characters from all typecode assignments. The TASSIGN parameter may be specified more than once in a TCODE command. Syntax Options TCODE TASSIGN = option(s) Table 4-39 lists the parameter option(s) and definition(s). Table 4-39.
SPECIFYING INPUT PARAMETERS TRESET This parameter disassociates one or more characters (or all characters) in a set from one or more types. Syntax Options TCODE TRESET = option(s) Table 4-40 lists the parameter option(s) and definition(s). Table 4-40. TRESET parameter option(s) and definition(s) Option(s) Definition(s) typespec,’inputspec’) (’inputspec1’,[’inputspec2’], [...
SPECIFYING INPUT PARAMETERS Points to note Note the following when using the TCODE command: • The LPS accepts lowercase characters expressed literally or symbolically, that is, preceded by the pound sign ( # ) functioning as a switch case operator. • A hyphen (-) specifies the range of contiguous characters (as in the examples below), where the contiguity is based upon actual codes.
SPECIFYING INPUT PARAMETERS Examples Following are a few examples of how to use the command. Example 1 Basic character set used for default types is ASCII. Operator’s keyboard display has uppercase and lowercase character capability: T1: TCODE DEFAULT=ASCII, TASSIGN=(3, (A ’A’, - ,A ’Z’)), TASSIGN=(4, (A ’a’, - ,A ’z’)); Example 2 Basic character set used for default types is EBCDIC.
SPECIFYING INPUT PARAMETERS VOLUME command Table 4-42 summarizes the VOLUME command parameters. Table 4-42.
SPECIFYING INPUT PARAMETERS BMULT This parameter specifies a multiplication factor you can use to determine true block length. Syntax Options VOLUME BMULT = option(s) Table 4-43 lists the parameter option(s) and definition(s). Table 4-43. BMULT parameter option(s) and definition(s) Option(s) Definition(s) value Specifies a multiplication factor that you extract from the tape label and apply to the block length to determine the true block length.
SPECIFYING INPUT PARAMETERS Table 4-44. CODE parameter option(s) and definition(s) Option(s) Definition(s) keyword Specifies a specific, standard, system-defined code translation table. The available options are: • • • • • • • • • ASCII BCD EBCDIC H2BCD H6BCD IBMBCD PEBCDIC NONE USER USER refers to the single unlabeled CODE command defined within the JDE or JDL. If you specify more than one CODE parameter, use identifiers so that they can be referenced in your JSL.
SPECIFYING INPUT PARAMETERS EOV This parameter specifies the action the system takes when it encounters an end-of-volume (EOV) on the input data tape. Syntax Options VOLUME EOV = option(s) Table 4-45 lists the parameter option(s) and definition(s). Table 4-45. EOV parameter option(s) and definition(s) Option(s) Definition(s) ([PAUSE | NOPAUSE], [EOF | NOEOF]) This option has the following components: • PAUSE Displays a message when EOV is encountered.
SPECIFYING INPUT PARAMETERS Table 4-46. HOST parameter option(s) and definition(s) Option(s) Definition(s) host-type Specifies one of the following options: • • • • • • • • • • • • • • • • • • • • • • • • • • • • IBMOS ANSI B2500 B2700 B3500 B3700 B4700 B6700 DEC PDP11 DUMP GRASP H2000 H6000 IBMDOS IBMONL ICL2900 NCR OCTDUMP OLDUMP OSWTR POWER POWERVS RSX11 UNDEF UNIVAC 1100 US70 XEROX The default is IBMOS. Considerations For online systems, you must specify IBMONL or OLDUMP.
SPECIFYING INPUT PARAMETERS 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. Refer to the “Offline specifications“ appendix for more information on offline formats. If an online job (JDE) is called out in an offline JDL that changed the system default values, the job may print incorrectly.
SPECIFYING INPUT PARAMETERS LCODE This parameter specifies the code translation table to use in interpreting the tape label. Syntax Options VOLUME LCODE = option(s) Table 4-47 lists the parameter option(s) and definition(s). Table 4-47. LCODE parameter option(s) and definition(s) Option(s) Definition(s) keyword Specifies a specific, standard, system-defined code translation table.
SPECIFYING INPUT PARAMETERS LPACK This parameter specifies whether undefined labels (LABEL=UNDEF) are packed or unpacked. Syntax Options VOLUME LPACK = option(s) Table 4-48 lists the parameter option(s) and definition(s). Table 4-48. LPACK parameter option(s) and definition(s) Option(s) Definition(s) NO Indicates that no unpacking operation is to be performed. If YES is specified, the UNPACK parameters specify the required unpacking method for both the labels and the input data.
SPECIFYING INPUT PARAMETERS MINLAB This parameter specifies the smallest physical block to treat as a label for undefined labels (LABEL=UNDEF). Syntax Options VOLUME MINLAB = option(s) Table 4-50 lists the parameter option(s) and definition(s). Table 4-50. MINLAB parameter option(s) and definition(s) Option(s) Definition(s) value Specifies in bytes the maximum length of the smallest physical block. The value can range from 1 to 4095 bytes.
SPECIFYING INPUT PARAMETERS OPTIMIZE This parameter enhances the performance of the data stream. Syntax Options VOLUME OPTIMIZE = option(s) Table 4-51 lists the parameter option(s) and definition(s). Table 4-51. OPTIMIZE parameter option(s) and definition(s) Option(s) Definition(s) keyword Specifies one of the following options: • NCCHECK Disables channel 9 and channel 12 detection. The host is not notified by the LPS each time channel 9 or 12 is recognized when this option is selected.
SPECIFYING INPUT PARAMETERS OSCHN This parameter specifies the channel the system uses to signal the end of a report generated by an IBM OS Writer. Syntax Options VOLUME OSCHN = option(s) Table 4-52 lists the parameter option(s) and definition(s). Table 4-52. OSCHN parameter option(s) and definition(s) Option(s) Definition(s) value Specifies the vertical format unit (VFU) channel the system uses to signal the end of a report.
SPECIFYING INPUT PARAMETERS OSTLP This parameter specifies the number of trailer banner pages generated by an IBM OS Writer. Syntax Options VOLUME OSTLP = option(s) Table 4-54 lists the parameter option(s) and definition(s). Table 4-54. OSTLP parameter option(s) and definition(s) Option(s) Definition(s) value Specifies the number of trailer pages which precede the report. The default is 0. PLABEL This parameter specifies whether the tape labels are printed.
SPECIFYING INPUT PARAMETERS RMULT This parameter specifies a multiplication factor the record length uses to determine the true record length. Syntax Options VOLUME RMULT = option(s) Table 4-56 lists the parameter option(s) and definition(s). Table 4-56. RMULT parameter option(s) and definition(s) Option(s) Definition(s) value An integer from 1 to 15. The default is 1.
SPECIFYING INPUT PARAMETERS TCODE This parameter specifies the set of type assignments to use for masked comparisons. Syntax Options VOLUME TCODE = option(s) Table 4-58 lists the parameter option(s) and definition(s). Table 4-58.
SPECIFYING INPUT PARAMETERS UNPACK This parameter specifies the unpacking method of the input data when required. Syntax Options VOLUME UNPACK = option(s) Table 4-59 lists the parameter option(s) and definition(s). Table 4-59. UNPACK parameter option(s) and definition(s) Option(s) Definition(s) NONE Does not perform the unpacking operation. The default is NONE. T4X3 or T4X3H2 Specifies unpacking routines in which 6-bit characters are extracted and restored as 8-bit bytes.
SPECIFYING INPUT PARAMETERS Table 4-60 lists the components of this example and their definitions. Table 4-60. Example components and definitions Component Definition m Positive decimal number of the form nnn.dd (up to two digits to the right of the decimal point) V2 Even (back) side shift value in inches BEGIN Scan line in inches as specified in the PDE (hpos in portrait, vpos in landscape) ALI Anticipated scan alignment (estimated inches equivalent, 3 scans=.01 in.
SPECIFYING INPUT PARAMETERS Input sources Data to be processed by the printing system may originate from several sources. These sources are magnetic tape (offline processing), a host computer (online processing in 3211 and 4245, XPAF, or XPMF-VMS modes or communication through the Ethernet). For information on XPAF, refer to Printing Documents with XPAF User Reference. For information on XPMF-VMS, refer to the Xerox Print Management Facility—VMS version User Guide.
SPECIFYING INPUT PARAMETERS Online-specific commands This section explains how to create a JDE or JDL, DJDE processing, online optimization and copy-sensitive copy modification entries (CME). Creating a JDE or JDL An online job descriptor library (JDL) and its job descriptor entries (JDEs) are created by the user according to the same rules and syntax as other entries. The one PDL command that must be specified for normal online processing is VOLUME HOST=IBMONL.
SPECIFYING INPUT PARAMETERS Figure 4-4.
SPECIFYING INPUT PARAMETERS DJDE processing Printing is controlled through parameters from the user-defined JDE file which may be dynamically modified by dynamic job descriptor entries. DJDEs are user created and are processed by the LPS as part of the print data from the host machine. The chapter “Specifying dynamic job descriptor entries (DJDEs)” defines their format and the PDL statements necessary to let the system know they are part of the input data.
SPECIFYING INPUT PARAMETERS Universal character set buffers (UCSBs) The IBM 3211/4245 universal character set buffer (UCSB) feature is supported by the LPS. The UCSB is used by the LPS software as a basis for generation of folded and unfolded translate tables. In a folded translate table, uppercase characters are substituted for only those lowercase characters which are defined as unprintable in the UCSB.
SPECIFYING INPUT PARAMETERS Forms control buffer (FCB) The 3211/4245 forms control buffer (FCB) defines channel positions and forms length. Online users may restrict the forms control buffer information by accepting or suppressing the normal processing of host-transmitted FCB input. This can be accomplished by the FCB=IGNORE parameter of the LINE command.
SPECIFYING INPUT PARAMETERS Online record length The default record length supported by the Xerox laser printing systems is 150 bytes, the same default as the 3211/4245 printer. However, the you can choose to use larger record lengths with the following restrictions: • For print record lengths from 151 bytes to 214 bytes, do not use the print position indexing feature that is normally available on the IBM 3211/4245.
SPECIFYING INPUT PARAMETERS Online recovery In the event of a system failure, data that is formatted for print and stored on disk can be imaged upon system restart if job recovery is requested. Data which was being received and processed at the time of the rollover is lost and requires retransmission. The amount of data which requires retransmission depends on two factors: • The options specified in the VOLUME command OPTIMIZE parameter and DJDEs that indicate the use of interleaved graphics.
SPECIFYING INPUT PARAMETERS Online dump The online dump feature allows you to generate a hard copy of the command and data transmission taking place between the host computer and the LPS. Starting and ending dump sessions The dump session is started with a START command when the LPS is online and in the idle state. The online dump JDE/JDL used must specify VOLUME HOST=OLDUMP and CODE=EBCDIC. The dump session is terminated by either the operator ENDJOB command or the offline operator command.
SPECIFYING INPUT PARAMETERS • NO-OP command from the host is not dumped since it is intercepted and processed by the OLI hardware and is transparent to the LPS software. • Hardware errors are reported in the system error log, but are not dumped due to Host, OLI, or driver interface constraints. • Commands processed when input is stopped, for example, when paper trays become empty, are not dumped. • Print records longer than the specified RECORD LENGTH value are truncated without warning.
SPECIFYING INPUT PARAMETERS Valid download file types Files may be downloaded in two formats: card-image files and LPSlabeled files. Certain destination file types are not accepted for either LPS-labeled or card-image files. These are file types OSD, SAF, SYS, $Y$, and TSK. In addition, card-image format files are restricted to destination file types CMD, FSL, JSL, MSC, PCH, TMP, and TPF.
SPECIFYING INPUT PARAMETERS Offline mode For offline operations, the input medium to the printing system is magnetic tape, which may be recorded in one of a variety of standard vendor formats. As a programmer, you define the tape input deblocking and record format parameters that reduce physical tape blocks first to logical records, then to print lines.
SPECIFYING INPUT PARAMETERS Packed data formats Six-bit characters may be written onto a 9-track tape in a 4-by-3 packed (or compressed) format. That is, four 6-bit data bytes are compressed into three 8-bit data bytes. Two methods of packing these bits together exist. One method is used by Honeywell 6000 users (T4X3), while Honeywell 2000 users employ a slightly different method of packing (T4X3H2).
SPECIFYING INPUT PARAMETERS Multivolume processing All multivolume reports that force input to make multiple passes over the data are handled in the following manner. For each copy requested, a complete pass is made over the group of volumes that make up the current report. The input processor is forced to make multiple passes over the input data for multicopy reports that specify copy-sensitive CMEs, and (optionally) for multicopy reports that exceed the size of the print file.
SPECIFYING INPUT PARAMETERS 4-68 XEROX DOCUPRINT 180 LPS PDL REFERENCE
5. 5Defining clusters The DocuPrint 180 LPS provides several methods for feeding paper. There are internal trays (trays 1-3) and a bulk input enablement (tray 7). Each of the input source trays can be addressed and used individually. They can also be addressed in groups, such as pairs, or groups of three and used in groups as clusters. Cluster features Clusters are a systematic method provided for feeding specific paper stock to print jobs.
DEFINING CLUSTERS What clusters do for the programmer and operator As the programmer, you group any combination of trays into a cluster. Group the trays together because they hold the same stock or they hold stock which differs only in size. You can specify the cluster’s paper stock by any combination of weight, color, size, and so on.
DEFINING CLUSTERS • Do not, however, use FEED=MAIN and FEED=AUX in conjunction with stocksets. • You must use the FEED=MAIN operator command at the start of a job if the data stream is controlling trays, cluster information, and so on. • You cannot edit CLUSTR.LIB. It is automatically updated by the CLU and CLP commands which enter clusters in the database or modify cluster definitions.
DEFINING CLUSTERS Stockset applications Each page has a particular stockset and a particular cluster associated with it. The cluster is always verified because it determines from which trays a page may feed. The stockset is verified only if the current page calls a different stockset than the previous page called. Stockset changes require the cluster checks described in table 5-1. Table 5-1.
DEFINING CLUSTERS Defining clusters and stocksets with PDL and DJDE The PDL commands and DJDEs listed here relate to clusters. For more detailed information on each command, refer to the chapters “Specifying output parameters” and “Specifying dynamic job descriptor entries (DJDEs).” PDL commands The STOCKSET and OUTPUT commands specify cluster and stocks in your JSLs. The STOCKSET and OUTPUT commands and their syntax are shown in tables 5-2 and 5-3. Table 5-2.
DEFINING CLUSTERS Points to note Note the following when defining clusters and stocksets with PDL and DJDE commands: 5-6 • Assign each cluster a unique logical name which begins with a letter and consists of 1 to 6 alphanumeric characters. Make certain that the cluster name is not a keyword, parameter, or option used by the LPS. Group the clusters used by each application into a stockset. • Stocksets convert cluster references to cluster names. (Cluster references are recommended but are not required.
DEFINING CLUSTERS Steps for creating clusters The steps you should take to create a cluster are listed below. Figure 5-1 provides a visual representation of these steps. Figure 5-1. Steps for creating clusters Follow these steps: Step 1. Determine the stocks the application will use. Step 2. Create a JSL file and compile it to produce an STK file: Define a logical mnemonic name (a cluster reference) for each stock (for instance, COVER in the example below).
DEFINING CLUSTERS Step 4. Use the FEED= DJDE in the JSL file to specify the cluster to be used. For example: ... ...data for cover letter... DJDE FEED=BILPAG,END; ...data for bill... DJDE FEED=SUMMRY,END; ...data for summary sheet (and in the JSL) OUTPUT STOCKS=BILLS, FEED=COVER; Note: The specified cluster must be identified in the active stockset. If clusters are used in the print job, the OUTPUT command requires the STOCKS= parameter; the FEED= parameter is optional.
DEFINING CLUSTERS Keeping stockset changes to a minimum Each formatted page is associated with the active stockset and the active FEED= option stock identified by the INIFEED parameter of the STOCKSET command, the FEED parameter of the OUTPUT command, or the FEED DJDE. A stockset change causes the LPS output task to make additional checks when a page is to be printed. These checks can result in a printer cycle down if any cluster in the new stockset presents a tray overlap or sizing problem.
DEFINING CLUSTERS 5-10 XEROX DOCUPRINT 180 LPS PDL REFERENCE
6. 6Print format commands Print format commands serve many different functions, the most common of which specify the physical characteristics of a print job, define the placement of data on the page, and identify system responses to error conditions. Table 6-1 summarizes these PDL commands. The function, syntax, and usage of the parameters available with these commands are described in individual sections of this chapter. Table 6-1.
PRINT FORMAT COMMANDS ABNORMAL command The ABNORMAL command allows you to restrict certain operator functions and define system responses to error conditions Table 6-2 summarizes ABNORMAL command parameter functions. Table 6-2 summarizes the ABNORMAL command parameters. Table 6-2.
PRINT FORMAT COMMANDS ERROR This parameter specifies the required system response to abnormal conditions detected in input while processing or compiling DJDEs. Syntax Options ABNORMAL ERROR = option(s) Table 6-3 lists the parameter option(s) and definition(s). Table 6-3.
PRINT FORMAT COMMANDS designated black-only calls for the green primary and the ink currently loaded in the printer is red. Syntax Options ABNORMAL IMISMATCH = option(s) Table 6-4 lists the parameter option(s) and definition(s). Table 6-4. IMISMATCH parameter option(s) and definition(s) Option(s) Definition(s) STOP Prompts the operator to load the requested primary or abort the report or job.
PRINT FORMAT COMMANDS ISUBSTITUTE This parameter specifies whether operator-initiated ink substitution is allowed. Syntax Options ABNORMAL ISUBSTITUTE = option(s) Table 6-5 lists the parameter option(s) and definition(s). Table 6-5. ISUBSTITUTE parameter option(s) and definition(s) Option(s) Definition(s) ANY Any operator-initiated substitution is allowed. This is the default. The default is ANY. NONE Example Considerations No operator-initiated substitution is allowed.
PRINT FORMAT COMMANDS OTEXT This parameter specifies that the system is to stop and display a WAIT message when the recovery marker page is printed. This delay allows the operator to verify the output report in the near vicinity of the marker page. The default is NOWAIT, which means that the message is still displayed upon printing of the marker page, but printing does not stop. Syntax Options ABNORMAL OTEXT = option(s) Table 6-6 lists the parameter option(s) and definition(s). Table 6-6.
PRINT FORMAT COMMANDS REP This parameter specifies that the first data page delivered to the bin following a printer jam recovery or a system crash may be offset from the rest of the report. Syntax Options ABNORMAL REP = option(s) Table 6-8 lists the parameter option(s) and definition(s). Table 6-8. REP parameter option(s) and definition(s) Option(s) Definition(s) NO Specifies that the page will not be offset. YES Specifies that the page will be offset.
PRINT FORMAT COMMANDS operator assistance is requested, that is, the operator or user is requested to mount a preceding tape volume (offline) or return to point of origin or last valid checkpoint (online). Marker page The system produces a marker page (refer to figure 6-1) as a function of the input processor and inserts it into the print job at the point of crash. It is printed after the output processor has printed data that was already processed by input before the crash occurred.
PRINT FORMAT COMMANDS Figure 6-1.
PRINT FORMAT COMMANDS ACCT command The system maintains report processing information in two files which are accessible to the user. Both files can be saved on tape or transmitted to the host through the host file transfer facility for further processing. One method accumulates overall usage statistics on a department or JDL basis. Refer to your Xerox DocuPrint 180 LPS Operations Reference for further information on the accounting file printout, initialization, and structure.
PRINT FORMAT COMMANDS name only once with the ACCOUNT parameter, but it must be done before a print job is run using the DEPT name. If the name is not entered with the ACCOUNT parameter, the accounting data for this report is accumulated in the NODEPT entry in the accounting log. However, the DEPARTMENT entry on the accounting page for this report lists the requested department name followed by an asterisk to denote that no specific accounting by this name was performed.
PRINT FORMAT COMMANDS Figure 6-2.
PRINT FORMAT COMMANDS Figure 6-3.
PRINT FORMAT COMMANDS DEPT This parameter defines the name under which accounting statistics should be accumulated for this report job. Syntax Options ACCT DEPT = option(s) Table 6-11 lists the parameter option(s) and definition(s). Table 6-11. DEPT parameter option(s) and definition(s) Option(s) Definition(s) sc A string constant of up to 31 characters representing a department code or name under which accounting information is maintained.
PRINT FORMAT COMMANDS Points to note Note the following when using the ACCT command: • If the report completion code on the accounting page is nonzero, an accounting page is delivered to the tray even if USER=NONE is coded. This is done to notify the user of a possible report integrity problem. However, if the report is duplex and the first integrity problem occurs within the last eight back sides, the report completion code on the forced accounting page is zero.
PRINT FORMAT COMMANDS ac:CME command The copy modification feature (also referred to as spot-carbon) allows certain parts of report output to be replaced on selected copies with predefined static data or to specify font changes within the variable data. CMEs define a rectangular space on the printed page within which printed data is replaced with a substitution string or in which a font change occurs. More than one CME may be applied to a job.
PRINT FORMAT COMMANDS Cataloged CMEs CMEs need not be part of a user’s JDL. They may be created as separate disk files and used as if they were part of the JDL that references them. This is done by creating a JSL file containing only CMEs and using the PDL processor to compile it. For each CME, PDL creates an object file on disk, cataloged in the CME directory. The CME identifier is used as the object file name.
PRINT FORMAT COMMANDS FONTS This parameter specifies an index into the font list (PDE command or DJDE) for font switching on input data or CME data. A PDE command is selected by the FORMAT parameter of the OUTPUT command. Syntax Options ac:CME FONTS = option(s) Table 6-15 lists the parameter option(s) and definition(s). Table 6-15.
PRINT FORMAT COMMANDS LINE This parameter specifies the line range of the CME. Syntax Options ac:CME LINE = option(s) Table 6-16 lists the parameter option(s) and definition(s). Table 6-16. LINE parameter option(s) and definition(s) Option(s) Definition(s) {n | (n,m) | (n,-)} This option has the following components: • n The initial line number of the copy modification rectangle • m The number of lines to repeat the information. If not specified, the information applies only to the starting line.
PRINT FORMAT COMMANDS POSITION This parameter specifies the initial character position of the CME in the print line. Syntax Options ac:CME POSITION = option(s) Table 6-17 lists the parameter option(s) and definition(s). Table 6-17. POSITION parameter option(s) and definition(s) Option(s) Definition(s) n An integer value between 1 (the first position of the print line) and the value specified by the length rightpart of the DATA= parameter in the LINE command. The default is 1.
PRINT FORMAT COMMANDS LINE=(11,20),POS=1,FONT=3,POS=40,FONT=1,POS=80 ,FONT=2, LINE=(31,50),POS=1,FONT=2,POS=40,FONT=3,POS=80 ,FONT=1; • Form and variable data Under certain circumstances, a form and its associated variable data do not align properly, even though it appears that both use the same line spacing. Variable data has a line-spacing value that is computed as dots per line, and rounding is done on that value.
PRINT FORMAT COMMANDS Examples This section shows two examples of using the CME command. Example 1 The following is an example of copy-sensitive CMEs. CME1: CME LINE=3,POS=59,CONSTANT=’FIRST QUARTER’; CME2: CME LINE=(37,3),POS=81,CONSTANT=(6)’*’; CME3: CME LINE=(1,60),POS=5,FONT=2,POS=12,FONT=1; OUTPUT COPIES=3,MODIFY=(CME1,1,1), MODIFY=(CME2,2,1),MODIFY=(CME3,3,1); For the first copy of the report, line 3 is modified by the text ’FIRST QUARTER’.
PRINT FORMAT COMMANDS EXPORT command A “segment” is a set of consecutively delivered sheets whose management as a set or segment has been specified by PDL or DJDE command. The EXPORT statement enables specification in PDL of the new Segment Management capabilities, including the following: • • • • Division of reports into segments Generation of separator sheets Use of segment numbers on separator sheets Use of segment recovery in place of page recovery.
PRINT FORMAT COMMANDS SEPARATORS This parameter specifies that the printer software save an internal copy of the first data page of the report and use it to generate segment separator sheets. Syntax Options EXPORT SEPARATORS = option(s) Table 6-19 lists the parameter option(s) and definition(s). Table 6-19.
PRINT FORMAT COMMANDS SNUMBER This parameter specifies that the printer merge the current segment sequence number (beginning with 001) into any separator sheets produced. The format of the printed segment sequence number for all separators except a LAST separator in the last segment is: PART nnn (8 characters). nnn is a three digit number with leading zeros. The format for the LAST separator in the last segment is: PART nnn of nnn (15 characters).
PRINT FORMAT COMMANDS SPLIT This parameter specifies the use of segment management, and is required in order for the other EXPORT parameters to work. Syntax Options EXPORT SPLIT = option(s) Table 6-21 lists the parameter option(s) and definition(s). Table 6-21. SPLIT parameter option(s) and definition(s) Option(s) Definition(s) (min, max) Specifies the minimum and maximum numbers of sheets, including any separator sheets, allowed in a segment.
PRINT FORMAT COMMANDS SRECOVER This parameter specifies the mode of jam, or error, recovery. Syntax Options EXPORT SRECOVER = option(s) Table 6-22 lists the parameter option(s) and definition(s). Table 6-22. SRECOVER parameter option(s) and definition(s) Option(s) Definition(s) PAGE Specifies standard recovery. The printer resumes with the first sheet not successfully delivered. The default is PAGE. SEGMENT Specifies reprinting of the entire currently printing segment.
PRINT FORMAT COMMANDS Points to note Note the following when using the EXPORT command: • SNUMBER If you specify a line and column value for SNUMBER that is off the page, the segment number will not print. Furthermore, if the system encounters a valid SNUMBER dynamic job descriptor entry (DJDE) under this condition, unpredictable results may occur. • SPLIT = OFF Segment management processing is turned off when the LPS encounters a SPLIT=OFF dynamic job descriptor entry (DJDE).
PRINT FORMAT COMMANDS • Resetting the segment number You may set a new segment number after the current one is terminated. This is accomplished when the system encounters a series of two DJDEs: SPLIT=OFF followed by SPLIT=(min,max). In an online environment, banner pages are routed to the current job output destination. For example, if a job is being sent to a third party finishing device, the banner page will be sent there, also.
PRINT FORMAT COMMANDS LINE command The LINE command provides parameters which allow the user to define the characteristics of the user portion of the input data record and how it is to be printed. Table 6-23 summarizes the LINE command parameters. Table 6-23.
PRINT FORMAT COMMANDS DATA This parameter specifies the location and length of the print line data within an input data record. Syntax Options LINE DATA = option(s) Table 6-24 lists the parameter option(s) and definition(s). Table 6-24.
PRINT FORMAT COMMANDS FONTINDEX This parameter specifies that a field within a user data record defines the index to a specific font to be used for that line. If FONTINDEX is not specified, none is used. Syntax Options LINE FONTINDEX = option(s) Table 6-26 lists the parameter option(s) and definition(s). Table 6-26.
PRINT FORMAT COMMANDS MARGIN This parameter specifies the left margin on a physical page. Syntax Options LINE MARGIN = option(s) Table 6-27 lists the parameter option(s) and definition(s). Table 6-27. MARGIN parameter option(s) and definition(s) Option(s) Definition(s) {value | This option has the following components: (value, value-type)} • value The form nnn.mm (a positive decimal number with up to 2 digits to the right of the decimal point) which is the distance from the left margin.
PRINT FORMAT COMMANDS OVERPRINT This parameter specifies the manner in which overprint lines are handled. (Overprint lines are print lines whose carriage control specifies printing with no line spacing since the last printed line.) Syntax Options LINE OVERPRINT = option(s) Table 6-28 lists the parameter option(s) and definition(s). Table 6-28.
PRINT FORMAT COMMANDS PCC This parameter specifies the position (and possible translation) of the printer carriage control field. Syntax Options LINE PCC = option(s) Table 6-29 lists the parameter option(s) and definition(s). Table 6-29.
PRINT FORMAT COMMANDS PCCTYPE This parameter specifies a carriage control set used in printing a job. Syntax Options LINE PCCTYPE = option(s) Table 6-30 lists the parameter option(s) and definition(s). Table 6-30.
PRINT FORMAT COMMANDS UCSB This parameter specifies UCSB options. Syntax Options LINE UCSB = option(s) Table 6-31 lists the parameter option(s) and definition(s). Table 6-31. UCSB parameter option(s) and definition(s) Option(s) Definition(s) IGNORE Suppresses the host transmitted universal character set buffer (UCSB). If IGNORE is coded, the CODE parameter of the VOLUME command defines the character translation. For online systems only.
PRINT FORMAT COMMANDS Points to note Note the following when using the LINE command: • FONTINDEX Although the maximum bit-opt value may be 7 (allowing a maximum font index value of 127), the maximum number of fonts is constrained by the size of available input and output dynamic memory, font memory size, and the CME or PDE FONTS parameter. Also, internal table structures limit the number of fonts which can be invoked on a single page to 94 fonts.
PRINT FORMAT COMMANDS The height of the last font used determines the initial base line of that first print line. The FONTINDEX byte, if selected, is processed for every record, DJDEs, RPAGE, and all criteria records. A valid FONTINDEX byte should be present in all records since it controls line spacing and override line spacing at page transitions. • Font index bytes It is advisable to put the font index byte in the beginning of a variable record to conserve tape space.
PRINT FORMAT COMMANDS Examples This section shows examples of using the LINE command. Example 1 LINE DATA=(1,132),PCC=(0,NOTRAN), PCCTYPE=IBM1403,FONTINDEX=133; The LINE command above defines the characteristics of the following record structure shown in figure 6-4. Figure 6-4. Sample data record structure The print-data-offset parameter of the DATA parameter (the number of bytes between the start of the user portion of the record and the first character of the record to be printed) is 1 byte.
PRINT FORMAT COMMANDS Example 3 LINE PCCTYPE=NONE, DATA=(1,57), VFU=V1; Figure 6-5.
PRINT FORMAT COMMANDS MESSAGE command The MESSAGE and ROUTE commands permit the user to inform the operator of special conditions. The MESSAGE command displays user-defined text to the operator. Example The following MESSAGE command informs the operator that blue paper is required for copy 2 of a 4 copy report. Printing is suspended at the appropriate points so that the operator can load the paper.
PRINT FORMAT COMMANDS ITEXT This parameter specifies a text message to be output to the operator during input processing. Syntax Options MESSAGE ITEXT = option(s) Table 6-34 lists the parameter option(s) and definition(s). Table 6-34. ITEXT parameter option(s) and definition(s) Option(s) Definition(s) NONE Specifies that no text message is output to the operator during input processing. The default is NONE.
PRINT FORMAT COMMANDS OTEXT This parameter specifies a text message to be output to the operator during job printing. Syntax Options MESSAGE OTEXT = option(s) Table 6-35 lists the parameter option(s) and definition(s). Table 6-35. OTEXT parameter option(s) and definition(s) Option(s) Definition(s) NONE Specifies that no text message is output to the operator during job printing. The default is NONE. 6-44 sc Specifies a text message of up to 80 characters (maximum of 400 characters per report).
PRINT FORMAT COMMANDS BTEXT This parameter supports the PC UI report audit logging feature which creates an audit log on the UI hard disk. The audit log is initiated and terminated by including enabling data in the job stream. The PDL/ DJDE command, BTEXT, is implemented primarily to support barcode audit logging which is not implemented in the DocuPrint 180 LPS. BTEXT report definition parameters are, however, useful without the installation of a barcode reader.
PRINT FORMAT COMMANDS Table 6-36. BTEXT parameter option(s) and definition(s) Option(s) Definition(s) LDT=[* | U | W | BW | SM | M | Log stale date indicator. Once this date has passed, Q | 0...365|yy-mm-dd] the audit log may be deleted or overwritten without warning to the operator. This option has the followihg components: RSQ=[Y | N] 6-46 • * Asterisk: Operator is not notified of re-runs but the report is renamed with a unique version as if the operator had been notified and accepted the re-run.
PRINT FORMAT COMMANDS Table 6-36. BTEXT parameter option(s) and definition(s) Option(s) Definition(s) DDE=[Y | N] Duplicate detection enablement. (Y)es indicates the audit report will flag duplicate sheets delivered. This option must be set to (N)o if multiple copies of a report or pages within the report are printed. For outof-order deliveries, the job must be run in NOSEQ or BAR ALI mode so that the IOT will not catch and purge the mis-sequenced pages.
PRINT FORMAT COMMANDS Table 6-36. BTEXT parameter option(s) and definition(s) Option(s) Definition(s) PRD=yy-mm-dd Process date. If specified, it prints in the audit report header. SEQ=sss Sequence number. It may be up to five digits, for a maximum value of 65534. This is required in order to identify non-delivered, out of sequence, or duplicate pages. The value of this parameter must match the bar code text to be printed on the page.
PRINT FORMAT COMMANDS BTEXT parameter rules Note the following rules when using the BTEXT parameter: • All parameters have the form: Keyword=value • XEROX DOCUPRINT 180 LPS PDL REFERENCE Each value must be specified as shown in the BTEXT command syntax. A value may be a keyword as shown in the BTEXT command syntax or text described as follows: — xxx Alphanumeric text, including spaces.
PRINT FORMAT COMMANDS Points to note Note the following when using the BTEXT parameter: • If RNA (report name) is not specified, no audit logging will be performed. • Although the BTEXT command can be placed in the JSL, it will usually be placed in a DJDE as most of the parameters will be unique to a job. When placed in the JSL, it is specified under the PDL MESSAGE command.
PRINT FORMAT COMMANDS • The BTEXT report parameter(s) must precede the first BTEXT page detail parameter. The ESS software does not check for this. It is up to the user to code the application correctly. • Reports with multiple copies are not expected to be audited in the normal course of operations, as in the case of check printing; this implies multiple copies of checks.
PRINT FORMAT COMMANDS Example 1 • BTEXT commands are treated as text strings by the PDL/DJDE compiler and forwarded to the PC UI to process. Therefore, it is possible that JSLs containing BTEXT will compile successfully even though errors exist in the BTEXT command string. It is up to the PC UI to process the BTEXT commands and flag any errors found. The same goes for BTEXT DJDEs.
PRINT FORMAT COMMANDS waste management data. If a job consists of many reports, all those reports must be reviewed for waste management. Use the Summary, Waste Management and Operation Detail options in the Audit Log Display (or Print) window to obtain a summary report with each waste management event and all logged operations. • Reconciliation, sequence error, and duplicate error auditing must be performed with job stream BTEXT.
PRINT FORMAT COMMANDS Other Audit Logging points to note Note the following: • Delete logs regularly. For maximum control, audit logs are never automatically deleted. The following exceptions exist: — A rerun of a report that had no stale date specified (LTD=0). The current log replaces the old log. — A rerun of a report where the stale date has expired. The current log replaces the old log.
PRINT FORMAT COMMANDS — • If both JSL and job stream BTEXT are to take effect, JSL BTEXT must not have an RNA parameter, and job stream BTEXT must follow the first data record and contain the RNA parameter. Note that the RNA parameter must precede any page detail parameters.
PRINT FORMAT COMMANDS OUTPUT The OUTPUT command controls the organization and format of a report. This includes control of the number of copies of a report, the forms to be printed with the variable data, report offsetting, and the use of simplex or duplex mode. Many graphics features may be invoked with this command; these are explained in greater detail later in this chapter and in the Xerox DocuPrint 180 LPS Operations Reference. Table 6-36 summarizes the OUTPUT command parameters. Table 6-37.
PRINT FORMAT COMMANDS Table 6-37.
PRINT FORMAT COMMANDS BFORM This parameter prints a form on the back side of a duplex data page. In association with the duplex printing mode DUPLEX=YES, a page containing only a form (no variable data can be printed with this page) may be printed on the back side of a user page. This feature can be used to print static data on the back of each page in a report without the use of DJDEs or the repetitive processing of that data.
PRINT FORMAT COMMANDS COLLATE This parameter specifies whether pages are to be collated or uncollated. Syntax Options OUTPUT COLLATE = option(s) Table 6-38 lists the parameter option(s) and definition(s). Table 6-39. COLLATE parameter option(s) and definition(s) Option(s) Definition(s) YES Specifies that the output pages are collated The default is YES. NO Specifies that the output is not collated. If DUPLEX=YES, then COLLATE=NO is ignored.
PRINT FORMAT COMMANDS COVER This parameter specifies that cover pages are to be picked from the AUX cluster. These cover pages may be placed at the front or back of each copy of a report. Syntax Options OUTPUT COVER = option(s) Table 6-40 lists the parameter option(s) and definition(s). Table 6-41. COVER parameter option(s) and definition(s) Option(s) Definition(s) NONE Specifies that no cover pages are to be picked. The default is NONE.
PRINT FORMAT COMMANDS CYCLEFORMS This parameter specifies a set of forms to be associated with report pages in a cyclical fashion. Refer to the examples at the end of this section. Syntax Options OUTPUT CYCLEFORMS = option(s) Table 6-41 lists the parameter option(s) and definition(s). Table 6-42. CYCLEFORMS parameter option(s) and definition(s) Option(s) Definition(s) form-id | (form-id1[,form-id2][,...
PRINT FORMAT COMMANDS DENSITY This parameter is listed for compatibility purposes only; it is not supported on the DocuPrint 180 LPS. Syntax Options OUTPUT DENSITY = option(s) Table 6-42 lists the parameter option(s) and definition(s). Table 6-43. DENSITY parameter option(s) and definition(s) Option(s) Definition(s) FIX NOFIX DEFAULT The default is DEFAULT. Considerations DESTINATION This parameter specifies the output destination of paper.
PRINT FORMAT COMMANDS DUPLEX This parameter specifies whether printing is to occur in duplex (print on both sides of a sheet) or simplex (print on a single side). Syntax Options OUTPUT DUPLEX = option(s) Table 6-44 lists the parameter option(s) and definition(s). Table 6-45. DUPLEX parameter option(s) and definition(s) Option(s) Definition(s) YES Selects duplex printing. NO Specifies simplex printing. The default is NO. FACEUP This parameter specifies faceup delivery of pages.
PRINT FORMAT COMMANDS FEED This parameter controls the stock on which the page is printed. Syntax Options OUTPUT FEED = option(s) Table 6-46 lists the parameter option(s) and definition(s). Table 6-47. FEED parameter option(s) and definition(s) Option(s) Definition(s) stockreference Specifies the stock assigned to a stock-name by the STOCKSET command in effect at the time the page is printed.
PRINT FORMAT COMMANDS FORMAT This parameter specifies a page descriptor entry (PDE) to be used in formatting the printed output, such as location of starting print line for each logical page on the physical page, font usage, and page orientation. Syntax Options OUTPUT FORMAT = option(s) Table 6-47 lists the parameter option(s) and definition(s). Table 6-48.
PRINT FORMAT COMMANDS FORMS This parameter specifies forms to be associated with the report copies. Different forms may be associated with different copies of a report by the use of multiple FORMS left parts on the same OUTPUT command. Syntax Options OUTPUT FORMS = option(s) Table 6-48 lists the parameter option(s) and definition(s). Table 6-49.
PRINT FORMAT COMMANDS GRAPHICS This parameter specifies how graphics are to be processed in a job. Syntax Options OUTPUT GRAPHICS = option(s) Table 6-49 lists the parameter option(s) and definition(s). Table 6-50. GRAPHICS parameter option(s) and definition(s) Option(s) Definition(s) NO Indicates that there are no graphics in this job. The default is NO. Considerations YES Indicates there are graphics. MOVE Indicates that all referenced graphic disk files are to be copied into the print file.
PRINT FORMAT COMMANDS IMAGE This parameter specifies, for batch mode processing only, the initial graphic imaging parameters to be used. Syntax Options OUTPUT IMAGE = option(s) Table 6-50 lists the parameter option(s) and definition(s). Table 6-51. IMAGE parameter option(s) and definition(s) Option(s) Definition(s) vpos Specifies the vertical position of the top edge of the graphic, as an offset, relative to 0,0 on the current physical page (the position that would be specified by a PDE BEGIN of 0,0).
PRINT FORMAT COMMANDS INVERT This parameter allows you to invert the current position of the page. A page can effectively be rotated 180°—head-to-head and head-totoe. Inversion is also used for page orientation for finishing functions. Syntax Options OUTPUT INVERT = option(s) Table 6-51 lists the parameter option(s) and definition(s). Table 6-52. INVERT parameter option(s) and definition(s) XEROX DOCUPRINT 180 LPS PDL REFERENCE Option(s) Definition(s) FRONT Specifies page inversion on front sides.
PRINT FORMAT COMMANDS MODIFY This parameter specifies CMEs to be associated with report copies. Syntax Options OUTPUT MODIFY = option(s) Table 6-52 lists the parameter option(s) and definition(s). Table 6-53. MODIFY parameter option(s) and definition(s) Option(s) Definition(s) cme-id | This option has the following components: (cme-id,[init][,copies]) | • cme-id NONE The command identifier of a CME. The CME may be coded within a JSL or coded and cataloged separately for use by several JSLs.
PRINT FORMAT COMMANDS NTO1 This parameter specifies, on a report basis, whether all copies of a particular report are printed last page to first (n-to-1). NTO1 is the command parameter keyword. Syntax Options OUTPUT NTO1 = option(s) Table 6-53 lists the parameter option(s) and definition(s). Table 6-54. NTO1 parameter option(s) and definition(s) Option(s) Definition(s) YES Specifies last page to first printing. To print n-to-1, output processing must print the report starting with the last page.
PRINT FORMAT COMMANDS NUMBER This parameter specifies page numbering on the output pages of a report. The page number character string is placed on the page at the specified line number based on the line spacing of the specified font. If override line spacing is specified for the font, it does not affect where the page number character string is to be printed. Syntax Options OUTPUT NUMBER = option(s) Table 6-54 lists the parameter option(s) and definition(s). Table 6-55.
PRINT FORMAT COMMANDS OFFSET This parameter specifies offset control on a report basis. Syntax Options OUTPUT OFFSET = option(s) Table 6-55 lists the parameter option(s) and definition(s). Table 6-56. OFFSET parameter option(s) and definition(s) Option(s) Definition(s) ALL Results in an offset of each copy of each report. The default is ALL. FIRST Specifies that an offset is to occur only on the first copy of a report. NONE Specifies that there is to be no offset at any time.
PRINT FORMAT COMMANDS OSTK This parameter specifies ordered stocks. Syntax Options OUTPUT OSTK = option(s) Table 6-56 lists the parameter option(s) and definition(s). Table 6-57. OSTK parameter option(s) and definition(s) Option(s) Definition(s) [(clu-def,[mod],[pos], [RES | NORES],[TABS], [size[DOTS | IN | CM]] [,L | P])] This option has the following components: • clu-def The name of the cluster containing the ordered stock (either a cluster-name or a clusterreference). No default.
PRINT FORMAT COMMANDS PAPERSIZE This parameter specifies the paper size to be used for printing the job. Syntax Options OUTPUT PAPERSIZE = option(s) Table 6-57 lists the parameter option(s) and definition(s). Table 6-58. PAPERSIZE parameter option(s) and definition(s) Option(s) Definition(s) A3 16.54 by 11.69 inches (297 by 420 mm) A4 8.27 by 11.69 inches (287 by 270 mm) B4 10.12 by 14.33 inches (257 by 364 mm) B5 7.17 by 10.12 inches (178 by 254 mm) USLEGAL 8.
PRINT FORMAT COMMANDS PURGE This parameter specifies whether or not the system should delete graphic disk files at the end of report. This is only true for document interleaved. Syntax Options OUTPUT PURGE = option(s) Table 6-58 lists the parameter option(s) and definition(s). Table 6-59. PURGE parameter option(s) and definition(s) Option(s) Definition(s) NO Specifies that graphic disk files should not be deleted.
PRINT FORMAT COMMANDS SF1FUNCTION This parameter provides control over third-party finishing devices that conform to the DFA standard. Using this command, you can invoke sheet finisher function number 1 through the DFA channel C6. Syntax Options OUTPUT SF1FUNCTION = option(s) Table 6-60 lists the SF1FUNCTION parameter option(s) and definition(s). Table 6-61.
PRINT FORMAT COMMANDS SHIFT Image shift is the shifting of the image data (system page) relative to the physical page. This shifting is in the scan counting direction (vertical for landscape and horizontal for portrait). The SHIFT parameter specifies whether the image of the form and data on a page is to be shifted, and if so, by what values. This parameter is used to shift the image of the data in the y-direction for three-hole paper, binding, finishing, and edgemarking.
PRINT FORMAT COMMANDS SIZING This parameter specifies how the system matches the paper sizes in bins when the LPS is unattended. Syntax Options OUTPUT SIZING = option(s) Table 6-63 lists the parameter option(s) and definition(s). Table 6-64. SIZING parameter option(s) and definition(s) Option(s) Definition(s) SEMIAUTO The standard mode of operation. The default is SEMIAUTO. BEST Intended for use when the LPS is unattended. Called a nonstop mode because the LPS does not cycle down.
PRINT FORMAT COMMANDS STOCKS This parameter defines the stockset and its associated stock(s) to be used in a report. If the stockset-name does not reference a STOCKSET command coded earlier in the same JDL, the system assumes that the stockset exists globally as an STK file, which is read at print time. In this case, PDL inserts a message in the JSL file listing, indicating that an STK file will be used at print time.
PRINT FORMAT COMMANDS SYSPPR This parameter specifies the system page paper size for a job. Syntax Options OUTPUT SYSPPR = option(s) Table 6-65 lists the parameter option(s) and definition(s). Table 6-66. SYSPPR parameter option(s) and definition(s) Option(s) Definition(s) USLEGAL 8.5 by 14 inches (216 by 279 mm) A3 16.54 by 11.69 inches (420 by 297 mm) A4 8.27 by 11.69 inches (210 by 297 mm) B4 10.12 by 14.33 inches (257 by 364 mm) USLETTER 8.
PRINT FORMAT COMMANDS TMODE This parameter specifies paper sizes in order to improve throughput efficiency. Syntax Options OUTPUT TMODE = option(s) Table 6-66 lists the parameter option(s) and definition(s). Table 6-67. TMODE parameter option(s) and definition(s) Option(s) Definition(s) (width [,width unit]) This option has the following components: • width The process direction measurement that determines the default pitch mode.
PRINT FORMAT COMMANDS TRANS This parameter specifies whether transparencies are used for the print job. Transparencies cannot be handled by the high-capacity feeder/ stacker. Due to this restriction, transparency jobs must feed from the processor feed trays (trays 1 or 2; also known as MAIN and AUX feed) and stack to the sample tray. Syntax Options OUTPUT TRANS = option(s) Table 6-67 lists the parameter option(s) and definition(s). Table 6-68.
PRINT FORMAT COMMANDS XSHIFT This parameter specifies whether the image of the form and data on a page is to be shifted, and if so, by what values. This parameter is used to shift the image of the data for two-hole paper, binding, finishing, and edgemarking. XSHIFT allows shifting in the x-direction for short-edge binding. Syntax Options OUTPUT XSHIFT = option(s) Table 6-69 lists the parameter option(s) and definition(s). Table 6-70.
PRINT FORMAT COMMANDS XMP Xerographic mode persistence (XMP) controls xerographic mode switching (XMS) to use for the report. Depending on the option specified, the effect is to maximize throughput or minimize toner usage. OUTPUT XMP may be specified in V5.0 and/or V4.0 JDLs. The DocuPrint 180 LPS is capable of processing highlight color jobs and printing them in monochrome, thus, ignoring that XMP was specified.
PRINT FORMAT COMMANDS Points to note — OUTPUT command Note the following when using the OUTPUT command. These points to note list parameters followed by the applicable action or system response. • • DUPLEX=YES — Any job that runs in simplex mode runs in duplex mode except transparencies. — A recoverable dispatching or imaging error on an evennumbered page results in one additional hole in the paper path and up to seven aborted pages to the sample tray.
PRINT FORMAT COMMANDS Example 1: The default order is 1TON, OUTPUT NTO1=NO is specified, and a JDE or JDE dynamic job descriptor entry (DJDE) containing NTO1=YES is invoked. The system does not process the DJDE. Example 2: The default order is 1TON and OUTPUT NTO1=YES is specified. The system allows NTO1 printing if NTO1 threshold values (n) are within permitted limits. Note that NTO1 DJDEs are never allowed with the 1TON system default. Example 3: The default order is NTO1 and OUTPUT NTO1=NO is specified.
PRINT FORMAT COMMANDS • DUPLEX=NO, ACCT USER=TRAY, BFORM ignored, RPAGE SIDE=NUBACK, forced to NUFRONT If transparency (TRANS) is specified, the input task forces these parameters. Any operator key-ins, however, override the JSL specifications. • CYCLEFORMS, FORMS Both may be used within a report; however, only the last parameter specified is in effect at any given time.
PRINT FORMAT COMMANDS stock. Having recognized it, INPUT then adds n dots (width of the tab) to the paper size in the slow scan direction. The IOT disables any dynamic width checking whenever it encounters a tab. The portrait/landscape parameter of the OSTK statement allows either to be specified. The only one supported by the DocuPrint 180 is portrait (P), and this is the default condition.
PRINT FORMAT COMMANDS — When feeding from tab stock: – Be sure to revert the DJDEs back to: FEED=regular-stock SIMPLEX=YES or DUPLEX=YES after printing the tab stock. • – Ensure that PFEED does not specify the tray that contains the tab stock. – Use the OSTK command before running a tab job.
PRINT FORMAT COMMANDS • Paper sizes The PAPERSIZE parameter is not supported as a DJDE. Therefore, a JDE page-oriented DJDE that calls out the desired paper size is needed. — When specifying paper sizes, if the JSL specifies the paper size using the keyword method (such as USLEGAL, A4, or B4), then the FSL must also use the same method. If the JSL specifies 8.5,14 and FSL specifies USLEGAL, the INPUT will display an error message. OS6670 FORM PAPER SIZE TOO SMALL.
PRINT FORMAT COMMANDS • Using pitch and the TMODE parameter effectively Paper sizes each have an associated pitch mode. There are six processing modes available on your LPS. These are called pitch modes. A pitch is a term describing the number of pages that can be imaged on the printer photoreceptor belt. A pitch mode is a phrase that describes how many pitches can occur during one complete photoreceptor revolution.
PRINT FORMAT COMMANDS — XEROX DOCUPRINT 180 LPS PDL REFERENCE Estimating the time needed to run your print jobs for scheduling purposes. To better understand the potential value of specifying pitch modes in your JSLs, consider these hypothetical situations: – Your finishing device folds and binds your printed output but accepts pages at a considerably slower rate than the 180 pages-per-minute capability of your DocuPrint 180 laser printing system.
PRINT FORMAT COMMANDS As you can see, there are no absolutes and no set methods for accomplishing your printing goals. The variables involved include individual finishing device requirements, the paper sizes required by your applications, the complexity of each page, the number of pages in each application, and so forth. But a general understanding of the relationship between paper size and pitch mode, and the advantages of specifying pitch modes will help you optimize your printing activities.
PRINT FORMAT COMMANDS You may also specify pitch mode boundaries in centimeters (CM), DOTS, and XDOTS. The minimum and maximum scan values with these units of measurement and the pitch mode ppm print speeds are shown in table 6-72. • Purging stock The DocuPrint 180 LPS can purge tab sheets whenever the tab cycle is not in sync with the formatted data. This may be caused by paper jams or running multiple jobs in succession.
PRINT FORMAT COMMANDS Examples This section shows examples of using the OUTPUT command. Example 1 OUTPUT GRAPHICS=MOVE,UNITS=150,CYCLEFORMS=NONE,FORMAT=PDE 1,RESOLUTION=300; Example 2 OUTPUT COPIES=3,DUPLEX=YES,SHIFT=YES,OFFSET=FIRST, NUMBER=(1,66,132),COVER=(FRONT,SEP),FORMS=GBAR; Pages printed with this OUTPUT command are in duplex mode with a margin shift of 75 dots. Three copies of the report are made, the first of which is offset; the second and third copies are stacked on top of the first.
PRINT FORMAT COMMANDS Example 5 The commands in figure 6-7 illustrate the use of cycleforms with multiple copies. Note that every copy of a particular page has the same form whether COLLATE=YES or NO. The pages in the following example are not logical pages but are one side of a logical sheet of paper. Figure 6-7.
PRINT FORMAT COMMANDS PDE command The PDE command specifies a page descriptor entry (PDE) which defines formatting information 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. Table 6-73 summarizes the PDE command parameters. Table 6-74.
PRINT FORMAT COMMANDS Table 6-75. Standard LPS print format cpi Approx. point size Page size and orientation* BEGIN values Default font id 8.1 13.6 9 11 by 8.5 (.18,.66) L0112B 150 8.1 15 9 11 by 8.5 (.18,.50) L0212A 88 132 10.7 13.6 7 11 by 8.5 (.14,.66) L0312A FMT4 88 150 10.7 15 7 11 by 8.5 (.14,.50) L0412A FMT5 49 100 6 10 12 11 by 8.5 (.17,.50) L0512A FMT6 80 100 8.1 13.6 9 8.5 by 11 (.57,.58) P0612A FMT7 60 90 6 12 12 8.5 by 11 (.50,.
PRINT FORMAT COMMANDS Multiple logical pages on a physical page Multiple BEGINs define multiple logical pages (a user-defined page image bordered by top of form and bottom of form, left and right margins) on one physical page (one side of a sheet). Up to 63 logical pages may be defined per physical page. These logical pages may be defined in any order on the physical page and placed on the physical page in the order the BEGIN parameters appear in the PDE command.
PRINT FORMAT COMMANDS The following sections describe the syntax of the command parameters and explanations of the parameter options. BEGIN This parameter specifies the location of the starting print line of a logical page for graphics. The vpos parameter specifies the vertical position of the first character of the first print line on the logical page. It may be specified in inches (IN) or centimeters (CM). The default is inches.
PRINT FORMAT COMMANDS FONTS This parameter specifies the fonts to be used in printing variable input data and CME data. Syntax Options ac:PDE FONTS = option(s) Table 6-76 lists the parameter option(s) and definition(s). Table 6-77. FONTS parameter option(s) and definition(s) Option(s) Definition(s) (f1[,f2][,...]) | ((f1,s1)[,(f2,s2)][,...
PRINT FORMAT COMMANDS PMODE This parameter specifies the printing mode for each physical sheet. Syntax Options ac:PDE PMODE = option(s) Table 6-77 lists the parameter option(s) and definition(s). Table 6-78. PMODE parameter option(s) and definition(s) Option(s) Definition(s) LANDSCAPE Indicates that printing is to be parallel to the long edge of paper. The default is LANDSCAPE. PORTRAIT XEROX DOCUPRINT 180 LPS PDL REFERENCE Indicates that printing is to be parallel to the narrow edge of paper.
PRINT FORMAT COMMANDS Points to note Note the following when using the PDE command: • 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. For both the input and output tasks, the number of fonts specified in the FONTS parameter must be at least equal to the largest number of fonts required to print any page within the job.
PRINT FORMAT COMMANDS Examples This section shows examples of using the PDE command. Example 1 PDE1: PDE PMODE=LANDSCAPE,BEGIN=(.861,.7),FONTS=(L0112B, L01BOB); PDE2: PDE PMODE=PORTRAIT,BEGIN=(1.3,.37),FONTS=((P08TYA,6.8, (P080AA,6.8)); LI: JDE; OUTPUT FORMAT=PDE1; P1: JDE; OUTPUT FORMAT=PDE2; Two PDEs are defined and referenced in separate JDEs. PDE1 specifies a landscape page and two landscape fonts; PDE2 defines a portrait page and 2 portrait fonts with override line spacing.
PRINT FORMAT COMMANDS ROUTE command The ROUTE command allows the user to print identifying information (text and an optional form) on the page preceding a report. The ROUTE command may be coded within a JDL or in a disk file of ROUTE commands. Table 6-78 summarizes the ROUTE command parameters. Table 6-79. Summary of ROUTE command parameters Parameter Specifies Offline Online DJDE RFORM Form to be printed with RTEXT preceding a report copy. Y Y Y RTEXT Text to be printed preceding a report copy.
PRINT FORMAT COMMANDS RFORM This parameter specifies a form to be printed with all RTEXT pages. If RTEXT data is not specified, RFORM is not honored. However, RTEXT can be specified as one blank character (or space) to print an RFORM on the routing page without any accompanying text. Syntax Options ROUTE RFORM = option(s) Table 6-79 lists the parameter option(s) and definition(s). Table 6-80.
PRINT FORMAT COMMANDS RTEXT This parameter specifies text to be printed on a separate page preceding a report (or copy ply). Syntax Options ROUTE RTEXT = option(s) Table 6-80 lists the parameter option(s) and definition(s). Table 6-81. RTEXT parameter option(s) and definition(s) Option(s) Definition(s) sc | (sc,[passnum | ALL], This option has the following components: [line,[col[,fontindex]]]) • sc Specifies the message to be printed (1 to 132 characters).
PRINT FORMAT COMMANDS Considerations The font index is associated only with a particular string. To print an entire RTEXT page in the same font, the font index must be given with each string. Strings without a font index are printed with the first alphanumeric font (specified in the font parameter of the PDE command). If more than one font is used to print any number of RTEXT strings on a page, the line and the character spacing values of the different fonts are used to place RTEXT on the page.
PRINT FORMAT COMMANDS STOCKSET command The STOCKSET command defines a set of stocks used in a report. This allows output to verify the exclusivity of all stocks in terms of trays currently assigned to them. For your LPS, a stock-name is represented by a cluster. For more information refer to the feeder tray chapter in your Xerox DocuPrint 180 LPS Operator Guide. Stocksets are also the means of associating stock references with stock names.
PRINT FORMAT COMMANDS INIFEED This parameter specifies which stock to use in the absence of any FEED parameter. If not specified, the INIFEED parameter defaults to the first stock name specified in the ASSIGN parameter. Syntax Options ac:STOCKSET INIFEED = option(s) Table 6-83 lists the parameter option(s) and definition(s). Table 6-84. INIFEED parameter option(s) and definition(s) Option(s) Definition(s) stock-name stockreference The default is the first stock-name.
PRINT FORMAT COMMANDS Points to note Note the following when using the STOCKSET command: System-generated pages, such as with the VOLUME command PLABEL parameter or the IDEN command OPRINFO parameter, are formatted using 8.5 by 11-inch paper, unless the system has been sysgened for A4 paper. These system-generated pages are printed using the STOCKSET command SYSPAGE parameter that is in effect. If no STOCKSET parameters are in effect, cluster MAIN is used, unless overridden by an operator key in.
PRINT FORMAT COMMANDS VFU The VFU command is used to assign 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 is also used to assign line numbers to the top of form and the bottom of form. Top of form indicates the number of lines from the top (as defined by the PDE BEGIN values) of an output page to the first print line on the page.
PRINT FORMAT COMMANDS ASSIGN This parameter specifies the output line-to-channel assignments. Syntax Options ac:VFU ASSIGN = option(s) Table 6-86 lists the parameter option(s) and definition(s). Table 6-87. ASSIGN parameter option(s) and definition(s) Option(s) Definition(s) (channo,lineno) This option has the following components: • channo The number of the channel being assigned. It is an integer in the range 0 to 15.
PRINT FORMAT COMMANDS TOF This parameter specifies the top-of-form line number. Syntax Options ac:VFU TOF = option(s) Table 6-88 lists the parameter option(s) and definition(s). Table 6-89. TOF parameter option(s) and definition(s) Option(s) Definition(s) value Specifies the number of lines from the top of the output page to the first print line on the page (top of form). The top-of-form specification is independent of channel assignments.
PRINT FORMAT COMMANDS Example Following is an example of how to use the ROUTE 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.
7. 7Using logical processing The logical processing (sometimes referred to as “special processing”) commands enable the user to specify logical functions performed on either a record, a set of records, or on a block basis. The following table summarizes the functions that may be performed and the corresponding PDL commands. Table 7-1 summarizes the commands associated with logical processing. Table 7-1.
USING LOGICAL PROCESSING Logical processing command format To define a logical processing command fully, you must specify one or two fields in the record or block to be tested. In general, a logical processing command has the following format: command TEST = test-exp; The logical processing command tests the value of the specified testexp and directs the flow of processing based on the result of the test.
USING LOGICAL PROCESSING CRITERIA command The basic element used to describe a test for a logical function is the CRITERIA command. Each CRITERIA command describes a field in either a record or block and the specific test to be performed. The CRITERIA command requires an identifier that can be specified in any of the logical processing commands, as a TEST parameter. The definition of the TEST parameters for logical processing commands is described in the “Test expressions ”section.
USING LOGICAL PROCESSING CHANGE This parameter defines test specifications for a logical processing function with change mode criteria. Syntax Options CRITERIA CHANGE = option(s) Table 7-3 lists the parameter option(s) and definition(s). Table 7-3.
USING LOGICAL PROCESSING CONSTANT This parameter defines test specifications for a logical processing function with constant mode criteria in block processing. Syntax Options CRITERIA CONSTANT = option(s) Table 7-4 lists the parameter option(s) and definition(s). Table 7-4.
USING LOGICAL PROCESSING Test expressions The activation of testing is done by coding the TEST parameter of any logical processing command described in this chapter. Either one or two CRITERIA commands can be specified. The following is a definition of the test expression for a logical processing command.
USING LOGICAL PROCESSING either an AND or an OR. The formats of these TEST parameters may be as follows: TEST = (cri,AND,cri-id-2); or TEST = (cri,OR,cri-id-2); The cri-id and cri-id-2 are the identifiers for two CRITERIA commands. The parentheses in this format are required.
USING LOGICAL PROCESSING Combining change and constant modes The CRITERIA tables may specify either change mode or constant mode functions; there are no restrictions on their usage or combination. There are two special cases: when the record or block is too short to include the field being tested and when the line being tested contains no record, that is, it has been skipped. If the test specifies a constant mode function, the CRITERIA fails.
USING LOGICAL PROCESSING Examples This section shows two examples of using the CRITERIA command. Example 1 The following are examples of CRITERIA commands including the TABLE commands they reference. The identifiers C1 and C2 are referenced by a logical processing TEST parameter.
USING LOGICAL PROCESSING String comparison concepts This section focuses on string comparisons, character types, and masked comparisons using default and non-default type assignments. String comparisons String comparisons for logical processing are specified using the CRITERIA and TABLE commands.
USING LOGICAL PROCESSING Masked comparisons using default type assignments Performing masked comparisons using unmodified standard default type assignments requires coding the following: • TCODE command. Used either to modify a set of standard default type assignments or to define a completely new set (refer to processing sequence 3 in figure 7-1). Refer to the “Character type assignments” section in the chapter “Specifying input parameters,” for detailed information on the TCODE command.
USING LOGICAL PROCESSING Figure 7-1.
USING LOGICAL PROCESSING BANNER command The stacked reports feature enables the online and offline user to define a series of reports in a single file. This is accomplished by specifying an end-of-report condition in the coded logical processing commands RSTACK (online and offline) and BANNER (online use only). End-of-report is that point in processing a report when all of the pages of a copy of a report have been formatted to disk and processing has begun on the next report.
USING LOGICAL PROCESSING HCOUNT This parameter specifies the total number of consecutive header banner pages which must be detected to satisfy the test expression. Syntax Options BANNER HCOUNT = option(s) Table 7-7 lists the parameter option(s) and definition(s). Table 7-7. HCOUNT parameter option(s) and definition(s) Option(s) Definition(s) value Specifies the total number of consecutive header banner pages which must be detected to satisfy the test expression. The default is 0.
USING LOGICAL PROCESSING HRPTNA This parameter specifies that for each report a subfield of the first record satisfying the banner selection criteria is to be displayed as the REPORT NAME on the LPS system controller in response to the JOBS command or STATUS function key. (For jobs with HCOUNT=0, that is, trailers only, the report name is associated with the report that precedes the trailer banner page. Syntax Options BANNER HRPTNA = option(s) Table 7-9 lists the parameter option(s) and definition(s).
USING LOGICAL PROCESSING TEST For online jobs, this parameter defines the test expression for detection of a banner page for either change mode or constant mode criteria. Syntax Options BANNER TEST = option(s) Table 7-11 lists the parameter option(s) and definition(s). Table 7-11. TEST parameter option(s) and definition(s) Option(s) Definition(s) test-exp The format and syntax of a test-exp are defined in the “Test expression definition” section.
USING LOGICAL PROCESSING Points to note Table 7-13 shows the effect of the TCOUNT and HCOUNT parameters of the BANNER command under the conditions listed and the results of each. Table 7-13.Summary of BANNER command parameter conditions and results Condition Parameter Result LPS positions to TOF after end-ofreport processing If TCOUNT = 0 The page after the first header is positioned at TOF.
USING LOGICAL PROCESSING BSELECT and BDELETE commands Interspersed blocks within one offline report or file may be either selected for or deleted from printing by use of the BDELETE and BSELECT commands. TEST—BSELECT and BDELETE commands These commands can also be used selectively to delete specialized blocks, for example, control blocks and unsupported labels, that are on the data tape but are not to be printed. Syntax for the TEST parameter of BSELECT and BDELETE commands is as follows.
USING LOGICAL PROCESSING Examples This section shows examples of using the BSELECT and BDELETE commands. Example 1 The following commands illustrate the use of BSELECT to process interspersed reports (refer to the following figure) on a block basis. T1: TABLE CONSTANT=(’P’); C1: CRITERIA CONSTANT=(0,1,EQ,T1); BSELECT TEST=(C1); The contents of the first byte of each tape block (offset=0, length=1) is examined for the character constant ’P’.
USING LOGICAL PROCESSING RAUX command Feeding a single sheet of paper from the auxiliary tray may be controlled from within the input data stream. If a data record satisfying the RAUX test criteria is found, the page on which the record is found is printed on a sheet of paper picked from the auxiliary tray. For simplex printing, the next page is printed on a sheet of paper selected from the main tray, unless it also contains a record satisfying the RAUX test criterion.
USING LOGICAL PROCESSING • Since DJDE processing occurs prior to RAUX processing, DJDE records are not checked for satisfying the RAUX criteria (offline only). Example Following is an example of using the RAUX command: T1: TABLE CONSTANT=’CUSTOMER COPY’; C1: CRITERIA CONSTANT=(20,13,EQ,T1); RAUX TEST=C1; Figure 7-3. 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.
USING LOGICAL PROCESSING RFEED command The logical processing RFEED command allows you to change cluster names on a page-by-page basis without using DJDEs. The RFEED command allows you to specify paper fed from different clusters if certain criteria are met on a record basis. RFEED is essentially an extension of the RAUX command in that it allows you to specify virtually any cluster-name or cluster-reference without being limited to the AUX cluster.
USING LOGICAL PROCESSING Points to note Note the following when using the RFEED command: • Satisfaction of the RFEED criteria will cause the current page to feed from the cluster defined in the RFEED command. • If a criteria is met, the cluster name will remain in effect until the next RFEED criteria is met or a new report is processed. • • RFEED is not available as a DJDE. In a multiple RFEED criteria command, the order in which the criteria are specified makes a difference in the job application.
USING LOGICAL PROCESSING RSELECT and RDELETE commands Interspersed records within one report or file may either be deleted from or selected for printing by use of the RDELETE and RSELECT commands. These commands can also selectively delete specialized records, for example, control records and offset records that are on the data tape but are not to be printed. The following section describes the syntax of the command parameters and explanations of the parameter options.
USING LOGICAL PROCESSING Example The following commands illustrate the use of RDELETE to process interspersed reports on a record basis (refer to figure 7-4). T1: TABLE CONSTANT=(’EFGH’); C1: CRITERIA CONSTANT=(104,4,EQ,T1); RDELETE TEST=C1; If the contents of a deletion control field located 104 bytes from the start of the user portion of the record are equal to the constant ’EFGH’, the record is not printed. In the following example, records 2 and 6 would not be printed. Figure 7-4.
USING LOGICAL PROCESSING ROFFSET command The logical processing function ROFFSET provides the capability for online and offline users to initiate a page offset in the stacker tray under control of the input data, that is, data and DJDE records. These special user-controlled offsets can be used to simplify job distribution by creating separate stacks for each distribution entity.
USING LOGICAL PROCESSING TEST This parameter defines test expression for offsetting pages to the stacker tray. Syntax Options ROFFSET TEST = option(s) Table 7-19 lists the parameter option(s) and definition(s). Table 7-19. TEST parameter option(s) and definition(s) Option(s) Definition(s) test-exp The format and syntax of a test-exp are defined in the “Test expression definition” section. If a test-exp is satisfied, the record causes an offset in the stacker tray.
USING LOGICAL PROCESSING Example Following is an example of using the ROFFSET command. A file has multiple reports without any delimiters separating the reports (as illustrated below). 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. T1: TABLE CONSTANT=(’PAGE...
USING LOGICAL PROCESSING RPAGE command The RPAGE command allows for the repositioning of the current (or next) logical page. Refer to figures 7-5 and 7-6 for a pictorial description of the effect of the RPAGE parameters. Table 7-5 summarizes RPAGE command parameters. Table 7-20 summarizes the RPAGE command parameters. Table 7-20. Summary of RPAGE command parameters Parameter Specifies Offline Online DJDE SIDE Side of physical page on which to reposition the logical page.
USING LOGICAL PROCESSING SIDE This parameter defines the side of the physical sheet on which the repositioned logical page is to appear. Syntax Options RPAGE SIDE = option(s) Table 7-21 lists the parameter option(s) and definition(s). Table 7-21. SIDE parameter option(s) and definition(s) Option(s) Definition(s) side-opt Available side-opt parameters are: NUFRONT (the default), BACK, NUBACK, NEXT. In duplex (with no BFORM), side-opt produces the following results.
USING LOGICAL PROCESSING TEST This parameter defines the test expression for detection of an RPAGE record. Syntax Options RPAGE TEST = option(s) Table 7-22 lists the parameter option(s) and definition(s). Table 7-22. TEST parameter option(s) and definition(s) Option(s) Definition(s) test-exp The format and syntax of a test-exp are defined in the “Test expression definition” section. The logical page on which this record normally prints is called the “current logical page.
USING LOGICAL PROCESSING Points to note Note the following when using the RPAGE command. These points apply to offline jobs only: • 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/deletion is performed prior to RPAGE processing.
USING LOGICAL PROCESSING Figure 7-6.
USING LOGICAL PROCESSING Figure 7-7.
USING LOGICAL PROCESSING RSTACK command The stacked reports feature enables the online and offline user to define a series of reports in a single file. This is accomplished by specifying an end-of-report condition in the coded logical processing commands RSTACK (online and offline) and BANNER (online use only). End-of-report is that point in processing a report when all of the pages of a copy of a report have been formatted to disk and processing has begun on the next report.
USING LOGICAL PROCESSING Delimiter display Display of the delimiter (performed only when DELIMITER=YES) is dependent on the mode (Single/Multi) in which the job is run. Single or multiple report mode is a selectable parameter on the offline START command. If the print job is run in single-report mode, the first delimiter of the next report is displayed. This occurs after an end-of-report is encountered. To begin the next single-report job, the operator must key in another START command.
USING LOGICAL PROCESSING subsequent report unless it also satisfies the TEST (or DJDE) criteria of the starting JDE or JDL. — If RSTACK is specified in the JDE or JDL of the START command but not in the selected JDE or JDL, RSTACK processing is suspended until end of report is triggered by BANNER page detection. — If ACCTINFO is specified in the JDE or JDL of the START command, the ACCTINFO parameter cannot be changed or deleted in a selected JDE or JDL (even if RSTACK is suspended).
USING LOGICAL PROCESSING DELIMITER This parameter specifies whether or not records that are separated from other records are part of the subsequent report. Syntax Options RSTACK DELIMITER = option(s) Table 7-25 lists the parameter option(s) and definition(s). Table 7-25. DELIMITER parameter option(s) and definition(s) Option(s) Definition(s) YES Specifies that all consecutive records satisfying the TEST criteria separate one report from another but are not part of either report.
USING LOGICAL PROCESSING PRINT If DELIMITER=YES is coded, the user may specify if the report delimiters are to be printed, and if so, the output destination of the printed delimiters. Syntax Options RSTACK PRINT = option(s) Table 7-27 lists the parameter option(s) and definition(s). Table 7-27. PRINT parameter option(s) and definition(s) Option(s) Definition(s) BIN Specifies that report delimiters are to be printed and the output delivered to the output stacker tray.
USING LOGICAL PROCESSING Points to note Note the following when using the RSTACK command: • If the TEST expression on the RSTACK command consists solely of a change mode CRITERIA command, DELIMITER=NO must be coded. • An RSTACK command containing a TEST expression specifying a constant mode CRITERIA command and DELIMITER=NO can be used to detect a heading of a report as a report boundary.
USING LOGICAL PROCESSING RSUSPEND and RRESUME commands The print suppression logical processing function permits the user to delete from printing groups of records that are distinguishable at the start and end, but whose intermediate records may not be unique or distinguishable. (Print suppression or resumption is invoked by the use of two separate commands—RSUSPEND and RRESUME.) The tests for each command are independent and must be described separately.
USING LOGICAL PROCESSING BEGIN This parameter specifies the BEGIN options. Syntax Options RSUSPEND BEGIN = option(s) Table 7-29 lists the parameter option(s) and definition(s). Table 7-29. BEGIN parameter option(s) and definition(s) Option(s) Definition(s) CURRENT Specifies whether printing stops or resumes on the current or next record for offline jobs. For RSUSPEND, if CURRENT is coded, the record satisfying test-exp does not print. For RRESUME, if CURRENT is coded, the record is printed.
USING LOGICAL PROCESSING Points to note Note the following when using the RSUSPEND and RRESUME commands: • • XEROX DOCUPRINT 180 LPS PDL REFERENCE RSUSPEND — Make sure that if an RSUSPEND command is coded, an RRESUME command must also be present for the job. A warning is issued by the PDL compiler if one command, but not both, is invoked for a job. However, the JDE is compiled as programmed. — The RSUSPEND command is intended to suspend records within a report.
USING LOGICAL PROCESSING Example Following is an example of using the RSUSPEND and RRESUME commands.
USING LOGICAL PROCESSING TABLE command The TABLE command is used to build a table of constants for use by the logical processing commands. Each constant included in a TABLE command is examined by the system to see if it is equal in value to the input data field specified in the CONSTANT parameter of the CRITERIA command. The TABLE command must precede its reference in a CRITERIA command.
USING LOGICAL PROCESSING MASK This parameter defines mask characters used within string constants (specified by CONSTANT parameter) and indicates which character positions have special type testing and what that testing is. Syntax Options ac:TABLE MASK = option(s) Table 7-32 lists the parameter option(s) and definition(s). Table 7-32. MASK parameter option(s) and definition(s) Option(s) Definition(s) (ignore-char [,charspeci1] [,charspeci2][,...
USING LOGICAL PROCESSING Examples This section shows examples of using the TABLE command. Example 1 The following are sample TABLE commands. The identifiers T1, T2, and T3 are each referenced by a CRITERIA command.
USING LOGICAL PROCESSING Therefore, in this example, only data strings that begin with A7 can possibly pass the entire test. Example 4 T2: TABLE MASK=(’*’,’:’,’!’),CONSTANT=(’DATE ::/ ::/:: ID!!!’); The TABLE command above sets up the character-to-type associations shown in table 7-34. Table 7-34.
8. 8Specifying dynamic job descriptor entries (DJDEs) Dynamic job descriptor entries (DJDEs) are parameters embedded within the input data stream and are used to modify the printing environment established by a job descriptor entry (JDE) “on the fly.” Dynamic job descriptor entry processing enables certain JDE parameters to be changed on a page-to-page or record-to-record basis. The IDEN command coded in a JDE notifies the system that DJDE records are included in the input data stream.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) Benefits of using DJDEs Some of the benefits derived from changing these job parameters with DJDEs are as follows: • The printing system does not stop between reports nor does it require operator intervention. The operator starts up a job on the printing system and typically returns to it only when minor operational activity is required. • • Forms may be changed on a page-to-page basis.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) Page- and record-oriented DJDEs There are two types of DJDEs: page-oriented and record-oriented. Page-oriented Page-oriented DJDEs change specific pages within a report and can change these pages differently in different copies. Such parameters may be placed within the report itself and take effect at the next page boundary. They may also appear at report boundaries to effect changes on all pages of a report (or report-ply).
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) Table 8-1 lists the page-oriented DJDEs. Table 8-1. 8-4 Page-oriented DJDEs DJDE Function BEGIN Specifies the location of the starting print line of a logical page for graphics. BFORM Specifies that a form be printed on the back side of a printed page. COLLATE Specifies whether the pages of a job are to be collated (placed into sets) or uncollated (like pages placed together).
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) Table 8-1. Page-oriented DJDEs (continued) DJDE Function RFORM Specifies whether a form is printed on all RTEXT pages. RTEXT Specifies text to be printed on a separate page preceding a report. SEFMAP Specifies a font mapping table different than the one specified in the JDL. SEPARATORS Specifies that the next data page in a report be used to generate segment separator sheets. SHIFT Specifies a shift of image on the page for binding purposes.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) Record-oriented Record-oriented DJDEs take effect immediately at the next record following the last record of the set of DJDE records of which they are a part; that is, after an END parameter, a compiled record-oriented DJDE takes effect immediately. 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.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) IDEN command To invoke DJDE processing, an IDEN command must be coded in the JDL. This command notifies the system that DJDE records may be part of the input data stream. It also describes the search criteria for locating and identifying DJDE records. The DJDE record (or records) are interspersed among the data records in the input data stream.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) OPRINFO This parameter specifies whether the DJDE record is to be printed to the tray or not. Syntax Options OPRINFO = option(s) Table 8-5 lists the parameter option(s) and definition(s). Table 8-5. OPRINFO parameter option(s) and definition(s) Option(s) Definition(s) YES Specifies that the DJDE record is to be printed and delivered to the tray. NO Specifies that the DJDE record will not be printed. The default is NO.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) SKIP This parameter offsets to the starting column of the DJDE parameters. Syntax Options SKIP = option(s) Table 8-7 lists the parameter option(s) and definition(s). Table 8-7. SKIP parameter option(s) and definition(s) Option(s) Definition(s) value Specifies the number of bytes (beginning at 0) from the beginning of the user portion of the record to the beginning of the DJDE parameters. It may be a negative number. The default is 1.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) DJDE record specification DJDE records are created by the user as part of the data stream. The system looks for them only if a DJDE prefix has been specified by an IDEN command within the JDL used to process the job. DJDE information is contained in one or more records, each of which may be up to the maximum record length specified for the job input data.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) XEROX DOCUPRINT 180 LPS PDL REFERENCE • After a set of DJDEs is terminated by an END parameter, there must be one or more data records before the next DJDE packet. DJDE records directly following a previously terminated DJDE parameter set are ignored. • If the file containing the DJDE is variable-blocked, the program that blocks the file may strip off trailing blanks.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) Application of DJDEs The following occurrences should be noted when using DJDE records: The specific parameters included in a DJDE packet are the only ones modified when the DJDE is applied. The only exceptions are the JDE=DJDE and JDL=DJDE, which cause all processing parameters contained in the JDE to be updated except for those listed in the “Job parameter modification restrictions” section.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) The normal page transition is caused by a skip from the bottom of a page to the top of the next, generally channel 1. The LPS knows a page transition has occurred only because the channel 1 assignment is on a line number less than the present line number of the current page, and therefore a page transition must have been created. Unfortunately, positioning to the old channel 1 line number has already occurred.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) DJDE operator information pages The changes to the JDE, specified in the DJDE, are incorporated when END parameter is encountered. The changes begin on the next record or page following the last DJDE record. The specification OPRINFO=YES in the JDE ensures that the DJDE records are printed and sent to the tray at the next page transition after an END parameter. The DJDE records are printed on a separate page from the report data.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) Table 8-8. Parameters which cannot be changed through a JDE (continued) Command Parameter(s) BLOCK All parameters RECORD All parameters BANNER All parameters Changing the online BANNER offset criteria or VOLUME command OPTIMIZE parameter in a selected JDE causes unpredictable results and should not be attempted. The selected JDE should specify all JDE parameters which stay the same as the original JDE as well as the changes.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) Duplex DJDE page printing When certain DJDEs (listed below) are invoked between an oddnumbered page (front side) and an even-numbered page (back side), the following printing sequence occurs. The odd-numbered page is printed as usual, but with a blank back side. What would have been printed on the back side (the even-numbered page) is printed on the front of the next sheet.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) Effect of multiple logical pages If multiple BEGINs are being used to define multiple logical pages on one physical page (as described in the “Multiple logical pages on physical page” section in the chapter "Print format commands") the following points should be considered: • With the exception of DEPT and SHIFT, all page-oriented DJDEs are applied at a logical page boundary.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) Online DJDE restrictions Online DJDE restrictionsIf an online job has header pages only (no trailers), DJDEs in the first header page of a report are recognized but not applied. Also, if headers only are defined, DJDEs invoked within the current report are applied to the first header page of the following report.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) DJDE parameter definitions The following sections describe the syntax of the command parameters and explanations of the parameter options. ALTER This parameter specifies new imaging parameters for graphics previously referenced using the hold (automatic reimaging) parameter. Syntax Options ALTER = option(s) Table 8-10 lists the parameter option(s) and definition(s). Table 8-10.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) ASSIGN This parameter specifies an assignment of a VFU channel number to a page line number or set of line numbers. It is possible to have multiple ASSIGN parameters within a DJDE. They take effect at the next record following a DJDE END parameter. DJDE assignments affect only those channel assignments specified. Other assignments remain the same.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) BSEQ Note: The DocuPrint 180 LPS does not support the barcode option. This syntax will cause the error message "Barcode reader not found continue I or Abort I" will be displayed at the beginning of the job. This parameter allows processing of barcode data streams with the ability to cross-check the three components of the system, namely, the PC-UI, the ESS and the IOT.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) BSKIP Note: The DocuPrint 180 LPS does not support the barcode option. This syntax will cause the error message "Barcode reader not found continue I or Abort I" will be displayed at the beginning of the job. This parameter specifies allows processing of barcode data streams with the ability to cross-check the three components of the system, namely, the PC-UI, the ESS and the IOT.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) Table 8-14. BSIDE parameter option(s) and definition(s) Option(s) Definition(s) ODD Indicates that the system will assign sequence and presence information assuming that only odd sides are to be considrered. The default is ODD. EVEN Indicates that only even sides will be considered when assigning sequence and presence information. If EVEN is coded for a simplex job, the job will contain no bar code sequence or presence information.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) BATCH This parameter is supported for online batch mode jobs only. It permits normal processing of online banner pages for batch mode jobs by delimiting the batch mode graphic data. It must be used precisely to mark the beginning and ending of online batch mode data. The first graphic (or IMAGE DJDE) must be preceded immediately by a BATCH=START DJDE, and the last graphic must be followed immediately by a BATCH=END DJDE.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) BFORM This parameter specifies that a form be printed on the back side of a user page (must have DUPLEX=YES). It takes effect as soon as the data is read into the system. BFORM parameters are the same as for the OUTPUT command. Syntax Options BFORM = option(s) Table 8-14 lists the parameter option(s) and definition(s). Table 8-17.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) BOF This parameter specifies the bottom-of-form line number. It takes effect at the next record following a DJDE END parameter. A value is defined the dame as for VFU BOF in the chapter "Print format commands." Syntax Options BOF = option(s) Table 8-15 lists the parameter option(s) and definition(s). Table 8-18.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) Table 8-19. BTEXT parameter option(s) and definition(s) Option(s) Definition(s) RNA=xxx Report name (maximum of 16 characters). This keyword is required in the first BTEXT of each report to be audited. It may only occur once per report. For clarity in relating the audit reports to SFS reports, this should be the same value used for job accounting. This parameter must be present to audit a job or report.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) Table 8-19. BTEXT parameter option(s) and definition(s) Option(s) Definition(s) DDE=[Y | N] Duplicate detection enablement. (Y)es indicates the audit report will flag duplicate sheets delivered. This option must be set to (N)o if multiple copies of a report or pages within the report are printed. For out-of-order deliveries, the job must be run in NOSEQ or BAR ALI mode so that the IOT will not catch and purge the mis-sequenced pages.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) Table 8-19. BTEXT parameter option(s) and definition(s) Option(s) Definition(s) PRA=nnn Page reconciliation amount. This is the total value of the page, up to 11 digits plus a decimal point may be specified. Commas are not allowed. This option is required in order to print an audit report reconciliation on amount. Note: This parameter is dependent upon the SEQ parameter. TXT=xx...x Identifying text. It may be up to 64 characters.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) Points to note Note these points when using the BTEXT command: • If RNA (report name) is not specified, no audit logging is performed. • Bar code text that prints on the pages is placed in the job stream by the application to enable barcode features. • Although the BTEXT command can be placed in the JSL, it will usually be placed in a DJDE as most of the parameters will be unique to a job.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) is processed. The ESS software does not check for this. It is up to the user to code the application correctly. • Multiple DJDE BTEXT commands on a page must appear in the same DJDE packet because only one page-oriented DJDE packet can take effect per page. • The BTEXT report parameter(s) must precede the first BTEXT page detail parameter. The ESS software does not check for this. It is up to the user to code the application correctly.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) • The maximum lingth of all BTEXT strings within a DJDE packet or in the JSL MESSAGE sommand is determined by the following: 509-N where N is the number of BTEXT commands in the JSL MESSAGE command or DJDE packet. Due to string length limitations, it is imperative that BTEXT strings not be padded with unnecessary blank characters. Example 1: $DJDEBTEXT=’RNA=CK0409,CJN=HR0525’,; $DJDEBTEXT=’RRA=1533249.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) Example 2 DJDE to print a report with sheet reconciliation only: $DJDE BTEXT=’RNA=Personnel Reviews, CJN=HR052,NSE=249’,; $DJDE BTEXT=’SEQ=1,TXT=326769 Harold R. Adams’,END; Example 3 Sample DJDE to audit a report with sheet reconciliation only, and without page details: $DJDE Example 4 BTEXT=’RNA=Admin 31,NSE=4230’,END; Sample JSL for a test run.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) CANCEL Cancels, effective on the current page, the hold (automatic reimaging) specified by the H parameter of an IMAGE or GRAPHIC parameter. Syntax Options CANCEL = option(s) Table 8-18 lists the parameter option(s) and definition(s). Table 8-22. CANCEL parameter option(s) and definition(s) Option(s) Definition(s) (name1 name identifies the graphic(s) being held. [,name2][,...] ) ALL Specifies that all graphics being held are to be cancelled.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) COPIES This parameter specifies the number of copies of a report to produce at the next page boundary. 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 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 zero is in effect are processed normally.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) DATA This parameter specifies the location and length of printable data within an input record. It takes effect at the next record following a DJDE END parameter. Syntax Options DATA = option(s) Table 8-21 lists the parameter option(s) and definition(s). Table 8-25.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) DUPLEX This parameter specifies whether printing is to occur on both sides of a page (duplex mode) or a single side (simplex mode). It takes effect on the next page boundary. Syntax Options DUPLEX = option(s) Table 8-23 lists the parameter option(s) and definition(s). Table 8-27. DUPLEX parameter option(s) and definition(s) Option(s) Definition(s) YES Selects duplex printing. NO Selects simplex printing.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) FEED This parameter controls the stock on which the page is printed. FEED=stock-reference references the stock assigned to a stockname by the STOCKSET command in effect at the time the page is printed. Syntax Options FEED = option(s) Table 8-24 lists the parameter option(s) and definition(s). Table 8-28.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) FILE This parameter provides a capability of loading files to the LPS disks while a print job is in progress. The print job may be invoked solely for the purpose of downloading permanent files. Although intended primarily for use with online systems, this parameter is not restricted to online use. Syntax Options FILE = option(s) Table 8-25 lists the parameter option(s) and definition(s). Table 8-29.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) FONTINDEX This parameter allows the user to specify a certain location in the input record where an index to the font to be used is stored. It takes effect on the next logical page boundary. The FONTINDEX parameters are the same as in the LINE command in the chapter "Print format commands." Syntax Options FONTINDEX = option(s) Table 8-26 lists the parameter option(s) and definition(s). Table 8-30.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) Options Table 8-27 lists the parameter option(s) and definition(s). Table 8-31. FONTS parameter option(s) and definition(s) Option(s) Definition(s) ((f1,s1 [LPI | XDOTS | DOTS]) [, (f2,s2 [LPI | XDOTS | DOTS]) ] [,...
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) FORMAT This parameter specifies an entirely new page descriptor entry (PDE) to be used for formatting control. It takes effect on the next page boundary. Syntax Options FORMAT = option(s) Table 8-28 lists the parameter option(s) and definition(s). Table 8-32. FORMAT parameter option(s) and definition(s) Option(s) Definition(s) pde-id Refers to a separately cataloged file in the PDE library on disk.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) Points to note Note the following when using the FORMAT and FORMS commands: XEROX DOCUPRINT 180 LPS PDL REFERENCE • Since there is ambiguity between the FORMAT and FORMS parameters, if either is abbreviated to the first three letters, the parameter defaults to FORMAT. • Paper size can only be changed in a job stream by using a JDE to call out the desired paper size, that is, through the PAPERSIZE parameter of the OUTPUT command.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) GRAPHICS This parameter specifies that the DJDE is a graphic sentinel. That is, it immediately precedes and identifies a graphic in the report data stream. This parameter, when specified, must be the only parameter in a DJDE packet. If no textual data has been previously encountered, the graphic is document interleaved and copied to an IMG type disk file.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) Options Table 8-30 lists the parameter option(s) and definition(s). Table 8-34. GRAPHICS parameter option(s) and definition(s) Option(s) Definition(s) (name,vpos{UN | CM | IN | DOTS | This option has the following components: XDOTS} name ,hpos{UN | CM | IN | DOTS | XDOTS} • Identifies the graphic. If document interleaved, it becomes ,[,H][,n[/d]]) the file name with which the IMG file is written.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) IMAGE In batch mode, this OVERPRINT = parameter defines new imaging parameters for subsequent graphics. In all other modes, it defines imaging parameters for the named graphic. Syntax Options IMAGE = option(s) Table 8-31 lists the parameter option(s) and definition(s). Table 8-35.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) The parameters T, H, and n/d are not order dependent. They may be coded as needed without extra position holding commas. If the UN parameter is used to define position, the UNITS parameter must precede this command in the OUTPUT command. Example IMAGE=(IMG1, 3, 2), END; INVERT This parameter specifies that the following pages are to be inverted.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) ITEXT This parameter specifies a text message to be output during input processing. It takes effect on the next page boundary. The parameters are the same as for the MESSAGE ITEXT parameter defined in the "Print format commands" chapter." Syntax Options ITEXT = option(s) Table 8-33 lists the parameter option(s) and definition(s). Table 8-37.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) JDL The jdl-id specifies the name of the JDL to be invoked at the next page boundary. The jdl-id must exist on disk in the JDL directory. If only JDL is specified (not JDE) in the DJDE, the JDE to be used is the one named in the START command. In a DJDE packet containing a JDL parameter, other record- or page-oriented DJDE parameters override parameters specified by the JDL DJDE.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) MARGIN This parameter specifies the left printing margin within each logical page. It takes effect at the logical page following a DJDE END parameter. The parameters are the same as in the LINE command defined in the chapter "Print format commands." Syntax Options MARGIN = option(s) Table 8-37 lists the parameter option(s) and definition(s). Table 8-41.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) MODIFY This parameter specifies the copy modification entry (CME) to be used in report processing. It takes effect at the next logical physical page boundary. A cme-id refers to a file which is separately cataloged in the CME directory. Refer to the “CME” section in the chapter "Print format commands" for further information. The parameters are the same as those in the OUTPUT command defined in the chapter "Print format commands.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) NUMBER This parameter specifies page numbering control. It takes effect on the next logical page boundary. The parameters are the same as those for OUTPUT command. Syntax Options NUMBER = option(s) Table 8-39 lists the parameter option(s) and definition(s). Table 8-43.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) OTEXT This parameter specifies a text message to be output to the operator during job printing. It takes effect on the next page boundary. The parameters are the same as for the MESSAGE command defined in the chapter "Print format commands." Syntax Options OTEXT = option(s) Table 8-40 lists the parameter option(s) and definition(s). Table 8-44.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) OVERPRINT This parameter specifies overprint control. Overprint lines are print lines whose carriage control specifies printing with no line spacing after the last printed line. It takes effect on the next record following a DJDE END; parameter. If FONTINDEX has been invoked in a JDE or DJDE, OVERPRINT takes effect at the next logical page boundary. OVERPRINT parameters are the same as for the LINE command.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) PMODE This parameter specifies the printing mode for each page. LANDSCAPE indicates that printing is to be parallel to the long edge of paper. PORTRAIT indicates that printing is to be parallel to the narrow edge of paper. If PMODE is changed through a DJDE command, the BEGIN command should be respecified (even if the same horizontal and vertical position has been specified in the previous BEGIN parameter).
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) RTEXT This parameter specifies text to be printed on a separate page preceding a report. It takes effect on the next page boundary. The parameters are the same as for the ROUTE command defined in the chapter "Print format commands." RTEXT parameters must be in ascending passnum sequence. Syntax Options RTEXT = option(s) Table 8-44 lists the parameter option(s) and definition(s). Table 8-48.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) SAVE This parameter must occur prior to or at the end of the report and specifies IMG files updated during the current report which are not to be purged when the report’s output processing is completed. This DJDE parameter is used to override, for specific files, automatic file deletions specified by PURGE=YES in the JDE’s OUTPUT command. Syntax Options SAVE = option(s) Table 8-45 lists the parameter option(s) and definition(s). Table 8-49.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) SEFMAP This parameter specifies a mapping table different than the one defined in the PDL command on a page-by-page basis. Syntax Options SEFMAP = option(s) Table 8-46 lists the parameter option(s) and definition(s). Table 8-50.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) SEPARATORS This parameter specifies that the printer software save an internal copy of the next data page in the report and use it to generate segment separator sheets. If separators are already in effect when this DJDE is encountered, it replaces the prior specification and subsequent separators are generated using the new specification. Syntax Options SEPARATORS = option(s) Table 8-47 lists the parameter option(s) and definition(s). Table 8-51.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) SF1FUNCTION This parameter specifies to the finisher whether (YES) or not (NO) to begin a particular operation on the current sheet. SF1FUNCTION invokes the C6 signal of the electronic interface between the LPS and a third party finishing device. Refer to your vendor’s third party device documentation for detailed information. Syntax Options SF1FUNCTION = option(s) Table 8-48 lists the parameter option(s) and definition(s). Table 8-52.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) SHIFT This parameter specifies a shift of the image on the page for purposes of binding. It takes effect on a physical page boundary. Syntax Options SHIFT = option(s) Table 8-50 lists the parameter option(s) and definition(s). Table 8-54. SHIFT parameter option(s) and definition(s) Option(s) Definition(s) v1 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.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) SIDE This parameter specifies repositioning of the new logical page to the first logical page of the given side of a physical sheet. It takes effect at a logical page boundary. The parameters are the same as for the RPAGE command. The SIDE DJDE triggers repositioning for only a single logical page and does not otherwise override the SIDE parameter of the RPAGE command. It is intended to be used instead of the RPAGE command, not with the RPAGE command.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) SNUMBER This parameter specifies that the printer merge the current segment sequence number into any subsequent segment separator sheets produced. SNUMBER can be modified as a DJDE under the following conditions: Syntax Options • Both SEPARATORS and SNUMBER are previously defined in either a JDE or JDL or as DJDEs. • If the SEPARATORS parameter is not specified in the EXPORT command, it must be specified as a DJDE, along with the SNUMBER DJDE.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) SPLIT This parameter specifies the use of segment management. When segment management is in effect, an end of segment condition occurs whenever max sheets (including separators) are generated or an end-of-copy or end-of-report condition occurs. Syntax Options SPLIT = option(s) Table 8-53 lists the parameter option(s) and definition(s). Table 8-57.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) SRECOVER This parameter specifies the recovery mode. When used as a DJDE, SRECOVER must be specified prior to the first data record in the report or it is ignored. Syntax Options SRECOVER = option(s) Table 8-54 lists the parameter option(s) and definition(s). Table 8-58. SRECOVER parameter option(s) and definition(s) XEROX DOCUPRINT 180 LPS PDL REFERENCE Option(s) Definition(s) PAGE Specifies standard jam recovery.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) STIMING This parameter is provided for possible compatibility with other Xerox software supporting third party finishing devices and is ignored by the Xerox DocuPrint 180 LPS. The STIMING DJDE, although ignored by the DocuPrint 180 LPS, specifies that the printer accommodate timing constraints needed by finishing equipment interfaced with the Programmable Bypass Transport.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) TMODE This parameter specifies process direction measurement for determining default pitch mode. Syntax Options TMODE = option(s) Table 8-57 lists the parameter option(s) and definition(s). Table 8-61. TMODE parameter option(s) and definition(s) Option(s) Definition(s) (width [,width unit]) This option has the following components: • width The process direction measurement that determines the default pitch mode.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) TRANS This parameter specifies whether or not transparencies are used in the print job. Syntax Options TRANS = option(s) Table 8-59 lists the parameter option(s) and definition(s). Table 8-63. TRANS parameter option(s) and definition(s) Option(s) Definition(s) YES Specifies that transparencies are used in the print job. NO Specifies that transparencies are not used in the print job.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) Points to note Note the following when using DJDE parameters: • TOF The DJDE top-of-form (TOF) command affects the first data record following the DJDE record. Depending on the time of a page transition, this may not take effect on the desired page. In other words, even though a DJDE TOF is processed during the processing of the next record, a page transition may have occurred before the DJDE TOF value could take effect.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) • SNUMBER If the system encounters a valid SNUMBER dynamic job descriptor entry after an incorrect EXPORT command SNUMBER parameter had been specified, unpredictable results may occur. SNUMBER as a DJDE may only be used to change current line or column numbers and fontindex values that are specified in the SNUMBER parameter of the EXPORT command used in the JDL.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) Example 2 Before the DJDE short-edge feed parameter, the contents of the memory font mapping table where: ((font1,font2),(font3,font4)) DJDE SEFMAP parameter: SEFMAP=((font1,font7),(font5,font6),REP); After this DJDE SEFMAP parameter is processed, the contents of the memory font mapping table are: ((font1,font7),(font5,font6)) XEROX DOCUPRINT 180 LPS PDL REFERENCE 8-71
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) DJDE FILE parameter This DJDE provides a capability of loading card-image or LPSlabeled files to the LPS disk while a printing job is in progress. The print job may be invoked solely for the purpose of downloading files; in other situations, the files may be interleaved with variable text data so that they are available when referenced by input or output processing.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) Points to note Note the following when using the DJDE FILE parameter: • If the file name or file type specified in the DJDE FILE parameter differ from those in the label record, the file is renamed as specified in the label record. This renaming feature for LPS-labeled files allows five restricted types of files to be downloaded as different file types. • If a disk file already exists with the specified file name, it is replaced.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) Card-image file processing The FILE parameter is checked for valid parameters, and an appropriate amount of disk space is made available for the file. • If the destination file type is not acceptable for a card-image file, the preceding DJDE packet is printed on an OPRINFO page together with the message: FILE PROCESSING ERROR - ILLEGAL DESTINATION FILE TYPE. Input then proceeds to read and discard the extent of the file.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) File processing mode is concluded, and print mode is resumed with the DJDE record unless the DJDE record contains another FILE parameter. LPS-labeled file processing The FILE parameter is checked for valid parameters, and the LPS label record at the beginning of the file is read. If the destination file type is acceptable, the file size field is obtained from the label record, and the extent of the file is calculated.
SPECIFYING DYNAMIC JOB DESCRIPTOR ENTRIES (DJDES) Delimited records for LPS-labeled files To prevent loss of data through trailing blank suppression procedures on the host spooler, data records for LPS-labeled files must be delimited by appending an extra non-blank character at the end of each record. The same non-blank character must be used with all records processed in the file processing mode.
9. 9Using graphics This chapter contains information on the following topics: • • • • • • • • Graphics considerations Input for graphics Processing modes Tape formats Online formats PDL command and DJDE options for graphics Performance Restrictions Graphics considerations There are several PDL parameters available for graphics handling. These include four JDE OUTPUT command parameters and six DJDEs. Tables 9-1 and 9-2 summarize these parameters.
USING GRAPHICS Input for graphics Named graphics may be input to the LPS through magnetic tape or the online channel. They may be input either separately from or interleaved with textual data. If input separately, they are recorded as permanent disk files. If interleaved with textual data, they may or may not be recorded as permanent disk files. (Refer to the “Processing modes” section for a discussion of this operation.
USING GRAPHICS Block mode In block mode, a graphic is obtained from the input data stream immediately following the textual data to be imaged on the same page (refer to the “Page interleaved” section of this chapter). The graphic is copied directly to the print file adjacent to the page's formatted textual information. Separate graphic disk files are not created. In block mode, the output software reads graphics from the print file into graphics memory.
USING GRAPHICS Document interleaved In this format, a report’s data stream begins with a set of one or more graphics prior to the first record of text. These graphics are copied one at a time to named IMG disk files. When the report has finished printing, the IMG files created are automatically deleted, unless the user has explicitly specified otherwise.
USING GRAPHICS Batch mode In this mode, a report contains only graphics imaged one per page and an optional IMAGE DJDE preceding each graphic. These graphics are copied to the print file and processed as block mode graphics. Rules 1 and 4 for document interleaved graphics apply (refer to the “Document interleaved” section). Note: Block or record delimiters are not permitted. Except for the graphics themselves, the input stream may contain only optional DJDE IMAGE records.
USING GRAPHICS Online formats This section covers the following topics: • • • • • Noninterleaved Document and page interleaved Batch mode Document interleaved graphic file transfers Management of image files Noninterleaved HOSTCOPY is the mechanism for transferring noninterleaved graphics through the online channel to disk. The HOSTCOPY utility supports IMG files in Xerox system tape format.
USING GRAPHICS parameters for subsequent graphics. The actual batch mode data stream is defined by the BATCH=START and BATCH=END DJDEs. • There is no change in the maximum record length when processing batch mode graphic records. However, every record within the graphic must be terminated by a byte containing an appended terminating character which is the same for all records of the graphic.
USING GRAPHICS PDL command and DJDE options for graphics Several PDL commands are available for graphic handling. These include four job descriptor entry (JDE) OUTPUT commands and six dynamic job descriptor entries (DJDEs). Tables 9-1 and 9-2 summarize these commands. The DJDEs are record oriented because they take effect immediately. For example, the ALTER, CANCEL, and IMAGE commands may appear anywhere on the page and are applied to the page on which they occur.
USING GRAPHICS Performance This section covers the following topics: • • • Random mode Online Document interleaved file creation Random mode Random mode requires a separate disk access by the output processing task for every graphic on a page. The more graphics on a page and the larger the graphics, the more likely it is that paper path holes are created. Online It should be noted that sending interleaved graphics across the online interface impacts system performance.
USING GRAPHICS Restrictions This section summarizes graphic restrictions, some of which have been mentioned elsewhere in this document. These restrictions are grouped according to whether they affect graphic features. Graphic feature restrictions Note the following graphic feature restrictions: • Tape formats supported by interleaved graphic processing are restricted to LPS compatible fixed or variable record structures, that is, RECORD STRUCTURE = F, FB, V, or VB only.
A. APDL command and DJDE summary This appendix may be used as a quick reference for information about PDL commands and command parameters. The following definitions describe the conventions used in this appendix. Conventions Symbols used in the command syntax are listed in table A-1. Table A-1. Symbols used in command syntax Symbol Meaning ac Command identifier. Consists of 1 to 6 alphanumeric characters (A through Z and 0 through 9). One of the characters must be alpha. dd Command identifier.
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) Command Parameter Default LPS DJDE orienta Offline Online -tion ac:PCC ADVTAPE ASSIGN DEFAULT INITIAL MASK YES — DEFAULT TOF X’FF’ All All All All All Y Y Y Y Y N N N N N — — — — — ac:PDE BEGIN FONTS PMODE .18 IN, .
PDL COMMAND AND DJDE SUMMARY Table A-2.
B. BPDL command quick reference Conventions Symbols used in the command syntax are listed in table A-1. Table B-1. XEROX DOCUPRINT 180 LPS PDL REFERENCE Symbols used in command syntax Symbol Meaning ac Command identifier. Consists of 1 to 6 alphanumeric characters (A through Z and 0 through 9). One of the characters must be alpha. dd Command identifier. Same as ac except restriction of having one alpha character is removed.
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 (continued) Command Syntax Default OUTPUT OUTPUT BFORM = {form-id | (form-id[,ini | t[,copies]][,INK[S],inkref[,inkref][,...])} NONE OUTPUT COLLATE = {YES | NO} YES OUTPUT COPIES = number 1 OUTPUT COVER = cover-opt NONE OUTPUT CYCLEFORMS = {form-id[,form-id],...) | (form-id[,(INK[S],inkref[,inkref],...)]) | ([,form-id[INK[S],inkref[,inkref]...
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 (continued) Command Syntax Default ac:STOCKSET ASSIGN = {stock-descriptor | (stock-descriptor1[,stock-descriptor2][,...])} — ac:STOCKSET IN I FEED = {stock-name | stock-reference} first stock-name — ac:STOCKSET SYSPAGE = {stock-name | stock-reference | MAIN | AUX} ac:SYSTEM ac:TABLE ac:TCODE ac:VFU VOLUME — ac:TABLE CONSTANT = (sc1[,sc2][,...]) — MASK = (ignore-chart([,charspeci1],charspeci2][,...
PDL COMMAND QUICK REFERENCE B-8 XEROX DOCUPRINT 180 LPS PDL REFERENCE
C. CCharacter code assignment This appendix illustrates the following character code assignments: • • • • • • • • IBM BCD code set Honeywell 200/2000 BCD code set Honeywell 6000 BCD code set Fieldata translation UNIVAC ASCII character set Standard ASCII character set Standard EBCDIC character set Xerox EBCDIC to extended ASCII hexadecimal translation values IBM BCD code set Figure C-1 presents the IBM BCD code set. Figure C-1.
CHARACTER CODE ASSIGNMENT Honeywell 200/2000 BCD code set Figure C-2 presents the Honeywell 200/2000 BCD code set. Figure C-2.
CHARACTER CODE ASSIGNMENT Honeywell 6000 BCD code set Figure C-3 presents the Honeywell 6000 BCD code set. Figure C-3.
CHARACTER CODE ASSIGNMENT Fieldata translation Figure C-4 presents the Fieldata translation. Figure C-4.
CHARACTER CODE ASSIGNMENT UNIVAC ASCII character set Figure C-5 presents the UNIVAC ASCII character set. Figure C-5.
CHARACTER CODE ASSIGNMENT Standard ASCII character set Figure C-6 presents the standard ASCII character set. Figure C-6.
CHARACTER CODE ASSIGNMENT Standard EBCDIC character set Figure C-7 presents the standard EBCDIC character set. Figure C-7.
CHARACTER CODE ASSIGNMENT Xerox EBCDIC to extended ASCII hexadecimal translation values Figure C-8 presents the Xerox EBCDIC to extended ASCII hexadecimal translation values. Figure C-8.
D. DOffline specifications This appendix provides offline specifications. Input unpacking examples Figure D-1 shows several input unpacking examples. Figure D-1.
OFFLINE SPECIFICATIONS Valid host computer and label specifications Figure D-2 shows the valid host computer and label specifications. Figure D-2.
OFFLINE SPECIFICATIONS Each shaded area of this table shows the label that is substituted by PDL when an invalid host/label pair is specified. Each X indicates a valid label specification parameter for each type of host. Host system JDLs on system software tape Job description library (JDL) source files supplied on operating system software (OSS) tape are summarized in table D-1. Table D-1.
OFFLINE SPECIFICATIONS Table D-1. JDL source files on OSS tape (continued) JDL JDEs provided for XEROX ANSI-labeled tapes Unlabeled tapes Xerox ANSI-labeled tapes JDEs to print unknown tapes Printing tapes without attempting to deblock the tape properly After an LPS software system is created by the user, the source for these JDLs is resident in the JSL directory. Use the Editor PRINT parameter or the PDL compiler to obtain a printout of the JDL(s) desired.
E. EEditor quick reference This appendix summarizes the basic Editor commands and steps for creating and modifying JSLs. For detailed information on using the Editor, refer to your Xerox DocuPrint 180 LPS Operations Reference. Note that you may enter the Editor commands by keying in only the first three letters, for example, CLEAR can be entered as CLE, and INSERT can be entered as INS.
EDITOR QUICK REFERENCE full command line, a continuation of a previous command line, or a comment line. For example, if you wish to add line 00011, following 000010, you would simply enter 11. Step 6. Input the text, your JSL coding, by entering the text after the line number which appears on the system controller display. For example, the display would show: EDIT>INSERT 10,10 00010.
EDITOR QUICK REFERENCE DISPLAY • Display a particular portion of the work file by entering: DISPLAY n-y n is the starting line number to be displayed. y is the ending line number to be displayed. • Display a single line, or record, of the work file by entering: DISPLAY n n is the desired line. • Display a particular word or phrase within a work file wherever it exists by entering: FIND/x/ x is the word or phrase to be found and displayed.
EDITOR QUICK REFERENCE Modifying a portion of the work file line To modify portions of a line, you must first enter: MODIFY n n is the number of the line to be modified, for example, MODIFY 60. Then you can perform any of the following activities: • Substituting one set of characters for another by entering: S/x/y or C / x / y / x is the text to be replaced. y is the text to be inserted.
EDITOR QUICK REFERENCE • Insert a set of characters following other characters by entering: F/x/y/ x is the word preceding the text to be added. y is the text to be added. or F [k]/x/y/ k is the occurrence of string x in each line specified in the MODIFY command that is affected by the F command. k defaults to 1 when not specified, while 0 indicates that all occurrences of the first set of characters, or string x, in the specified lines are affected. Add a space between F and k in the command.
EDITOR QUICK REFERENCE n is the starting line number. m is the ending line number. i is the increment of line numbering you want. This command deletes all lines from n to m. It initiates automatic line numbering at n for you to enter code and increments each line by your value for i. • Renumber lines of text by entering: RENUMBER n,i n is the starting line number. i is the increment of line numbering you want. After modifying a file, you may find significant gaps in the sequence of line numbers.
Glossary A3 Paper size measuring 297 by 420 mm. A4 Paper size measuring 210 by 297 mm. abort To terminate the printing of a job or execution of a program before it completes. algorithm Computational procedure that can be repeated any number of times. alignment Positioning of an image on a page for printing. alphanumeric AIM ASCII application applications software ascender Set of characters including the letters A through Z, numerals 0 through 9, and all printable special symbols.
GLOSSARY auxiliary menu B4 background job Menu that contains options not displayed in a window. The symbol for an auxiliary menu is a box containing three horizontal lines. Paper size measuring 250 by 353 mm. Low-priority job, usually batched, that is executed automatically as system resources become available. backup file File copied to a storage medium for safekeeping in case the original is damaged or lost.
GLOSSARY bit map Visual representation of graphic images in which a bit defines a picture element (pixel); for example, if a bit is 1, the corresponding pixel is printed. bit mapped Display image generated bit by bit for each point or dot. A softwaredriven scanner is used to create characters or graphics. blocking Process of combining two or more records into a single block of data which can then be moved, operated upon, or stored, as a single unit by the computer.
GLOSSARY character character cell character code Digitized space containing a single character within a font set. Code representing alphanumeric information, for example, ASCII. character code identifier Code associated with the universal identifier “Xerox” to indicate the version of the Xerox character code standard used to code Interpress strings. character set Number of different characters used by a particular device, including alphabetic, numeric, and special characters such as symbols.
GLOSSARY communication line Telecommunication line connecting devices at one location with devices at other locations in order to transmit and receive information. communication link Physical means, such as data link, connecting one location to another to transmit and receive information. communications compatibility Ability of two devices to transmit information to each other.
GLOSSARY copy-sensitive Term used to indicate jobs in which multiple copies of a report will contain different data, as with paychecks and banking statements. cpi characters per inch. Designates the number of characters per inch for a particular typeface. See also pitch. CPU central processing unit. Interprets and executes instructions, performs all operations and calculations, and controls input and output units and auxiliary attachments. data 1.
GLOSSARY descender desktop Portion of alphabetic character that extends below the baseline. See also ascender, x height. Basic display screen of the PC UI. device Any piece of hardware other than the central processing unit (CPU). digitize To express or represent data in digital (binary) form so that it can be processed electronically. disk drive display DJDE DMR Device that can read or write magnetic media.
GLOSSARY elite embedded blanks Blank spaces within a command line. Ethernet Xerox local area network (LAN) that allows data to be transmitted by cable from one device to another, enabling it to share the network. extended metrics Measurements used in Interpress to alter the size of fonts, allowing more precision with character escapement. Used for rendered characters. FCB forms control buffer. Buffer for controlling the vertical format of printed output. FDL forms description language.
GLOSSARY font Set of images, usually characters and symbols, having common characteristics such as style, width, height, and weight. form 1. Compiled forms source library (.FSL) file. 2. Printed or typed document with blank spaces for inserting information. Specific arrangement of lines, text, and graphics stored in a computer under an identifying name. Page of data that, when preceded by proper commands, is stored on the system disk as a permanent file.
GLOSSARY hardware Physical components, such as mechanical, magnetic, and electronic elements of a system, as opposed to programs, procedures, rules, and associated documentation. Hardware is operated by software and firmware. HCF high-capacity feeder. Feeder tray capable of holding 2500 sheets of 20 pound/75 gsm paper. The high-capacity feeder trays are the primary paper supply for the DP180 LPS. They are located in the bottom half of the feeder/stacker modules. HCS high-capacity stacker.
GLOSSARY input processing insert interface Formatting control for the pages of a report. To add text or graphics to a document. Device by which two systems connect and communicate with each other. interpolation Series of logical rules implemented in the printer to convert a 300 spi input video stream to a 600 spi output video stream. Interpolation is functionally analogous to bit doubling (2x scaling), except the logical rules result in superior output.
GLOSSARY label landscape page orientation Orientation of print lines or top of an illustration parallel to the long edge of the paper if the sheet is within the standard size range. (Sheets larger than standard have the reverse print orientation.) language Defined set of characters and symbols combined together by specific rules. See also high-level language; low-level language. laser printing Technology that uses a laser to transfer character forms to a page by direct or indirect means.
GLOSSARY literal load location Alphanumeric beginning with a letter, optionally including an asterisk, period, colon, or slash, and not enclosed in single quotes. To enter data into storage or working registers. Place in which data can be stored. log Collection of messages or message segments placed on an auxiliary storage device for accounting or data collection purposes. logical page In the Xerox printing systems environment, a formatted page that is smaller than the physical page.
GLOSSARY media Vehicles or devices by which information is stored or transmitted. Classifications include source, input, and output. medium Object or material on which data is stored, for example, magnetic tape or floppy disk. memory Space in a device where information is kept, or the ability of a device to keep information until needed. menu message Unit of information transmitted by one facility to another in a form that the receiving facility can understand and act upon.
GLOSSARY nonimpact printer object file Printer that forms characters without any strikes of a key or element against the paper. Source file converted into machine language (binary code). offline Devices not under the active control of a central processing unit. For example, a computer makes output to a magnetic tape. The tape is then used by an offline printing system to produce printed data. Offline operations are much slower than online operations. See also online.
GLOSSARY overprint lines Print lines whose carriage control specifies printing with no line spacing after the last printed line. overprint ratio Maximum number of variable data and form characters that may be intersected by a single scan line. override overstrike page page orientation parameter pass-through job To print characters over each other. 1. In computer programming, a block of instruction, data, or both that can be located in main or auxiliary storage. 2.
GLOSSARY intensity. Pixels are definable locations on a display used to form images. For graphic displays, more pixels generally provide higher resolution. Spots, dots, and pixels are used interchangeably. point Unit of measurement equal to 0.0139 inch. Points are always used to express type size and leading. There are 12 points to a pica and about 72 points to every inch. See also pica. point size Height of character set from the top of its ascenders to the bottom of its descenders in units (points).
GLOSSARY purge To delete data from a system. queue List of documents waiting to be processed. RAM raster data rasterization read/write head record Binary data, usually consisting of dots arranged in scan lines, according to the print order. Creation of a page’s bit map image for printing. Input/output device that reads and writes data in the form of magnetic dots on the surface of an external storage medium, such as a magnetic disk. Collection of data or words treated as a unit.
GLOSSARY scroll bar SCSI secondary storage Part of a window that allows you to view information extending beyond the window display. small computer system interface. Accepted standard for connecting peripheral devices to computers. Form of storage external to a system, such as magnetic tapes or floppy disks. security 1. Procedure for limiting access to the system resources, programs, or files, to authorized personnel. 2. Protecting programs and files from unintentional or undesired modification.
GLOSSARY special processing spooling Process of releasing data from main memory and storing it temporarily until a peripheral device is ready to accept it, for example storing text before sending it to a printer. spot Unit of measurement representing a fraction of an inch, for example, 300 spots per inch (spi). May also be referred to as a picture element (pixel) or dot. statement Detailed written instructions in a program step. A statement is written according to specific rules called syntax.
GLOSSARY system disk system file system generation system page Magnetic disk storage medium, usually of large capacity, that is not removable as opposed to floppy disk or disk packs. Master software program that keeps all components working together. Process whereby the system is made ready to operate. Typically involves selecting the operative parameters and activating the relevant software. Maximum area in which text and graphics can be imaged on a printing system.
GLOSSARY terminal Device equipped with a keyboard and connected to a computer or a network testing 1. Process of running a program for the express purpose of discovering any errors it may contain. 2. For computer-oriented systems, the process of verifying a system’s ability to meet performance objectives in a simulated environment or validating its actual performance in a live environment. text text string throughput Consecutive series of characters to be printed exactly as specified in a command.
GLOSSARY type style UCS Italic, condensed, bold, and other variations of typeface that form a type family. Universal Character Set. Printer feature that permits the use of a variety of character upload To copy files from a remote peripheral device to a host. LPS files are not copied to the host because one of the LPS functions is to store files for the host.
GLOSSARY x axis xdot Unit of measurement representing a fraction of an inch. It may also be referred to as a picture element (pixel) or spot, for example, 1/600 spots per inch (spi). xerographic engine Component of a printer that develops an image, transfers it to paper, and fuses it for output as hardcopy. x height y axis Height of lowercase letters without their ascenders or descenders (height of letter “x”). See also ascender; descender.
GLOSSARY CPU CR DCE DDCMP central processing unit carriage return data communications equipment Digital Data Communication Message Protocol DEC Digital Equipment Corporation DFA Document Feeding and Finishing Architecture DJDE dynamic job descriptor entry DMR data mode ready (DEC interface for LPS) DOS disk operating system dpi DSDD dots per inch double sided double density DSU digital signal unit DSR disk save and restore DSSD DTE EBCDIC ENET EOT EP double sided single density data term
GLOSSARY FDL forms description language FDR file directory FFM font file management FIS Font Interchange Standard FMS file management subsystem FPS formatting print service FSL forms source library FST font specification table GCR group code recording gsm grams per square meter HCF high-capacity feeder HCS high-capacity stacker HFDL HIP hpos Host Interface Processor horizontal positioning IBM International Business Machines Corporation IFU Interpress font utility IG IGM I/O G
GLOSSARY IPFONTS Interpress fonts IPL initial program load IPM Interpress mapping ips inches per second JCB job control block JCL job control language JDE job descriptor entry JDL job descriptor library JID job identifier JSL job source library LAN local area network laser light amplification by stimulated emission of radiation LED light-emitting diode LEF long-edge feed LF long-edge feed lpi lines per inch LPS Laser Printing System MTU magnetic tape unit (refers to the 9
GLOSSARY OSDS OSEXEC OSS PC PCC PC UI PDL PE operating system executive operating system software personal computer printer carriage control personal computer user interface print description language phase encoded ppm pages per minute PQA print quality adjustment PROM PSC pt PWBA QIC programmable read-only memory printer subsystem controller point printed wiring board assembly 1/4 inch cartridge RAM random access memory ROS raster output scanner SAFES SAN sci SCSI SDLC SEF GLOSSARY-28 operat
GLOSSARY SFS status file services SIF sequence insert file SNA spi SST system network architecture spots per inch system software tape sysgen system generation TL/DL text line/display list TOF top of form tpi tracks per inch TPJ test pattern job TXC total xerographic convergence UCS Universal Character Set UCSB Universal Character Set Buffer UI user interface VM virtual memory vpos VS WAN vertical positioning virtual storage wide area network XCSC Xerox Customer Support Center
GLOSSARY GLOSSARY-30 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 XEROX DOCUPRINT 180 LPS PDL REFERENCE
Index Numerals 3211/4245 mode, 4-56 4850/4890 HighLight Color LPS applications, 3-28 to 3-30 forms, 3-29 to 3-30 4050/4090/4650/9700F LPS, creating applications, 3-30 running jobs, 3-30 A ABNORMAL command, 6-2 to 6-9 ABORT parameters, 6-3 ac:CME command, 6-17 to 6-23 accounting data, 6-10 installation reports, 6-12 to 6-14 usage, overall, 6-10 to 6-11 ACCT command parameters specifying JSL, 3-11 print format, 6-10 to 6-16 ACCTINFO parameter, 7-37 ADJUST parameter, 4-2 Advanced Image Subsystem (AIS), 1-2 AL
INDEX features, 5-1 processing overview, 5-1 specifying, 5-3 to 5-4 storing MAIN, 5-2 AUX, 5-2 AUTO, 5-2 usage, 5-3 CMEs cataloged, 6-18 specific commands, online, 4-59 specifying, 6-17 using, 3-13 CODE command ASSIGN parameter, 4-9 DEFAULT parameter, 4-10 coded instructions, see programs coding features, 2-16 process, 2-16 COLLATE parameter DJDE, 8-25 OUTPUT, 6-48 columns, creating JSL, 3-9 combining modes, 7-8 commands END, 2-13 IDEN parameter, 1-6 JOB, 2-13 keyword, 2-3 levels catalog, 2-12 to 2-13 JDE,
INDEX defining characteristics, 6-31 clusters, 5-5 to 5-9 paper requirements, 3-13 system responses, 6-3 deleting specialized records, 7-24 delimiter accounting page, 7-36 display, 7-36 modes, 7-35 parameters, 7-38 DENSITY parameter, 6-51 DEPT parameter, 6-15 DESTINATION parameter DJDE command, 8-27 JSL command, 3-14 OUTPUT command, 6-51 disk access, separate, 9-9 creating system, E-1 to E-6 stored files, E-2 display, status, 7-36 DJDEs application, 8-11 to 8-12 file effectiveness, 8-64 parameter, 8-63 to
INDEX G graphics considerations, 9-1 DJDE options, 9-8 feature restrictions, 9-10 handling modes batch, 9-2 to 9-3 block, 9-2 to 9-3 move, 9-2 random, 9-2 inputting, 9-2 memory, 1-2 online, 9-9 parameters DJDE, 8-36 to 8-37 OUTPUT command, 6-56 PDL command options, 9-8 performance, 9-9 position, 6-72 random mode, 9-9 restrictions, 9-10 grouping PDL commands, 2-16 H H2 and H6 constants, 2-8 hardware components, 1-2 firmware, 1-2 HCOUNT parameter, 7-14 hexadecimal constants, 2-7 hierarchy of replacement, 2-1
INDEX JSL columns, 3-9 creating, 3-10 to 3-16 editor, 3-10 identifier, naming, 3-10 requirements, 3-9 specifying, 3-9 structure, 2-10 to 2-15 VFU, 3-10 K keyword constant, 2-6 L Laser Printing System, see LPS LENGTH parameters, 4-4 levels Command, 2-10 to 2-11 ID catalog, 2-12 END, 2-13 to 2-15 JDE, 2-13 JDL, 2-12 JOB, 2-13 system, 2-12 LINE command ac:CME, 6-20 parameters, 6-31 to 6-41 references, 3-11 LINENUM parameters, 7-5 list parameter options, 2-5 LMULT parameters, 4-4 log, page, 1-6 logical pages,
INDEX recovery, 4-63 report separation, 4-59 restrictions, DJDE, 8-18 specific commands CMEs, 4-59 DJDE processing, 4-59 JDE, creating, 4-57 to 4-58 JDL, creating, 4-57 to 4-58 optimization, 4-59 Operator Communication Subsystem, see OCS operator functions, restricting, 6-2 information, DJDE, 8-13 operating system executive, 1-5 software, 1-3 to 1-4 OPRINFO parameter, 8-7 options, cover parameter, 6-49 ordered stocks, 5-9 OSTK parameter, 6-63 OTEXT parameter ABNORMAL command, 6-6 DJDE command, 8-45 MESSAGE
INDEX RECORD command parameters ADJUST, 4-19 CONSTANT, 4-20 FORMAT, 4-20 LENGTH, 4-21 LMULT, 4-21 LTHFLD, 4-22 OFFSET, 4-22 POSTAMBLE, 4-23 PREAMBLE, 4-23 STRUCTURE, 4-24 formats, 4-68 structure, 4-68 recovery, automatic, 6-8 registration shift and skew landscape, 3-23 portrait, 3-24 margins, maintaining, 3-24 REP parameter, 6-7 replacement, hierarchy, 2-16 to 2-20 reports batch mode, 9-6 processing, 9-6 online, 9-6 separation, 7-13 Report task (RPT), 1-6 repositioning logical page, 7-29 RESOLUTIONs parame
INDEX output requirements, 3-14 VFUs, 3-10 SPLIT parameter DJDE command, 8-56 EXPORT command, 6-27 SRECOVER parameter DJDE command, 8-57 EXPORT command, 6-28 standard character set ASCII, C-6 EBCDIC, C-7 Start command, 1-8 status display, 7-36 STIMING parameter DJDE command, 8-58 EXPORT command, 6-28 STOCKS parameter DJDE command, 8-58 OUTPUT command, 6-28 STOCKSET applications, 5-4 changes, 5-9 command, 6-96 to 6-98 string comparisons, 7-10 constants ASCII, 2-7 character, 2-7 EBCDIC, 2-7 to 2-8 H2 and H6,
INDEX PLABEL, 4-51 RMULT, 4-52 RSAT, 4-52 TCODE, 4-53 UNPACK, 4-54 V valid host specifications computer, D-2 to D-3 label, D-2 to D-3 value constants, 2-6 variable data, 1-6 name constants, 2-6 VFU parameter 6-99 to 6-102 VOLUME command parameters BMULT, 4-39 CODE, 4-40 to 4-41 EOV, 4-41 HOST, 4-41 to 4-43 INTERPRESS, 4-44 LABEL, 4-45 LCODE, 4-46 LPACK, 4-47 MAXLAB, 4-47 MINLAB, 4-48 OPTIMIZE, 4-49 OSCHN, 4-50 OSHDP, 4-50 OSTLP, 4-51 XEROX DOCUPRINT 180 LPS PDL REFERENCE W WAIT messages, 6-6 work file,
INDEX INDEX-10 XEROX DOCUPRINT 180 LPS PDL REFERENCE
