Xerox XDPE/400 (also known as EOMS I-Services) Support & Software User Guide

A generic packet can be specified three ways:
•

Through the resource list, using list processing

•

Through an XES packet specified with the Generic XES packet 

(GENXES) parameter of the Create XES packet (CRTXES) 

command

•

Through the Font Identifier (FONT) printer file parameter

NOTE: XDPE/400 does not reset any parameters specifically set by 

generic packet processing, making the results of generic packet 

processing unpredictable. Many XDPE/400 and printer commands 

can affect the way a command in a generic packet will work.

If you use generic packets, be sure to reset all appropriate parameters 

either within the generic packet, or in a generic packet in the beginning of 

the next job. Thoroughly test your job before putting it into production, and 

again after you make ANY changes to XDPE/400 parameters for that job.
A generic packet contains only the name of an ASCII file, stored in the 

XDPEFLR/GENXES subfolder. XDPE/400 downloads the ASCII file 

contents directly into the data stream. The file contents do not have to be 

XDPE/400-specific. They can be any type of data, including text, XES 

commands, and resources.

NOTE: When using logical processing in XES jobs, XDPE/400 will not 

insert a specified generic XES packet at the bottom of a page. Also, 

generic packets inserted at the bottom of the page will overprint the 

last print line of the page. To remedy the situation, include vertical 

spacing control in the generic packet.

Generic packets are processed differently depending on how they are 

invoked, through list processing, through an XES packet, or through the 

FONT printer file parameter. Each processing method is described in the 

following sections.