Xerox DOCUPRINT 4890, DOCUPRINT 4850 User Manual

XEROX

Xerox 4850/4890 HighLight Color

Laser Printing Systems

Print Description Language Reference

Version 5.0 November 1994 720P93590

Xerox Corporation

701 S. Aviation Boulevard

El Segundo, CA 90245

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

Publication number: 720P93590

Xerox® and all Xerox products mentioned in this publication are trademarks of Xerox Corporation. Products and trademarks of other companies are also acknowledged.

Changes are periodically made to this document. Changes, technical inaccuracies, and typographic errors will be corrected in subsequent editions.

This document was created on the Xerox 6085 Professional Computer System using VP software. The typefaces used are Optima, Terminal, and monospace.

Introduction			xiii

	Document conventions		xiii

1. Overview			1-1

	Input data streams		1-1

	Offline mode		1-2

		Host tape formats	1-2

		Data representation	1-2

		Packed data formats	1-2

		Record formats	1-3

		Record structure	1-3

		Multivolume processing	1-3

	Online mode		1-4

		4245 processing mode features	1-4

		Online-specific commands	1-4

		DJDE processing	1-4

		Copy-sensitive CMEs	1-5

		Report separation	1-5

		Online record length	1-5

		Online recovery	1-6

		Online dump	1-6

		Downloading files from the host to the LPS	1-9

		FCBs	1-10

		Vertical format control processing	1-10

		UCSBs for 3211	1-11

	PDL command and DJDE syntax		1-12

		Command length	1-13

		Identifiers	1-13

		Command keywords	1-14

		Parameter keywords	1-14

		Parameter options	1-14

		Value constants	1-15

		String constants	1-15

	JSL structure		1-18

		JDL name	1-18

XEROX 4850/4890 HIGHLIGHT COLOR LPS PRINT DESCRIPTION LANGUAGE REFERENCE

iii

TABLE OF CONTENTS

		ID level	1-18
		System or JDL level	1-18

		Catalog level	1-19

		Job or JDE level	1-19

		Comments	1-19

		END command	1-20

		Hierarchy of replacement	1-20

		PDL library	1-22

	JDL creation		1-25

		Required components of a JSL	1-25

		Steps in creating a JDL	1-25

	JDL coding		1-26

	Data definition commands		1-26

	Print format commands		1-27

	Printer control (DJDE) commands		1-28

		DJDE orientation	1-29

		DJDE record specification	1-33

		Application of DJDEs	1-34

		DJDE operator information pages	1-36

		Job parameter modification restrictions	1-36

	Logical processing commands		1-38

		Logical processing command format	1-39

		Logical processing commands with TEST parameters	1-40

		TEST expression definition	1-40

		String comparison concepts	1-41

		Character types	1-42

		Masked comparisons using default type assignments	1-42

	JSL compilation		1-43

		Printing a job	1-43

2. Data definition commands			2-1

	BLOCK command		2-1

		ADJUST	2-1

		CONSTANT	2-1

		FORMAT	2-2

		LENGTH	2-2

		LMULT	2-3

		LTHFLD	2-3

		OFFSET	2-3

		POSTAMBLE	2-3

		PREAMBLE	2-4

iv	XEROX 4850/4890 HIGHLIGHT COLOR LPS PRINT DESCRIPTION LANGUAGE REFERENCE

		TABLE OF CONTENTS
	ZERO	2-4

	Example	2-4

ac:CODE command		2-5

	ASSIGN	2-5

	DEFAULT	2-6

	Examples	2-6

IDEN command		2-6

	OFFSET	2-7

	OPRINFO	2-7

	PREFIX	2-7

	SKIP	2-8

ac:PCC command		2-8

	ADVTAPE	2-9

	ASSIGN	2-9

	DEFAULT	2-10

	INITIAL	2-11

	MASK	2-11

	Example	2-11

RECORD command		2-12

	ADJUST	2-12

	CONSTANT	2-12

	FORMAT	2-12

	LENGTH	2-13

	LMULT	2-13

	LTHFLD	2-13

	OFFSET	2-13

	POSTAMBLE	2-14

	PREAMBLE	2-14

	STRUCTURE	2-14

	Example	2-14

ac:TCODE command		2-16

	DEFAULT	2-17

	TASSIGN	2-17

	TRESET	2-19

VOLUME command		2-20

	BMULT	2-20

	CODE	2-20

	EOV	2-21

	HOST	2-22

	INTERPRESS	2-22

XEROX 4850/4890 HIGHLIGHT COLOR LPS PRINT DESCRIPTION LANGUAGE REFERENCE

TABLE OF CONTENTS

		LABEL	2-24
		LCODE	2-24

		LPACK	2-24

		MAXLAB	2-25

		MINLAB	2-25

		OPTIMIZE	2-25

		OSCHN	2-26

		OSHDP	2-26

		OSTLP	2-26

		PLABEL	2-26

		RMULT	2-27

		RSAT	2-27

		TCODE	2-27

		UNPACK	2-28

		VCODE	2-28

		Examples	2-30

3. Print format commands			3-1

	ABNORMAL command		3-1

		ERROR	3-1

		IMISMATCH	3-2

		ISUBSTITUTE	3-3

		OTEXT	3-4

		SECURITY	3-5

	ACCT command		3-6

		DEPT	3-6

		USER	3-7

		Example	3-8

	ac:CME command		3-8

		CONSTANT	3-8

		FONT	3-9

		INK	3-10

		LINE	3-11

		POSITION	3-12

	EXPORT command		3-12

		Interactions between EXPORT PDL statements and
		EXPORT DJDEs	3-12
		SEPARATORS	3-13

		SNUMBER	3-14

		SPLIT	3-14

		SRECOVER	3-15

vi	XEROX 4850/4890 HIGHLIGHT COLOR LPS PRINT DESCRIPTION LANGUAGE REFERENCE

		TABLE OF CONTENTS
	STIMING	3-15

ac:IDR command		3-16

	ICATALOG	3-17

	ILIST	3-17

	PALETTE	3-18

LINE command		3-18

	DATA	3-18

	FCB	3-18

	FONTINDEX	3-19

	INKINDEX	3-20

	MARGIN	3-21

	OVERPRINT	3-21

	PCC	3-22

	PCCTYPE	3-22

	UCSB	3-23

	VFU	3-23

	Examples	3-23

MESSAGE command		3-25

	ITEXT	3-25

	OTEXT	3-25

OUTPUT command		3-26

	BFORM	3-28

	COLLATE	3-29

	COPIES	3-30

	COVER	3-30

	CYCLEFORMS	3-30

	DENSITY	3-32

	DESTINATION	3-32

	DUPLEX	3-32

	FACEUP	3-33

	FEED	3-33

	FORMAT	3-33

	FORMS	3-35

	GRAPHICS	3-36

	IDFAULT	3-37

	IDR	3-37

	IMAGE	3-38

	IRESULT	3-39

	LOGO	3-40

	MODIFY	3-41

XEROX 4850/4890 HIGHLIGHT COLOR LPS PRINT DESCRIPTION LANGUAGE REFERENCE

vii

TABLE OF CONTENTS

		NTO1	3-42
		NUMBER	3-43

		OFFSET	3-43

		PAPERSIZE	3-44

		PURGE	3-45

		RESOLUTION	3-45

		SF1FUNCTION	3-45

		SF2FUNCTION	3-46

		SHIFT	3-46

		SIZING	3-47

		STAPLE	3-47

		STOCKS	3-48

		UNITS	3-48

		XMP	3-48

		Examples	3-49

	ac:PDE command		3-49

		Multiple logical pages on physical page	3-50

		BEGIN	3-51

		FONTS	3-52

		PMODE	3-52

		Examples	3-53

	ac:ROUTE command		3-54

		RFORM	3-54

		RTEXT	3-54

	ac:STOCKSET command		3-56

		ASSIGN	3-56

		INIFEED	3-56

		SYSPAGE	3-57

		Example	3-57

	ac:VFU command		3-58

		ASSIGN	3-59

		BOF	3-60

		TOF	3-60

		Example	3-60

4. Logical processing commands			4-1

	BANNER command		4-1

		HCOUNT	4-1

		HJOBNO	4-2

		HRPTNA	4-2

		TCOUNT	4-2

viii	XEROX 4850/4890 HIGHLIGHT COLOR LPS PRINT DESCRIPTION LANGUAGE REFERENCE

		TABLE OF CONTENTS
	TEST	4-3

	TYPE	4-3

BDELETE command		4-4

	TEST	4-4

BSELECT command		4-5

	TEST	4-5

	Examples	4-5

ac:CRITERIA command		4-6

	CHANGE	4-6

	CONSTANT	4-7

	LINENUM	4-8

	VALUE	4-9

LMODIFY command		4-11

RAUX command		4-12

	TEST	4-12

	Example	4-12

RDELETE command		4-13

	TEST	4-13

	Example	4-13

RFEED command		4-14

	TEST	4-14

ROFFSET command		4-15

	PASSES	4-15

	TEST	4-16

	Example	4-16

RPAGE command		4-17

	SIDE	4-17

	TEST	4-19

	WHEN	4-19

RRESUME command		4-21

	BEGIN	4-21

	TEST	4-21

	Example	4-22

RSELECT command		4-23

	TEST	4-23

RSTACK command		4-23

	ACCTINFO	4-24

	DELIMITER	4-24

	HRPTNA	4-25

	PRINT	4-25

XEROX 4850/4890 HIGHLIGHT COLOR LPS PRINT DESCRIPTION LANGUAGE REFERENCE

TABLE OF CONTENTS

		TEST	4-25
		Example	4-26

	RSUSPEND command		4-26

		BEGIN	4-27

		TEST	4-27

	ac:TABLE command		4-28

		CONSTANT	4-28

		MASK	4-29

		Examples	4-29

5. Print control commands			5-1

	ALTER		5-1

	ASSIGN		5-2

	BATCH		5-3

	BEGIN		5-3

	BFORM		5-4

	BOF		5-5

	C text		5-5

	CANCEL		5-6

	COLLATE		5-6

	COPIES		5-6

	DATA		5-7

	DEPT		5-7

	DESTINATION		5-8

	DUPLEX		5-8

	END		5-8

	FEED		5-9

	FILE		5-9

	FONTINDEX		5-10

	FONTS		5-11

	FORMAT		5-12

	FORMS		5-12

	GRAPHICS		5-13

	ICATALOG		5-15

	IDFAULT		5-15

	IDR		5-15

	ILIST		5-16

	IMAGE		5-16

	INKINDEX		5-18

	IRESULT		5-18

	ITEXT		5-19

x	XEROX 4850/4890 HIGHLIGHT COLOR LPS PRINT DESCRIPTION LANGUAGE REFERENCE

			TABLE OF CONTENTS
	JDE		5-19

	JDL		5-19

	LOGO		5-20

	MARGIN		5-23

	MODIFY		5-23

	NUMBER		5-24

	OTEXT		5-24

	OVERPRINT		5-25

	PALETTE		5-26

	PMODE		5-26

	RFORM		5-26

	RTEXT		5-27

	SAVE		5-28

	SF1FUNCTION		5-28

	SF2FUNCTION		5-28

	SEPARATORS		5-29

	SHIFT		5-30

	SIDE		5-31

	SNUMBER		5-32

	SPLIT		5-33

	SRECOVER		5-34

	STIMING		5-35

	STOCKS		5-35

	TOF		5-36

	XMP		5-36

6. Highlight color printing			6-1

	Optimizing performance with xerographic mode persistence (XMP)		6-1

		Xerographic mode	6-1

		Xerographic mode persistence (XMP)	6-1

	Ink substitution		6-2

	4850/4890 inks		6-3

	Coding for efficient queue management		6-3

		Resource mode	6-3

		Guidelines for efficient coding in resource mode	6-4

		Stitching	6-5

	Referencing inks		6-6

		Ink catalogs	6-6

		Inkname elements	6-7

		Printing tints and shades	6-7

		Specifying inks	6-7

XEROX 4850/4890 HIGHLIGHT COLOR LPS PRINT DESCRIPTION LANGUAGE REFERENCE

TABLE OF CONTENTS

	Adding highlight color to existing applications			6-9
	Highlight color coding tips			6-11

7. Graphics				7-1

	Processing modes			7-1

			Batch mode	7-1

			Block mode	7-1

			Move mode	7-1

			Random mode	7-2

	Tape formats			7-2

			Noninterleaved	7-2

			Document interleaved	7-2

			Page interleaved	7-3

			Batch mode	7-4

	Online formats			7-5

			Noninterleaved	7-5

			Document and page interleaved	7-5

			Batch mode	7-6

			Document interleaved graphic file transfers	7-7

			Management of image files	7-7

	PDL command options			7-7

	Performance considerations			7-8

	Graphic features restictions			7-8

8. Paper stocks and clusters				8-1

	Programming tasks			8-1

	Paper stock commands and DJDEs			8-1

			Cluster guidelines	8-2

	Specifying paper stocksets			8-3

	Using clusters in print jobs			8-4

			Simple and OTEXT applications	8-4

			STOCKSET applications	8-4

			Mixing applications	8-5
Appendices
Appendices

	A.	PDL and DJDE command summary		A-1

	B.	Character code assignments		B-1

	C.	Offline specifications		C-1

	D.	Online specifications		D-1

Glossary				GLOSSARY-1

Index				INDEX-1

xii	XEROX 4850/4890 HIGHLIGHT COLOR LPS PRINT DESCRIPTION LANGUAGE REFERENCE

Introduction

The Xerox 4850/4890 HighLight Color LPS Print Description Language Reference explains the key concepts involved with the Xerox print description language (PDL) and describes the commands and parameters you use to create and control print jobs.

This reference is intended for both novice and experienced PDL programmers. It assumes some prior knowledge or experience with computer programming.

Document conventions

This manual uses the following conventions:

{} Curly brackets indicate required selection of characters, values, or keywords.

...	Ellipses indicate that you can repeat a parameter or option, or list
	a series of parameters or options.
[ ]	Square brackets indicate optional command characters, values, or
	keywords.
\|	Vertical bars are used to separate option choices. The vertical
	bar stands for ªor.º
bold	Bold is used for characters you enter at the command line.
italics	Italics is used for variable names or numbers.
TERMINAL FONT	Terminal or monospace font is used to represent text that
	displays on the system screen.
underline	System default parameters are underlined.
UPPERCASE	Uppercase letters are used for command and parameter
	keywords.

XEROX 4850/4890 HIGHLIGHT COLOR LPS PRINT DESCRIPTION LANGUAGE REFERENCE

xiii

1. Overview

This chapter contains basic information on using Xerox print description language (PDL) to create and control print jobs.

For a job to be printed on a Xerox Laser Printing System (LPS), you first create a file of PDL commands to define the source and format of the input media, processing requirements, and the print format, such as forms, fonts, highlight color, accounting options, operator messages, and finishing. Each PDL command has a set of parameters that define these characteristics.

The source or uncompiled file of PDL commands is called a job source library (JSL). All JSL files must be compiled before they can be referenced to print a job. The object or compiled file of a JSL file is called a job descriptor library (JDL).

The primary element of a JSL is a job descriptor entry (JDE). The key words ºJDEº and ºJOBº are used interchangeably when coding JSL. This sometimes causes confusion from an ONLINE host perspective because a host job, delimited by the RSTACK and/or BANNER commands (discussed in the ªLogical processing commandsº chapter), is processed by the LPS as a report, and thus one LPS job may consist of multiple host jobs/reports sent in sequence. A particular JOB in a JDL may be generally used to print various reports (e.g., a 2-up format), or specific to a particular report format. A JDE name is specified along with the JDL name in order to define print job characteristics as the job is started. DJDEs may be used to select a different JDE, or otherwise alter formatting on the fly. Any characteristics not specified explicitly in the JSL will be derived from system generation settings or other system defaults.

Dynamic job descriptor entries (DJDEs) can be inserted into the input data stream to enable you to modify print job

characteristics dynamically on a page-by-page or record-by-record basis. A record is a line of data as defined in the RECORD command (discussed in the ªData definition commandsº

chapter).

Input data streams

Before anything else, you must know the source of the input data and code the input data characteristics into your JSL. Data processed by the printing system may originate from several sources, including magnetic tape (offline processing), a host computer (online processing in 3211 or 4245 modes), through remote communications, or over an Ethernet connection.

XEROX 4850/4890 HIGHLIGHT COLOR LPS PRINT DESCRIPTION LANGUAGE REFERENCE

1-1

OVERVIEW

Offline mode

For offline operations, magnetic tape may be recorded in one of a variety of standard formats. As the programmer, you define the tape blocking and record format parameters. These parameters reduce physical tape blocks first to logical records, then to print lines. You can also code special processing commands that enable logical report processing.

Before selecting the PDL commands that describe a specific job tape, you must understand the concepts of host formats, block and record structure, tape translation code, and packed data formats.

Host tape formats

The LPS processes data tapes in standard host formats. Refer to the ªCharacter code assignmentsª appendix for information on these host formats. You must specify the appropriate generated tape format in the HOST parameter of the VOLUME command. The VOLUME command is discussed in the ªData definition commandsº chapter. The format of each tape is described in the

Xerox LPS Tape Formats Manual.

Data representation

The LPS recognizes EBCDIC, ASCII, several versions of binary coded decimal (BCD) tape codes, and the Xerox LPS native format. It also accepts the VOLUME command CODE = NONE parameter, which instructs the system not to translate the input data. If the codes are not sufficient for a particular tape, you may create a new code translation table or modify an existing one. Tables showing the correspondence between standard recording codes and printed characters are contained in the ªCharacter code assignmentsª appendix. Within a JDL, tape codes are selected by the CODE parameter of the VOLUME command.

Packed data formats

Six-bit characters may be written onto an open-reel 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. There are two methods of packing these bits together. One method uses the Honeywell 6000 (T4X3), while Honeywell 2000 uses a slightly different method of packing (T4X3H2).

Whenever an unpacking method is included in the JDL, the system unpacks the characters before processing the data . Each 6-bit character is extracted, and two high-order zeros are appended. Normally, after data is unpacked, it must be translated. The character code set is defined in the CODE parameter of the VOLUME command. For a 4-by-3 unpacking method, the data is generally encoded in BCD, and you can specify one of the three standard BCD CODE parameter options (H2BCD, H6BCD, and IBMBCD).

1-2	XEROX 4850/4890 HIGHLIGHT COLOR LPS PRINT DESCRIPTION LANGUAGE REFERENCE

OVERVIEW

Record formats

All tape records input to the printing system are either blocked or unblocked with a fixed length, a variable length, or an undefined format. The BLOCK and RECORD commands define the format of the input data.Tape label contents may also describe blocking and record structure and, in some cases, override BLOCK and RECORD commands specified in the JDL source file. These labels are described in the ªData definition commandº chapter and in the Xerox LPS Tape Formats Manual.

Record structure

A record is arbitrarily divided into two portions: operating system and user. The operating system portion of the record contains information supplied by the host operating or spooling system. The user portion of the record contains information provided by the application or user program running on the host system. The boundary between the two portions of the record is traditionally between the record length and the printer carriage control (PCC) field. If there is no record length field, there is no operating system portion of the record. The input record characteristics that define the components of a record are described in the ªRECORD commandº section of the ªData definition commandsº chapter.

Multivolume processing

All multivolume reports that force input to make multiple passes over the data are handled in the following way: 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 copy modification entries (CMEs), and optionally for multicopy reports that exceed the size of the print file. CMEs are discussed in the ªCopy modification entriesª section in the ªPrint format commandsºchapter. The choices available for handling print file saturation are discussed under the VOLUME command (RSAT parameter) in the ªData definition commandsº chapter.

If a multivolume report requires multiple passes, messages appear on the system controller display with instructions on which actions to take.

If you have multiple volume jobs and multiple laser printing systems, you may want to print each volume on a separate system. This requires that each volume be processed independently. Refer to the VOLUME command (EOV parameter) in the ªData definition commandsº chapter for more information about this processing.

If a system rollover occurs while processing a multivolume report, the system displays the following message before performing a forward tape space to the recovery point:

ENTER ©CON I© WHEN VOLUME x IS MOUNTED

As before, volume 1 is the start-of-job, and the volume specified by n is the volume containing data for the last page written to the print file before the system rollover.

XEROX 4850/4890 HIGHLIGHT COLOR LPS PRINT DESCRIPTION LANGUAGE REFERENCE

1-3

OVERVIEW

±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±Ë

Online mode

±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±Ë±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±Ë±±±±±±±±±±±±

A channel-attached LPS can receive input from the host computer in online 3211 or 4245 mode. In online mode, the data stream emulates IBM 3211 or 4245 line printer format, with or without embedded DJDEs. All commands coded for the 3211 may be coded for the 4245.

4245 processing mode features

The 4245 processing mode allows your LPS to correctly execute the printing instructions coded within the job stream for the IBM 4245 printer.

The 4245 is identical to the 3211 in that all 3211 commands can also be coded for the 4245.

Online-specific commands

You create an online job descriptor library (JDL) and its job descriptor entries (JDEs) according to the same rules and syntax as other entries. The one PDL command that must be specified for normal online processing is VOLUME HOST=IBMONL. The HOST parameter of the VOLUME command performs two functions:

·Allows the LPS to accept data from the online channel

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

The defaults that are automatically selected when VOLUME

HOST=IBMONL is specified are as follows:

RECORD	LENGTH = 150;
LINE	PCCTYPE = IBM3211,
	DATA = (0,150);

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

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

The OPTIMIZE parameter of the VOLUME command allows you to select options that enhance online throughput. Refer to the ªVOLUME commandº section in the ªData definition commandsº chapter for additional information.

DJDE processing

Printing is controlled through parameters from a user-defined

.JDL file. These parameters may be dynamically overridden by

1-4	XEROX 4850/4890 HIGHLIGHT COLOR LPS PRINT DESCRIPTION LANGUAGE REFERENCE

OVERVIEW

dynamic job descriptor entries (DJDEs). The DJDEs that you specify are processed by the LPS as part of the input print data from the host system. The ªPrint control (DJDE) commandsº chapter defines their syntax and options. The IDEN command enables the system to identify DJDEs as part of the input data. Refer to the ªData description commandsº chapter for information on the IDEN command.

Print-and-skip carriage control commands, which are associated with online DJDE records, are treated as skip-immediate carriage control commands. If the LPS is not at the channel specified, a skip occurs. If it is already there, no skip occurs unless the last command received with a data record was a print-without- spacing command. Print-and-space carriage control commands associated with DJDE records are ignored.

Nonprint files, such as font files, can be downloaded from the host using the FILE DJDE. This DJDE is described in the ªPrint control (DJDE) commandsº chapter.

Copy-sensitive CMEs

Copy modification entries (CMEs) that are copy sensitive (that is, a copy range has been specified on the MODIFY parameter of the OUTPUT command) are ignored online since the data is not automatically available multiple times. To produce copy-sensitive output, you must transmit data the number of times the data needs to be modified. Thus, if you want six copies of a report and one CME applies to copies 1 through 4, and another CME applies to copies 5 and 6, you must transmit the report from the host system twice. The first transmission contains a copy count of 4 with CME1 specified, and the second transmission contains a copy count of 2 with CME2 specified. As an alternative, the application may be printed successfully with only one transmission by using copy-sensitive forms. Refer to the FORMS parameter of the OUTPUT command in the ªPrint format commandsº chapter for additional information.

Report separation

Report separation is defined in terms of banner page detection or other user-defined processing criteria. Logically separated reports are physically offset from one another in the output trays. The two logical processing commands that can control online

report separation are BANNER and RSTACK. Refer to the ªLogical processing commandsº chapter for additional information.

Online record length

The default record length supported by Xerox laser printing systems is 150 bytes, the same default as the 3211 printer. However, you may 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 3211 or 4245. This feature is invoked only with FCBs. If FCB=IGNORE is invoked, this restriction is not significant.

XEROX 4850/4890 HIGHLIGHT COLOR LPS PRINT DESCRIPTION LANGUAGE REFERENCE

1-5

OVERVIEW

·For print record lengths from 215 bytes to 2 140 bytes, you must not use the OPTIMIZE parameter of the VOLUME command, which provides for online buffering for improved performance.

·If the data record transmitted from the host exceeds the RECORD command LENGTH parameter values specified, the record is truncated to the specified record length and no warning is provided. This action is consistent with the 3211 or 4245 printers.

·The online dump JDL specifies a RECORD LENGTH of 150 bytes. If you are planning to use a longer record length, modify the JDL to dump the data accurately.

·You cannot change the LENGTH parameter of the RECORD command with a DJDE since this would require dynamic rebuffering. Consider modifications to the default online JDL to simplify operations in the online environment.

·You can change the OPTIMIZE parameter of the VOLUME command with the DJDE JDE subject to the restrictions listed for the OPTIMIZE parameter. Refer to the ªVOLUME commandº section of the ªData description commandsº chapter for additional information.

To select a record length longer than 150 bytes, you must specify the new value as the LENGTH parameter on the RECORD

command, and must also modify the DATA parameter of the LINE command to print the extended character or record length.

Figure 1-5, appearing later in this chapter, shows a complete online job source library (JSL).

Online recovery

After a system failure, data acquired from the host and stored on system disk can be imaged upon system restart if you have requested job recovery. Only data that was being received at the time of the power failure is lost and must be retransmitted.

For power failures, the amount of data that requires retransmission can be up to 8 KB. In all other rollover conditions, the data is normally recovered.

Online dump

The online dump feature allows you to generate a hardcopy of the command and data transmission taking place between the host computer and the LPS.

Starting and ending dump sessions

You may begin an online dump session with a START command when the LPS is online and in the idle state. You must use the DFLT JDE within the OLDUMP JDL to specify VOLUME HOST=OLDUMP and CODE=EBCDIC.

The dump session is terminated by either the operator ENDJOB command or the offline operator command. Other online operator commands during a dump session perform the standard functions. These are described in the operator guide for your

1-6	XEROX 4850/4890 HIGHLIGHT COLOR LPS PRINT DESCRIPTION LANGUAGE REFERENCE

OVERVIEW

Xerox 4850 or 4890 LPS. Figure 1-1, appearing later in this chapter, is a sample printed online dump.

Dump format

Each host command directs the printer to perform an operation or provides control information used during printing. The control information could be printed with carriage control, carriage control only, or printer control, such as load FCB. All print commands and some control commands transmit data to and from the LPS. The dump format for each of these commands contains a HEADER and DATA segment. The HEADER segment consists of the fields shown in table 1-1.

Table 1-1. Print format command

Field	Definition
HOST COMMAND	The English translation of the host
	command in hexadecimal

END STATUS	One byte of status in hexadecimal
	transmitted to the host

SEQ#	Incremental count in decimal of the
	host commands received during a
	dump session. The maximum
	number generated is 999,999

LENGTH	Length in decimal of the data
	transmitted

DATE and TIME	Date and time when the host
	command was received by the dump
	processor. The time includes tics of
	seconds where one tic is
	approximately one millisecond.

The DATA segment consists of the input data in hexadecimal transmitted to or from the host as well as EBCDIC translation based upon the CODE command. Input data that cannot be translated is left as blanks. Each line of data is preceded by a byte count in hexadecimal.

Online dumps have these restrictions:

·DJDEs, BANNER, and other logical processing functions are not processed when the dump job is running, so you must enter an operator ENDJOB command to end the dump.

·The 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, as when paper trays become empty, are not dumped.

·Print records longer than the specified RECORD command LENGTH parameter value are truncated without warning. If records longer than 150 bytes are to be sent, the RECORD command LENGTH parameter in the OLDUMP JDL should be modified to the longer length.

XEROX 4850/4890 HIGHLIGHT COLOR LPS PRINT DESCRIPTION LANGUAGE REFERENCE

1-7

Xerox DOCUPRINT 4890, DOCUPRINT 4850 User Manual

OVERVIEW

·The HIP START ... command is accepted, but the host interface processor (HIP) is unable to submit a print job while the system is online.

Figure 1-1. Sample printed online dump

1-8	XEROX 4850/4890 HIGHLIGHT COLOR LPS PRINT DESCRIPTION LANGUAGE REFERENCE

OVERVIEW

Downloading files from the host to the LPS

There are three methods of downloading files:

·HOSTCOPY utility

·FILE dynamic job descriptor entry

·LPS and host file transfer.

Files may be downloaded in two formats: card-image files and LPS-labeled 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.

HOSTCOPY

HOSTCOPY provides a means for accepting files from the host computer and storing them on the LPS system disk. Files in two different formats may be transmitted:

·User-created card-image files

·LPS-labeled files (such as font, logo, and patch tapes). Refer to the Xerox 4850/4890 HighLight Color LPS System Programming and Administration Guide for information on the HOSTCOPY command.

The utility requires the system to be placed offline and idle, then rebooted from disk to enter the operator HOSTCOPY command from the system menu. It does not allow files to be transferred while normal printing activity is taking place.

FILE dynamic job descriptor entry

The FILE dynamic job descriptor entry (DJDE) transfers files while normal printing activity is taking place. However, the file to be transferred may need to be preconditioned to prevent trailingblank truncation by the host spooler. FILE provides a capability of loading card-image or LPS-labeled files to the LPS disk while a printing job is in progress.

FILE is record-oriented and is applied immediately. It can be included with other record-oriented or page-oriented DJDE commands in a DJDE packet. Refer to the ªPrint control (DJDE) commandsº chapter for FILE syntax and to the Xerox 4850/4890 HighLight Color LPS System Programming and Administration Guide for information on card-image file processing.

LPS and host file transfer

A third method of file transfer uses the LPS and host file transfer interface. This interface transfers user files and allows you to obtain the status of the reports submitted for printing on the LPS. A remote connection between the host and LPS is used for file transfer.

XEROX 4850/4890 HIGHLIGHT COLOR LPS PRINT DESCRIPTION LANGUAGE REFERENCE

1-9

OVERVIEW

FCBs

The 3211 and 4245 forms control buffer (FCB) defines channel positions and forms length. You may restrict the forms control buffer information by accepting or suppressing the normal processing of host-transmitted FCB input. You can accomplish this by specifying the FCB=IGNORE parameter of the LINE command.

Vertical format control processing

The interaction of the vertical format controls (VFU) in the JSL and the FCB sent from the host is as follows:

·When you enter a START command, the VFU table and its associated bottom-of-form (BOF) in the JDE come into effect.

·If no VFU is specified in the JDE, the last FCB sent from the host is retrieved from the disk and becomes active.

·If no BOF is specified in the JDE, the length of the last FCB sent from the host is retrieved from the disk and becomes BOF. Note that top-of-form (TOF) is not affected by the FCB.

·If you specify FCB=PROCESS and an FCB is sent from the host, it overrides the previous FCB or VFU. Its length replaces the previous BOF. Furthermore, its contents and length are saved on the disk.

·When a DJDE is used to change a channel assignment, any previous assignments to the channel being changed are suspended until the end of report. At the end of report, DJDE changes are discarded and the last active FCB or VFU comes back into effect.

·When system generation is executed, the FCB saved on disk is reinitialized to the length of 66 lines with the following channel assignments:

Channel	1	2	3	4	5	6	7	8	10	11	12	9
Line	4	10	16	22	28	34	40	46	52	58	64	66

The default corresponds to the STD2 default supplied by

IBM.

·If a print-and-skip-to-channel command is sent for an undefined channel, the LPS executes a print-and-space-one command.

·If you specify FCB=PROCESS, an FCB load causes positioning to TOF. If the system is already at TOF, page eject is suppressed. If the line number prior to the FCB load is greater than TOF, a page eject occurs.

·The print position indexing (PPI) byte of the FCB is not suppressed by FCB=IGNORE. If an FCB with a PPI byte is received, indexing is invoked; if an FCB without a PPI byte is received, indexing is turned off (even if FCB=IGNORE). Use of the PPI byte to shift the starting print position may cause problems in recognition of both DJDEs and banner pages.

1-10	XEROX 4850/4890 HIGHLIGHT COLOR LPS PRINT DESCRIPTION LANGUAGE REFERENCE

OVERVIEW

UCSBs for 3211

The 3211 universal character set buffer (UCSB) feature is supported by the LPS. LPS software uses UCSBs as a basis for generating folded and unfolded translate tables. In a folded translate table, uppercase characters are substituted for only those lowercase characters defined as unprintable in the UCSB. Any lowercase characters defined as printable in the UCSB are still printed as lowercase if available in the font. In an unfolded translate table, blanks are substituted for characters defined as unprintable in the UCSB. The translate table is rebuilt at the start of each report, when a selected JDE or JDL is processed, when a new UCSB is transmitted from the host, and when a new FOLD or UNFOLD command is received.

The selection of a folded or unfolded translate table is based on the FOLD and UNFOLD channel commands. If FOLD has been most recently received from the host, a folded translate table is built. If UNFOLD is the current command, an unfolded table is built.

You may restrict UCSB information by accepting or suppressing the normal processing of host-transmitted UCSB data by using the UCSB=IGNORE parameter of the LINE command. If UCSB=IGNORE, lowercase characters print normally if they are present in the font and as blanks if they are not. The translate table is rebuilt only at the start of a report.

You may change the UCSB parameter from IGNORE to PROCESS in a selected JDE, but the translate table is not rebuilt until a UCSB LOAD, FOLD or UNFOLD is transmitted from the host.

For most online reports, specification of UCSB=IGNORE is appropriate. The LPS font capability normally negates the need for these translations, which were originally defined to handle print train characteristics. If, however, a report using lowercase characters is printed using a font without lowercase, you may do one of the following:

·Switch to UCSB=PROCESS in a selected JDE

·Load a UCSB with lowercase characters defined as not printable and with FOLD specified.

At the start of the next report, UCSB=IGNORE comes back into effect and the translate table is rebuilt based on the CODE command in the JDL file.

UCSB processing for 3211

When a UCSB is transmitted from the host, it is saved on an LPS disk. When sysgen is executed, the UCSB saved on the disk is reinitialized to define all characters as printable.

If you specify UCSB=PROCESS and the UCSB suppresses special characters used in DJDE syntax, for example, ; ( ), DJDE syntax errors result.

Code UCSB=IGNORE if a code other than EBCDIC is specified.

If you specify UCSB=PROCESS, a UCSB load causes the CODE default to revert to EBCDIC until the end of the report or until a selected JDE or JDL is processed.

XEROX 4850/4890 HIGHLIGHT COLOR LPS PRINT DESCRIPTION LANGUAGE REFERENCE

1-11

OVERVIEW

UCSBs should be ignored in the 4245 mode by coding UCSB=IGNORE. The UCSB host commands (LOAD UCSB, FOLD, and UNFOLD) are processed if UCSB=PROCESS is specified in the job source library (JSL), however the host does not normally issue such commands in 4245 mode.

PDL command and DJDE syntax

You must code each PDL command with the words placed in a specific order and using certain punctuation marks in specific locations. This ordering of words and punctuation is called the syntax of the PDL language.

A PDL command consists of as many as nine elements:

·Identifier, which is used for some commands so that they may be referenced by other commands

·Colon (:), which always follows an identifier

·Command keyword (required)

·Parameter keyword (left part)

·Equal sign (=), which joins a parameter with its parameter options

·Parameter option (right part)

·Parentheses, which group multiple parameter options together

·A comma or blank space, which separates one parameter from another within a command

·A semicolon (;) at the end of a command statement (required).

A command keyword and a semicolon are the two required elements.

Figure 1-2, a diagram of a VFU command statement, illustrates the command syntax rules.

Figure 1-2. Command statement components

This PDL command has an identifier (VFU0005:), a command keyword (VFU), and three parameters with options:

ASSIGN = (1,5), TOF = 5, BOF = 66;

1-12	XEROX 4850/4890 HIGHLIGHT COLOR LPS PRINT DESCRIPTION LANGUAGE REFERENCE

OVERVIEW

Command length

You code a JSL using PDL commands through the system editor task. The editor accepts up to 80 characters per line. A record is the complete set of PDL syntax elements for a command and frequently uses several lines. Refer to your Xerox 4850/4890 HighLight Color LPS System Programming and Administration Guide for information on using the editor.

Identifiers

The purpose of an identifier is to provide a label for a command so it can be referenced by other commands. If the identifier is coded with the command, it is called an ID command. Not all commands have identifiers. The following commands require identifiers:

·ac:CATALOG

·ac:CME

·ac:CODE

·ac:CRITERIA

·ac:IDR

·dd:JDE

·dd:JDL

·dd:JOB

·ac:PCC

·ac:PDE

·ac:ROUTE

·ac:STOCKSET

·dd:SYSTEM

·ac:TABLE

·ac:TCODE

·ac:VFU.

Identifiers have these requirements:

·1 to 6 characters in length. The convention ac indicates that at least one of the characters must be alphabetic (letter). dd indicates that the alphabetic restriction does not apply. These unrestricted identifiers apply only to the SYSTEM (or JDL) and JOB (or JDE) commands.

·No blanks within the identifier are allowed. For example, VFU 1: VFU; is invalid, whereas VFU1: VFU is valid.

·Must be separated from the command with a colon, such as VFU1: VFU in figure 1-5.

·Avoid these categories of restricted names to prevent possible errors:

±Command keywords, such as OUTPUT, PDE, and RSTACK

±Parameter keywords, such as LCODE, UCSB, and BFORM

±Abbreviated operator command keywords CAR (CARTRIDGE) and TAP (TAPE)

±DJDE keywords, such as PMODE, RTEXT, and BATCH

±Resident task files, such as .PDL, .FDL, .FNT, .LGO, .CME,

.LIB, and .FRM

±System utilities, such as INPUT, EDIT, DSR, IPD, and OCS.

XEROX 4850/4890 HIGHLIGHT COLOR LPS PRINT DESCRIPTION LANGUAGE REFERENCE

1-13

OVERVIEW

Command keywords

Command keywords have the following requirements:

·Every command must have a keyword;

·Must be coded with either the first three characters of the command or the whole the command. For example, RECORD can be coded as REC or RECORD. The exception is FORMS. Do not abbreviate FORMS to FOR or FORM because the system interprets it as FORMAT.

Parameter keywords

Some commands have multiple parameters available. For example, FORMS, DUPLEX, and COPIES are parameter keywords of the OUTPUT command:

OUTPUT FORMS = form-id,

DUPLEX = YES or NO,

COPIES = value;

Parameters have these requirements:

·Must be coded with the first three characters of the command or the whole command. For example, DUPLEX can be coded as DUP or DUPLEX.

·Must be followed by an equal sign (=) and at least one parameter option, as shown in figure 1-2.

Parameter options

Most parameters have multiple parameter options available.

Parameter options have the following requirements:

·Are placed on the right side of the equal sign (=)

·Multiple options for the same parameter must be enclosed in parentheses

·Can consist of either keywords or variable names and values. For example:

OUTPUT FORMS = form-id, DUPLEX = YES or NO, COPIES = value;

YES and NO are parameter option keywords. form-id and value are variables.

Parameter options are also called right part constants and may take one of two forms: value constants and string constants.

1-14	XEROX 4850/4890 HIGHLIGHT COLOR LPS PRINT DESCRIPTION LANGUAGE REFERENCE

OVERVIEW

Value constants

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

PDE	BEGIN = (1, 1, .37);
BLOCK	LENGTH = 1320;
RECORD	LENGTH = 132;
OUTPUT	IMAGE = (1.30CM, 0.85IN);

String constants

String constants are normally used to specify strings of characters or to reference identifier parameters. String constants may be expressed as keywords, variable names, hexadecimal, character, ASCII, EBCDIC, octal, or H2 and H6 values, and also as decimal numbers for use with LMODIFY logical processing.

Keywords

Keywords are terms that direct the system to perform specific predetermined activities. Keywords always consist of the same characters, for example:

BLOCK	ZERO = YES;
ABNORMAL	ERROR = CONTINUE,
	OTEXT = WAIT;
ACCT	USER = BOTH;

YES, CONTINUE, WAIT, and BOTH are parameter option keywords.

Variable names

You may use string constants to name objects such as forms, files, fonts, departments, and so on. Each name you assign identifies the unique object you wish to specify for your print jobs for example:

OUTPUT	FORM = SMPLE,
	BFORM = SMPBK,
	FEED = BLUCVR
	MODIFY = CME12;

SMPLE, SMPBK, BLUCVR, and CME12 are variable parameter option names.

Hexadecimal

Hexadecimal constants are 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 that the following expression is in hexadecimal and ended with an apostrophe (`). For example:

IDEN PREFIX=X'C1C2C3C4';

XEROX 4850/4890 HIGHLIGHT COLOR LPS PRINT DESCRIPTION LANGUAGE REFERENCE

1-15

OVERVIEW

Characters

Character constants are normally used as string constants, but they may also be numeric value constants. Each character, including embedded blanks, results in one byte. A character constant must immediately be preceded and followed by the apostrophe (') character. For example:

IDEN PREFIX='THIS IS A CHARACTER CONSTANT';

CONSTANT='ABCDE';

If the apostrophe character (') is required in a character constant, it must be defined in some other fashion, such as the hexadecimal constant X'7D'. Character constants are inherently defined as EBCDIC and take their actual values from the standard EBCDIC table definition. Refer to the ªCharacter code assignmentsª appendix for EBCDIC table definitions.

ASCII

ASCII constants are used as string constants. Each character results in one byte. The constants must be preceded by the characters A apostrophe (A') and followed by an apostrophe character. For example:

IDEN PREFIX=A'ABC';

IDEN PREFIX=A'ABC!44EF'

is equivalent to:

IDEN PREFIX=X'414243444546'.

The three-character sequence required for a hexadecimal representation of a character results in one byte.

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

EBCDIC

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

IDEN PREFIX=E'ABC!C4EFG'

is equivalent to the hexadecimal:

IDEN PREFIX=X'C1C2C3C4C5C6C7'

Each character represented in EBCDIC results in one byte. Each three-character sequence representing a character in hexadecimal results in one byte. EBCDIC is the default, therefore, E 'xxx' is usually not required. It is required, however, when the EBCDIC string has a hexadecimal representation in it, as in the example above.

1-16	XEROX 4850/4890 HIGHLIGHT COLOR LPS PRINT DESCRIPTION LANGUAGE REFERENCE

+ 271 hidden pages

Xerox DOCUPRINT 4890, DOCUPRINT 4850 User Manual

Table of contents

Introduction

1. Overview

Introduction

Document conventions

1. Overview

Input data streams

Host tape formats

Data representation

Packed data formats

Record formats

Record structure

Multivolume processing

4245 processing mode features

Online-specific commands

DJDE processing

Copy-sensitive CMEs

Report separation

Online record length

Online recovery

Online dump

Downloading files from the host to the LPS

FCBs

Vertical format control processing

UCSBs for 3211

Command length

Identifiers

Command keywords

Parameter keywords

Parameter options

Value constants

String constants