XDPE/400
User Documentation
Version 2.1.4
September 2001
720P94604
Xerox welcomes your suggestions and feedback on this
document. You can contact us by e-mail or FAX at:
E-mail:
FAX:
USA 3260 [email protected]
407-869-2098 (Attention: Documentation)
©2001 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 that are
displayed on the screen, such as icons, screen displays, looks,
etc.
Produced in the United States of America.
Xerox®, The Document Company®, the digital X®, and the
identifying product names and numbers herein are trademarks of
Xerox Corporation.
All non-Xerox brands and product names are trademarks or
registered trademarks of their respective companies.
Companies, names, and data used in examples herein are
fictitious unless otherwise noted.
Changes are periodically made to this document. Changes,
technical inaccuracies, and typographic errors will be corrected
in subsequent editions.
This document was created using FrameMaker document
publishing software. The typefaces are Arial and Monotype.com.
Table of contents
Section One: Introduction to XDPE/400
1. Getting Started
XDPE/400 system overview............................................................................................... 1-4
AS/400 printing..................................................................................................... 1-4
Printing with XDPE/400 ......................................................................................... 1-6
XDPE/400 features and functions....................................................................................... 1-7
Printer control commands ...................................................................................... 1-7
High-end printing and processing ........................................................................... 1-7
Resource management ......................................................................................... 1-8
Monitoring output queues ...................................................................................... 1-9
Supported printers ............................................................................................................ 1-9
Xerox Production Print Mode printers...................................................................... 1-9
Xerox Distributed Print Mode printers.................................................................... 1-10
Xerox Printer Control Language printers ............................................................... 1-10
Xerox PostScript printers ..................................................................................... 1-11
Generic printer devices ....................................................................................... 1-11
2. New and updated XDPE/400 features
New features in XDPE/400 2.1.4 ........................................................................................ 2-1
Generic device support ......................................................................................... 2-1
OS/400 5.1 support............................................................................................... 2-1
VIPP 2001 compliance .......................................................................................... 2-1
N-series printers in VIPP mode support................................................................... 2-2
Revised parameters .............................................................................................. 2-2
New features in XDPE/400 2.1.3 ........................................................................................ 2-3
VIPP page-level support ........................................................................................ 2-3
PCL euro font support ........................................................................................... 2-3
OS/400 4.5.0 support ............................................................................................ 2-3
Added printer support............................................................................................ 2-3
Revised parameters .............................................................................................. 2-4
XDPE/400 2.1.3 distributed on CD-ROM ................................................................. 2-5
User documentation distributed on CD-ROM ........................................................... 2-5
New features in XDPE/400 2.1.2 ........................................................................................ 2-6
VIPP job-level support........................................................................................... 2-6
Xerox extended job ticket support........................................................................... 2-6
OS/400 4.3.0 and 4.4.0 support.............................................................................. 2-6
Added PCL printer support .................................................................................... 2-7
Euro font certification ............................................................................................ 2-7
Revised parameters .............................................................................................. 2-7
New commands.................................................................................................... 2-8
XDPE/400 User Documentation (9/2001)
iii
Table of contents
New features in XDPE/400 2.1.1 ........................................................................................ 2-9
Trailer separator page support ............................................................................... 2-9
Duplex extended support....................................................................................... 2-9
OS/400 4.2.0 compliance ...................................................................................... 2-9
Added printer support.......................................................................................... 2-10
New and revised parameters ............................................................................... 2-10
New features in XDPE/400 2.1......................................................................................... 2-12
Banner page enhancements ................................................................................ 2-12
Added PCL printer support .................................................................................. 2-12
Revised parameters ............................................................................................ 2-12
New features in XDPE/400 2.0......................................................................................... 2-14
Multi-up printing.................................................................................................. 2-14
Report distribution for multi-part print jobs ............................................................. 2-14
42XX internal interface enhancements .................................................................. 2-15
PCL packet enhancements .................................................................................. 2-15
Network print support .......................................................................................... 2-15
Spool file processing without printer device ........................................................... 2-16
Banner page enhancements ................................................................................ 2-16
New and revised parameters ............................................................................... 2-16
Section Two: Installing and Customizing XDPE/400
3. Migration actions
XDPE/400 2.1.4 migration actions ...................................................................................... 3-1
Installation considerations...................................................................................... 3-1
OS/400 version requirements................................................................................. 3-2
Converting from XDPE/400 2.0 .......................................................................................... 3-2
4. Installation requirements
Requirements .................................................................................................................. 4-1
AS/400 system requirements ................................................................................. 4-1
Security requirements ........................................................................................... 4-2
Printer requirements ............................................................................................. 4-3
Supported printer/interface box configurations ......................................................... 4-9
Interface settings ................................................................................................ 4-11
OS/400 device description ................................................................................... 4-11
Migration issues ............................................................................................................. 4-12
Displaying your XDPE/400 library and folder information......................................... 4-12
Recording your current global values .................................................................... 4-12
Collecting changes you made to XDPE/400 objects ............................................... 4-13
Customizing XDPE/400 default commands............................................................ 4-13
XDPE/400 User Documentation (9/2001)
iv
Table of contents
5. Installing XDPE/400
Creating an XDPE/400 user profile..................................................................................... 5-2
Backing up your current XDPE/400 system ......................................................................... 5-3
Installing the base files...................................................................................................... 5-4
Recreating your XDPEFLR object changes ......................................................................... 5-6
Resetting your global values .............................................................................................. 5-6
Restoring your customized XDPE/400 application library objects........................................... 5-6
Installing corrective maintenance ....................................................................................... 5-6
Removing your old version of XDPE/400 ............................................................................ 5-7
Adding the XDPE/400 application library to your library list ................................................... 5-7
6. Customizing XDPE/400
Work with Global Values screens ....................................................................................... 6-1
Changing global values ......................................................................................... 6-1
Work with Global Values (first screen)..................................................................... 6-2
Work with Global Values (second screen) ............................................................... 6-6
Work with Global Values (fourth screen)................................................................ 6-10
Work with Global Values (fifth screen)................................................................... 6-14
Separator page customization ......................................................................................... 6-20
Monitor Queue-generated separator pages ........................................................... 6-20
Separator page contents formatting ...................................................................... 6-20
Generating separator pages in VIPP mode............................................................ 6-26
Monitor Queue job log..................................................................................................... 6-28
XDPE/400 command customization.................................................................................. 6-29
Example 1.......................................................................................................... 6-29
Example 2.......................................................................................................... 6-31
Using A4 paper for NPS and DocuSP printers (PCL mode only) .......................................... 6-31
7. Performing an installation verification procedure
IVP requirements ............................................................................................................. 7-2
XPPM IVP............................................................................................................ 7-2
PCL IVP .............................................................................................................. 7-2
VIPP IVP ............................................................................................................. 7-3
Starting Monitor Queue ..................................................................................................... 7-4
Executing the IVP............................................................................................................. 7-5
Creating XDPE/400 IVP parameters ....................................................................... 7-6
Verifying your output......................................................................................................... 7-6
IVP sample output ............................................................................................................ 7-7
DJDE Direct Mode IVP...................................................................................................... 7-7
DJDE Indirect Mode IVP ................................................................................................. 7-21
DJDE Combined Mode IVP ............................................................................................. 7-27
XES Direct Mode IVP...................................................................................................... 7-37
XES Indirect Mode IVP ................................................................................................... 7-43
XES Combined Mode IVP ............................................................................................... 7-49
XDPE/400 User Documentation (9/2001)
v
Table of contents
PCL Direct Mode IVP...................................................................................................... 7-55
PCL Indirect Mode IVP.................................................................................................... 7-59
PCL Combined Mode IVP ............................................................................................... 7-65
VIPP Direct Mode IVP..................................................................................................... 7-71
VIPP Indirect Mode IVP .................................................................................................. 7-77
VIPP Combined Mode IVP .............................................................................................. 7-83
Section Three: Printing Documents with XDPE/400
8. Print job configuration
Choosing a command generation method ........................................................................... 8-1
Setting the command generation method ............................................................................ 8-3
Using the Packet data (PACKETDATA) parameter................................................... 8-3
Configuring your printer file................................................................................................ 8-4
Creating Xerox printer control packets ................................................................................ 8-4
Downloading resources..................................................................................................... 8-5
Starting Monitor Queue ..................................................................................................... 8-6
9. XDPE/400 commands and menus
Commands ...................................................................................................................... 9-1
Menus ............................................................................................................................. 9-3
Command group menus ........................................................................................ 9-3
Task-specific menus ............................................................................................. 9-4
10. Creating and modifying printer files
Creating Xerox printer files .............................................................................................. 10-1
Setting general spooling parameters..................................................................... 10-1
Setting the Packet data (PACKETDATA) parameter ............................................... 10-2
Setting Xerox printing features (Indirect method).................................................... 10-4
Examples of creating Xerox printer files ................................................................ 10-4
Managing Xerox printer files ............................................................................................ 10-6
Changing Xerox printer files ................................................................................. 10-6
Overriding Xerox printer files.............................................................................. 10-14
11. Modifying spool files
Changing the command generation method ...................................................................... 11-1
Changing formatting and job processing attributes ............................................................. 11-1
Examples of changing spool file attributes......................................................................... 11-5
Example 1.......................................................................................................... 11-6
Example 2.......................................................................................................... 11-6
Example 3.......................................................................................................... 11-6
XDPE/400 User Documentation (9/2001)
vi
Table of contents
12. DJDE command generation
Using DJDE control commands ....................................................................................... 12-2
Indirect method .............................................................................................................. 12-3
Modifying printer file parameters........................................................................... 12-4
Direct method ................................................................................................................ 12-7
Default DJDE packet........................................................................................... 12-7
Combined method .......................................................................................................... 12-8
Application order of DJDE commands................................................................... 12-8
Creating and managing DJDE packets ............................................................................. 12-9
Packet name syntax............................................................................................ 12-9
Using the Create DJDE packet menu.................................................................... 12-9
Using the Change DJDE packet menu ................................................................ 12-17
Using the DJDE packet Text List utility ................................................................ 12-19
Using the OS/400 Source Entry Utility (SEU) ....................................................... 12-26
13. XES command generation
Using XES control commands ......................................................................................... 13-1
File processing mode (PROCMODE) restriction................................................................. 13-2
Indirect method .............................................................................................................. 13-3
Modifying printer file parameters........................................................................... 13-4
Direct method ................................................................................................................ 13-7
Default XES packet............................................................................................. 13-7
Combined method .......................................................................................................... 13-8
Application order of XES control commands .......................................................... 13-8
Creating and managing XES packets ............................................................................... 13-9
Creating XES packets ......................................................................................... 13-9
Changing XES packets ..................................................................................... 13-19
Deleting XES packets ....................................................................................... 13-21
Generic packets ........................................................................................................... 13-22
How generic packets are processed ................................................................... 13-22
Creating a generic packet ASCII file ................................................................... 13-24
14. XES color command generation
Creating XES color packets ............................................................................................. 14-2
Packet name syntax............................................................................................ 14-2
Packet creation procedure ................................................................................... 14-3
Packet parameters.............................................................................................. 14-6
Packet default color values .................................................................................. 14-7
IBM color command names ................................................................................. 14-9
Changing XES color packets ......................................................................................... 14-11
Starting XES color processing ....................................................................................... 14-12
XDPE/400 User Documentation (9/2001)
vii
Table of contents
15. PCL command generation
Using PCL control commands.......................................................................................... 15-1
File processing mode (PROCMODE) restriction................................................................. 15-2
Indirect method .............................................................................................................. 15-3
Modifying printer file parameters........................................................................... 15-4
Direct method ................................................................................................................ 15-8
Default Xerox PCL packet.................................................................................... 15-8
Combined method .......................................................................................................... 15-9
Application order of PCL control commands .......................................................... 15-9
Creating and managing Xerox PCL packets .................................................................... 15-10
Creating Xerox PCL packets .............................................................................. 15-10
Changing Xerox PCL packets ............................................................................ 15-27
Deleting Xerox PCL packets .............................................................................. 15-30
Displaying Xerox PCL packets ........................................................................... 15-31
Working with Xerox PCL packet macro invocation types ....................................... 15-34
Generic packets ........................................................................................................... 15-37
Creating a generic packet ASCII file ................................................................... 15-37
Inserting generic packets................................................................................... 15-38
Example of using a generic packet for constant back forms................................... 15-40
Xerox PCL printer tray selection..................................................................................... 15-45
DC265LP and DC255LP printer tray selection ..................................................... 15-46
N32 and N24 printer tray selection...................................................................... 15-47
NPS and DocuSP printer tray selection ............................................................... 15-48
Printer tray selection for other PCL printers ......................................................... 15-50
16. Xerox job ticket packet generation
Job ticket processing ...................................................................................................... 16-1
Internal job ticket commands................................................................................ 16-2
Processing conflicts ............................................................................................ 16-3
Order of precedence ........................................................................................... 16-3
Separator page considerations............................................................................. 16-4
Creating and managing extended job ticket packets........................................................... 16-5
Rules for creating extended job ticket packets ....................................................... 16-5
Creating extended job ticket packets..................................................................... 16-6
Changing, displaying, and printing extended job ticket packets ................................ 16-8
Deleting extended job ticket packets ................................................................... 16-10
17. VIPP command generation
VIPP functionality supported............................................................................................ 17-2
General processing requirements and considerations ........................................................ 17-2
Generating VIPP command elements ............................................................................... 17-3
Indirect method................................................................................................... 17-4
Direct method................................................................................................... 17-10
Combined method ............................................................................................ 17-11
PostScript DSC packets ................................................................................................ 17-13
Creating a PostScript DSC packet ...................................................................... 17-13
Inserting DSC packets through the FONT ID printer file parameter......................... 17-13
XDPE/400 User Documentation (9/2001)
viii
Table of contents
Samples provided by XDPE/400 .................................................................................... 17-14
Using the XDPE/400 VIPP resource commands .............................................................. 17-15
Creating VIPP resources or PostScript DSC packets ............................................ 17-15
Editing, displaying, or printing a VIPP resource or PostScript DSC packet .............. 17-24
Deleting a VIPP resource or DSC packet ............................................................ 17-27
18. Using Monitor Queue
Monitor Queue operation................................................................................................. 18-2
Starting a Monitor Queue session .................................................................................... 18-4
Monitor Queue parameters .................................................................................. 18-6
WAITTIME processing notes.............................................................................. 18-21
Examples of starting a Monitor Queue session .................................................... 18-22
Displaying a Monitor Queue session............................................................................... 18-24
Changing a Monitor Queue session................................................................................ 18-26
Ending a Monitor Queue session ................................................................................... 18-28
Parameters ...................................................................................................... 18-29
Non-zero WAITTIME......................................................................................... 18-29
Clearing multiple Monitor Queue sessions........................................................... 18-30
Resetting a Monitor Queue session ................................................................................ 18-31
Monitor Queue messages ............................................................................................. 18-32
19. Managing print operations
Monitor Queue processing modes .................................................................................... 19-1
*JOB mode processing........................................................................................ 19-2
*PAGE mode processing ..................................................................................... 19-6
Working with Monitor Queue jobs................................................................................... 19-10
Field descriptions.............................................................................................. 19-11
Job accounting............................................................................................................. 19-12
20. Remote/Network printing
Supported printer/interface box configurations ................................................................... 20-3
Local and remote printer configurations................................................................. 20-3
Network printer configurations.............................................................................. 20-3
Considerations ............................................................................................................... 20-6
Using generic packets (XES and PCL modes) ....................................................... 20-6
Interfaces........................................................................................................... 20-6
Using Host Print Transform with TCP/IP ........................................................................... 20-7
Customizing Host Print Transform ........................................................................ 20-7
Setting up TCP/IP support ............................................................................................... 20-8
Creating the sending TCP/IP output queue............................................................ 20-8
Starting the sending writer ................................................................................. 20-12
Starting a Monitor Queue session....................................................................... 20-14
Remote/Network resource downloading.......................................................................... 20-16
XDPE/400 User Documentation (9/2001)
ix
Table of contents
21. Resource management
Copying resources to the XDPEFLR resource folder .......................................................... 21-3
Copying resources from an AS/400 database file ................................................... 21-3
Copying resources from a PC .............................................................................. 21-4
Downloading resources manually (DJDE, XES, and PCL modes) ........................................ 21-5
Example of downloading resources manually ........................................................ 21-5
Downloading PCL macros ................................................................................... 21-8
Downloading PCL fonts ..................................................................................... 21-10
Downloading resources manually (NPS and DocuSP printers in VIPP mode) ..................... 21-12
Downloading VIPP or PostScript resources ......................................................... 21-13
Downloading resources manually (N-series printers in VIPP mode) ................................... 21-17
Example of downloading resources manually ...................................................... 21-17
Downloading resources automatically............................................................................. 21-19
4213 environment saving .............................................................................................. 21-19
Using euro fonts with your PCL print jobs........................................................................ 21-20
Changes to your AS/400 system ........................................................................ 21-20
XDPE/400 and your Xerox PCL printer ............................................................... 21-24
Euro font considerations .................................................................................... 21-26
22. List processing
Creating a list source member ......................................................................................... 22-2
Creating a Xerox resource list.......................................................................................... 22-4
Parameters ........................................................................................................ 22-5
Configuring a list processing job....................................................................................... 22-6
Example of using list processing to download resources..................................................... 22-7
Creating a source list of resources........................................................................ 22-7
Creating a Xerox resource list .............................................................................. 22-7
Downloading the resources.................................................................................. 22-9
Multiple printer list support............................................................................................. 22-10
Downloading PCL fonts and macros using a resource list ................................................. 22-11
23. Logical processing
Logical processing considerations .................................................................................... 23-3
Restarting a PCL constant back print job............................................................... 23-3
Logical processing considerations and restrictions ................................................. 23-3
Duplex printing ................................................................................................... 23-5
Placement of XES forms...................................................................................... 23-6
Performance considerations ................................................................................ 23-6
Creating logical processing packets.................................................................................. 23-7
Packet name syntax............................................................................................ 23-7
Packet creation procedure ................................................................................... 23-8
Packet parameters.............................................................................................. 23-9
Changing logical processing packets .............................................................................. 23-13
Starting logical processing............................................................................................. 23-15
XDPE/400 User Documentation (9/2001)
x
Table of contents
24. Multi-part printing
Creating a multi-part packet............................................................................................. 24-3
Considerations ................................................................................................... 24-5
Example of a multi-part packet ............................................................................. 24-6
Changing a multi-part packet ........................................................................................... 24-8
Deleting a multi-part packet ............................................................................................. 24-9
Starting multi-part processing ........................................................................................ 24-10
25. Multi-up printing
DJDE multi-up generation ............................................................................................... 25-1
XES multi-up generation ................................................................................................. 25-5
Requirements..................................................................................................... 25-6
Creating multi-up XES packets............................................................................. 25-7
PCL multi-up generation................................................................................................ 25-15
Indirect method................................................................................................. 25-15
Direct method................................................................................................... 25-15
Requirements................................................................................................... 25-16
Creating multi-up PCL packets ........................................................................... 25-17
VIPP multi-up generation .............................................................................................. 25-27
Indirect method................................................................................................. 25-28
Direct method................................................................................................... 25-29
Requirements................................................................................................... 25-29
26. Troubleshooting
Monitor Queue solutions ................................................................................................. 26-1
Job does not print ............................................................................................... 26-1
Multiple Monitor Queue session database errors.................................................... 26-2
Monitor Queue Diagnostic Utility........................................................................... 26-4
Switching from A4 size paper to US letter size paper is unsuccessful ....................... 26-5
XDPM (XES) solutions and considerations........................................................................ 26-6
Duplex job using Flex i-data box prints simplex ...................................................... 26-6
Considerations when using generic packets .......................................................... 26-7
PCL solutions, considerations, and limitations ................................................................... 26-8
Multiple copies do not print with DEVCLS set to *NET ............................................ 26-8
NPS printer will not print duplex............................................................................ 26-9
Jobs sent to network printers do not print some special characters ........................ 26-10
Problems using three-hole paper with 4220/4230 printers ..................................... 26-11
Considerations when using generic packets ........................................................ 26-12
Known PCL limitations ...................................................................................... 26-14
VIPP solutions ............................................................................................................. 26-16
Jobs print with incorrect line spacing................................................................... 26-16
Job sent to NPS printer shows “ineligible” status .................................................. 26-16
DP65 jobs print additional, incomplete copies when using trailer pages .................. 26-16
NPS printer will not print duplex.......................................................................... 26-17
LPP duplex jobs print simplex ............................................................................ 26-18
Multiple copy jobs print incorrectly when using trailer pages .................................. 26-19
XDPE/400 User Documentation (9/2001)
xi
Table of contents
27. Messages
XDPE/400 message details ............................................................................................. 27-1
Locating error messages ................................................................................................. 27-3
Using the WRKMONQJOB command ................................................................... 27-4
Accessing the on-screen display .......................................................................... 27-6
Accessing DSPJOBLOG ..................................................................................... 27-7
Accessing the QUSRSYS/QEZJOBLOG output queue ........................................... 27-7
Section Four: Appendices
A. XDPE/400-supported interface boxes
3X Twinax Printstation interface ........................................................................................ A-1
42XX INTERNAL interface ............................................................................................... A-3
4450 INTERNAL interface ................................................................................................ A-4
Agile 5250 OPTIMA interface............................................................................................ A-4
XPPM mode........................................................................................................ A-4
XDPM mode ....................................................................................................... A-5
BARR interface ............................................................................................................... A-6
Flex i-data 5250 C/RS-Xerox interface............................................................................... A-8
XPPM considerations ........................................................................................... A-9
XDPM considerations........................................................................................... A-9
IBM AS/400 Client Access interface .................................................................................A-10
Smart interface...............................................................................................................A-11
Solimar interface ............................................................................................................A-11
Spur/USAII interface .......................................................................................................A-12
B. XDPE/400 distributed samples and resources
SAMPLE file contents ...................................................................................................... B-1
XDPEFLR resource folder ................................................................................................ B-2
XDPEFLR contents (letter version) ........................................................................ B-3
XDPEFLR contents (A4 version) ........................................................................... B-6
C. Processing notes
Spool file scanning .......................................................................................................... C-1
SCS commands .................................................................................................. C-2
Multi-up processing.............................................................................................. C-3
Logical processing and color processing ................................................................ C-3
Color processing.................................................................................................. C-3
D. SCS commands for the 5225 and 5219 printers
SCS commands .............................................................................................................. D-1
Set FID through GFID SCS command in 5219 printer emulation mode.................................. D-3
XDPE/400 User Documentation (9/2001)
xii
Table of contents
Section Five: Glossary
Section Six: Index
XDPE/400 User Documentation (9/2001)
xiii
Table of contents
XDPE/400 User Documentation (9/2001)
xiv
Section One:
Introduction to XDPE/400
XDPE/400 is a print management facility for use on an IBM AS/400. As
such, XDPE/400 provides enhanced document formatting and printer
control for many of your daily printing requirements. It uses standard
OS/400 screens and procedures and does not require any changes to
your application programs.
This document provides the information you need to install and print
documents with XDPE/400. Also included are the information and
procedures you may need when migrating from an older version of
XDPE/400 to XDPE/400 2.1.4.
XDPE/400 documentation is delivered in PDF format on a CD-ROM. It is
designed to be viewed online; however, page layouts have been
maintained so that you can duplex print all or part of the documentation
as necessary.
Introduction to XDPE/400 (9/2001)
1.
1
Getting Started
This chapter contains the following information:
•
A brief description of this manual and how to use it
•
An overview of AS/400 and XDPE/400 printing
•
The major features and functions offered by the Xerox Document
Print Executive for the IBM AS/400 (XDPE/400) software
The product information and instructions presented herein apply only to
XDPE/400 Version 2, Release 1, Modification 4.
NOTE: Xerox only supports the XDPE/400 features and functions
documented in the user documentation, XDPE/400 maintenance
bulletins, or help displays. Do not assume support is provided if it is
not explicitly documented.
Before you begin
Before you install the XDPE/400 software, make sure you meet the
installation requirements discussed in this manual. Before you begin to
use the XDPE/400 software, verify that XDPE/400 has been installed and
the IVP run successfully.
To install the XDPE/400 software, you must know how to use standard
AS/400 CL commands, including CRTUSRPRF, ADDIRE, RSTLIB, and
RSTDLO. For information about these commands, refer to the OS/400 CL
Reference and the OS/400 Printer Device Programming.
In addition, you should be familiar with the basic AS/400 printing
concepts, the Xerox printers supported by XDPE/400, and any twinax
interface boxes you want to use with these Xerox printers. If you will be
using network-attached printers, you should also be familiar with basic
networking concepts. Refer to the OS/400 Printer Device Programming
for a complete explanation of the AS/400 printing process.
Introduction to XDPE/400 (9/2001)
1-1
Getting Started
About this manual
This document is divided into these sections:
•
Section One: Introduction to XDPE/400 provides an introduction to
the XDPE/400 software and provides an overview of the new
features and enhancements distributed with XDPE/400.
•
Section Two: Installing and Customizing XDPE/400 provides the
information you should consider before migrating from an earlier
version of XDPE/400 to 2.1.4, along with the information you need to
install XDPE/400, configure your AS/400 to print with XDPE/400,
and perform the installation verification procedure (IVP).
•
Section Three: Printing Documents with XDPE/400 provides the
information you need to print AS/400-generated documents on Xerox
printers. These topics are discussed:
—
Configuring your AS/400 print jobs to print using XDPE/400
—
Managing printer and spool files
—
Using XDPE/400 to create printer control packets
–
–
–
–
–
–
Dynamic job descriptor entry (DJDE) control packets
Xerox escape sequence (XES) control packets
XES color control packets
PCL control packets
Xerox extended job ticket packets
VIPP Job Descriptor Tickets (JDTs)
—
Managing your printer resources
—
Using the XDPE/400 high-end processing and printing features
–
–
–
–
List processing
Logical processing
Multi-part printing
Multi-up printing
—
Using the Monitor Queue to monitor and process your print jobs
—
Using XDPE/400 to print to local, remote, or network printers
—
Troubleshooting procedures for problem diagnosis and
correction
—
Displaying messages generated by XDPE/400
•
Section Four: Appendices provides information about supported
twinax interface boxes; lists the samples and resources distributed
with XDPE/400; provides information about the implementation of
multi-up processing, logical processing, and color processing; and
provides a list of the SCS commands for the 5225 and 5219 printers.
•
Section Five: Glossary provides a glossary of the terms used within
the documentation as they relate to XDPE/400.
•
Section Six: Index contains indexed information to help you locate
specific topics.
Introduction to XDPE/400 (9/2001)
1-2
Getting Started
Conventions used in this manual
These conventions are used in this manual:
•
The name of the main XDPE/400 printer control batch job is Monitor
Queue. This manual does not distinguish between XDPE/400 and
the Monitor Queue when referring to the Monitor Queue functions.
•
Keywords for command parameters and attributes in non-procedural
text appear in UPPERCASE letters. For example, ENDMONQ.
•
Spool file attributes and parameter names in non-procedural text are
documented as they appear on your AS/400 display. In most cases,
they appear in Initial uppercase letters. For example, Separator
page source.
•
Variable information appears in italics. For example, tape device
name.
•
Commands and keywords within procedures and examples appear
in UPPERCASE BOLD characters. For example, STRMONQ.
•
Document titles appear in italics.
•
References to other chapters within this document are enclosed in
quotes.
•
Blue text within the body of a PDF file is used to indicate an active
link to the named section or feature.
NOTE: A note is a hint that assists you in performing a task or
understanding the text. For greater emphasis, notes appear in blue text.
CAUTION: A caution notifies you that an action or omission may
result in damage to your equipment, software, or data. For greater
emphasis, cautions appear in red text.
Introduction to XDPE/400 (9/2001)
1-3
Getting Started
XDPE/400 system overview
XDPE/400 is a print management facility for use on an IBM AS/400. As
such, XDPE/400 provides enhanced document formatting and printer
control for many of your daily printing requirements. It uses standard
OS/400 screens and procedures and does not require any changes to
your application programs.
These are some of the tasks you can perform on a Xerox printer with
XDPE/400:
•
Merge data with an electronic form
•
Print multiple copies of a job
•
Print on both sides of the sheet of paper (duplex printing)
•
Print multiple page images on a single sheet of paper (multi-up
printing)
•
Print in color
AS/400 printing
To print on an AS/400 system to a locally-attached printer, these elements
are required:
•
Application — A program that merges variable data with the
information in the printer file to create a spool file.
•
Printer file — An object containing parameters that determine how a
print job should be created.
•
Spool file — A file containing data that is ready for printing.
•
Output queue — An object containing a list of spool files waiting to
be processed.
•
Printer writer — An AS/400 object that formats the spool file and
sends it to a local print device.
Figure 1-1 illustrates these elements.
Introduction to XDPE/400 (9/2001)
1-4
Getting Started
Figure 1-1. AS/400 printing elements
In most common forms of local printing on the AS/400, an application
program creates a printer file or references a printer file that you have
created. The application merges the printer file specifications with your
data, such as a report, to create a spool file.
The spool file contains attributes that are created from the printer file.
These attributes specify how the job should be printed. The spool file is
placed in an output queue where the printer writer sends it to the printer
or over a network.
Refer to the OS/400 Printer Device Programming for a complete
explanation of the AS/400 printing process.
Network printing is similar to local printing, but with some important
differences. For information on network printing, refer to chapter 20 in
Section Three: Printing Documents with XDPE/400.
Introduction to XDPE/400 (9/2001)
1-5
Getting Started
Printing with XDPE/400
The part of XDPE/400 that processes print jobs is called the Monitor
Queue. Monitor Queue is used in conjunction with the AS/400 printer
writer to process spool files for printing on Xerox printers.
The Monitor Queue takes spool files placed in the application output
queue, processes them, and places them in the processed output queue.
From there they are written to the printer by the printer writer, as shown
in figure 1-2.
For information about how XDPE/400 operates, see Section Three:
Printing Documents with XDPE/400.
Figure 1-2.
Introduction to XDPE/400 (9/2001)
XDPE/400 and AS/400 printing elements
1-6
Getting Started
XDPE/400 features and functions
XDPE/400 is fully compatible with the AS/400 and works within the
AS/400 printing architecture to provide post-processing for your AS/400
print jobs. XDPE/400 automatically tailors your print jobs to the specific
Xerox printer you are using. XDPE/400 supports DJDE, XES, PCL, VIPP
(PostScript), and extended job ticketing data streams.
Using XDPE/400, you can modify your print jobs as much or as little as
you want, often without having to know any printer control languages.
XDPE/400 provides a facility to create, manage, and download printer
control packets and other processing and printing resources.
A variety of connectivity options are available. XDPE/400 can monitor
multiple output queues automatically, processing jobs for both network
and locally-attached printers.
Printer control commands
XDPE/400-generated printer control commands allow you to control
printer functions, such as:
•
•
•
•
•
•
•
•
•
•
Fonts
Electronic form names
Paper type
Ink color
Margin settings
Number of copies
Simplex or duplex printing
Multi-up printing
Back overlay
Page orientation (even if the orientation is not supported by the IBM
printer that the Xerox printer is emulating)
For simple applications, XDPE/400 can generate printer control
commands for your jobs automatically without having to change your
application program.
High-end printing and processing
XDPE/400’s high-end printing and processing capabilities allow you to
fully utilize XDPE/400 and your printer, or to change a job after it has been
processed by the application. XDPE/400 provides an easy way to utilize
these features by including Xerox printer control commands in your line
mode documents using packets. A packet is a collection of printer control
commands.
In most cases, you can create printer control packets using familiar
OS/400 screens without having to learn Xerox printer programming
languages or the syntax for Xerox printer control commands.
If you plan to print to a Xerox XPPM printer, you need to create DJDE
packets. Likewise, if you plan to print to an XDPM, PCL, or PostScript
printer, your packets need to consist of XES, PCL, or VIPP commands,
respectively.
Introduction to XDPE/400 (9/2001)
1-7
Getting Started
Depending on your printer type and printer language, you can use
XDPE/400 to create processing packets for these high-end functions:
•
•
•
•
List processing
Logical processing
Multi-part printing
Multi-up printing
List processing
List processing allows you to create a list of objects to be processed with
a job. You can list:
•
Printer resources to be downloaded (fonts, forms, PDEs, macros,
etc.)
•
Printer control packets and a control character to specify the mode
of command generation
•
Logical processing packets
Logical processing
Logical processing allows you to dynamically change print specifications
on page boundaries within a job. XDPE/400 will search the print data for
a user-specified text string. When a match is found, the printer control
packet you specified will be inserted into the job on that page.
Multi-part printing
Multi-part printing allows you to print multiple versions of a single job. You
can specify different processing modes, packets, and destinations for
each version, tailoring each to your needs.
Multi-up printing
Multi-up printing prints multiple logical pages on a physical page. With
XDPE/400, you can print up to 32,767 logical pages on each physical
page, depending on the capabilities of your printer.
Resource management
For XPPM, XDPM, or PCL printers, XDPE/400 provides a series of menus
for your use in managing printer resources. These resource management
menus allow you to manually download resources to the printer. Or you
can use list processing to download resources for your jobs automatically.
Depending on the printer type, the printer resources can consist of fonts,
forms, images, logos, JDLs, PDLs, FSLs, JSLs, and macros.
For PostScript printers, XDPE/400 provides commands that allow you to
manually download VIPP or PostScript resources to the printer. The
printer resources can consist of fonts, forms, images, Job Descriptor
Tickets (JDTs), encoding tables, segments, and VIPP core and setup
files.
Introduction to XDPE/400 (9/2001)
1-8
Getting Started
Monitoring output queues
An XDPE/400 batch job called the Monitor Queue monitors your
application output queue for spool files that are ready to be processed for
printing. When one of these spool files is found, XDPE/400 generates
printer control commands and sends these commands to the printer with
your spool file.
You can start multiple sessions of Monitor Queue, but each session must
monitor a different output queue. Each session operates independently
and can be set up specifically for the needs of that session. For example,
you can have a session printing to a 4235 printer in XPPM mode running
concurrently with a session printing to a 4220 printer in PCL mode via a
network.
Supported printers
XDPE/400 supports these types of Xerox printers and data streams:
•
Xerox Production Print Mode (XPPM) printers using data streams
containing dynamic job descriptor entries (DJDEs)
•
Xerox Distributed Print Mode (XDPM) printers using data streams
containing Xerox Escape Sequences (XESs)
•
Printer Control Language (PCL) printers using PCL data streams
•
PostScript printers using Variable Data Intelligent PostScript
PrintWare (VIPP) data streams
Xerox Production Print Mode printers
These Xerox Production Print Mode (XPPM) printers accept data streams
containing dynamic job descriptor entries (DJDEs) as printer control
commands. The abbreviated model numbers in parenthesis are used in
place of the complete model number names in all other references in this
manual.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
9790
9700
8790
8700
4890
4850
4635
4450
4235
4135
4090
4050
3700
DocuPrint 180 LPS (180 LPS)
DocuPrint 96 (DP96)
DocuPrint 92C LPS (92C LPS)
Introduction to XDPE/400 (9/2001)
1-9
Getting Started
Xerox Distributed Print Mode printers
These Xerox Distributed Print Mode (XDPM) printers accept data streams
containing Xerox Escape Sequences (XESs) as printer control
commands:
•
•
•
•
•
4700
4235
4213 II
4030
3700
Xerox Printer Control Language printers
These Xerox Printer Control Language (PCL) printers process PCL data
streams. The abbreviated model numbers in parenthesis are used in
place of the complete model number names in all other references in this
manual.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
4230/MRP (4230)
4220/MRP (4220)
4219/MRP (4219)
4215/MRP (4215)
Document Centre 265LP (DC265LP)
Document Centre 255LP (DC255LP)
DocuPrint 4890 NPS (4890 NPS)
DocuPrint 4850 NPS (4850 NPS)
DocuPrint 4635 NPS (4635 NPS)
DocuPrint 4520/4520mp (4520)
DocuPrint 4517/4517mp (4517)
DocuPrint 4512/4512mp (4512)
DocuPrint 4090 NPS (4090 NPS)
DocuPrint 4050 NPS (4050 NPS)
DocuPrint 180 NPS (180 NPS)
DocuPrint 96 NPS (DP96NPS)
DocuPrint 92C NPS (92C NPS)
DocuPrint 65 (DP65)
DocuPrint N32 (N32)
DocuPrint N24 (N24)
References to NPS printers refer to these NPS printer models: 4890 NPS,
4850 NPS, 4635 NPS, 4090 NPS, 4050 NPS, 180 NPS, DP96NPS, and
92C NPS.
References to DocuSP printers refer to the DP65 printer.
Introduction to XDPE/400 (9/2001)
1-10
Getting Started
Xerox PostScript printers
These Xerox PostScript printers process Variable Data Intelligent
PostScript PrintWare (VIPP) data streams. The abbreviated model
numbers in parentheses are used in place of the complete model number
names in all other references in this manual.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
DocuPrint
DocuPrint
DocuPrint
DocuPrint
DocuPrint
DocuPrint
DocuPrint
DocuPrint
DocuPrint
DocuPrint
DocuPrint
DocuPrint
DocuPrint
DocuPrint
DocuPrint
DocuPrint
DocuPrint
DocuPrint
4890 NPS (4890 NPS)
4850 NPS (4850 NPS)
4635 NPS (4635 NPS)
4090 NPS (4090 NPS)
4050 NPS (4050 NPS)
180 NPS (180 NPS)
96 NPS (DP96NPS)
92C NPS (92C NPS)
65 (DP65)
N4025 (N4025)
N3225 (N3225)
N2825 (N2825)
N2125 (N2125)
N2025 (N2025)
N40 (N40)
N32 (N32)
N24 (N24)
N17 (N17)
References to NPS printers refer to these NPS printer models: 4890 NPS,
4850 NPS, 4635 NPS, 4090 NPS, 4050 NPS, 180 NPS, DP96NPS, and
92C NPS.
References to DocuSP printers refer to the DP65 printer.
References to N-series printers refer to these N-series printer models:
N4025, N3225, N2825, N2125, N2025, N40, N32, N24, and N17.
Generic printer devices
Generic printer device support is available for the following data streams:
•
•
•
•
LCDS
PCL
PCL with Xerox Job Tickets
VIPP
Generic printer devices provide the ability to use new printers during the
time period between the introduction of the printer and the implementation
and verification of support for the printer in XDPE/400.
Generic device support capabilities are limited to the functional
capabilities common to all currently supported LCDS, PCL, and VIPP
printers.
Advanced features may be implemented by using generic packets, DSC,
or by adding entries to job tickets.
Introduction to XDPE/400 (9/2001)
1-11
Getting Started
Introduction to XDPE/400 (9/2001)
1-12
2.
2
New and updated XDPE/400 features
This chapter describes the new and updated features included in version
2.1.4 of XDPE/400. The enhancements made for versions 2.1.3, 2.1.2,
2.1.1, 2.1, and 2.0 also are listed here to help those users migrating from
previous versions of XDPE/400.
All features and enhancements listed in this chapter are documented
within this manual. Information added or modified for XDPE/400 2.1.4 is
marked with change bars in the margin; editorial and formatting changes
are not marked.
New features in XDPE/400 2.1.4
XDPE/400 offers several new features and enhancements for 2.1.4.
These new features and enhancements include:
•
•
•
•
•
Generic device support
OS/400 5.1 compliance
VIPP 2001 compliance
N-series printers in VIPP mode support
Revised parameters
Generic device support
XDPE/400 now supports the use of generic devices. Monitor Queue and
resource download commands have been modified to allow users to
specify non-specific print devices. Generic device types are:
•
•
•
•
•
•
*DOCUSP
*LCDS
*NPS
*PCL
*VIPP
*XJT
OS/400 5.1 support
XDPE/400 2.1.4 supports OS/400 5.1.
VIPP 2001 compliance
XDPE/400 2.1.4 supports VIPP 2001.
Introduction to XDPE/400 (9/2001)
2-1
New and updated XDPE/400 features
N-series printers in VIPP mode support
XDPE/400 now supports the following N-series printers:
•
•
•
•
•
•
•
•
•
DocuPrint
DocuPrint
DocuPrint
DocuPrint
DocuPrint
DocuPrint
DocuPrint
DocuPrint
DocuPrint
N4025 (N4025)
N3225 (N3225)
N2825 (N2825)
N2125 (N2125)
N2025 (N2025)
N40 (N40)
N32 (N32)
N24 (N24)
N17 (N17)
The following downloadable printer resources have been added:
•
•
•
•
•
DNLDVIPENC — Downloads VIPP encoding tables
DNLDVIPFNT — Downloads VIPP font resources
DNLDVIPFRM — Downloads VIPP form resources
DNLDVIPIMG — Downloads VIPP image resources
DNLDVIPJDT — Downloads VIPP JDT resources
NOTE: List processing support of VIPP-enabled printers is limited to
N-series printers. The list processing feature does not support
resource downloads or the use of generic files for DocuSP and NPS
printers in VIPP mode.
Revised parameters
This section lists the parameters that have been revised for XDPE/400
2.1.4 processing. For more information on these parameters, refer to
Section Three: Printing Documents with XDPE/400.
Monitor Queue parameters
•
Printer model (MODEL) — Specifies the printer model to be used
during your Monitor Queue session.
XPPM download resource (DNLDxxxRSC) parameters
•
Printer model (MODEL) — Specifies the model number of the Xerox
printer to download the resource.
PCL download resource (DNLDxxxRSC) parameters
•
Printer model (MODEL) — Specifies the model number of the Xerox
printer to download the resource.
Introduction to XDPE/400 (9/2001)
2-2
New and updated XDPE/400 features
New features in XDPE/400 2.1.3
New features and enhancements for 2.1.3 include:
•
•
•
•
•
•
•
VIPP page-level support
PCL euro font support
OS/400 4.5.0 compliance
Added printer support
Revised parameters
XDPE/400 2.1.3 distributed on CD-ROM
User documentation distributed on CD-ROM
VIPP page-level support
XDPE/400 now supports the processing of VIPP data streams for
PostScript printers on a page-level basis. Page-level support offers the
use of Job Descriptor Tickets (JDTs) at page boundaries using the
XDPE/400 logical processing feature.
VIPP now supports both the logical processing and list processing
features. However, the list processing feature currently does not support
either the downloading of resources or the use of generic files in VIPP
mode.
PCL euro font support
XDPE/400 is certified to process PCL jobs utilizing Xerox printer-resident
and downloadable euro fonts. The NPS, N32, and N24 PCL printers
support resident fonts.
OS/400 4.5.0 support
XDPE/400 2.1.3 supports OS/400 4.5.0. The following IBM maintenance
must be applied:
•
•
Cumulative maintenance C0231450
PTF SF63410
Added printer support
XDPE/400 now supports these printers:
•
XPPM printer — DocuPrint 92C LPS (92C LPS)
•
PCL/PostScript printer — DocuPrint 92C NPS (92C NPS)
Note these considerations when using the 92C NPS printer:
•
Automatic tray selection is based on the page size.
•
Resource downloading is not supported, except embedded within a
print job.
Introduction to XDPE/400 (9/2001)
2-3
New and updated XDPE/400 features
Revised parameters
This section lists the parameters that have been revised for XDPE/400
2.1.3 processing. For more information on these parameters, refer to
Section Three: Printing Documents with XDPE/400.
Global value parameters
•
Source file translation table (RESLIB) — Specifies the name of the
ASCII-to-EBCDIC translation table for the QDCXLATE API to use
when downloading source files (FSL or JSL) and multi-up packets to
Xerox printers.
•
PC/Support translation table (PCSLIB) — Specifies the name of the
translation table that the system uses when constructing printer
language commands, multi-up data, XES data, and XES resources
for local and network processing. XDPE/400 converts all printer
commands and data from EBCDIC to ASCII and writes them to an
ASCII spool file.
Logical processing (LPP) parameters
•
When to apply (WHEN) — Specifies when and where to insert the
printer control packet. *TOP is supported in VIPP mode; *BOTTOM
is not supported in VIPP mode.
Monitor Queue parameters
•
Printer model (MODEL) — Specifies the printer model to be used
during your Monitor Queue session.
•
Workstation customizing object (WSCST) — For network printing,
this parameter specifies the workstation customizing object that
contains the Host Print Transform table to be used for this Monitor
Queue session.
PCL font parameters
•
Font file name (PCLFONTS) — Specifies the name of the file in the
XDPEFLR/PCLFONTS folder that contains the font definition to be
downloaded. PCLFONTS can also specify a list name, preceded by
the at sign (@), that contains the names of multiple resources to be
downloaded.
Introduction to XDPE/400 (9/2001)
2-4
New and updated XDPE/400 features
PCL packet parameters
•
Font selection by attributes (FONT) — Selects the initial page font to
be used for the page by PCL font attributes. You must explicitly
specify all seven attributes to make sure the font you want matches
a font that is resident on the printer. If an exact match is not found,
the default printer font is used.
XPPM download resource (DNLDxxxRSC) parameters
•
Printer model (MODEL) — Specifies the model number of the Xerox
printer to download the resource.
XDPE/400 2.1.3 distributed on CD-ROM
XDPE/400 is now distributed on CD-ROM, in ISO 9660 format. The
XDPE/400 installation instructions have been modified to support the new
CD-ROM media, as well as the existing media types. See Section Two:
Installing and Customizing XDPE/400 for the updated installation
instructions.
User documentation distributed on CD-ROM
The XDPE/400 documentation is now available on CD-ROM, in ISO 9660
format. The documentation is saved in Portable Document Format (PDF),
which requires Adobe Acrobat Reader for viewing and printing. Acrobat
Reader 4.0 is included on the CD-ROM.
Introduction to XDPE/400 (9/2001)
2-5
New and updated XDPE/400 features
New features in XDPE/400 2.1.2
New features and enhancements for 2.1.2 include:
•
•
•
•
•
•
•
VIPP job-level support
Xerox extended job ticket support
OS/400 4.3.0 and 4.4.0 compliance
Additional PCL printers supported
Euro font certification
Revised parameters
New commands
VIPP job-level support
XDPE/400 now supports the processing of VIPP data streams for
PostScript printers on a job-level basis.
For additional information about VIPP command elements, refer to the
Xerox Variable Data Intelligent PostScript PrintWare (VIPP) Reference
Manual. See the PostScript Language Reference Manual for information
on PostScript command elements.
Xerox extended job ticket support
XDPE/400 now supports the use of Xerox extended job ticket packets for
setting up complex print jobs on PCL printers. This feature functions on
NPS and DocuSP printers in PCL mode with job ticket processing enabled
on the printer controller.
Extended job ticket packet processing is supported using the Direct and
Combined command generation methods. The Indirect command
generation method is not supported.
It is the responsibility of the user to know and understand the job ticket
command syntax and usage. For more information, refer to Xerox
Production Systems Job Ticket Programming Guide.
For a list of options available on your NPS and DocuSP printers, refer to
the Xerox Production Systems Job Ticket Programming Guide.
OS/400 4.3.0 and 4.4.0 support
XDPE/400 2.1.2 supports OS/400 4.3.0 and 4.4.0. The following IBM
corrective maintenance must be applied:
•
PTF SF52738 for OS/400 4.3.0
•
PTF SF51099 if you will be running an NPS printer in PCL mode
using NPS version 1.6 or higher, or in VIPP mode using any NPS
version
Introduction to XDPE/400 (9/2001)
2-6
New and updated XDPE/400 features
Added PCL printer support
XDPE/400 2.1.2 supports these additional PCL network printers:
•
•
DocuPrint 96 NPS (DP96NPS)
DocuPrint 65 (DP65)
Note these considerations when using the DP96NPS or DP65 printer:
•
Automatic tray selection is based on the page size.
•
Resource downloading is not supported, except embedded within a
print job.
NOTE: XDPE/400 capabilities are limited to the current level of PCL
support in XDPE/400 and to the functional abilities of the printers.
Euro font certification
XDPE/400 is certified to process DJDE and XES jobs utilizing the Xerox
Euro fonts. PostScript jobs utilizing the type 1 Euro fonts with
extension.pfb also have been certified. PCL and all other PostScript jobs
are not yet certified.
Revised parameters
This section lists the parameters that have been revised for XDPE/400
2.1.2 processing.
Monitor Queue parameters
•
Printer model (MODEL) — Specifies the model to be used during
your Monitor Queue session.
•
Printer mode (MODE) — Specifies the mode in which the printer will
operate.
•
Workstation customizing object (WSCST) — For network printing,
this parameter specifies the workstation customizing object that
contains the Host Print Transform table to be used for your Monitor
Queue session.
PCL packet parameters
•
Job ticket processing (XTICKET) — New parameter that allows for
the specification of extended job ticket processing subparameters,
which are valid for NPS and DocuSP printers only.
•
Paper type (PAPERTYPE) — Selects the source tray based on the
paper type. This parameter applies to the N32, N24, NPS, and
DocuSP printers only.
Introduction to XDPE/400 (9/2001)
2-7
New and updated XDPE/400 features
New commands
This section lists commands that have been added for XDPE/400 2.1.2
processing.
Xerox extended job ticket commands
•
Create Xerox Job Ticket (CRTXTCK) — Allows you to create a Xerox
extended job ticket packet.
•
Change Xerox Job Ticket (CHGXTCK) — Allows you to edit, display,
or print a Xerox extended job ticket packet.
•
Delete Xerox Job Ticket (DLTXTCK) — Allows you to delete a Xerox
extended job ticket packet.
VIPP commands
•
Create VIPP Resource (CRTVIPRSC) — Allows you to create a
VIPP resource.
•
Change VIPP Resource (CHGVIPRSC) — Allows you to edit,
display, or print a VIPP resource or DSC packet.
•
Delete VIPP Resource (DLTVIPRSC) — Allows you to delete a VIPP
resource or DSC packet.
•
Download VIPP Resource (DNLDVIPRSC) — Allows you to
download a VIPP or PostScript resource.
Introduction to XDPE/400 (9/2001)
2-8
New and updated XDPE/400 features
New features in XDPE/400 2.1.1
New features and enhancements for 2.1.1 include:
•
•
•
•
•
Trailer separator page support
Duplex extended support
OS/400 4.2.0 compliance
Additional PCL and XPPM printers supported
New and revised parameters
Trailer separator page support
XDPE/400 now has the ability to produce trailer separator pages. A trailer
page is a separator page that prints at the end of a job.
Trailer separator pages are enabled at the Monitor Queue level. The
Process separator page (BANNER) Monitor Queue parameter has been
modified to add the options TRAILER and BOTH. The existing option YES
directs the Monitor Queue to produce only banner pages; TRAILER
directs the Monitor Queue to produce only trailer pages; and BOTH
directs the Monitor Queue to print both banner and trailer pages.
This enhancement does not affect current banner separator page
processing. A trailer separator page template is included in
XDPE212\XDPEBANNER\TRAILER.
Duplex extended support
XDPE/400 duplex extended support allows you to choose between two
duplexing standards for PCL jobs — either the standard defined by
Hewlett Packard’s PCL or by IBM’s OS/400. You can select the duplex
standard of your choice through the Duplex standard (DUPLEXSTD)
global value.
OS/400 4.2.0 compliance
XDPE/400 2.1.1 has been modified to support OS/400 version 4.2.0. If
you are running XDPE/400 on OS/400 version 4.2.0, all modules in the
XDPE/400 application library must be converted to run within the 64-bit
RISC architecture of OS/400 4.2.0. Depending on the configuration of
your AS/400 system, the XDPE/400 application library may be converted
automatically during installation.
Introduction to XDPE/400 (9/2001)
2-9
New and updated XDPE/400 features
Added printer support
XDPE/400 2.1.1 supports these additional printers:
•
PCL printers
—
—
—
—
—
•
Document Centre 265LP
Document Centre 255LP
DocuPrint 180 NPS
DocuPrint N32
DocuPrint N24
XPPM printers
—
—
DocuPrint 180 LPS
DocuPrint 96
New and revised parameters
Several parameters have been added or revised for XDPE/400 2.1.1
processing.
Monitor Queue parameters
•
Printer model (MODEL) — Specifies the printer model to be used
during your Monitor Queue session.
•
Process separator page (BANNER) — Specifies the type of
separator pages to be printed with your jobs, either
AS/400-generated or XDPE/400-generated.
•
Separator page source (BANNERSRC) — Specifies the source tray
for the selection of separator pages, both banners and trailers.
•
Data page source (DATASRC) — Specifies the source tray for the
selection of data pages.
Global Values
•
Source drawer assignments (DRAWER) — Maps values in the
Source drawer (DRAWER) printer file parameter to Xerox source
trays.
•
Duplex standard (DUPLEXSTD) — Specifies the duplex standard to
be set for all PCL data streams processed through XDPE/400, as
defined by either HP or IBM.
XPPM download resource (DNLDxxxRSC) parameters
•
Printer model (MODEL) — Specifies the model number of the Xerox
printer to download the resource.
Introduction to XDPE/400 (9/2001)
2-10
New and updated XDPE/400 features
Download PCL macro (DNLDPCLMAC) parameters
•
Printer model (MODEL) — Specifies the printer model number.
•
Macro name (MACRONAME) — Specifies the macro name to use in
subsequent PCL macro management commands.
Download PCL font (DNLDPCLFNT) parameters
•
Printer model (MODEL) — Specifies the printer model number.
•
Font name (FONTNAME) — Specifies the font name to use in
subsequent PCL font management commands. This parameter
applies only to the N32 and N24 printers.
Printer file parameters for PCL processing
•
DUPLEX — Specifies whether to print the output on one side
(simplex) or on both sides (duplex) of the page.
•
DRAWER — Specifies the source drawer from which paper is fed
into the printer.
•
PAGESIZE — Specifies the length and width of the page to be
printed.
PCL packet parameters
•
Print on both sides of sheet (DUPLEX) — Specifies whether to print
on both sides or on one side of a sheet.
•
Source tray (TRAY) — Selects the correct paper tray on a job or
page level.
•
Margin setting (MARGIN) — Assigns page margin settings.
•
Font selection by alphanumeric font name (FONTNAME) — Allows
for the invocation of a pre-loaded font.
•
Paper type (PAPERTYPE) — Selects the source tray based on
paper type.
Introduction to XDPE/400 (9/2001)
2-11
New and updated XDPE/400 features
New features in XDPE/400 2.1
Enhancements for 2.1 include:
•
•
•
Banner page enhancements
Additional PCL printers supported
Revised parameters
Banner page enhancements
In preparation for the year 2000 compliance, the sample banner page
templates supplied with XDPE/400 have been updated to accommodate
the updated field size of a four-digit year. The banner templates included
with XDPE/400 are located in the SAMPLE file in the XDPE/400
application library.
Added PCL printer support
XDPE/400 2.1 supports these additional network printers in PCL mode:
•
•
•
•
•
•
•
•
DocuPrint
DocuPrint
DocuPrint
DocuPrint
DocuPrint
DocuPrint
DocuPrint
DocuPrint
4890 NPS
4850 NPS
4635 NPS
4520/4520mp
4517/4517mp
4512/4512mp
4090 NPS
4050 NPS
Revised parameters
Several parameters have been revised for XDPE/400 2.1 processing.
Monitor Queue parameters
•
Printer model (MODEL) — Specifies the printer model to be used
during this Monitor Queue session.
•
Separator page source (BANNERSRC) — Specifies the source tray
for printing banner pages.
•
Data page source (DATASRC) — Specifies the source tray for
printing data pages.
Introduction to XDPE/400 (9/2001)
2-12
New and updated XDPE/400 features
Global Values
•
Source drawer assignments (DRAWER) — Maps values in the
Source drawer (DRAWER) printer file parameter to Xerox source
trays.
PCL macro and PCL font parameters
•
Printer model (MODEL) — Specifies the printer model.
PCL packet parameters
•
Source tray (TRAY) — Selects the correct paper tray on a job or
page level.
Introduction to XDPE/400 (9/2001)
2-13
New and updated XDPE/400 features
New features in XDPE/400 2.0
New features and enhancements for 2.0 include:
•
•
•
•
•
•
•
•
Multi-up printing
Report distribution for multi-part print jobs
42XX internal interface enhancements
PCL packet enhancements
Network print support
Spool file processing without printer device
Banner page enhancements
New and revised parameters and fields
Multi-up printing
Multi-up printing allows you to print multiple pages of output on one
physical page. XDPE/400 now has two levels of multi-up functionality. In
addition to the *INDIRECT method of multi-up generation allowing up to 4
logical pages per physical side, you may now print up to 32,767 logical
pages per physical page in *DIRECT mode using the enhanced multi-up
printing features for XES and PCL packets.
Multi-up printing using *DIRECT mode is controlled by the Number of
pages per side (PAGESPSIDE) XES or PCL packet parameter and the
Multi-up packet name (PCLMUP or XESMUP) packet parameter. The
PAGESPSIDE parameter specifies the number of logical pages to place
on a page, while the PCLMUP or XESMUP parameter specifies the
multi-up packet to use. These values work together to create the desired
output.
Report distribution for multi-part print jobs
Processing for multi-part print jobs has been enhanced to allow you to
specify an output queue and library for each item on the packet list. This
enables you to send each spool file to a different output queue. Note,
however, that each output queue must support the data stream type you
specify in the Monitor Queue.
NOTE: Because only one printer/interface box configuration can be
specified for a Monitor Queue session, all of the printer/interface
boxes linked to the output queues you specify in a multi-part job must
support this configuration.
Also, you can now print multi-part packets in conjunction with TCP/IP and
Host Print Transform to send PCL ASCII spool files to network-attached
printers.
Introduction to XDPE/400 (9/2001)
2-14
New and updated XDPE/400 features
42XX internal interface enhancements
The MRP feature allows you to set the i-data Y36 command through
XDPE/400. This enhancement applies only to the 42XX i-data interface
box used with the 4230, 4220, 4219, and 4215 printers.
The Y36 command determines how the interface box handles IBM SCS
control codes that are sent to it. A value for MRP internal interface (MRP)
can be entered in both the Monitor Queue and PCL packets. If a value is
entered for the MRP internal interface (MRP) Monitor Queue parameter,
that value is used as the default for that Monitor Queue session. If the
Monitor Queue encounters a PCL packet that contains a value for the
MRP internal interface parameter other than *NONE, that value overrides
the MRP parameter value in the Monitor Queue for the duration of the job
using that PCL packet. When the job has finished processing, XDPE/400
resets the MRP parameter to the default Monitor Queue value.
For more information about this feature, refer to the i-data Twinax
XES/PCL Interface Controller for Xerox Printers Programmer’s Guide.
PCL packet enhancements
In addition to enhanced MRP processing, the *COR option was added for
the Paper Orientation field on the Create Xerox PCL Packets menu. This
option selects Computer Output Reduction (COR) processing, which
reduces output by 70 percent to fit on a letter-sized page in landscape
orientation.
XDPE/400 reduces the logical page size using these processing options:
•
Substitutes the original fonts with smaller fonts
—
—
—
—
14
15
20
27
pitch
pitch
pitch
pitch
for
for
for
for
10
12
15
17
pitch
pitch
pitch
pitch
fonts
fonts
fonts
fonts
•
Reduces the vertical line spacing to 70 percent of the full size
•
Modifies the top and left margins to 1/2 inch
For more information on the *COR option, refer to the i-data Twinax
XES/PCL Interface Controller for Xerox Printers Programmer’s Guide.
Network print support
In addition to the implementation of TCP/IP in XDPE/400, you may now
print documents over the network using TCP/IP and the Host Print
Transform (HPT) feature.
HPT is an IBM OS/400 utility that converts an EBCDIC SCS data stream
into an ASCII data stream. XDPE/400 uses HPT internally to transform the
spool files for use with ASCII printers.
Introduction to XDPE/400 (9/2001)
2-15
New and updated XDPE/400 features
Spool file processing without printer device
You may now process spool files independently of the actual printing of
those files. Previously, you were required to specify a printer writer that
was connected to an active printer that had to be available at the time of
processing.
With this enhancement, XDPE/400 can process spool files when the
processing resources are available, and print the files when the printers
are available.
Banner page enhancements
The &PRINTEXT variable data token was added to banner page
processing. When used, this token prints on the bottom of each page of
printed output and on the separator page. The field width is 30 characters,
and the data is taken from the spool file attribute.
New and revised parameters
Several parameters have been added and revised for XDPE/400 2.0
processing.
Monitor Queue parameters
•
Device class (DEVCLS) — Specifies the class of printing device,
whether it is printing locally, printing over a network to an SCS
EBCDIC-configured printer, or printing over a network to an ASCII
printer.
•
MRP internal interface (MRP) — For a 42XX i-data interface box
attached to a 4230, 4220, 4219, or 4215 printer only, specifies the
Y36 command to use for determining how the interface box handles
IBM control codes that are sent to it.
•
Printer model (MODEL) — Specifies the printer model to be used
during this Monitor Queue session.
•
Printer writer (WTR) — Specifies the name of the printer writer or
device description file assigned to Monitor Queue.
•
Workstation customizing object (WSCST) — Specifies the name of
the workstation customizing object that contains the HPT tables you
wish to use for this Monitor Queue session.
•
Library — Specifies the name of the library where the WSCST is
located.
Introduction to XDPE/400 (9/2001)
2-16
New and updated XDPE/400 features
XES packet parameters
•
Multi-up packet name (XESMUP) — Specifies the name of the
multi-up packet that contains the relevant font and positioning
information for this job.
•
Number of copies (COPIES) — Specifies the number of copies of a
job to be printed.
•
Number of pages per side (PAGESPSIDE) — Specifies the number
of logical pages to be printed on each physical page.
•
MRP internal interface (MRP) — For a 42XX i-data interface box
attached to a 4230, 4220, 4219, or 4215 printer only, specifies the
Y36 command to use for determining how the interface box handles
IBM control codes that are sent to it.
•
Multi-up packet name (PCLMUP) — Specifies the name of the
multi-up packet that contains the relevant font and positioning
information for this job.
•
Number of pages per side (PAGESPSIDE) — Specifies the number
of logical pages to be printed on each physical page.
•
Paper orientation (ORIENT) — Specifies the page orientation to use
when printing the document.
Multi-part packet parameters
•
Output queue — Specifies the queue where the spool file created by
the multi-part printer control packet is sent.
•
Library — Specifies the name of the library where the output queue
is located.
Introduction to XDPE/400 (9/2001)
2-17
New and updated XDPE/400 features
Introduction to XDPE/400 (9/2001)
2-18
Section Two:
Installing and Customizing XDPE/400
Installing and Customizing XDPE/400 (9/2001)
3.
3
Migration actions
This chapter contains information and/or procedures you may need when
migrating from an older version of XDPE/400 to XDPE/400 2.1.4. The
following topics are covered:
•
•
XDPE/400 2.1.4 migration actions
Converting from XDPE/400 2.0
If you are converting from any version of XDPE/400 to XDPE/400 2.1.4,
make sure you read “XDPE/400 2.1.4 migration actions.” If you are
converting from XDPE/400 2.0, you also need to read “Converting from
XDPE/400 2.0.”
XDPE/400 2.1.4 migration actions
If you are converting to XDPE/400 2.1.4 from any version of XDPE/400,
read and consider all the information in this section carefully before
applying the XDPE/400 2.1.4 base tape.
Installation considerations
Note these considerations when installing XDPE/400 2.1.4:
•
The name of the XDPE/400 application library will change to
XDPE214.
•
All XDPE/400 objects in the XDPE/400 application library will be
replaced.
•
Public authority for XDPE/400 folders, subfolders, and documents
will be set to the minimum authority needed for XDPE/400
processing.
•
If you will be printing *INDIRECT or *COMBINED IVPs on A4 paper
using an NPS or DocuSP printer, issue this command before running
the first IVP:
CHGPRTF
FILE(XDPE214/XIVPRTF)
PAGESIZE(70 124 *ROWCOL)
Installing and Customizing XDPE/400 (9/2001)
3-1
Migration actions
OS/400 version requirements
Your AS/400 system must have the following:
•
OS/400 version 4.4.0, 4.5.0, or 5.1
•
These OS/400 PTFs:
—
For 4.4.0, no OS/400 PTFs are required.
—
For 4.5.0, apply cumulative maintenance C0231450 and PTF
SF63410.
—
For 5.1, no OS/400 PTFs are required.
Converting from XDPE/400 2.0
If you are converting to XDPE/400 2.1.4 from 2.0, read and consider the
following before applying the XDPE/400 2.1.4 base tape.
•
All source samples included with XDPE/400, including workstation
customizing objects and banner templates, are now located in a file
called SAMPLE in the XDPE/400 application library.
•
In preparation for the year 2000 compliance, the XDPE/400 banner
templates have been updated to allow for a four-digit year instead of
a two-digit year. The field width of the &DATE, &FILEDATE, and
&JOBDATE data tokens has been increased from 8 characters to 10
characters.
If you have a customized banner page template you want to use
instead of the samples supplied with XDPE/400, you should allow for
the additional size of these fields.
Installing and Customizing XDPE/400 (9/2001)
3-2
4.
4
Installation requirements
This chapter describes the system requirements and migration issues that
need to be addressed before installing XDPE/400.
Requirements
Before you install XDPE/400, make sure that your AS/400 system and
Xerox printer configuration are ready to work with XDPE/400.
XDPE/400 runs in IBM-supported OS/400 environments. When IBM
releases new operating system release levels, XDPE/400 will be updated
to ensure compatibility. Conversely, when IBM withdraws support for an
operating system release level, Xerox also will withdraw support of that
release level six months later. Contact your local Xerox representative or
review the bulletin accompanying your latest maintenance to verify
specific supported software release levels.
AS/400 system requirements
To install and run XPDE/400, your AS/400 system must meet these
requirements:
•
OS/400 version 4.4.0, 4.5.0, or 5.1. These IBM PTFs are required:
—
For 4.4.0, no PTFs are required.
—
For 4.5.0, apply cumulative maintenance C0231450 and PTF
SF63410.
—
For 5.1, no PTFs are required.
•
Twinaxial workstation controller or TCP/IP
•
A minimum of 35 megabytes (MB) of available disk storage
•
At least one of these devices:
—
—
—
—
—
CD-ROM drive
1/4-inch cartridge tape drive
8-mm cartridge tape drive
1/2-inch 3480 or 3490 tape drive
1/2-inch reel-to-reel tape drive (1600 bpi)
NOTE: XDPE/400 is distributed on CD-ROM. Other media types
are available upon request.
Installing and Customizing XDPE/400 (9/2001)
4-1
Installation requirements
Security requirements
The following sections list security requirements for running XDPE/400.
Requirements are provided for level 30 and lower, and for levels 40 and
50. These requirements apply to all levels:
•
To use XDPE/400, your user profile does not require *JOBCTL and
*SPLCTL special authority. The XDPEUSR user profile has
*JOBCTL and *SPLCTL special authorities, which are adopted for
every Monitor Queue session. Refer to OS/400 Advanced Series
Security — Basic for more information about security
implementation.
•
You must be entered in the system directory and have *JOBCTL and
*SPLCTL special authority to start, change, end, or reset a Monitor
Queue session. Refer to “Creating an XDPE/400 user profile” in
chapter 5 for instructions on enrolling a user in the system directory.
•
Time slice (TIMESLICE) and Run priority (RUNPTY) global values
require *JOBCTL special authority to change.
Determining your security level
The security requirements for using XDPE/400 depend on the security
level of your system. Use this command to determine your system’s
security level:
DSPSYSVAL SYSVAL(QSECURITY)
Requirements for level 30 and lower
In this document, it is assumed that XDPE/400 users have Public
authority (*PUBLIC). For security levels up to and including 30, the
security requirements for XDPE/400 users are as follows:
•
You must have *USE authority to the XDPEUSR user profile object
(*USERPRF). You can verify or change this authority using the Edit
Object Authority (EDTOBJAUT) command.
•
You must have at least *USE authority to the MONQJOBD job
description object (*JOBD) in the XDPE/400 application library. You
can verify or change this authority using the Edit Object Authority
(EDTOBJAUT) command.
•
You must have at least *USE authority to all the objects in XDPEFLR
required for each job. You can verify this authority using the Display
DLO Authority (DSPDLOAUT) command or change this authority
using the Change DLO Authority (CHGDLOAUT) command.
•
You must have these authorities for the output queue to be
monitored:
—
The *OUTQ object requires *OBJMGT special authority and
*CHANGE authority. You can verify or change this authority
using the Edit Object Authority (EDTOBJAUT) command.
—
The Authority to check (AUTOCHK) parameter must be
*DTAAUT. You can verify or change this authority using either
the Create Output Queue (CRTOUTQ) or Change Output Queue
(CHGOUTQ) commands.
Installing and Customizing XDPE/400 (9/2001)
4-2
Installation requirements
•
You must have *CHANGE and *OBJMGMT authority to the
XDPEMQSESS file. You can verify or change this authority using the
Edit Object Authority (EDTOBJAUT) command.
•
To work with XDPE/400, you must have *USE authority for specific
IBM-supplied programs (API objects of the type *PGM). Consult your
security administrator for any security-related issues before
changing the authorities to the following programs.
Spool file APIs
User space APIs
HFS APIs
Other APIs
QSYS/QSPCRTSP
QSYS/QUSCRTUS
QSYS/QHFOPNDR
QSYS/QWCRSVAL
QSYS/QSPGETSP
QSYS/QUSCHGUS
QSYS/QHFOPNSF
QSYS/QSYRUSRI
QSYS/QSPOPNSP
QSYS/QUSDLTUS
QSYS/QHFDLTSF
QSYS/QSPPUTSP
QSYS/QHFRDDR
QSYS/QSPCLOSP
QSYS/QHFRNMSF
QSYS/QHFCLODR
QSYS/QHFCLOSF
QSYS/QHFRDSF
QSYS/QHFWRTSF
Requirements for levels 40 and 50
In addition to the security requirements for security levels up to and
including 30, security levels 40 and 50 require that the XDPEUSR user
profile have *SAVSYS special authority as well as authorization to these
objects in the QSYS library:
•
•
RSTLIB (type *CMD)
RSTDLO (type *CMD)
Every user, other than XDPEUSR, who wants to start a Monitor Queue
session must be enrolled in the system directory.
To enroll a user in the system directory, enter this command and press
ENTER:
ADDDIRE
USRID(user address)
USRD('Monque Starter')
USER(userid)
where
user address
Directory address of the user profile
userid
User ID, which can contain up to 8 characters
Printer requirements
This section lists the software release levels required for each printer
supported by XDPE/400.
Installing and Customizing XDPE/400 (9/2001)
4-3
Installation requirements
Xerox Production Print Mode printers
Table 4-1 lists the XPPM printers supported by XDPE/400 and the printer
software versions supported for each of the printers.
Table 4-1.
XPPM printers
Xerox printer
1
Printer software versions
3700
5.3 and higher
4050
2.1 and higher
4090
3.0 and higher
4135
3.5 and higher
42351
1.5 and higher
4450
2.1 and higher
4635
8.3 and higher
4850
3.7 and higher
4890
4.0 and higher
8700
10 and higher
8790
2.1 and higher
9700
10 and higher
9790
2.1 and higher
180 LPS
V3C2 R2.4 and higher
DP96
V3C2 R2.4 and higher
92C LPS
V5.4 R1.3 and higher
Refer to the “4235 mode switching” section of this chapter.
Installing and Customizing XDPE/400 (9/2001)
4-4
Installation requirements
Xerox Distributed Print Mode printers
Table 4-2 lists the XDPM printers supported by XDPE/400 and the printer
software versions supported for each of the printers.
Table 4-2.
XDPM printers
Xerox printer
1
Printer software versions
4700
1.0 and higher
42351
1.0 and higher
4213 II
2.1
4030
1.0
3700
2.6 and higher
Refer to the “4235 mode switching” section of this chapter.
Installing and Customizing XDPE/400 (9/2001)
4-5
Installation requirements
Xerox Printer Control Language printers
Table 4-3 lists the PCL printers supported by XDPE/400 and the printer
software versions supported for each of the printers.
Table 4-3.
Xerox PCL printers
Xerox printer
Printer software versions
4890 NPS
1.4.2 and higher
1.6.1c and higher for resident euro fonts
4850 NPS
1.4.2 and higher
1.6.1c and higher for resident euro fonts
4635 NPS
1.4.2 and higher
1.6.1c and higher for resident euro fonts
4520
4.03 and higher
4517
1.00.56-0075 and higher
4512
M
4230
2.20 and higher
4220
2.20 and higher
4219
2013.109 Rel. 4 and higher
4215
2013.109 Rel. 4 and higher
4090 NPS
1.4.2 and higher
1.6.1c and higher for resident euro fonts
4050 NPS
1.4.2 and higher
1.6.1c and higher for resident euro fonts
180 NPS
1.5 and higher
1.6.1c and higher for resident euro fonts
92C NPS
1.6.1 and higher
1.6.1c and higher for resident euro fonts
DC265LP
5.06 and higher
DC255LP
5.06 and higher
DP96NPS
1.5.4 and higher
1.6.1c and higher for resident euro fonts
DP65
DocuSP 1.05.05
N32
1.82.06 and higher
1.87 and higher for resident euro fonts
N24
1.82.06 and higher
1.87 and higher for resident euro fonts
Installing and Customizing XDPE/400 (9/2001)
4-6
Installation requirements
Xerox PostScript printers
Table 4-4 lists the PostScript printers supported by XDPE/400 to run in
VIPP mode and provides the printer and VIPP software versions
supported by XDPE/400 for each printer.
Table 4-4.
Xerox PostScript printers
Xerox printer
Printer software
versions supported
VIPP software
versions supported
4890 NPS
1.5.4 and higher
2.0, 2.1 and higher
4850 NPS
1.5.4 and higher
2.0, 2.1 and higher
4635 NPS
1.5.4 and higher
2.0, 2.1 and higher
4090 NPS
1.5.4 and higher
2.0, 2.1 and higher
4050 NPS
1.5.4 and higher
2.0, 2.1 and higher
180 NPS
1.5.4 and higher
2.0, 2.1 and higher
92C NPS
1.6.1 and higher
2.0, 2.1 and higher
DP96NPS
1.5.4 and higher
2.0, 2.1 and higher
DP65
1.10.05 and higher
2.1 and higher
N4025
1.12.02 and higher
2.1 and higher
N3225
1.12.02 and higher
2.1 and higher
N2825
1.12.02 and higher
2.1 and higher
N2125
1.12.02 and higher
2.1 and higher
N2025
1.1202 and higher
2.1 and higher
N40
1.87 and higher
2.1 and higher
N32
1.87 and higher
2.1 and higher
N24
1.87 and higher
2.1 and higher
N17
1.86 and higher
2.1 and higher
Installing and Customizing XDPE/400 (9/2001)
4-7
Installation requirements
4235 mode switching
The Xerox 4235 release 1.5 printer allows you to switch from one print
language (XPPM, XDPM, HP, XS) to another without reconfiguring the
printer. You can override the current print language with another desired
language by embedding Mode Switch (=MCK=) command strings in the
beginning of your data stream and enabling Emulation Mode Switching on
the printer.
If you do not enable Emulation Mode Switching, the 4235 prints the Mode
Switch commands as text instead of interpreting them as commands. For
detailed information on enabling Emulation Mode Switching, refer to the
“System configuration” chapter of the Xerox 4235 Laser Printing Systems
System Administrator Guide.
NOTE: When running jobs to the 4235 in XPPM mode, be sure the
JSL contains only DJDEs supported for the 4235 in XPPM mode.
Refer to 4235 Laser Printing Systems XPPM PDL/DJDE Reference
for more information.
Generic printer devices
Table 4-5 lists the data streams and related printer language levels
supported by generic printer devices.
Table 4-5.
Generic printer devices
Printer designation
Minimum software level
*DOCUSP
PCL version 5
*LCDS
N/A
*NPS
PCL version 5
*PCL
PCL version 5
*VIPP
VIPP version 2.1
*XJT
PCL version 5
Installing and Customizing XDPE/400 (9/2001)
4-8
Installation requirements
Supported printer/interface box configurations
XDPE/400 allows printing to three different device classes: local, remote
(via TCP/IP), and network (via TCP/IP and HPT). The printer/interface box
configurations supported for each type are listed in the following sections.
For more information about configuring your interface box for XDPE/400,
refer to appendix A, “XDPE/400-supported interface boxes.”
Local and remote printing
If you use XDPE/400 with either the local or remote device classes, you
must use a twinaxial-connected interface box to convert the print data
stream for the printer. XDPE/400 supports these twinax-to-Xerox printer
interface boxes:
•
•
•
•
•
•
•
•
•
•
•
3X Twinax Printstation
42XX INTERNAL
4450 INTERNAL
Agile 5250 OPTIMA
BARR
Flex i-data 5250 C/RS-Xerox
IBM AS/400 Client Access (PC Support)
MPI
Smart
Solimar
Spur/USAll
Table 4-6 shows supported configurations for local and remote printing.
I
Table 4-6.
Interface boxes for XDPE/400-supported printers
Printers
Modes
4235, 3700
4700, 4213,
4030 II
4450
4230, 4220,
4219, 4215,
*PCL
9790, 9700, 8790, 8700, 4890,
4850, 4635, 4135, 4090, 4050,
180 LPS, 92C LPS,
DP96,*LCDS
XPPM
Flex, Agile, Smart,
3X (4235 only)
None
INTERNAL
None
Spur/USAII, Solimar, BARR
XDPM
Flex, Agile, MPI,
PCSUPP,
3X (4235 only)
Flex, Agile,
MPI,
PCSUPP
None
None
None
PCL
None
None
None
PCSUPP,
INTERNAL
None
Installing and Customizing XDPE/400 (9/2001)
4-9
Installation requirements
Network printing
Network printing uses TCP/IP in conjunction with the IBM feature called
Host Print Transform (HPT). The HPT feature included with XDPE/400
allows printing to ASCII format printers without an SCS interface box.
These printers are supported with this feature:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
4890 NPS
4850 NPS
4635 NPS
4520
4517
4512
4230
4220
4219
4215
4090 NPS
4050 NPS
180 NPS
92C NPS
DC265LP
DC255LP
DP96NPS
DP65
N4025
N3225
N2825
N2125
N2025
N40
N32
N24
N17
*DOCUSP
*NPS
*PCL
*VIPP
*XJT
NOTE: When installing the interface for your NPS printer in PCL mode,
you must set the Enable Xerox job ticket processing option to YES.
Table 4-7 shows supported configurations for network printing.
Table 4-7.
Mode
Interface boxes for XDPE/400-supported network printers
4230, 4220,
4219, 4215,
*PCL
4520, 4517, 4512,
DC265LP,
DC255LP,
N32/N24, *PCL
4890 NPS, 4850 NPS, 4635 NPS,
4090 NPS, 4050 NPS, 180 NPS,
92C NPS, DP96 NPS, DP65, N32,
N24, *DOCUSP, *NPS, *VIPP, *XJT
N4025, N3225,
N2825, N2125,
N2025, N40, N17
PCL
PCSUPP,
INTERNAL
PCSUPP
PCSUPP
—
PostScript
—
—
PCSUPP
PCSUPP
Installing and Customizing XDPE/400 (9/2001)
4-10
Installation requirements
Interface settings
Verify that the interface between your AS/400 system and your Xerox
printer is set up to emulate an IBM printer and to convert SNA character
mode data. Table 4-8 shows the available interface emulation for each
printer mode. Refer to your specific printer manual for the correct
emulation setting for your printer.
For XPPM mode printers, be sure the Spur or the Solimar interface box is
set to emulate the 5225.
Also verify that the AS/400 can print to the Xerox printer using the AS/400
printer writer.
Table 4-8.
Interface emulation by printer mode
Printer type
1
Interface emulation
Interface data
conversion
XPPM
IBM 5219 1 or IBM 5225
EBCDIC
XDPM
IBM 3812, IBM 5219, or IBM 5225
ASCII
PCL
For twinax only:
IBM 3812, IBM 5219, or IBM 5225
ASCII
PostScript
Not applicable
Not applicable
Setup depends on the interface being used.
OS/400 device description
You must create a device description for your non-network or twinax
locally-attached Xerox printer. If your AS/400 is set up to automatically
configure devices upon connection, the system creates the device
description as soon as you plug in the printer. The OS/400 system value
QAUTOCFG specifies whether devices that are added to the system are
configured automatically.
You can refer to your OS/400 device description when you run sample
jobs at the end of installation.
Installing and Customizing XDPE/400 (9/2001)
4-11
Installation requirements
Migration issues
If you do not currently have any version of XDPE/400 installed on your
AS/400, skip to chapter 5, “Installing XDPE/400.”
Displaying your XDPE/400 library and folder information
You can display the software information for your current XDPE/400
library and folder. Enter DSPXDPEVER and press ENTER to:
•
Display the name, release level, and maintenance (PTF) level of
your XDPE/400 library and folder
•
Display the format (A4 or LETTER) and ID number of your
XDPE/400 folder
For users running XDPE/400 2.1.0 or later, if you need to obtain this
information on a specific XDPE/400 library, press F4 instead of ENTER.
The system prompts you to type in the library name of your choice.
Recording your current global values
If you currently have any version of XDPE/400 installed on your AS/400,
it is imperative that you perform these steps to record your current global
values; they will not be reflected in the version of XDPE/400 you are
installing.
Step 1.
Enter WRKGBLVAL to display the Work With Global Values screen.
Step 2.
Record your current values for the parameters on the first screen, either
by using the PRINT SCREEN key on your keyboard to print an image of
each screen, or by writing them down.
Step 3.
Page forward to display the next screen of global values. Record the
values as you did for the first screen.
Step 4.
Repeat steps 2 and 3 until you have recorded the parameters for all 5 of
the Work With Global Values screens.
Installing and Customizing XDPE/400 (9/2001)
4-12
Installation requirements
Collecting changes you made to XDPE/400 objects
If you currently have any version of XDPE/400 installed on your AS/400,
be aware that if you altered any objects in the subfolders that were
originally distributed with XDPE/400, your alterations will be overwritten
when you install this new version of XDPE/400.
You will be instructed later to create a backup copy of your XDPEFLR
resource folder. Refer to appendix B for a list of the subfolders contained
in XDPEFLR.
Take time now to determine which of your site objects have been altered
and not renamed. For these objects, determine what alterations you have
made to them. After you install the new XDPEFLR, if you want to use the
objects as before, you must make your alterations to the objects in the
new XDPEFLR.
To facilitate easier installation of XDPEFLR updates in the future, do not
alter objects in XDPEFLR subfolders that are distributed with the
XDPE/400 software. Instead, make a renamed copy of the object, then
make your alterations in the renamed copy.
Customizing XDPE/400 default commands
If you are a current user of XDPE/400 and have altered any of the
XDPE/400 command objects without creating a CL program for those
modifications, the changes you made will not be reflected in the version
of XDPE/400 you are installing.
Take time now to verify which commands you have changed in your
current version. To incorporate those changes in the version you are
currently installing, add them at the conclusion of the installation
procedure. See chapter 6 for more information on customizing XDPE/400
commands.
Installing and Customizing XDPE/400 (9/2001)
4-13
Installation requirements
Installing and Customizing XDPE/400 (9/2001)
4-14
5.
5
Installing XDPE/400
This chapter contains the procedures needed to prepare for and install
XDPE/400. It contains instructions for both new XDPE/400 sites as well
as for sites that are already using XDPE/400.
Installing XDPE/400 is a process that you can complete using standard
OS/400 procedures. The basic steps are:
•
•
•
•
•
•
Creating an XDPE/400 user profile
Backing up your current XDPE/400 system
Installing the XDPE/400 software
Restoring your customized XDPEFLR objects
Resetting your global values
Restoring your customized XDPE/400 application library objects
XDPE/400 software consists of the XDPE/400 application library and a
folder of resources, called XDPEFLR. Figure 5-1 shows these two
components.
Figure 5-1.
XDPE/400 software components
Installing and Customizing XDPE/400 (9/2001)
5-1
Installing XDPE/400
Creating an XDPE/400 user profile
Skip this section if you have an earlier version of XDPE/400 installed on
your system.
To install XDPE/400 software, you must know how to use standard
OS/400 commands, including CRTUSRPRF, ADDDIRE, RSTLIB, and
RSTDLO. For information about these commands, refer to the OS/400 CL
Reference.
Perform these steps to create an XDPE/400 user profile:
Step 1.
Sign on with a user profile that has *SECADM special authority.
Step 2.
Create the XDPE/400 user profile by entering this command:
CRTUSRPRF
USRPRF(XDPEUSR)
TEXT('XDPE User')
SPCAUT(*JOBCTL *SAVSYS *SPLCTL)
Step 3.
Enroll the XDPEUSR in the system directory by entering this command:
ADDDIRE
USRID(XDPEUSR address)
USRD('XDPE User')
USER(XDPEUSR)
where
address
Step 4.
Directory address of the XDPEUSR profile. If a unique
directory address is needed for site-specific network
communications, follow your site’s addressing standard. If
no specific network addressing is necessary, use
XDPEUSR.
Grant *USE authority for the DMPOBJ command and its command
processing program to the XDPEUSR user profile by entering these
commands:
GRTOBJAUT
OBJ(DMPOBJ)
OBJTYPE(*CMD)
USER(XDPEUSR)
AUT (*USE)
GRTOBJAUT
OBJ(QSCDOBJ)
OBJTYPE(*PGM)
USER(XDPEUSR)
AUT (*USE)
Installing and Customizing XDPE/400 (9/2001)
5-2
Installing XDPE/400
Backing up your current XDPE/400 system
Skip this section if you do not currently have XDPE/400 installed on your
AS/400.
If you currently have any version of XDPE/400 installed on your AS/400,
it is imperative that you perform the following steps to back up your
current XDPE/400 system.
Step 1.
Enter this command to save your current XDPE/400 application library to
tape:
SAVLIB
LIB(library)
DEV(device)
SEQNBR(*END)
LABEL(*LIB)
where
library
The name of the XDPE/400 application library is XDPEvrm,
where
•
•
•
device
Step 2.
v is the version number
r is the release number
m is the modification number
Name of the device on which the tape is mounted.
Enter this command to save your current XDPEFLR folder to tape:
SAVDLO
DLO(*ALL)
FLR(XDPEFLR)
DEV(device)
SEQNBR(*END)
LABEL(label)
where
device Name of the device on which the tape is mounted.
label
A label that you will use again when you restore your saved
XDPEFLR objects from tape.
Installing and Customizing XDPE/400 (9/2001)
5-3
Installing XDPE/400
Installing the base files
Follow these instructions to install the base files from tape or CD-ROM.
Before you begin, ensure that all users are no longer using XDPE/400
functions or do not have the XDPE/400 application library or folders
allocated.
CAUTION: Once you begin this installation process, do not start
Monitor Queue until you are instructed to do so. Doing so may result
in later Monitor Queue abends. Instructions for starting Monitor
Queue are provided in chapter 7.
Step 1.
Sign on as XDPEUSR.
NOTE: If you currently have XDPE/400 installed on your system,
verify that there are no user libraries in the library list.
Step 2.
Mount the XDPE/400 installation tape or CD-ROM on an accessible drive.
NOTE: Viewing the contents of the CD-ROM is not required.
However, if you use the DSPOPT VOL(*ALL) DEV(OPT01) command
to display the CD contents, you may receive message OPT1825,
“Optical indexes are incorrect for optical device OPT01.” If this
message appears, replace *ALL in the command line with either
*MOUNTED or with the volume serial number of the CD.
Step 3.
Download the distribution materials from tape or CD-ROM by entering this
command:
NOTE: LODRUN requires *SAVSYS authority.
LODRUN
DEV(device)
where
device One of these values:
•
•
•
*OPT — Specifies the default CD-ROM device
*TAP — Specifies the default tape device
name — Specifies the OS/400 device name of the tape
device or CD-ROM device
The following prompt will display:
Reply page format, *A4 or *US, to install base maintenance or reply
*NO.
Installing and Customizing XDPE/400 (9/2001)
5-4
Installing XDPE/400
If you reply *A4 or *US, the installation will automatically restore the
XDPE/400 executable objects and resource folder. No other action is
required. Skip steps 4 and 5 and go to the next section.
If you want to complete the installation at a later time, reply *NO. This will
allow you to manually restore the XDPE/400 executable objects and
resource folder at your convenience. Follow steps 4 and 5 when you are
ready to complete the installation.
Step 4.
Restore the XDPE/400 executable objects by entering this command:
RSTLIB
SAVLIB(library)
DEV(*SAVF)
SAVF(BBxxxx/library)
where
library
The name of the XDPE/400 application library is XDPEvrm,
where
•
•
•
v is the version number
r is the release number
m is the modification number
BBxxxx The volume serial number found on the installation tape or
CD-ROM.
Step 5.
Restore the XDPE/400 resource folder, XDPEFLR, by entering this
command:
RSTDLO
DLO(*ALL)
SAVFLR(XDPEFLR)
DEV(*SAVF)
SAVF(BBxxxx/label)
where
BBxxxx The volume serial number found on the installation tape or
CD-ROM.
label
One of these values:
•
XDPEFLRLET — Specifies 8.5 by 11 inch (letter size) paper
support
•
XDPEFLRLA4 — Specifies A4 paper support
Installing and Customizing XDPE/400 (9/2001)
5-5
Installing XDPE/400
Recreating your XDPEFLR object changes
For any objects originally distributed with XDPE/400 to which you have
made alterations, such as JSLs or packets, recreate the alterations in the
new version of the object(s).
To facilitate easier installation of XDPEFLR updates in the future, do
not alter objects in XDPEFLR subfolders that are distributed with the
XDPE/400 software. Instead, make a renamed copy of the object,
then make your alterations in the renamed copy.
Resetting your global values
If you had XDPE/400 installed on your system before this installation, you
now need to reset your global values that you recorded in the “Recording
your current global values,” section in chapter 4.
Restoring your customized XDPE/400 application library
objects
Copy any previously customized objects that were maintained in the old
XDPE/400 application library to the new XDPE/400 application library.
NOTE: Before restoring your customized objects, we recommend that
you first rename them so as not to write over the newly installed
version.
Installing corrective maintenance
If there is any maintenance included with your version of XDPE/400, you
should install it at this time. See the maintenance bulletin accompanying
the corrective maintenance for the installation procedure.
Installing and Customizing XDPE/400 (9/2001)
5-6
Installing XDPE/400
Removing your old version of XDPE/400
If you currently have an older version of XDPE/400 installed on your
AS/400, it is recommended that you remove it after installing and testing
the new version of XDPE/400. Use the DLTLIB command to delete the
XDPE/400 application library.
CAUTION: Do not delete the XDPEFLR resource folder. XDPEFLR is
used with every version of XDPE/400.
Adding the XDPE/400 application library to your library list
The XDPE/400 application library must be in the library list before anyone
can use XDPE/400 commands. This must be done each time anyone logs
on the system. To add the XDPE/400 library to the user library list, enter
this command:
ADDLIBLE
LIB(library)
where
library
The name of the XDPE/400 application library is XDPEvrm,
where
•
•
•
v is the version number
r is the release number
m is the modification number
There are a couple of alternatives to adding the XDPE/400 library to the
user library list each time anyone logs on the system. These options need
only be set up one time, but must be done by the system administrator
with the proper authorities. The options are:
•
Add the XDPE/400 library to the job description for a group of users
with the Create Job Description (CRTJOBD) or Change Job
Description (CHGJOBD) OS/400 command.
•
Add the XDPE/400 library to the QUSRLIBL system value for all
users with the Change System Value (CHGSYSVAL) OS/400
command.
Installing and Customizing XDPE/400 (9/2001)
5-7
Installing XDPE/400
Installing and Customizing XDPE/400 (9/2001)
5-8
6.
6
Customizing XDPE/400
This chapter contains the procedures to configure and customize your
system. These topics are discussed:
Setting up the global parameter values that the Monitor Queue uses for each session
•
Customizing and using separator pages generated by AS/400 and
XDPE/400
•
Using the Monitor Queue job log
•
Customizing XDPE/400 commands
Work with Global Values screens
This section describes how to access the Work with Global Values
screens. You define the XDPE/400 global values to customize XDPE/400.
The system uses these global values to initialize Monitor Queue at the
start of a Monitor Queue session. All methods of printer control packet
generation use the XDPE/400 global values.
The XDPE/400 global value command (WRKGBLVAL) allows you to set
default parameters for the AS/400 during installation. You can modify
these parameters at any time after the initial installation without
reinstalling XDPE/400.
Changing global values
Follow these steps to display the Work with Global Values screens and
change the global values. The five Work with Global Values screens are
shown on the following pages, along with information about each
parameter.
Step 1.
Enter WRKGBLVAL and press ENTER. The first Work with Global Values
screen displays some of the current global values.
Step 2.
Enter the appropriate values for each field and press ENTER.
Step 3.
Press the Page Up or Page Down keys to display the remaining Work
with Global Values screens, and enter the appropriate values.
Installing and Customizing XDPE/400 (9/2001)
6-1
Customizing XDPE/400
Work with Global Values (first screen)
This section describes the parameters that appear on the first Work with
Global Values screen, as shown in figure 6-1.
Figure 6-1.
Work with Global Values screen (first screen)
Work with Global Values (UPDTGLOBAL)
Type choices, press Enter.
IDEN Prefix (a string) . . . .
Offset . . . . . . . . .
Skip . . . . . . . . . .
RSTACK String (a string) . . .
Offset . . . . . . . .
JDE or PDE? . . . . . . . . .
JDE/PDE name creation mode . .
JDE/PDE id for portrait:
one page per physical side .
two pages per physical side.
four pages per physical side
JDE/PDE id for landscape:
one page per physical side .
two pages per physical side.
four pages per physical side
Run priority . . . . . . . . .
F3=Exit F4=Prompt
F24=More keys
.
.
.
.
.
.
.
DJDE
2___
7___
RSTACK
0___
*PDE
*NAME
0-211
0-211
0-211
*JDE, *PDE
*NAME, *AUTO
. ONEPOR
. TWOPOR
. FORPOR
JDE/PDE id, *NONE
JDE/PDE id, *NONE
JDE/PDE id, *NONE
.
.
.
.
JDE/PDE id, *NONE
JDE/PDE id, *NONE
JDE/PDE id, *NONE
1-99
ONELAN
TWOLAN
FORLAN
40
F5=Refresh
F12=Cancel
More...
F13=How to use this display
IDEN parameters
The IDEN statement notifies the printing system that DJDE records may
be part of the input data stream. It also describes the characteristics of a
DJDE record so that the system can identify DJDEs and locate the DJDE
parameters. The IDEN statement syntax and interpretation are described
in the corresponding printer PDL/DJDE reference manual.
When the printer finds this character string, it recognizes it as a DJDE
record and examines the rest of the record for DJDE options. OFFSET
specifies where in the record to look for the IDEN PREFIX. SKIP specifies
where to look for the position of the DJDE parameters.
The following example of an IDEN statement uses the parameters
provided in the default centralized printer online JSL:
IDEN PREFIX='DJDE',SKIP=7,OFFSET=2;
NOTE: XDPE/400 IDEN global values must match the IDEN values in the
JDE/JDL that is invoked on the printer with the START command. If you
change the global values while a Monitor Queue session is active, you
must end or reset the session before the global values can take effect.
Installing and Customizing XDPE/400 (9/2001)
6-2
Customizing XDPE/400
IDEN Prefix (IPREFIX)
Specifies the character string used to identify DJDE records in the print
data stream. The syntax of the parameter is:
PREFIX=string
PREFIX specifies a string of up to 10 characters that Xerox printers use
to recognize DJDE records. Any record within the data stream that
contains this string, at the location specified by the offset parameter, is
recognized and processed as a DJDE record.
You also can use hexadecimal values to represent text strings. To use a
hexadecimal value, enclose the string in single quotes and precede it with
an X. For example, you can enter the string ABC as X'C1C2C3'.
IDEN Offset (IOFFSET)
Defines the starting position of the DJDE prefix string. The syntax of the
parameter is:
OFFSET=value
OFFSET specifies the number of bytes (counting from 0) from the
beginning of the user portion of the record to the beginning of the prefix
string constant of the DJDE record.
IDEN Skip (ISKIP)
Defines the starting position of the DJDE parameters within the DJDE
record. The syntax of the parameter is:
SKIP=value
SKIP specifies the number of bytes (counting from 0) from the beginning
of the user portion of the record to the beginning of the DJDE options. This
value may be negative.
RSTACK parameters
For DJDE data streams, the RSTACK, CRITERIA, and TABLE statements
provide the test criteria the printer uses to detect an end-of-report. An
end-of-report is the point in a spool file after which there are no more
pages to print.
This is an example of an RSTACK statement:
T1:TABLE CONSTANT=('RSTACK');
C1:CRITERIA CONSTANT=(0,6,EQ,T1);
RSTACK TEST=C1,DELIMITER=YES;
NOTE: The XDPE/400 RSTACK global values must match the
RSTACK values in the JDE/JDL that is invoked on the printer with the
START command. If you change the global values while a Monitor
Queue session is active, you must end or reset the session before the
global values can take effect.
Installing and Customizing XDPE/400 (9/2001)
6-3
Customizing XDPE/400
RSTACK String (RSTRING)
Defines the character string that is used to test for an end-of-report. The
TABLE command uses the character string as a character constant for the
logical processing statements.
The syntax of the parameter is:
label: TABLE CONSTANT=('string');
where
label
Specifies the TABLE command that defines the string to use for
comparison.
string
Specifies a constant used to detect the end of a report.
You also can use hexadecimal values to represent text strings. To use a
hexadecimal value, enclose the string in single quotes and precede it with
an X. For example, you can enter the string ABC as X'C1C2C3'.
RSTACK Offset (ROFFSET)
Specifies the location of the RSTACK string in the print data record.
ROFFSET is the number of bytes (counting from 0) relative to the start of
the record of the character constant that detects the end of the record.
This is specified in a CRITERIA statement in the JSL.
The syntax of the parameter is:
label: CRITERIA CONSTANT=(offset,length,comparison,label);
where
label
Specifies the TABLE command that defines the string to use
for comparison.
offset
Position of the comparison string from the start of the user
data portion of the print record.
length
Number of bytes to compare.
comparison Type of comparison to perform.
For this parameter, you must specify where the RSTACK string starts as
well as its length.
Installing and Customizing XDPE/400 (9/2001)
6-4
Customizing XDPE/400
JDE/PDE ID parameters
The JDE/PDE statement specifies the JDE or PDE to use when printing a
DJDE job. It provides the page formatting information for the job.
XDPE/400 allows you to specify whether a JDE DJDE or a PDE DJDE is
generated. The PDE-specific fields apply to both JDEs and PDEs.
JDE or PDE (JDEPDE)
JDE/PDE name creation
mode (JDEPDEMODE)
JDE/PDE id for portrait
(PDLIDP)
Specifies whether XDPE/400 generates a job descriptor entry (JDE) or a
page description entry (PDE) when printing a job.
Specifies whether the JDE/PDE name is selected from the JDE/PDE
name list or created from the spool file attributes. You can use one of
these values:
•
*NAME — The JDE/PDE name is selected from the PDLIDP and the
PDLIDL lists.
•
*AUTO — The JDE/PDE name is created from these spool file
attributes: pages per side, page size (width), and page rotation.
Specifies the JDE/PDE IDs for portrait orientation. This list defines the
JDEs/PDEs to use for one-up, two-up, and four-up printing. JDEs/PDEs
provide the formatting information, such as the fonts to use, upper-left
corner coordinates of the logical page, and the page orientation. The
syntax of the parameter is:
portrait-jde-name or portrait-pde-name
JDE/PDE id for landscape
(PDLIDL)
Specifies the JDE/PDE IDs for landscape orientation. This list defines the
JDEs/PDEs to use for one-up, two-up, and four-up printing. JDEs/PDEs
provide the formatting information, such as the fonts to use, upper-left
corner coordinates of the logical page, and the page orientation. The
syntax of the parameter is:
landscape-jde-name or landscape-pde-name
Run priority parameter
XDPE/400 provides parameters to specify a run-time priority (RUNPTY)
and the maximum amount of processor time allocated to a Monitor Queue
session over other jobs running in the QSPL subsystem (TIMESLICE).
The Run priority (RUNPTY) parameter is shown on the first Work with
Global Values screen; the Time slice (TIMESLICE) parameter is shown on
the second screen.
NOTE: The Time slice (TIMESLICE) and Run priority (RUNPTY)
global values require *JOBCTL special authority to change.
Run priority (RUNPTY)
Specifies the run-time priority for all Monitor Queue jobs that are started
after this value has been set. This value represents the relative
importance of a Monitor Queue job.
Run priority is a number between 1 (highest priority) and 99 (lowest
priority).
Installing and Customizing XDPE/400 (9/2001)
6-5
Customizing XDPE/400
Work with Global Values (second screen)
This section describes the parameters that appear on the second Work
with Global Values screen, as shown in figure 6-2.
Figure 6-2.
Work with Global Values screen (second screen)
Work with Global Values (UPDTGLOBAL)
Type choices, press Enter.
Time slice . . . . . . . . . .
Source file translation table
Library . . . . . . . . . .
Source file rcrd avrg length .
PC/Support translation table .
Library . . . . . . . . . .
F3=Exit
F4=Prompt
F24=More keys
Time slice (TIMESLICE)
.
.
.
.
.
.
2100_____
*XDPEDFT_
*LIBL__
10__
*XDPEDFT_
*LIBL__
F5=Refresh
F12=Cancel
1-9999999 milliseconds
Name, *XDPEDFT
Name, *LIBL
3-72
Name, *XDPEDFT
Name, *LIBL
More...
F13=How to use this display
Specifies the maximum amount of processor time allocated to Monitor
Queue jobs before other jobs are run. TIMESLICE is a number between 1
and 9999999 milliseconds.
NOTE: To change the TIMESLICE and Run priority (RUNPTY) global
values requires *JOBCTL special authority.
Source file translation table
(RESLIB)
A required parameter that specifies the name of the ASCII-to-EBCDIC
translation table for the QDCXLATE API to use when downloading source
files (FSL or JSL) and multi-up packets to Xerox printers. You can use
these values:
•
table-name — Specifies the name of the EBCDIC translation table to
be used.
•
*XDPEDFT — Specifies the default EBCDIC translation table
provided with OS/400.
Installing and Customizing XDPE/400 (9/2001)
6-6
Customizing XDPE/400
Library
Specifies the name of the library containing the ASCII-to-EBCDIC
translation table. You can use these values:
•
library-name — Specifies the name of the library containing the
translation table.
•
*LIBL — Uses the library list of the job to locate the translation table.
Source file rcrd avrg length
(RECSIZE)
Identifies the average size of the source file in records. The file size used
in the FILE=DJDE size field is the size of the source file in bytes, divided
by RECSIZE.
PC/Support translation table
(PCSLIB)
A required parameter that specifies the name of the translation table that
the system uses when constructing printer language commands, multi-up
data, XES data, and XES resources for local and network processing.
XDPE/400 converts all printer commands and data from EBCDIC to ASCII
and writes them to an ASCII spool file.
The OS/400 API QDCXLATE uses this translation table to translate
resources from EBCDIC to ASCII. The format of the table must be
compatible with the QDCXLATE requirements.
You can use these values:
•
table-name — Specifies the name of the ASCII translation table to
be used. This may be the name of one of the tables provided by
XDPE/400 or OS/400, or the name of a user-created table.
XDPE/400 provides tables XASCII1140 and XASCII1142.
XASCII1140 is compatible with these code pages:
—
—
—
—
ASCII code pages 850 and 1051
EBCDIC code page 37
Euro-enabled ASCII code pages 858 and 1252
Euro-enabled EBCDIC code pages 1140, 1141, 1144 through
1149
XASCII1142 is compatible with these code pages:
—
—
—
—
ASCII code pages 850 and 1051
EBCDIC code page 37
Euro-enabled ASCII code pages 858 and 1252
Euro-enabled EBCDIC code pages 1142 and 1143
For information on the tables provided with OS/400, see OS/400
International Application Development and OS/400 National
Language Support. For information on creating user translation
tables, see OS/400 CL Reference.
•
*XDPEDFT — Specifies the default ASCII translation table provided
with XDPE/400. This translation table is compatible with these code
pages:
—
—
—
—
Library
ASCII code pages 850 and 1051
EBCDIC code page 37
Euro-enabled ASCII code pages 858 and 1252
Euro-enabled EBCDIC code pages 1140, 1141, 1144 through
1149
Specifies the name of the library containing the EBCDIC-to-ASCII
translation table. You can use these values:
•
library-name — Specifies the name of the library containing the
translation table.
•
*LIBL — Uses the library list of the job to locate the translation table.
Installing and Customizing XDPE/400 (9/2001)
6-7
Customizing XDPE/400
Work with Global Values (third screen)
This section describes the parameters that appear on the third Work with
Global Values screen, as shown in figure 6-3.
Figure 6-3.
Work with Global Values screen (third screen)
Work with Global Values (UPDTGLOBAL)
Type choices, press Enter.
Attribute include/exclude flags:
Copy count . . . . . . . . . .
Duplex . . . . . . . . . . . .
Front overlay . . . . . . . . .
Back overlay. . . . . . . . . .
Font id/Multiple up attributes
Job name . . . . . . . . . . .
Priority. . . . . . . . . . . .
Pre-drilled paper . . . . . . .
DJDE termination mode . . . . .
Margins . . . . . . . . . . . .
Accounting code . . . . . . . .
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
*YES
*YES
*YES
*YES
*YES
*YES
*YES
*YES
*YES
*YES
*NO_
F12=Cancel
*YES,
*YES,
*YES,
*YES,
*YES,
*YES,
*YES,
*YES,
*YES,
*YES,
*YES,
*NO
*NO
*NO
*NO
*NO
*NO
*NO
*NO, *ALL
*NO
*NO
*NO
More...
F13=How to use this display
Spool file attribute parameters
These parameters identify a set of global flags that include or exclude the
spool file attributes to use when creating printer control packet
parameters.
Attribute include/exclude
flag (INHIBLST)
Specifies the spool file attributes to include or exclude when creating
printer control packet parameters. If you include these spool file
attributes, XDPE/400 generates the DJDE, XES, PCL, or VIPP commands
listed in table 6-1.
To include an attribute for a print job, enter *YES. To exclude an attribute,
enter *NO.
Installing and Customizing XDPE/400 (9/2001)
6-8
Customizing XDPE/400
Table 6-1
Attribute
flags
1
DJDE, XES, PCL, and VIPP commands created or inserted
Spool file
attributes
DJDE
commands
XES
commands
PCL
commands
VIPP commands or
PostScript DSC
Copy count
Copies
(COPIES)
COPIES
+C (copy
count)
—
VIPP
SETCYCLECOPY
Duplex
Print on both
sides
(DUPLEX)
DUPLEX
+zy (plex)
&l#S
VIPP DUPLEX_off,
DUPLEX_on, or
TUMBLEDUPLEX_on
Front
overlay
Front side
overlay
(FRONTOVL)
BFORM/FORM1
+zx (cycle
forms)
Macro #82
VIPP SETFORM
Back
overlay
Back side
overlay
(BACKOVL1)
BFORM
+zx (cycle
forms)
Macro #83
VIPP SETBFORM
Font id/
Multiple up
attributes
Font id
PDE or JDE
Generic XES
Generic PCL
PostScript DSC
XESMUP
PCLMUP
VIPP TWOUP or
SETMULTIUP
Job name
Job name
(JOB)
—
Inserts job
name into the
+Q (print job)
command
—
—
Priority
Output priority
(OUTPTY)
—
Inserts job
priority into the
+J (job priority)
command
—
—
Pre-drilled
paper
Pre-drilled
paper
(DRILLED)
SHIFT
+R (special
paper enable)
&l#U
VIPP SHIFT
DJDE
termination
mode
Align page
(ALIGN))
‘,END;’ at the
end of
XDPE/400generated
DJDEs
—
—
—
Margins
(printer file
attribute)
BEGIN
A command
sequence for
top and left
margins
A command
sequence for
top and left
margins
VIPP SETMARGIN
Accounting
code
(part of user
profile)
ACCT DEPT
—
—
—
Pages per side
(MULTIUP)
The DJDE used depends on the global value settings.
Installing and Customizing XDPE/400 (9/2001)
6-9
Customizing XDPE/400
Use these values for the DJDE termination mode global value:
•
*NO — A DJDE END command is placed at the end of every DJDE
packet, regardless of the ALIGN spool file attribute.
•
*YES — The value for the generation of a DJDE END command is
taken from the ALIGN spool file attribute.
Work with Global Values (fourth screen)
This section describes the parameters that appear on the fourth Work with
Global Values screen, as shown in figure 6-4.
Figure 6-4.
Work with Global Values screen (fourth screen)
Work with Global Values (UPDTGLOBAL)
Type choices, press Enter.
Source drawer assignments:
Drawer 1 . . . . . . . . . .
Drawer 2 . . . . . . . . . .
Drawer 3 . . . . . . . . . .
Drawer 4 . . . . . . . . . .
Drawer 5 . . . . . . . . . .
Drawer 6 . . . . . . . . . .
Drawer *E1 . . . . . . . . .
Predrilled shift support
Front side - long edge . . .
Back side - long edge . . .
Front side - short edge. . .
Back side - short edge . . .
Multiple-printer resource list
Back side overlay as BFORM . .
Solimar control mode . . . . .
F3=Exit F4=Prompt
F24=More keys
Source drawer assignments
(DRAWER)
*NONE_
*NONE_
*NONE_
*NONE_
*NONE_
*NONE_
*NONE_
*NONE,
*NONE,
*NONE,
*NONE,
*NONE,
*NONE,
*NONE,
+0
+0
+0
+0
*YES
*YES
*NO_
-300 to +300
-300 to +300
-300 to +300
-300 to +300
*YES, *NO
*YES, *NO
*YES, *NO
F5=Refresh
F12=Cancel
*MAIN,
*MAIN,
*MAIN,
*MAIN,
*MAIN,
*MAIN,
*MAIN,
*AUX,
*AUX,
*AUX,
*AUX,
*AUX,
*AUX,
*AUX,
*AUTO...
*AUTO...
*AUTO...
*AUTO...
*AUTO...
*AUTO...
*AUTO...
More...
F13=How to use this display
Allows you to map source drawers or bins specified by the Source drawer
(DRAWER) printer file parameter to Xerox printer source trays.Tray
selection may vary depending on your printer setup. If a printer does not
support a tray, the default tray will automatically be used.
NOTE: This parameter has no effect on NPS, DocuSP, or generic
printers in PCL or VIPP mode. For PCL printers, the effect of this
parameter varies depending on the printer used. Refer to the “Xerox
PCL printer tray selection,” section in chapter 15 for more information
on tray selection methods for the different PCL printers.
Installing and Customizing XDPE/400 (9/2001)
6-10
Customizing XDPE/400
XDPE/400 allows you to specify values for the 1, 2, 3, 4, 5, 6, and E1
source drawer assignment subparameters only.
NOTE: Source drawer assignment subparameters Drawer 5 and
Drawer 6 are valid for PCL printers only.
When a valid value of *NONE is specified, XDPE/400 uses the value
specified by the Data page source (DATASRC) Monitor Queue parameter.
Predrilled shift support
(SHIFT)
Specifies the values to use in shifting the combined form and data images
on a page to allow for binding or predrilled paper. If a shift is selected by
either a packet parameter or a printer file parameter, the amount of shift
is taken from this global value.
The valid value range is -300 to +300. The value entered is used
according to these printer types:
Printer mode and type
Units used
DJDE (centralized/XPPM)
300 dots per inch (dpi)
XES/XDPM
300 dots per inch (dpi)
PCL
300 dots per inch (dpi)
converted to decipoints (1/720
inch)
VIPP (PostScript)
300 dots per inch (dpi)
The Predrilled shift support (SHIFT) values are processed by XDPE/400
in this manner:
•
For XPPM (DJDE) printers, XDPE/400 maps the front long and back
long values to the SHIFT DJDE command. The minimum and
maximum values for DJDE are -75 and +75, respectively. If you enter
a value outside of this range, the minimum or maximum value will be
used. For a complete discussion of these values, refer to the
appropriate PDL/DJDE reference manual.
•
For XDPM (XES) printers, all values are on the SHIFT XES (zys)
command. The minimum and maximum values for XES are -75 and
+75, respectively. If you enter a value outside of this range, the
minimum or maximum value will be used. For a complete discussion
of these values, refer to the appropriate XES reference manual.
•
For PCL printers, XDPE/400 maps the front and back values to the
Left (long edge) Offset Registration command for portrait and the
Top (short edge) Offset Registration command for landscape. The
value in dots (1/300 inch) is converted to PCL decipoints (1/720
inch). For example, a valid value of 75 would be converted to 180
decipoints (1/4").
Installing and Customizing XDPE/400 (9/2001)
6-11
Customizing XDPE/400
•
For PostScript (VIPP) mode printers, all values are mapped into a
VIPP SHIFT command as shown below.
Predrilled shift support (SHIFT)
global value
VIPP SHIFT
command
parameter
Front side - long edge
Xfront
Back side - long edge
Xback
Front side - short edge
Yfront
Back side - short edge
Yback
The unit type from the most recently issued VIPP SETUNIT command
is used. The default is dots (1/300th inch). XDPE/400 does not
perform any unit conversion.
Multiple-printer resource list
(MPRLST)
Indicates how the system responds when a resource download list
contains resources that are incompatible with the printer mode.
NOTE: This parameter has no effect in VIPP mode.
You can specify one of these values:
•
*YES — XDPE/400 creates download lists without examining the
printer mode.
•
*NO — XDPE/400 ignores resources that are not compatible with the
printer mode.
Selecting *NO allows you to create a resource list that can be used on
different types of printers:
•
If the resource list is used by Monitor Queue, the system takes the
printer mode from the STRMONQ command specification.
•
If the resource list is used by a download command, the system
determines the printer mode by referring to the name of the folder
that contains the list.
—
If the resource list is in the XDPEFLR/FONTS folder, the system
assumes that the printer is operating in XPPM mode.
—
If the resource list is in the XDPEFLR/XESFONTS folder, the
system assumes that the printer is operating in XDPM mode.
—
If the resource list is in the XDPEFLR/PCLFONTS folder, the
system assumes that the printer is operating in PCL mode.
Installing and Customizing XDPE/400 (9/2001)
6-12
Customizing XDPE/400
Back side overlay as BFORM
(DJDEBFR)
Specifies how the spool file attribute is interpreted when creating a DJDE.
You can use one of these values:
•
*YES — Uses back side overlay as the form name in the BFORM=
DJDE command.
•
*NO — Uses back side overlay as the form name in the FORMS=
DJDE command that is inserted into the print data stream before the
even numbered pages.
Specifying *NO will force page level processing if the File processing
mode (PROCMODE) Monitor Queue parameter is set to *AUTO.
Solimar control mode
(SOLIMODE)
Specifies whether to insert control strings into the print data stream for
use by the Solimar interface box. These strings contain job information,
such as the name of the spool file being processed. This information can
be displayed on the Solimar host terminal. You can use one of these
values:
•
*YES — Inserts a control string before the prepend file and after the
postpend file.
•
*NO — Does not insert control strings into the print data stream for
use by the Solimar interface box.
Installing and Customizing XDPE/400 (9/2001)
6-13
Customizing XDPE/400
Work with Global Values (fifth screen)
This section describes the parameters that appear on the fifth Work with
Global Values screen, as shown in figure 6-5.
Figure 6-5.
Work with Global Values screen (fifth screen)
Work with Global Values (UPDTGLOBAL)
Type choices, press Enter.
XDPE control character mapping:
At-sign (@) . . . . . . . . .
Number-sign (#) . . . . . . .
Ampersand (&) . . . . . . . .
Plus-sign (+) . . . . . . . .
Average spool file size . . . .
Memory buffer size . . . . . . .
Multiple copies of sep. pages .
Duplex standard. . . . . . . . .
VIPP special packet data . . . .
F3=Exit F4=Prompt
F24=More keys
XDPE control character
mapping (CNTCHAR)
.
.
.
.
.
.
.
.
.
F5=Refresh
@
#
*AMP
*PLUS
20
32
*YES
*HP
*DFLT
F12=Cancel
Character value, *PLUS...
Character value, *PLUS...
Character value, *PLUS...
Character value, *PLUS...
1-1354 Pages
8, 16, 32, 64, 128
*YES, *NO
*HP, *IBM
*NONE, *DFLT, *XDPE, *BLNK
Bottom
F13=How to use this display
Allows you to specify the special characters XDPE/400 uses for special
processing functions. The four control character options are the at sign
(@), the number sign (#), the ampersand sign (&), and the plus sign (+).
You can input these characters as hexadecimal, octal, BCD, ASCII, or
EBCDIC character constants.
•
At-sign (@) — Value used by the XDPE/400 list processing function
to specify that the entry following is the name of a resource list. This
character is used in the User data (USRDTA) or Form type
(FORMTYPE) field of a spool file or in the resource file name field of
a download resource command. Refer to chapter 21 in Section
Three: Printing Documents with XDPE/400 for more information.
•
Number-sign (#) — Value used by XDPE/400 to specify that jobs are
to be processed with the Always generate (ALWAYS) Monitor Queue
parameter set to *DIRECT. This character is used in the User data
(USRDTA) or Form type (FORMTYPE) field of a spool file. Refer to
chapter 11 in Section Three: Printing Documents with XDPE/400 for
more information.
Installing and Customizing XDPE/400 (9/2001)
6-14
Customizing XDPE/400
•
Ampersand (&) — Value used by XDPE/400 separator page
processing to identify the variable data tokens used for separator
page templates. For more information on separator pages, refer to
“Separator page customization” later in this chapter and chapter 26
in Section Three: Printing Documents with XDPE/400.
•
Plus-sign (+) — Value used by XDPE/400 to specify that jobs are to
be processed with the Always generate (ALWAYS) Monitor Queue
parameter set to *COMBINED. This character is used in the User
data (USRDTA) or Form type (FORMTYPE) field of a spool file.
Refer to chapter 11 in Section Three: Printing Documents with
XDPE/400 for more information.
You can specify one of these values for each of the four control character
options:
•
Character value — Special character in single quotes.
•
*PLUS — Use this special value to represent the plus sign (+).
•
*LESS — Use this special value to represent the less than sign (<).
•
*GREATER — Use this special value to represent the greater than
sign (>).
•
*QUESTION — Use this special value to represent the question
mark (?).
•
*AMP — Use this special value to represent the ampersand (&).
Average spool file size
(FILESIZE)
Indicates the average size of the spool file that the Monitor Queue
processes. This only applies to page level spool file processing.
XDPE/400 uses the FILESIZE and BUFFER global values to determine
the size of the internal workspace for processing spool files. If the
FILESIZE value is smaller than the BUFFER value, the BUFFER value is
used instead of any calculated value. A page as defined here is 12K in
size. The valid values range from 1 through 1354 pages.
Memory buffer size
(BUFFER)
Specifies an estimate of how many buffers Monitor Queue should use
during a session. Memory buffer size only applies to page level spool file
processing. XDPE/400 uses the FILESIZE and BUFFER global values to
determine the size of the internal workspace for processing spool files. If
the FILESIZE value is smaller than the BUFFER value, the BUFFER value
is used instead of any calculated value. Each memory buffer is 4K in size.
The valid values are 8, 16, 32, 64, and 128.
Multiple copies of sep.
pages (MULCPYSEP)
Specifies whether a job that is printed in XPPM mode will have a copy of
the separator page printed with every copy of the job. This parameter
does not affect the number of separator pages that are printed if you are
printing in XDPM or PCL mode, or if the job is printed using separator
pages generated by OS/400. You can specify one of these values:
•
*YES — Prints a copy of the XDPE/400-generated pages with every
copy of every job.
•
*NO — Prints a copy of the XDPE/400-generated separator pages
only on the first page of the first job.
Installing and Customizing XDPE/400 (9/2001)
6-15
Customizing XDPE/400
Duplex standard
(DUPLEXSTD)
Specifies the duplex standard to be set for all PCL data streams
processed through XDPE/400, as defined by either Hewlett Packard (HP)
or IBM.
Xerox and printer twinax interface manufacturers use different standards
to translate IBM SCS print commands into PCL with regard to duplexing.
Therefore, when you send the same PCL duplex job through the IBM
OS/400 writer (outside of XDPE/400) and through XDPE/400, you may get
different results, depending on the orientation and what type of plexing
you desire. The Duplex standard (DUPLEXSTD) global value allows you
to choose which duplex standard you want to use for PCL jobs.
You can specify one of these values:
VIPP special packet data
(SPECPACK)
•
*HP — Uses the HP standard for printing PCL jobs (default). When
either portrait or landscape orientation is specified, duplex output is
generated with long-edge binding and tumble duplex output is
generated with short-edge binding.
•
*IBM — Uses the IBM standard for printing PCL jobs. When portrait
orientation is specified, duplex output is generated with long-edge
binding and tumble duplex output is generated with short-edge
binding. When landscape orientation is specified, duplex output is
generated with short-edge binding and tumble duplex output is
generated with long-edge binding.
Specifies the action to be taken when Monitor Queue detects a VIPP
special packet data name. The VIPP special packet data values affected
are *STD, XDPE, and blank.
You can specify one of these values:
•
*NONE — Monitor Queue will ignore all VIPP special packet data
values. No JDT will be used. If XDPE is specified, *INDIRECT
processing will be used for the spool file.
•
*DFLT — Monitor Queue will use a JDT with the name of default.jdt
when the VIPP special packet data field contains the value *STD.
•
*XDPE — Monitor Queue will use a JDT with the name of xdpe.jdt
when the VIPP special packet data field contains the value XDPE.
•
*BLNK — Monitor Queue will use a JDT with the name of default.jdt
when the VIPP special packet data field contains blanks.
Installing and Customizing XDPE/400 (9/2001)
6-16
Customizing XDPE/400
Portrait printing using the HP or IBM duplexing standard
NOTE: The Duplex standard (DUPLEXSTD) global value has no
effect on portrait printing. Both values produce the same result.
When you specify *YES for either the DUPLEX printer file parameter or
DUPLEX packet parameter, and Duplex standard is set to *HP or *IBM,
the result will be duplex with long-edge binding, as shown in this figure:
When you specify *TUMBLE for either the DUPLEX printer file parameter
or DUPLEX packet parameter, and Duplex standard is set to *HP or *IBM,
the result will be tumble duplex with short-edge binding, as shown below:
Installing and Customizing XDPE/400 (9/2001)
6-17
Customizing XDPE/400
Landscape printing using the HP duplexing standard
When you specify *YES for either the DUPLEX printer file parameter or
DUPLEX packet parameter, and Duplex standard is set to *HP, the result
will be duplex with long-edge binding, as shown in this figure:
When you specify *TUMBLE for either the DUPLEX printer file parameter
or DUPLEX packet parameter, and Duplex standard is set to *HP, the
result will be tumble duplex with short-edge binding, as shown in this
figure:
Installing and Customizing XDPE/400 (9/2001)
6-18
Customizing XDPE/400
Landscape printing using the IBM duplexing standard
When you specify *YES for either the DUPLEX printer file parameter or
DUPLEX packet parameter, and Duplex standard is set to *IBM, the result
will be duplex with short-edge binding, as shown in this figure:
When you specify *TUMBLE for either the DUPLEX printer file parameter
or DUPLEX packet parameter, and Duplex standard is set to *IBM, the
result will be tumble duplex with long-edge binding, as shown in this
figure:
Installing and Customizing XDPE/400 (9/2001)
6-19
Customizing XDPE/400
Separator page customization
XDPE/400 allows you to print using separator pages created by
XDPE/400 or by the OS/400 printer writer. You can select XDPE/400 or
the OS/400 printer writer through the Process separator page (BANNER)
Monitor Queue parameter.
If you use XDPE/400 to create your separator pages, the Process
separator page (BANNER) Monitor Queue parameter also allows you to
specify whether to generate a banner page, a trailer page, or both for each
job. Banner pages are separators that are generated at the beginning of
the file. Trailer pages are separators that are generated at the end of the
file.
NOTE: Unless specifically stated, all references to separator pages
apply to both banner and trailer pages. Also note that the OS/400
printer writer generates banner pages only.
Banner pages that are OS/400-generated print after any printer control
commands generated by XDPE/400 are applied. Banner pages that are
generated by XDPE/400 print before any user-specified printer control
commands are applied.
The number of separator pages generated by XDPE/400 or the OS/400
printer writer is determined by the File separators (FILESEP) Monitor
Queue parameter and the File separators (FILESEP) spool file attribute.
You can change the fixed text portion and the variable text portion format
of the separator pages.
Monitor Queue-generated separator pages
When Monitor Queue generates separator pages, the control comes from
several sources:
•
•
File separators (FILESEP) Monitor Queue parameter
File separators (FILESEP) spool file attribute
If the FILESEP Monitor Queue parameter is a numeric value, the number
of separators it specifies is generated. If the value of FILESEP is *FILE,
Monitor Queue checks the File separators (FILESEP) spool file attribute
to determine how many separator pages to generate. This number is the
same if OS/400 generated the separator pages.
Separator page contents formatting
When a Monitor Queue session starts, Monitor Queue looks for two
members, one called BANNER and one called TRAILER, in the
XDPEBANNER file in the XDPE/400 application library. Each member
contains a template that defines the format for the contents of the
separator pages.
Installing and Customizing XDPE/400 (9/2001)
6-20
Customizing XDPE/400
Modifying the banner and trailer templates
A separator page template is a series of text lines, one for each line of the
separator page. The text lines may contain fixed text and variable data
tokens. Variable data tokens are used to specify where to insert the
variable data into the text line. Refer to table 6-2 for more information
about variable data tokens.
The templates for the separator pages generated by XDPE/400 are in the
XDPE/400 application library. If you want to change the format of the
banner page, you must create a new banner template and replace the
XDPEBANNER/BANNER member with the new template. If you want to
change the format of the trailer page, you must create a new trailer
template and replace the XDPEBANNER/TRAILER member with the new
template. The SAMPLE file contains copies of the separator pages that
you can copy and edit using SEU.
NOTE: The appearance of the trailer page may change depending on
the print instructions you specified as part of your job.
When you create a separator page template for XDPE/400, you must
observe these rules:
•
The minimum length of a separator line is 10 characters.
•
The maximum length of a separator line is 150 characters, including
the variable data portion of the line.
•
The character “&,” which specifies the start of a token, can be used
as part of the fixed text. A misspelled token is unrecognized and is
printed as fixed data. For more information on the “&” (ampersand)
character, see the XDPE control character mapping (CNTCHAR)
global value description earlier in this chapter.
•
Tokens can appear in any order or in any position on a line.
•
The same token can be used more than once.
•
A maximum of 50 tokens can be used on a separator page. Any
number of tokens may appear on a line as long as the total does not
exceed the maximum for one page.
After you have created a new separator page template using SEU, you
must convert the source physical file member to a data physical file
member and place it in the XDPEBANNER file.
Installing and Customizing XDPE/400 (9/2001)
6-21
Customizing XDPE/400
To convert a source physical file member to a data physical file member
so you can use it as a separator page template, enter this command:
CPYF
FROMFILE(user-library-name/file-name)
TOFILE(library/XDPEBANNER)
FROMMBR(member-name)
TOMBR(separator-type)
MBROPT(*REPLACE)
FMTOPT(*CVTSRC)
where
library
The name of the XDPE/400 application library is
XDPEvrm, where
•
•
•
separator-type
v is the version number
r is the release number
m is the modification number
The type of separator page template you are converting;
enter BANNER for a banner page template or TRAILER
for a trailer page template.
Variable data tokens
Variable data tokens specify where to insert variable data into a line of
text. Table 6-2 lists the symbols and information that you need to generate
a separator page.
Installing and Customizing XDPE/400 (9/2001)
6-22
Customizing XDPE/400
Table 6-2.
Variable data tokens
Symbols
Description
Parameter source
Field width
&DATE
Current date
System value
10
&TIME
Current local time
System value
8
&JOBNAME
Job name
Spool file attribute
10
&JOBNUMBER
Job number
Spool file attribute
6
&USERNAME
User name
Spool file attribute
10
&SPLFNAME
Spool file name
Spool file attribute
10
&SPLFNUMBER
Spool file number
Spool file attribute
4
&FORMTYPE
Form type field contents
Spool file attribute
10
&USRDTA
User data field contents
Spool file attribute
10
&PAGES
Total number of pages
Spool file attribute
4
&STRPAGE
Initial page printed
Spool file attribute
4
&ENDPAGE
Last page printed
Spool file attribute
4
&COPIES
Total number of copies
Spool file attribute
4
&OUTQUEUE
Output queue name
Monitor Queue
10
&OUTQLIB
Output queue library
Monitor Queue
10
&FILEDATE
File open date
Spool file attribute
10
&FILETIME
Time that the file was opened
Spool file attribute
8
&WRITER
Printer writer name
WTR Monitor Queue
10
&PGMNAME
Program name that opened the file
Spool file attribute
10
&PGMLIB
Program library name that opened file
Spool file attribute
10
&ACCTCODE
Accounting code
Spool file attribute
15
&JOBTIME
Time that the job entered the system
System value
8
&JOBDATE
Date that the job entered the system
System value
10
&USRTXT
User text portion from user profile
User profile
50
&PRINTEXT
Print text — prints on bottom of each page
of printed output and on separator page
Spool file attribute
30
Installing and Customizing XDPE/400 (9/2001)
6-23
Customizing XDPE/400
Date and time format
The date and time separators used in the separator pages are the
site-specific separator characters, QDATESEP and QTIMESEP. The date
format is the site-specific format, QDATFMT. If Monitor Queue cannot
retrieve one of the date and time or format and separator values, a default
is substituted for that value, as shown in table 6-3. QDATESEP,
QTIMESEP, and QDATFMT are OS/400 system values.
Table 6-3.
Default separator values
Parameter
Default
QDATESEP
:
QTIMESEP
/
QDATEFMT
MDY
Installing and Customizing XDPE/400 (9/2001)
6-24
Customizing XDPE/400
Sample banner page template
The following example shows the BANXDPEN banner page template.
************** Xerox Document Print Executive **************
*
*
* XX
XX DDDDDDDDD
PPPPPPPPPPP
EEEEEEEEEEEE *
* XX
XX DDDDDDDDDD
PPPPPPPPPPPP EEEEEEEEEEEE *
*
XX
XX
DD
DD
PP
PP EE
*
*
XX
XX
DD
DD PP
PP EE
*
*
XX XX
DD
DD PP
PP EE
*
*
XXXX
DD
DD PPPPPPPPPPPP EEEEEEEE
*
*
XXXX
DD
DD PPPPPPPPPPP
EEEEEEEE
*
*
XX XX
DD
DD PP
EE
*
*
XX
XX
DD
DD PP
EE
*
*
XX
XX
DD
DD
PP
EE
*
* XX
XX DDDDDDDDDD
PP
EEEEEEEEEEEE *
* XX
XX DDDDDDDDD
PP
EEEEEEEEEEEE *
*
*
* Job name . . . . . . . &JOBNAME
*
* Job number . . . . . . &JOBNUMBER
*
* Job date . . . . . . . &JOBDATE
*
* Job time . . . . . . . &JOBTIME
*
* User name . . . . . . . &USERNAME
*
* &USRTXT
*
* Current date . . . . . &DATE
*
* Current time . . . . . &TIME
*
* Spool file name . . . . &SPLFNAME
*
* Spool file number . . . &SPLFNUMBER
* Form type . . . . . . . &FORMTYPE
*
* User data . . . . . . . &USRDTA
*
* Number of pages . . . . &PAGES
*
* Number of copies . . . &COPIES
*
* Starting page . . . . . &STRPAGE
*
* Ending page . . . . . . &ENDPAGE
*
* Output queue . . . . . &OUTQUEUE
*
* Output queue library . &OUTQLIB
*
* File date . . . . . . . &FILEDATE
*
* File time . . . . . . . &FILETIME
*
* Printer writer . . . . &WRITER
*
* Program name . . . . . &PGMNAME
*
* Program library . . . . &PGMLIB
*
* Accounting code . . . . &ACCTCODE
*
* Print Text . . . . . . &PRINTEXT *
*
*
* XX
XX DDDDDDDDD
PPPPPPPPPPP
EEEEEEEEEEEE *
* XX
XX DDDDDDDDDD
PPPPPPPPPPPP EEEEEEEEEEEE *
*
XX
XX
DD
DD
PP
PP EE
*
*
XX
XX
DD
DD PP
PP EE
*
*
XX XX
DD
DD PP
PP EE
*
*
XXXX
DD
DD PPPPPPPPPPPP EEEEEEEE
*
*
XXXX
DD
DD PPPPPPPPPPP
EEEEEEEE
*
*
XX XX
DD
DD PP
EE
*
*
XX
XX
DD
DD PP
EE
*
*
XX
XX
DD
DD
PP
EE
*
* XX
XX DDDDDDDDDD
PP
EEEEEEEEEEEE *
* XX
XX DDDDDDDDD
PP
EEEEEEEEEEEE *
*
*
************** Xerox Document Print Executive **************
Installing and Customizing XDPE/400 (9/2001)
*
6-25
Customizing XDPE/400
Generating separator pages in VIPP mode
XDPE/400 provides a Job Descriptor Ticket (JDT), called XDPSPR.JDT,
for PostScript printers that run in VIPP mode. This JDT is stored in the
XDPEFLR/JDTLIB folder.
XDPE/400 uses XDPSPR.JDT when creating separator pages for the
Direct and Combined methods. XDPSPR.JDT defines the overall page
layout format (such as orientation, margins, etc.) for banner and trailer
pages.
If you want to generate separator pages, you must download
XDPSPR.JDT to this printer controller directory on your PostScript printer:
/usr/xgfc/jdtlib/
Use the Download VIPP Resource (DNLDVIPRSC) or (DNLDVIPJDT)
commands for the N-series printers to download XDPSPR.JDT. For
instance, use the DNLDVIPRSC command for the DOCUSP and NPS
printers; use DNLDVIPJDT for the N-series printers. Refer to chapter 21
in Section Three: Printing Documents with XDPE/400 for a list of the
commands and more information on how to use the download commands.
NOTE: You may want to review the contents of XDPSPR.JDT before
downloading it to the printer controller directory. You can use the
Change VIPP Resource (CHGVIPRSC) command to review or
change the contents of XDPSPR.JDT. Refer to chapter 17 in Section
Three: Printing Documents with XDPE/400 for instructions about how
to use this command. If you want to customize the contents of
XDPSPR.JDT before downloading, see “Customizing the separator
page layout (VIPP mode only)” below.
Installing and Customizing XDPE/400 (9/2001)
6-26
Customizing XDPE/400
Customizing the separator page layout (VIPP mode only)
If you want to change the page layout of the separator pages, you must
modify XDPSPR.JDT and then download it to the printer controller.
NOTE: XDPSPR.JDT controls the page layout only. If you need to
change the fixed or variable text portion of a VIPP separator page,
see “Modifying the banner and trailer templates” earlier in this
chapter.
Perform these steps if you want to change XDPSPR.JDT:
Step 1.
Make a copy of XDPSPR.JDT before modifying it.
Step 2.
Edit XDPSPR.JDT using the Change VIPP Resource (CHGVIPRSC)
command. Refer to chapter 17 in Section Three: Printing Documents with
XDPE/400 for instructions on how to use this command.
CAUTION: Unpredictable results may occur if you specify the VIPP
SETCYCLECOPY command in XDPSPR.JDT and then generate
trailer pages for multiple copy print jobs. If you need to generate
trailer pages for multiple copy print jobs, use the File separators
(FILESEP) Monitor Queue parameter. Refer to chapter 18 and
chapter 26 for information about FILESEP and instructions on how to
troubleshoot and resolve this condition.
Step 3.
Use the Download VIPP Resource (DNLDVIPRSC) command or
(DNLDVIPJDT) command for N-series to download XDPSPR.JDT to this
printer controller directory on your PostScript printer:
/usr/xgfc/jdtlib/
Refer to chapter 21 for instructions on how to use this command.
Installing and Customizing XDPE/400 (9/2001)
6-27
Customizing XDPE/400
Monitor Queue job log
Monitor Queue uses the job description MONQJOBD in the XDPE/400
application library. This job description defines a message logging level
of 4 and a message severity level of 30.
A message level of 4 specifies that all messages with a severity level
greater than or equal to the specified message severity are to be logged.
Because not all messages have a severity greater than 30, not all Monitor
Queue messages are logged.
To change the Monitor Queue message logging parameters, type this
command and press ENTER before Monitor Queue is started:
CHGJOBD
JOBD(library/MONQJOBD)
LOG(message-level message-severity *NOLIST)
where
library
The XDPE/400 application library name of the
library is XDPEvrm, where
•
•
•
v is the version number
r is the release number
m is the modification number
message-level
The type of message logging.
message-severity
The severity of the messages logged.
Installing and Customizing XDPE/400 (9/2001)
6-28
Customizing XDPE/400
XDPE/400 command customization
Two examples for customizing XDPE/400 commands are supplied below.
Use the method that best meets the needs of your site.
Example 1
To customize the XDPE/400 commands so they will not be deleted during
the installation of future maintenance or upgrades, you can create CL
programs to customize the commands you wish to change using this
procedure.
NOTE: When calling Xerox Technical Support to report a problem, be
sure to inform your representative that you have customized
commands.
Step 1.
Create a local source library to contain local XDPE/400 modifications. Do
not use the XDPE/400 application library. Use this command:
CRTLIB
LIB(XDPECMDS)
TYPE(*TEST)
TEXT('XDPE local modifications')
Step 2.
Create a source physical file in the library you just specified. Use this
command:
CRTSRCPF
FILE(XDPEMODS/XDPECLSRC)
TEXT('CL source to implement local modifications to XDPE')
Step 3.
Create a member in the source physical file you just specified with type
CLLE using this command:
STRSEU
SRCFILE(XDPEMODS/XDPECLSRC) SRCMBR(XDPECMDDFT)
TYPE(CLLE)
TEXT('Modify XDPE command defaults')
Step 4.
Edit your source physical file member to create the source code of a CL
program to contain the Change Default Commands to make the actual
modifications using this command:
STRSEU
SRCFILE(XDPEMODS/XDPECLSRC) SRCMBR(XDPECMDDFT)
OPTION(2)
See the following source code example to determine the customization
commands to include in your file member.
Installing and Customizing XDPE/400 (9/2001)
6-29
Customizing XDPE/400
This example automatically changes the WAITTIME default to ‘0’ when
the STRMONQ command is issued, and changes the End
Schedule(SCHED) parameter to *IMMED when the ENDMONQ command
is issued:
/*SAMPLE CL PROGRAM TO MODIFY XDPE COMMAND DEFAULTS*/
/*LOCAL CHANGE TO ALWAYS START MONITOR QUEUE WITH ZERO WAITTIME*/
/*LOCAL CHANGE TO ALWAYS END MONITOR QUEUE WITH OPTION *IMMED*/
PGM PARM(&LIBRARY) /*SPECIFIES XDPE/400 APPLICATION LIBRARY*/
DCL VAR (&LIBRARY) TYPE(*CHAR) LEN(10)
CHGCMDDFT
CMD(&LIBRARY/STRMONQ) NEWDFT(‘WAITTIME(0)’)
CHGCMDDFT
CMD(&LIBRARY/ENDMONQ) NEWDFT(‘SCHED(*IMMED)’)
ENDPGM
This has the effect of creating new defaults for parameters used for these
commands. Any parameter settings can be specified, and other
XDPE/400 commands also can be customized, such as CRTXPCL and
CRTXLPP.
Step 5.
Compile your source physical file member using all defaults to create a
program that can be executed each time XDPE/400 maintenance is
applied. It will need to be reviewed for potential new or changed
parameters when a new version of XDPE/400 is installed prior to
execution. Use this command:
CRTCLPGM
PGM(XDPEMODS/XDPECMDDFT)
SRCFILE(XDPEMODS/XDPECLSRC)
Step 6.
Execute the generated *PGM to make the changes using the following
command:
CALL
PGM(XDPEMODS/XDPECMDDFT)
PARM(library)
where
library
The name of the XDPE/400 application library is XDPEvrm,
where
•
•
•
Step 7.
v is the version number
r is the release number
m is the modification number
Document the change in your local standard operating procedures.
Installing and Customizing XDPE/400 (9/2001)
6-30
Customizing XDPE/400
Example 2
This sample allows you to customize your STRMONQ commands. This
program starts the Monitor Queue session and indicates the fields to
change. You can customize the program for each printer.
?STRMONQ must be the first command in all the programs you customize
for the Start Monitor Queue option.
This example shows a customized program for STRMONQ:
PGM PARM(&OUTQLIB &OUTQ &PRINTER)
?STRMONQ ??(&OUTQLIB/&OUTQ) ??WTR(&PRINTER) INTERFACE(*FLEX) MODEL(4235) MODE(XDPM)
ENDPGM
In this example, you only need to enter the output queue and printer
specifications. The interface, model, and mode are already specified.
To make it easier for you to start a Monitor Queue session for different
printers, you can create a menu with the various STRMONQ commands
as the options.
Using A4 paper for NPS and DocuSP printers (PCL mode
only)
If you will be printing on A4 paper in PCL mode using an NPS or DocuSP
printer, you must modify the XDPE/400 PCL printer files using these
commands:
CHGPRTF
FILE(library/DSPXPCL)
PAGESIZE(70 83 *ROWCOL)
CHGPRTF
FILE(library/WRKXPCLMAC)
PAGESIZE(70 124 *ROWCOL)
where
library
The name of the XDPE/400 application library is XDPEvrm,
where
•
•
•
v is the version number
r is the release number
m is the modification number
Installing and Customizing XDPE/400 (9/2001)
6-31
Customizing XDPE/400
Installing and Customizing XDPE/400 (9/2001)
6-32
7.
7
Performing an installation verification
procedure
This chapter contains the installation verification procedure (IVP) used to
verify that XDPE/400 is working properly.
The IVP performs these functions:
•
•
•
Verifies the connectivity of the AS/400 to the Xerox printer
Verifies the correct installation of XDPE/400
Downloads the multi-up resources for XPPM printers
NOTE: Before you run an IVP on a network printer, make sure that
you have addressed all XDPE/400 setup requirements for your
printer. Refer to chapter 20 in Section Three: Printing Documents with
XDPE/400 for the requirements.
The IVP tests the major functional areas of XDPE/400 to ensure a working
product within your environment. After you customize XDPE/400 by
setting all required global values, use the Create XDPE/400 IVP Test
(CRTXIVP) command to create the IVP data streams for:
•
Resource loading (*DJDERSC) — Loads the XPPM mode resources
for multi-up printing.
•
Direct mode printing (*DIRECT) — For DJDE, XES, or PCL mode,
references a packet (XIVP) from the IVP printer file (XIVPRTF) to
create DJDE, XES, or PCL packets into the print data stream. For
VIPP mode, inserts a reference in the IVP print data stream to a JDT
(xivp.jdt) on the printer controller.
•
Indirect mode printing (*INDIRECT) — Creates a print data stream
with copies and duplex selected, and uses the IVP printer file
(XIVPRTF).
•
Combined mode printing (*COMBINED) — Uses both Direct and
Indirect mode settings to create DJDE, XES, and PCL packets or
insert a VIPP JDT reference for an IVP print data stream.
Installing and Customizing XDPE/400 (9/2001)
7-1
Performing an installation verification procedure
IVP requirements
Before running your IVP job, the Attributes include/exclude (INHIBLST)
Margins global value must be *YES.
Also note the additional requirements in the following sections before
running your DJDE, PCL, or VIPP IVP job.
XPPM IVP
Before you run the XPPM IVP, make sure you have performed these
tasks:
•
•
Assigned XDPE/400 global values
Started the printer with the appropriate JDEs/JDLs
You must modify the JSL used for the IVP to include:
•
An RSTACK test matching the RSTACK that XDPE/400 generates
•
An IDEN statement with parameters matching the DJDE packets that
XDPE/400 generates
This example is correct for the default RSTACK that XDPE/400
generates:
T1: TABLE CONSTANT=('RSTACK');
C1: CRITERIA CONSTANT=(0,6,EQ,T1);
RSTACK TEST=C1,DELIMITER=YES;
This example is correct for the default DJDE packets that XDPE/400
generates:
IDEN PREFIX='DJDE',OFFSET=2,SKIP=7;
PCL IVP
If you will be printing *INDIRECT or *COMBINED IVPs on A4 paper using
an NPS or DocuSP printer, issue this command before running the first
IVP:
CHGPRTF
FILE(library/XIVPRTF)
PAGESIZE(70 124 *ROWCOL)
where
library
The name of the XDPE/400 application library is XDPEvrm,
where
•
•
•
v is the version number
r is the release number
m is the modification number
Installing and Customizing XDPE/400 (9/2001)
7-2
Performing an installation verification procedure
VIPP IVP
Before you run the VIPP IVP, use the Download VIPP Resource
(DNLDVIP*) commands to download these resources to the printer
controller directory:
Table 7-1.
Resources required for the VIPP IVP
Resource name
Purpose
XDPE/400 location
Printer controller
directory destination
XIVP.JDT
JDT for generating the IVP using the
Direct and Combined methods
XDPEFLR/JDTLIB
/usr/xgfc/jdtlib/
XDPIVP.FRM
Form that is called by XIVP.JDT for
the Direct and Combined methods
XDPEFLR/FORMLIB
/usr/xgfc/formlib/
Refer to chapter 21 in Section Three: Printing Documents with XDPE/400
for instructions about how to use DNLDVIP* commands.
NOTE: In addition to XIVP.JDT and XDPIVP.FRM, the VIPP IVP may
use XDPSPR.JDT to generate separator pages for the Direct and
Combined methods, depending on the Monitor Queue parameters.
Therefore, XDPSPR.JDT also must reside in the printer controller
directory. Refer to “Generating separator pages in VIPP mode” in
chapter 6 for more information about XDPSPR.JDT.
Installing and Customizing XDPE/400 (9/2001)
7-3
Performing an installation verification procedure
Starting Monitor Queue
You must now start Monitor Queue in order to run the installation
verification procedure. If you started Monitor Queue at any time prior to
this point in the installation procedure, you may experience Monitor
Queue abends. Before preceding, sign off as XDPEUSR and sign on
using your own user profile.
Step 1.
Add the XDPE/400 application library to your library list.
Step 2.
Start a Monitor Queue session by entering STRMONQ.
Step 3.
Enter values for these Monitor Queue parameters and press ENTER:
•
•
•
•
•
•
•
Output queue and library (OUTQ)
Printer writer (WTR)
Interface box (INTERFACE)
Printer model (MODEL)
Printer emulation (PRTTYPE)
Software version (VERSION); applies only to the 4235 printer
Printer mode (MODE)
All other parameters must use the default. Note that for the Packet data
(PACKETDATA) parameter, you can specify either *USRDTA, which is
the default, or *FORMTYPE.
Refer to “Starting a Monitor Queue session” in chapter 20 of Section
Three: Printing Documents with XDPE/400 for additional parameters used
for remote and network printers.
You are now ready to perform the installation verification procedure.
Installing and Customizing XDPE/400 (9/2001)
7-4
Performing an installation verification procedure
Executing the IVP
Use the CRTXIVP command to verify the XDPE/400 installation and, if
you have an XPPM printer, to initialize the printer with the multi-up DJDE
resources. The CRTXIVP command generates the IVP spool files. You
can access CRTXIVP from the interactive command line using keywords,
through a fill-in display, or execute it in batch mode.
Follow these steps to access the IVP through a command:
Step 1.
Enter CRTXIVP and press F4. The Create XDPE IVP screen displays.
Step 2.
Enter the type of IVP and the output queue to use, and press ENTER.
Create XDPE IVP (CRTXIVP)
Type choices, press Enter.
Type of IVP . . . . . . . . . .
Output queue . . . . . . . . .
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
*DJDERSC, *INDIRECT...
Name
F12=Cancel
Installing and Customizing XDPE/400 (9/2001)
Bottom
F13=How to use this display
7-5
Performing an installation verification procedure
Creating XDPE/400 IVP parameters
Type of IVP (TYPE)
Specifies whether the IVP is a resource download or a test of a printer
control packet insertion method. Enter one of these four values:
•
DJDERSC — Downloads these resources to the printer specified on
the CRTXIVP screen:
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
—
Output queue (OUTQ)
P07TYA.FNT
L0112B.FNT
XGT30P.FNT
XGB20L.FNT
XGB10P.FNT
ONEPOR.FRM
ONELAN.FRM
TWOPOR.FRM
TWOLAN.FRM
FORPOR.FRM
FORLAN.FRM
ONEPOR.PDE
ONELAN.PDE
TWOPOR.PDE
TWOLAN.PDE
FORPOR.PDE
FORLAN.PDE
•
DIRECT — Prints a prepared job using the direct method.
•
INDIRECT — Prints a prepared job using the indirect method.
•
COMBINED — Prints a prepared job using the combined method.
Specifies the name of the output queue to which the system writes the
data downloaded by the IVP.
Verifying your output
After you run the IVP, compare your output to the samples shown in
appendix A. If your output is similar to the samples, you have successfully
completed your installation.
Installing and Customizing XDPE/400 (9/2001)
7-6
Performing an installation verification procedure
IVP sample output
Chapter 7, “Performing an installation verification procedure,” gives you
instructions for performing the IVP after you have installed XDPE/400.
When you perform the IVP, check your output against the samples
provided in this appendix and verify that they are similar. Printer banner
pages are not included with these samples.
Sample output is provided for these types of printers and modes:
•
•
•
•
•
•
•
•
•
•
•
•
DJDE direct mode
DJDE indirect mode
DJDE combined mode
XES direct mode
XES indirect mode
XES combined mode
PCL direct mode
PCL indirect mode
PCL combined mode
VIPP direct mode
VIPP indirect mode
VIPP combined mode
Due to differences in printer and interface box settings, your DJDE, XES,
PCL, and VIPP IVP output may vary slightly from the samples provided.
Also, due to production variations and paper sizes (Letter or A4) when
printing, your IVP output may not precisely match the samples provided.
DJDE Direct Mode IVP
A sample of the DJDE Direct Mode IVP output follows this page.
Installing and Customizing XDPE/400 (9/2001)
7-7
Performing an installation verification procedure
Installing and Customizing XDPE/400 (9/2001)
7-8
COPY 1 OF IVP TEST
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
2
3
COPY 2 OF IVP TEST
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
2
3
Performing an installation verification procedure
DJDE Indirect Mode IVP
A sample of the DJDE Indirect Mode IVP output follows this page.
Installing and Customizing XDPE/400 (9/2001)
7-21
Performing an installation verification procedure
Installing and Customizing XDPE/400 (9/2001)
7-22
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
Performing an installation verification procedure
DJDE Combined Mode IVP
A sample of the DJDE Combined Mode IVP output follows this page.
Installing and Customizing XDPE/400 (9/2001)
7-27
Performing an installation verification procedure
Installing and Customizing XDPE/400 (9/2001)
7-28
COPY 1 OF IVP TEST
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
2
3
COPY 2 OF IVP TEST
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
DJDE.
2
3
Performing an installation verification procedure
XES Direct Mode IVP
A sample of the XES Direct Mode IVP output follows this page.
Installing and Customizing XDPE/400 (9/2001)
7-37
Performing an installation verification procedure
Installing and Customizing XDPE/400 (9/2001)
7-38
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
Performing an installation verification procedure
XES Indirect Mode IVP
A sample of the XES Indirect Mode IVP output follows this page.
Installing and Customizing XDPE/400 (9/2001)
7-43
Performing an installation verification procedure
Installing and Customizing XDPE/400 (9/2001)
7-44
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
Performing an installation verification procedure
XES Combined Mode IVP
A sample of the XES Combined Mode IVP output follows this page.
Installing and Customizing XDPE/400 (9/2001)
7-49
Performing an installation verification procedure
XDPE *COMBINED IVP Test. Printer Mode is XES.
Installing and Customizing XDPE/400 (9/2001)
7-50
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
XES.
Performing an installation verification procedure
PCL Direct Mode IVP
A sample of the PCL Direct Mode IVP output follows this page.
Installing and Customizing XDPE/400 (9/2001)
7-55
Performing an installation verification procedure
Installing and Customizing XDPE/400 (9/2001)
7-56
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
FORM FORM FORM FORM FORM
11111111111111111111111
FORM FORM FORM FORM FORM
M
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
Performing an installation verification procedure
PCL Indirect Mode IVP
A sample of the PCL Mode IVP output follows this page.
Installing and Customizing XDPE/400 (9/2001)
7-59
Performing an installation verification procedure
Installing and Customizing XDPE/400 (9/2001)
7-60
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
Performing an installation verification procedure
PCL Combined Mode IVP
A sample of the PCL Combined Mode IVP output follows this page.
Installing and Customizing XDPE/400 (9/2001)
7-65
Performing an installation verification procedure
Installing and Customizing XDPE/400 (9/2001)
7-66
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
PCL.
Performing an installation verification procedure
VIPP Direct Mode IVP
A sample of the VIPP Direct Mode IVP output follows this page.
Installing and Customizing XDPE/400 (9/2001)
7-71
Performing an installation verification procedure
Installing and Customizing XDPE/400 (9/2001)
7-72
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
XDPE/400 Installation Verification Procedure
XDPE/400 IVP XDPE/400 IVP XDPE/400 IVP
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
*DIRECT
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
XDPE/400 Installation Verification Procedure
XDPE/400 IVP XDPE/400 IVP XDPE/400 IVP
Performing an installation verification procedure
VIPP Indirect Mode IVP
A sample of the VIPP Indirect Mode IVP output follows this page.
Installing and Customizing XDPE/400 (9/2001)
7-77
Performing an installation verification procedure
Installing and Customizing XDPE/400 (9/2001)
7-78
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
*INDIRECT
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
Performing an installation verification procedure
VIPP Combined Mode IVP
A sample of the VIPP Combined Mode IVP output follows this page.
Installing and Customizing XDPE/400 (9/2001)
7-83
Performing an installation verification procedure
Installing and Customizing XDPE/400 (9/2001)
7-84
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
XDPE/400 Installation Verification Procedure
XDPE/400 IVP XDPE/400 IVP XDPE/400 IVP
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
XDPE
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
*COMBINED
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
IVP
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Test.
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Printer
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
Mode
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
is
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
VIPP.
XDPE/400 Installation Verification Procedure
XDPE/400 IVP XDPE/400 IVP XDPE/400 IVP
Section Three:
Printing Documents with XDPE/400
Printing Documents with XDPE/400 (9/2001)
8.
8
Print job configuration
This chapter outlines the major steps necessary to configure your AS/400
print jobs to print using XDPE/400. The main steps are:
•
•
•
•
•
Choosing a command generation method
Configuring your printer file
Creating Xerox printer control packets
Downloading resources
Starting Monitor Queue
The procedures and examples used in this chapter are meant only as an
introduction and are not comprehensive. For a complete discussion of the
procedures and parameters used, refer to the appropriate chapter.
Choosing a command generation method
How you use XDPE/400 depends on the complexity of the jobs you want
to print. XDPE/400 generates printer control commands using one of
these methods: None, Indirect, Direct and Combined.
None
Using this method, XDPE/400 does not create or insert any Xerox printer
commands into the job. The spool file is sent to be printed “as-is.”
Indirect method
XDPE/400 converts the spool file attributes to Xerox printer commands
and creates a new spool file, integrating these commands with the data to
be printed. Use the Indirect method for simpler jobs that do not require
changes after they are created by the application.
Direct method
XDPE/400 creates printer control commands from a printer control packet
specified for the spool file, ignoring the spool file attributes. You should
use this method under these conditions:
•
You want to take advantage of features of your Xerox printing system
that you cannot specify through spool file attributes.
•
You want to access Xerox print job specifications stored on the
printer.
•
The operating environment at your site makes it undesirable to
modify printer file parameters.
•
You wish to use XDPE/400’s higher processing functions, such as
multi-part printing and logical processing.
To use this method, you must create the processing resources to use with
the job. Depending on the printer mode for which you are configuring the
job, you create DJDE, XES, or PCL printer control packets or you create
and download VIPP printer control JDTs.
Depending on the printer mode and the type of processing required to
produce the job, you may also create resource lists, logical processing
packets, multi-part packets, or multi-up packets.
For XDPE/400 to use the packet or JDT you created when processing the
spool file, the name of the packet or JDT must be entered in the
appropriate field in the printer file used to create the spool file.
Printing Documents with XDPE/400 (9/2001)
8-1
Print job configuration
Combined method
XDPE/400 creates printer control commands from the spool file attributes
and the printer control packets and combines them both in the new spool
file.
•
•
For DJDE, XES, and PCL data streams, you can decide the order in
which these commands will be sent to the printer.
—
For DJDE data streams, see your DJDE printer documentation
for the manner in which your DJDE printer implements these
commands.
—
For XES and PCL data streams, the last command sent
overrides any previous command.
For VIPP data streams, the spool file attributes override the
attributes specified in the printer control JDTs. In addition, XDPE/400
controls the sequence in which the printer control commands will be
sent to the printer. Refer to chapter 17 for information about how
VIPP printer control commands are handled when using the
Combined method.
This method allows you to use printer control packets to override only
those spool file attributes you wish, while using XDPE/400’s higher
processing functions. The requirements for using this method are the
same as for using the Direct method: you must create the appropriate
packets and reference them in your printer file. If no packet is specified,
then processing is the same as the Indirect method.
Printing Documents with XDPE/400 (9/2001)
8-2
Print job configuration
Setting the command generation method
You can specify the method used by XDPE/400 to generate control
commands for a job by using these parameters:
•
The Always generate (ALWAYS) and Order of sequence
(SEQUENCE) Monitor Queue parameters
•
The spool file attribute specified by the Packet data (PACKETDATA)
Monitor Queue parameter
ALWAYS and SEQUENCE specify the command generation method
when the Monitor Queue session is started. To vary the command
generation method from job to job, use the Packet data (PACKETDATA)
Monitor Queue parameter.
Using the Packet data (PACKETDATA) parameter
The Packet data (PACKETDATA) Monitor Queue parameter specifies
which spool file attribute(s) the Monitor Queue will use to find processing
information for that job. For all spooled files on a particular output queue,
Monitor Queue examines the appropriate spool file attribute(s) to
determine how to generate Xerox printer control information. For
example, if you specify *FORMTYPE for the PACKETDATA parameter,
the Monitor Queue will look in the Form type (FORMTYPE) spool file
attribute for the name of a packet to be processed with that spool file.
Refer to chapter 18 for more information on the PACKETDATA Monitor
Queue parameter.
In addition to identifying the name of a packet in the specified spool file
attribute, you can also specify an XDPE/400 control character. This
XDPE/400 control character, in conjunction with the Always generate
(ALWAYS) Monitor Queue parameter, determines the method of printer
control generation to be used for the job. The control characters are
defined in the global values.
Refer to table 10-1 in chapter 10 for the relationship between the contents
of the ALWAYS parameter and the spool file attribute indicated by the
PACKETDATA parameter. The XDPE/400 control character defaults of #
and + are used.
Printing Documents with XDPE/400 (9/2001)
8-3
Print job configuration
Configuring your printer file
The application you use to create your print job uses the printer file
parameters to create the spool file. Because printer file parameters
determine the attributes of the spool file, you can control what Monitor
Queue finds in your spool file attributes by modifying the parameters in
the printer file your application uses to create the spool file.
In addition to the OS/400 commands CRTPRTF, CHGPRTF, and
OVRPRTF, XDPE/400 supplies these commands to change or override
the printer file parameters that control spool file attributes for XDPE/400:
•
The Change Xerox Printer File (CHGXPRTF) command makes
permanent changes to a printer file.
•
The Override Xerox Printer File (OVRXPRTF) command overrides
printer file parameters for the duration of a particular job.
These commands provide an easy way to configure your jobs for
XDPE/400. They are similar to their OS/400 counterparts, but contain a
subset of the more widely used printer file parameters.
You can use the CHGXPRTF or OVRXPRTF command to set these
parameters:
•
•
•
•
•
•
•
•
Copy count
Duplex
Font ID
Front and back overlay
Multiple up
Page orientation
Predrilled offsetting
Source drawer
In addition to these print specifications, these commands allow you to
specify the type of command generation method to use and a packet
name if the Direct or Combined method is indicated.
Refer to chapter 10 for more information about how to use these
XDPE/400-supplied commands.
Creating Xerox printer control packets
XDPE/400 printer control packets allow you to control higher printing
functions without having to learn printer control languages.
XDPE/400 provides a facility for creating and changing packets for use
with XPPM (DJDE), XDPM (XES), Xerox PostScript (VIPP), or Xerox PCL
printers and those PCL printers capable of handling Xerox job ticketing.
In addition to these printer control packets, XDPE/400 allows you to
create packets that access the higher processing functions of XDPE/400
and your Xerox printer, such as:
•
•
•
•
Logical processing packets
Multi-part packets
Multi-up packets
Extended job ticket packets
Refer to the appropriate chapters for the data stream type and features
you want to use for your job.
Printing Documents with XDPE/400 (9/2001)
8-4
Print job configuration
Downloading resources
If your job requires print resources such as fonts or forms, these
resources must be resident on your printer before you print your job.
XDPE/400 provides two methods for downloading resources to your
printer:
•
Manual downloading using XDPE/400 download commands.
For XPPM (DJDE) printers, you can download these resources:
—
—
—
—
—
—
—
—
fonts
forms
images
logos
JDL objects
PDL objects
FSL source
JSL source
For XDPM (XES) printers, you can download these resources:
—
—
fonts
forms
For PCL printers, you can download these resources:
—
—
fonts
macros
For PostScript (VIPP) printers, you can download these resources:
—
—
—
—
—
—
—
•
fonts
forms
images
Job Descriptor Tickets (JDTs)
encoding tables
segments
VIPP core and setup files
Semi-automatic downloading using list processing. Using the list
processing facility, you can specify the resources to be downloaded
by XDPE/400 to your printer at the time your job is processed.
Refer to chapter 21, “Resource management,” or chapter 22, “List
processing,” for more information about using these facilities.
Printing Documents with XDPE/400 (9/2001)
8-5
Print job configuration
Starting Monitor Queue
To process the spool files created by your application, use the XDPE/400
Monitor Queue facility. Monitor Queue tailors each spool file to the print
device you have selected. In addition, Monitor Queue provides a second
layer of processing where any packets you have created for your jobs are
incorporated and higher processing functions are performed, such as
logical processing and multi-up printing.
The Monitor Queue contains a number of different options for printing
your jobs, including methods of command generation and environmental
settings such as banner page generation. Refer to chapter 18 for more
information about using the Monitor Queue.
Printing Documents with XDPE/400 (9/2001)
8-6
9.
9
XDPE/400 commands and menus
There are two ways that you can perform XDPE/400 functions. You can
access functions directly using the appropriate command for each
function, or you can access functions using XDPE/400-supplied menus.
Commands
You can access these XDPE/400 commands from the OS/400 command
line:
Global value
Installation verification
Printer file
DJDE
XES
XES color
PCL
Extended job ticketing
WRKGBLVAL — Works with the XDPE/400 global values
CRTXIVP — Initiates the installation verification procedure
CHGXPRTF — Changes printer file parameters
OVRXPRTF — Overrides printer file parameters
CRTDJDE — Creates a DJDE packet
CHGDJDE — Changes a DJDE packet
EDTDJDE — Edits a DJDE packet (full menu)
CRTXES — Creates an XES packet
CHGXES — Changes an XES packet
DLTXES — Deletes an XES packet
CRTXCOL — Creates a Xerox color packet
CHGXCOL — Changes a Xerox color packet
DLTXCOL — Deletes a Xerox color packet
CRTXPCL — Creates a PCL packet
CHGXPCL — Changes a PCL packet
DLTXPCL — Deletes a PCL packet
DSPXPCL — Displays a PCL packet
CRTXTCK — Creates extended job ticket packets
CHGXTCK — Changes, displays, and prints extended job ticket packets
DLTXTCK — Deletes extended job ticket packets
VIPP
CRTVIPRSC — Creates a VIPP resource or PostScript DSC packet
CHGVIPRSC — Edits, displays, and prints a VIPP resource or PostScript
DSC packet
DLTVIPRSC — Deletes a VIPP resource or PostScript DSC packet
Monitor Queue
STRMONQ — Starts a Monitor Queue session
CHGMONQ — Changes a Monitor Queue session
ENDMONQ — Ends a Monitor Queue session
DSPMONQ — Displays current Monitor Queue properties
RSTMONQ — Resets a Monitor Queue session
WRKMONQJOB — Displays current Monitor Queue sessions
DSPXDPEVER — Display XDPE Version
Printing Documents with XDPE/400 (9/2001)
9-1
XDPE/400 commands and menus
Xerox resource
DNLDFNTRSC — Downloads font resources
DNLDFRMRSC — Downloads form resources
DNLDIMGRSC — Downloads image resources
DNLDLGORSC — Downloads logo resources
DNLDJDLRSC — Downloads JDL resources
DNLDPDLRSC — Downloads PDL resources
DNLDFSLRSC — Downloads FSL resources
DNLDJSLRSC — Downloads JSL resources
DNLDXESFNT — Downloads XES font resources
DNLDXESFRM — Downloads XES form resources
DNLDPCLFNT — Downloads PCL fonts resources
DNLDPCLMAC — Downloads PCL macros resources
WRKXPCLMAC — Converts PCL macro invocation method
DNLDVIPRSC — Downloads VIPP or PostScript resources
DNLDVIPENC — Downloads VIPP encoding tables
DNLDVIPFNT — Downloads VIPP font resources
DNLDVIPFRM — Downloads VIPP form resources
DNLDVIPIMG — Downloads VIPP image resources
DNLDVIPJDT — Downloads VIPP JDT resources
List processing
CRTXRSCLST — Creates a Xerox resource list file
Logical processing
Multi-part printing
CRTXLPP — Creates a Xerox logical processing packet
CHGXLPP — Changes a Xerox logical processing packet
DLTXLPP — Deletes a Xerox logical processing packet
CRTXMPT — Creates a multi-part packet
CHGXMPT — Changes a multi-part packet
DLTXMPT — Deletes a multi-part packet
Printing Documents with XDPE/400 (9/2001)
9-2
XDPE/400 commands and menus
Menus
There are two types of XDPE/400 menus:
•
•
Command group menus
Task-specific menus
Each type of menu is described in more detail in the following sections.
XDPE/400 uses a buffer to store all commands that were input while in a
specific menu. When you select an XDPE/400 menu, none of the
commands you entered while in that menu are available when you return
to a previous XDPE/400 menu. When you are in an IBM menu, directly or
from an XDPE/400 menu, use F9 to retrieve all commands you entered
during the interactive session. However, this does not work for the
WRKMONQJOB command.
Command group menus
Command group menus consist of a set of general XDPE/400 menus.
Most XDPE/400 functions have an associated command group menu. The
command group menus display all of the menu-specific commands, as
well as any related commands or menus. You access command group
menus with the OS/400 convention GO CMDxxxx, where xxxx is the
specific menu.
These XDPE/400 command group menus are available:
•
CMDXDPE — General XDPE/400 Commands menu
•
CMDDJDE — Dynamic Job Descriptor Entry Commands menu
•
CMDXES — XES Packet Commands menu
•
CMDXRSC — Xerox Resource Commands menu
•
CMDMONQ — Monitor Queue Commands menu
•
CMDXLPP — Logical Processing Commands menu
•
CMDXCOL — Color Processing Commands menu
•
CMDXPCL — Xerox PCL Commands menu
•
CMDXMPT — Xerox Multi-part Commands menu
Figure 9-1 shows an example of the General XDPE/400 Commands
menu.
Printing Documents with XDPE/400 (9/2001)
9-3
XDPE/400 commands and menus
Figure 9-1.
General XDPE/400 Commands menu
CMDXDPE
Xerox Document Print Executive
System: XXXXXXXX
Select one of the following:
Commands
1. Dynamic Job Descriptor Entry (DJDE) commands
2. Xerox Escape Sequence (XES) packet commands
3. Xerox resource commands
4. Monitor Queue commands
5. Logical processing commands
6. Color processing commands
7. Xerox PCL commands
8. Xerox multi-part commands
CMDDJDE
CMDXES
CMDXRSC
CMDMONQ
CMDXLPP
CMDXCOL
CMDXPCL
CMDXMPT
Related command
11. Work with XDPE global values
12. Create a XEROX resource list
WRKGBLVAL
CRTXRSCLST
Selection or command
===>
F1=Help
F3=Exit
F4=Prompt
F9=Retrieve
F12=Cancel
F16=Major menu
Task-specific menus
Task-specific menus provide the commands that are related to the
specified function. You access task-specific menus with the WRKxxxx
convention, where xxxx is the specific function.
These XDPE/400 task-specific menus are available:
•
WRKXDPE — General XDPE/400 Task menu
•
WRKDJDE — Work with Dynamic Job Descriptor Entry Commands
menu
•
WRKXES — Work with XES Packet Commands menu
•
WRKXRSC — Work with Xerox Resource Commands menu
•
WRKMONQ — Work with Monitor Queue Commands menu
•
WRKXLPP — Work with Logical Processing Commands menu
•
WRKXCOL — Work with Color Processing Commands menu
•
WRKXPCL — Work with Xerox PCL Commands menu
•
WRKXMPT — Work with Xerox Multi-part Commands menu
Figure 9-2 shows an example of the General XDPE/400 Task menu.
Printing Documents with XDPE/400 (9/2001)
9-4
XDPE/400 commands and menus
Figure 9-2.
General XDPE/400 Task menu
WRKXDPE
Xerox Document Print Executive
System:
XXXXXXXX
Select one of the following:
1.
2.
3.
4.
5.
6.
7.
8.
11.
12.
Work
Work
Work
Work
Work
Work
Work
Work
with
with
with
with
with
with
with
with
Dynamic Job Descriptor Entry (DJDE) commands
XES packet commands
Xerox resource commands
Monitor Queue commands
logical processing commands
color processing commands
Xerox PCL commands
Xerox multi-part commands
Work with XDPE global values
Create a XEROX resource list
WRKDJDE
WRKXES
WRKXRSC
WRKMONQ
WRKXLPP
WRKXCOL
WRKXPCL
WRKXMPT
WRKGBLVAL
CRTXRSCLST
Selection or command
===>
F1=Help
F3=Exit
F4=Prompt
F9=Retrieve
Printing Documents with XDPE/400 (9/2001)
F12=Cancel
F16=Major menu
9-5
XDPE/400 commands and menus
Printing Documents with XDPE/400 (9/2001)
9-6
10.
10
Creating and modifying printer files
This chapter describes how to create and modify printer files. In the IBM
AS/400 environment, an application program refers to a printer file to
determine output characteristics. When the application runs, it creates a
spooled file whose attributes are built from the parameters of the
associated printer file.
You can change the specifications for the job before the application has
created the spool file either by modifying the printer file or by modifying
the spool file after it has been created. Though both methods are valid,
changing the printer file offers more flexibility than changing the spool file,
and is the recommended method for configuring your print job.
Creating Xerox printer files
Use the standard OS/400 Create Printer File (CRTPRTF) command to
create a printer file that specifies printing on a Xerox printer through
XDPE/400. To create a printer file, you must:
•
Understand the general spooling parameters that apply to Xerox
printers.
•
Set the value of the XDPE/400 Packet data (PACKETDATA) Monitor
Queue parameter to specify the command generation method.
•
Set the values for the parameters that control Xerox printing features
(if you specify the Indirect or Combined command generation
method).
Setting general spooling parameters
These printer file parameters determine how the system creates and
processes the spool file. When you create a Xerox printer file, consider
the following information before setting values for these parameters:
Spool the data (SPOOL)
Spooled output queue
(OUTQ)
Set SPOOL to *YES. Monitor Queue only processes spooled files.
Direct the spooled file to an output queue that is monitored by Monitor
Queue.
Spooled output schedule
(SCHEDULE)
Set SCHEDULE to *FILEEND or *JOBEND to determine when the spool
file is available to Monitor Queue.
Printer device type
(DEVTYPE)
Set DEVTYPE to *SCS (SNA Character Stream) to determine the format
of the output data included in the spool file for files you wish to have
processed by XDPE/400. *USERASCII can also be used if formatting by
XDPE/400 is not required (no printer control commands are generated).
Printing Documents with XDPE/400 (9/2001)
10-1
Creating and modifying printer files
Save spooled file (SAVE)
Set SAVE to *YES to return the spool file to the output queue after
processing and printing. This will require manual deletion of spool files on
a regular basis from the OS/400 output queue.
File separators (FILESEP)
You can set up Monitor Queue to generate the same number of separator
pages as specified in this parameter. Refer to chapter 18 for details.
Setting the Packet data (PACKETDATA) parameter
The Packet data (PACKETDATA) Monitor Queue parameter specifies
which spool file attribute(s) the Monitor Queue will use to find processing
information for that job. For all spooled files on a particular output queue,
Monitor Queue examines the appropriate spool file attribute(s) to
determine how to generate Xerox printer control information. For
example, if you specify *FORMTYPE for the PACKETDATA parameter,
the Monitor Queue will look in the Form type (FORMTYPE) spool file
attribute for the name of a packet to be processed with that spool file.
Refer to chapter 18 for more information on the PACKETDATA Monitor
Queue parameter.
In addition to identifying the name of a packet in the specified spool file
attribute, you can also specify an XDPE/400 control character. This
XDPE/400 control character, in conjunction with the Always generate
(ALWAYS) Monitor Queue parameter, determines the command
generation method to be used for the job. The control characters are
defined in the global values.
Table 10-1 shows the relationship between the contents of the ALWAYS
parameter and the spool file attribute indicated by the PACKETDATA
parameter. The XDPE/400 control character defaults of # and + are used.
Table 10-1.
Command generation methods
Spool file attribute value
ALWAYS value
XDPE
#packet-name
+packet-name
packet-name
blank
*NONE
Indirect
Direct
Combined
None
None
*INDIRECT
Indirect
Combined
Combined
Indirect
Indirect
*DIRECT
Indirect
Direct
Combined
Direct
None
*COMBINED
Indirect
Combined
Combined
Combined
Indirect
NOTE: If the spool file attribute field referenced by PACKETDATA is
blank, no packet will be used to process the job.
For VIPP processing, refer to the VIPP special packet data
(SPECPACK) parameter on the Work with Global Values
(UPDTGLOBAL) screen in chapter 6.
See table 10-1 for the command generation method that will be used.
Printing Documents with XDPE/400 (9/2001)
10-2
Creating and modifying printer files
For example, you can specify #JOB1 for the USRDTA spool file attribute
to indicate that Monitor Queue does the following:
•
Uses the Direct command generation method.
•
Retrieves the packet of Xerox printer control commands called JOB1
from the XDPE/400 folder.
In this example, you must create JOB1 in the appropriate XDPEFLR
subfolder before Monitor Queue can process any spool files created from
this printer file.
Note that even if you specify *NONE or *INDIRECT command generation
methods for the ALWAYS Monitor Queue parameter, XDPE/400 will still
look in the spool file attribute. For example, if the ALWAYS value is
*NONE and the packet name #packet01 is specified in the spool file
attribute named in the PACKETDATA parameter, the Monitor Queue will
switch to the Direct command generation method for that job.
The Always generate (ALWAYS) Monitor Queue parameter provides
some additional flexibility:
•
If ALWAYS is *DIRECT or *COMBINED when the Monitor Queue
session starts, Monitor Queue considers any text in the
PACKETDATA parameter as a packet name. The pound sign (#) or
plus sign (+) in front of the packet name is optional and specifies the
Direct or Combined command generation method, provided that the
Monitor Queue is started appropriately.
•
If ALWAYS is *INDIRECT when the Monitor Queue session starts,
Monitor Queue always translates spool file attributes into Xerox
printer control commands in addition to using the method specified
in the PACKETDATA parameter. You can leave the PACKETDATA
parameter blank and let Monitor Queue specify the Indirect
command generation method, provided that the Monitor Queue is
started appropriately.
Default packet processing
For DJDE, XES, and PCL jobs, XDPE/400 default processing provides a
function that is useful when either:
•
•
you want to use a default packet
a resource to be used with a job is not found
The Pass through option (PASSTHRU) Monitor Queue parameter can be
used to control default packet processing. When *NOPRINT is selected,
and the requested packet is not found, an error message will be issued
and the spool file will be put on hold without printing the job.
When *PRINT is selected, and the selected resource is not found,
XDPE/400 will look for a packet named DEFAULT in the appropriate
subfolder. If that packet is found, the job will be printed using that packet.
If the packet is not found, the Default packet option (DFTPKT) Monitor
Queue parameter specifies the next action to take.
In addition to the default packet processing described above for the Pass
through option, XDPE/400 provides this additional option: when
*FORMTYPE is selected for the Packet data Monitor Queue parameter,
and *STD is specified for the Form type spool file attribute, XDPE/400 will
process the job using the DEFAULT packet.
For information on VIPP processing, refer to the VIPP special packet data
(SPECPACK) parameter on the Work with Global Values (UPDTGLOBAL)
screen in chapter 6.
Printing Documents with XDPE/400 (9/2001)
10-3
Creating and modifying printer files
Setting Xerox printing features (Indirect method)
If you choose the Indirect command generation method, you can use the
various printer file parameters to specify the Xerox printing features you
want to use.
The spool file attributes that the Monitor Queue translates into Xerox
printer control commands differ depending on the mode of your Xerox
printer. These attributes and how Monitor Queue interprets them are
listed in chapter 11, “Modifying spool files.” Depending on your printer,
refer to the DJDE, XES, PCL, or VIPP command generation chapter for
the values you need to set in various printer file parameters to obtain the
results you want.
Examples of creating Xerox printer files
The following examples show how you can use various printer file
parameters to specify Xerox printing features.
Example 1
You are developing a new application to use a 2-up portrait format on a
Xerox printer. You have specified *FORMTYPE for the Packet data
(PACKETDATA) Monitor Queue parameter.
You must create a new printer file for the application program to use to
create its output. Use the parameter values shown in the following table.
All other parameters are appropriate for Xerox printing.
Printer file parameter
Value
Degree of page rotation (PAGRTT)
0
Pages per side (MULTIUP)
2
Form type (FORMTYPE)
XDPE
When you run the application program, Monitor Queue automatically
generates the necessary DJDEs or retrieves the necessary XES or PCL
multiple-up ASCII packets for insertion into the print stream. Then
XDPE/400 prints the document.
Printing Documents with XDPE/400 (9/2001)
10-4
Creating and modifying printer files
Example 2
You are developing a new application to use a 1-up portrait page format
with 80 lines rather than the number of lines specified in the default global
value PDE for 1-up portrait printing. You also want to use a specially
developed electronic form on each page of the output. You have specified
*USRDTA for the Packet data (PACKETDATA) Monitor Queue parameter.
Perform these steps:
Step 1.
Develop a PDE on your Xerox XPPM printer specifying the font and
number of lines per inch you want. Assign a numeric name to the PDE:
808080 (indicating 80 lines per page).
Step 2.
Create the form on the Xerox printer and call it FRMT80.
Step 3.
Create a printer file with the parameter values shown in this table.
Printer file parameter
Value
Font identifier (FONT)
808080
Front side overlay (FRONTOVL)
FRMT80
User data (USRDTA)
XDPE
Monitor Queue automatically generates the commands to activate the
necessary PDE and call the correct form.
You can also create a packet of Xerox printer control commands to
specify the electronic form and associated page format. You can then
enter the name of the packet in the USRDTA parameter. Refer to
“Examples of creating DJDE packets” in chapter 12 for an example of
using this method.
Printing Documents with XDPE/400 (9/2001)
10-5
Creating and modifying printer files
Managing Xerox printer files
You can use the Xerox printer file commands to access the printer file
parameters used by XDPE/400. Use these commands to modify printer
files:
•
•
CHGXPRTF (Change Xerox Printer File)
OVRXPRTF (Override Xerox Printer File)
These commands are similar to the OS/400 CHGPRTF and OVRPRTF
commands, except that they focus on the parameters used by XDPE/400.
They are not intended to replace the IBM commands for printer file
manipulation, but are only available to make it easier for you to access the
printer file parameters processed by XDPE/400. These commands affect
a subset of the printer file parameters. If you want to change printer file
parameters that are not listed in the following section, use the OS/400
CRTPRTF, CHGPRTF, or OVRPRTF commands.
Depending on the intended printer, see the DJDE, XES, PCL, or VIPP
command generation chapter for the effect of these parameters on
Indirect processing.
Changing Xerox printer files
Use the Change Xerox Printer File (CHGXPRTF) command to change
printer files. This command focuses on the parameters processed by
XDPE/400. You can modify these parameters with the CHGXPRTF
command (the corresponding keywords are shown in parentheses):
•
•
•
•
•
•
•
•
•
•
•
•
•
Printer file name (FILE)
Page orientation (ORIENT)
Pages per side (MULTIUP)
Number of copies to print (COPIES)
Print on both sides of sheet (DUPLEX)
Electronic form name (FORMS)
SPECIAL back form name (BFORM)
Pre-drilled paper (DRILLED)
Source drawer (DRAWER)
Type of printer control insert (METHOD)
Packet data (PACKETDATA)
Printer control packet name (DJDE)
DJDE packet termination mode (TERM)
Printing Documents with XDPE/400 (9/2001)
10-6
Creating and modifying printer files
Follow these steps to change a Xerox printer file:
Step 1.
Enter CHGXPRTF and press ENTER or F4. The Change Xerox Printer
File menu displays.
Change Xerox Printer File (CHGXPRTF)
Type choices, press Enter.
Printer file name . . . . .
Library name . . . . . .
*LIBL
Name
Name, *LIBL, *CURLIB...
Bottom
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
F12=Cancel
Printing Documents with XDPE/400 (9/2001)
F13=How to use this display
10-7
Creating and modifying printer files
Step 2.
Enter the name of the printer file you want to modify and the name of the
library in which the printer file resides, and press ENTER. The Change
Xerox Printer File menu displays additional parameters.
Change Xerox Printer File (CHGXPRTF)
Type choices, press Enter.
Printer file name . . . . . .
Library name . . . . . . .
*LIBL
Page orientation . . . . . . *SAME
Pages per side . . . . . . . *SAME
Number of copies to print . .
Print on both sides of sheet
*SAME
Electronic form name. . . . . *SAME
SPECIAL back form name. . . . *SAME
Pre-drilled paper . . . . . . *SAME
Source drawer . . . . . . . . *SAME
Type of printer control insert *INDIRECT
Packet data . . . . . . . . . *USRDTA
Printer control packet name . .*NONE
DJDE termination mode . . . . *END
Name
Name, *LIBL, *CURLIB...
*LAND, *PORT, *ILAND...
*Same, 1, 2, 4
1-255
*YES, *NO, *TUMBLE, *SAME
*SAME, *NONE, FRM id
FRM id, *SAME
*YES, *NO, *SAME, *NONE
1, 2, 3, 4, 5, 6, *E1, *SAME
*INDIRECT, *DIRECT, *COMBINED
*USRDTA, *FORMTYPE
Name, F4 for list
*SAME, *END, *NOEND
Bottom
F3=Exit F4=Prompt
F24=More keys
Step 3.
F5=Refresh
F12=Cancel
F13=How to use this display
Modify the parameters you want, following the conventions described in
the next section, and press ENTER.
NOTE: Press F9 to display the Printer control packet name and DJDE
termination mode parameters.
Printing Documents with XDPE/400 (9/2001)
10-8
Creating and modifying printer files
Printer file parameters
Printer file name (FILE)
Library name
Page orientation (ORIENT)
Modifies a specified printer file.
Specifies the name of the library in which the printer file resides. You can
use these values:
•
Name — Predefined library name
•
*LIBL — Uses the library list to locate the printer file
•
*CURLIB — Uses the current library for the job to locate the printer
file
•
*USRLIBL — Uses only the libraries listed in the user portion of the
library to locate the printer file
•
*ALL — Searches all libraries of the system
•
*ALLUSR — Searches all nonsystem libraries
Specifies the orientation in which to print the job. You can use these
values:
•
•
•
•
•
*LAND — Specifies landscape orientation
*PORT — Specifies portrait orientation
*ILAND — Specifies inverse landscape orientation
*IPORT — Specifies inverse portrait orientation
*SAME — Leaves the value unchanged
Depending on the printer mode, this parameter has the following effect:
Pages per side (MULTIUP)
•
In DJDE mode, this parameter assigns a default page orientation
value. This value specifies one of the two lists of XDPE/400 global
page descriptor entries (PDEs or JDEs).
•
In XES or PCL modes, the name of the PDE or JDE on the printer
can be generated from the page rotation, number of pages for each
side, and the page width. Refer to chapter 25 for more information
on this option.
•
In VIPP mode, this parameter only changes the orientation; it has no
effect on multi-up printing. Refer to chapter 25 for information
regarding orientation in VIPP mode.
Specifies the number of logical pages to print on a single side of a sheet
of paper. You can use these values:
•
•
•
•
1 — Prints one logical page on each physical page
2 — Prints two logical pages on each physical page
4 — Prints four logical pages on each physical page
*SAME — Leaves the value unchanged
For XPPM mode, two sets of PDEs are provided to support this feature.
The names of these PDEs are in the default list in the WRKGLBVAL
command. The name of the PDE or JDE on the printer can be generated
from the page rotation, number of pages for each side, and the page width
(as in the XES and PCL modes). Refer to chapter 25 for more information
on this option.
Number of copies to print
(COPIES)
Specifies the number of copies to print. You can use these values:
•
•
1 to 255 — Prints from 1 to 255 copies
*SAME — Leaves the value unchanged
Printing Documents with XDPE/400 (9/2001)
10-9
Creating and modifying printer files
Print on both sides of sheet
(DUPLEX)
Prints on both sides (duplex) of a sheet of paper or prints on one side
(simplex) of a sheet of paper. You can use these values:
•
*YES — Prints duplex
•
*NO — Prints simplex
•
*TUMBLE or *YES — Prints duplex in DJDE mode
•
*TUMBLE — Prints tumble duplex in XES, PCL, and VIPP modes
•
*SAME — Leaves the value unchanged
NOTE: For this parameter to be in effect for an NPS printer running
NPS version 1.6 or higher in PCL mode, or any version of NPS in
VIPP mode, duplex printing must be enabled using either the remote
output queue or the Virtual Printer on the NPS controller. If you are
unable to print in duplex, refer to chapter 26 for instructions on how
to correct the problem.
Electronic form name
(FORMS)
Prints a specified form on every page. You can specify from one to six
characters for the form name. You can use these values:
•
•
•
SPECIAL back form name
(BFORM)
*SAME — Leaves the value unchanged
*NONE — No form is used
form-id — Identifies the electronic form to be printed
Identifies a back form name. You can use these values:
•
form-id — Identifies the form to be printed on the reverse side of a
duplex page
•
*SAME — Leaves the value unchanged
•
*NONE — Does not use any form
Depending on the printer mode, XDPE/400 uses this parameter in the
following manner:
•
In DJDE mode, this parameter specifies the name of a form to print
on the reverse side of duplex pages. If DUPLEX is *NO, this
parameter is ignored. You can specify a one-to-six characters form
name.
NOTE: Depending on the XDPE/400 global value, variable data
cannot be merged with this form. If DUPLEX is *YES, BFORM
converts a simplex application into a duplex application, where
the reverse side of a sheet is a fixed form.
Printing Documents with XDPE/400 (9/2001)
10-10
Creating and modifying printer files
If the XDPE/400 global value indicates to use a traditional FORM
DJDE option, variable data is merged with the form regardless of the
DUPLEX parameter.
•
In XES or PCL mode, this parameter specifies the name of the back
side form. You can specify a one- to eight-character form name.
•
In VIPP mode, this parameter specifies the name of the constant
back form on which to print on the reverse side of duplex pages. If
DUPLEX is *NO, the constant form is printed on a separate simplex
page in between each simplex page with variable data. You can
specify a one- to eight-character form name.
Refer to the Xerox Variable Data Intelligent PostScript PrintWare
(VIPP) Reference Manual for information about the SETBFORM
parameter and its relationship to other parameters.
NOTE: The form must reside on the printer controller before it
can be used by the printer. Refer to chapter 21 for information
about how to download a VIPP form to the printer controller.
Pre-drilled paper (DRILLED)
Instructs the printer to use the Page Shift value for predrilled paper. You
can use these values:
•
*YES — Enables special paper handling
•
*NO — Disables special paper handling
•
*NONE — Specifies that a command is not generated for the Page
Shift value
•
*SAME — Leaves the value unchanged
The Page Shift value is specified to the Xerox printer through the
Predrilled shift support (SHIFT) global value.
Source drawer (DRAWER)
Specifies the source drawer from which paper feeds to the Xerox printer.
NOTE: This parameter has no effect on NPS, DocuSP, and generic
printers in PCL or VIPP mode. NPS and DocuSP printers perform
automatic tray selection based on the page size or media type. For
information about how to specify source drawers in VIPP mode, refer
to chapter 17.
The XDPE/400 global values area contains the mapping of these IBM
values to Xerox paper trays. You can use these values:
•
•
•
•
•
•
•
•
1 — XDPE/400 global value for source drawer 1
2 — XDPE/400 global value for source drawer 2
3 — XDPE/400 global value for source drawer 3
4 — XDPE/400 global value for source drawer 4
5 — XDPE/400 global value for source drawer 5
6 — XDPE/400 global value for source drawer 6
*E1 — XDPE/400 global value for envelope source drawer
*SAME — Leaves the value unchanged
Printing Documents with XDPE/400 (9/2001)
10-11
Creating and modifying printer files
Type of printer control insert
(METHOD)
Packet data (PACKETDATA)
Printer control packet name
(DJDE)
Specifies the type of printer control packet generation method to use.
Based on this parameter, XDPE/400 will insert either XDPE or a control
character (# or +) in the field specified by the PACKETDATA parameter in
the printer file. The Monitor Queue uses the PACKETDATA value to
determine the method of command generation. You can use these values:
•
*INDIRECT — Causes the job to be printed using the Indirect
command generation method
•
*DIRECT — Causes the job to be printed using the Direct command
generation method
•
*COMBINED — Causes the job to be printed using the Combined
command generation method
Specifies the spool file attribute where XDPE/400 inserts the DJDE, XES,
or PCL packet or VIPP JDT name and processing information. You can
use these values:
•
*USRDTA — Uses the User data (USRDTA) spool file attribute
•
*FORMTYPE — Uses the Form type (FORMTYPE) spool file
attribute
Specifies the name of a printer control packet or JDT to use. The packet
or JDT name is used only with the Direct or Combined methods. You can
use these values:
•
name — Specifies the packet or JDT name.
—
For DJDE mode, the name can be a one- to six-character packet
name.
—
For XES, PCL, and VIPP modes, the name can be a one- to
eight-character packet or JDT name.
Do not precede the name with any XDPE/400 special character. If you
do, the job will not run. Special characters are used when specifying
packet and JDT names using IBM printer file commands.
•
F4 (for current list) — Provides a list of existing DJDE packets when
you press F4. The F4 list is valid only for DJDE packets.
•
*NONE — Specifies that no packet or JDT is used.
The printer control packet or JDT can be found in the following location:
Printer mode
Packet or JDT folder location
DJDE
XDPEFLR/DJDE
XES
XDPEFLR/XES
PCL
XDPEFLR/PCL
VIPP
XDPEFLR/JDTLIB
NOTE: For VIPP mode, the JDT must reside on the printer controller
in order to be used by the printer. Refer to chapter 21 for information
about how to download a VIPP JDT to the printer controller.
Printing Documents with XDPE/400 (9/2001)
10-12
Creating and modifying printer files
DJDE termination mode
(TERM)
Specifies whether the DJDE packets created by XDPE/400 are terminated
by an END. You can use this parameter with the Indirect, Direct, and
Combined methods for DJDE data streams only. You can use these
values:
•
*SAME — Leaves the value unchanged (default value).
•
*END — Terminates DJDE packets created by XDPE/400 by
inserting an “END” immediately after the packet.
If a user-supplied packet immediately follows the XDPE/400 packet,
the user-supplied packet is not applied until the next page.
•
*NOEND — Does not insert an “END” string. Used if either the
application program or the interface box inserts a DJDE packet into
the print data stream immediately after the DJDE packet created by
XDPE/400.
Examples of changing Xerox printer files
These examples show how you can use the CHGXPRTF command after
you start the Monitor Queue session with the default start-up parameters.
Refer to chapter 18 for examples of starting Monitor Queue sessions.
Example 1
This example shows how to change a printer file after replacing an
existing production 5225 printer with a new Xerox 4850.
Direct one of the output queues previously directed to the 5225 printer to
the 4850 printer. The existing output queue prints accounting reports on
standard green bar paper. The printer file that creates these spool files is
called ACCTRPTS. You must modify the printer file to print the reports on
the 4850 printer in landscape format with an electronic green bar form.
This form is stored on the printer and is called GRNBAR.
Enter CHGXPRTF (Change Xerox Printer File) and make these entries:
Printer file nameACCTRPTS
Page orientation*LAND
Electronic form nameGRNBAR
Monitor Queue automatically generates the necessary DJDEs based on
the resulting spool file attributes, which allows the reports to print on the
4850 printer.
Example 2
You are moving an existing 5219 application to a new Xerox 4235 printer
(in XDPM mode). You want to print duplex using predrilled, three-hole
paper. The existing printer file is called TRDOC.
Enter CHGXPRTF (Change Xerox Printer File) and make these entries:
Printer file nameTRDOC
Print on both sides of sheet*YES
Pre-drilled paper*YES
Monitor Queue automatically generates the necessary XES commands
based on the resulting spool file attributes, and the system prints the
reports on the 4235 printer.
Printing Documents with XDPE/400 (9/2001)
10-13
Creating and modifying printer files
Overriding Xerox printer files
Use the Override Xerox Printer File (OVRXPRTF) command to
temporarily override the printer file parameters of a printer file at the
session or job level.
OVRXPRTF allows you to modify the same set of printer file parameters
as the CHGXPRTF command with one consideration. If you enter a value
for any one of these parameters, you must enter a value for them all:
•
•
•
Type of printer control insertion (METHOD)
Packet data (PACKETDATA)
Printer control packet name (DJDE)
For a list of the parameters, the procedure, and the menus displayed, see
“Changing Xerox printer files” earlier in this chapter.
Examples of overriding Xerox printer files
These examples show how you can use the OVRXPRTF command after
you start the Monitor Queue session with the default start-up parameters.
Refer to chapter 18 for examples of starting Monitor Queue sessions.
Example 1
A series of DJDE packets were developed to format the output from a
particular application in different ways. Refer to chapter 12 for information
about creating DJDE packets.
Before you run the job, specify that the system should use the RJOB2
packet to format and print the job. Call the printer file RSAM2, and specify
*FORMTYPE for the Packet data (PACKETDATA) Monitor Queue
parameter.
Enter OVRXPRTF (Override Xerox Printer File) and make these entries:
Printer file nameRSAM2
Type of printer control insertion*DIRECT
Packet data*FORMTYPE
Printer control packet nameRJOB2
You must change the Monitor Queue start-up parameter that specifies the
packet data field to *FORMTYPE.
The Monitor Queue includes the DJDEs from the RJOB2 packet with your
spool file and the system prints your output.
Printing Documents with XDPE/400 (9/2001)
10-14
Creating and modifying printer files
Example 2
You need five copies of the output. The application is using the OUT65
printer file. Enter this command at an OS/400 command prompt and run
the job as usual:
OVRXPRTF
FILE(OUT65)
COPIES(5)
The system produces five copies on the Xerox printer.
Example 3
This example verifies the results of a particular packet of XES commands.
The printer file is called STNDRD, and the XES packet is called CUST2.
Enter this command at an OS/400 command prompt and run the job as
usual:
OVRXPRTF
FILE(STNDRD)
METHOD(*DIRECT)
DJDE(CUST2)
If the packet does not yield the expected results, make changes to the
packet, reenter the OVRXPRTF command, and run the job again.
Printing Documents with XDPE/400 (9/2001)
10-15
Creating and modifying printer files
Printing Documents with XDPE/400 (9/2001)
10-16
11.
11
Modifying spool files
This chapter describes how to modify the OS/400 spool file attributes. You
can modify the Xerox printing features to print a job by changing the
attributes of a spool file. You can use the standard OS/400 Change
Spooled File Attributes (CHGSPLFA) command or option 2 (Change) on
the Work with All Spooled Files menu.
Xerox recommends that you change your job at the printer file level rather
than the spool file level if you know this information:
•
How you want to format or enhance your output before running your
application program
•
The name and library of the printer file used by your application to
generate the spool file
Refer to chapter 10 for more information on “Creating and modifying
printer files.”
Changing the command generation method
The Packet data (PACKETDATA) Monitor Queue parameter determines
which spool file attribute will be used to determine the command
generation method. Refer to chapter 18 for more information.
If you need to change the method of printer control generation specified
in the spool file, you must change the spool file attribute indicated by the
PACKETDATA parameter. Refer to table 10-1 in chapter 10 for the
possible values for the PACKETDATA parameter in your spool file and
how Monitor Queue interprets them.
Changing formatting and job processing attributes
This section describes the spool file attributes that you can change at print
time. The Monitor Queue translates them into Xerox printer control
commands if you are using the Indirect or Combined method of printer
control generation. The attributes are listed in the same order as they are
displayed on the standard OS/400 Change Spooled File Attributes menu.
Align page (ALIGN)
Determines whether to add an END statement to the DJDEs sent to the
printer with this job. You only need to specify this attribute if the
application program or the interface box is generating DJDEs in addition
to the ones the Monitor Queue generates.
This spool file attribute is used for XPPM (DJDE) processing only. Refer
to chapter 12 for more information. You can use these values:
•
•
•
*SAME — Leaves the value unchanged
*NO — An END statement is added to the job
*YES — No END statement is added to the job
Printing Documents with XDPE/400 (9/2001)
11-1
Modifying spool files
Back side overlay
(BACKOVL)
Generates the appropriate printer control command to use a different form
on the back side of duplex pages. You can use these values:
•
name — Specifies a form to be printed on the back of duplex pages.
The name must follow these conventions:
—
In DJDE mode, the form name must contain six characters
followed by an optional .X extension. For example, TAXFRM.X
yields a printer control command to merge data with form
TAXFRM on the printer, while TAX02.X and MKTVALX23 are not
valid form name specifications and a Xerox printer control
command is not generated.
You can use a special form name of NONE.X to clear a previously
established form name.
—
In XES, PCL, or VIPP mode, the form name can contain from
one to eight characters.
•
*NONE — Does not print a form on the back of duplex pages. A
value of *NONE does not generate a Xerox control command.
•
*SAME — Leaves the value unchanged.
Depending on the printer mode, XDPE/400 uses this parameter in the
following manner:
•
In DJDE mode, this parameter specifies the name of a form to print
on the reverse side of duplex pages. Variable data is not merged
with this form.
•
In XES or PCL mode, this parameter specifies the name of the back
side form. This back side form can contain variable data.
•
In VIPP mode, this parameter specifies the name of the constant
back form on which to print on the reverse side of duplex pages. If
DUPLEX is *NO, the constant form is printed on a separate simplex
page in between each simplex page with variable data.
Refer to the Xerox Variable Data Intelligent PostScript PrintWare
(VIPP) Reference Manual for information about the SETBFORM
parameter and its relationship to other parameters.
NOTE: The form must reside on the printer controller before it
can be used by the printer. Refer to chapter 21 for information
about how to download a VIPP form to the printer controller.
Printing Documents with XDPE/400 (9/2001)
11-2
Modifying spool files
Character identifier (CHRID)
Specifies the graphic character set and code page for the printer file.
CHRID allows you to print text that has different character identifier
codes.
NOTE: If you change the OS/400 System value QCHRID to use
euro-capable values, or if your application includes a job description
with a euro-capable CHRID, you do not need to change this
parameter if it is currently set to *SYSVAL or *JOBCCSID. See “Using
euro fonts with your PCL print jobs” in chapter 15 for more information
on using the System value to specify a euro code page and character
set.
You can use these values:
Copies (COPIES)
•
*DEVD — Uses the default value that the device is designed to
handle. This is the default value for CHRID.
•
*SYSVAL — Uses the value specified for the system running the
application.
•
*JOBCCSID — Uses the value taken from the coded character set
identifier (CCSID) of the job.
•
graphic-character-set code page — Specify the character set and
code page values that match those specified for the printer. Values
range from 1 through 32767. If you are using the euro currency
symbol, you must specify 695 for the character set and a code page
value that contains the euro currency symbol. See “Using euro fonts
with your PCL print jobs” in chapter 15 for a list of euro code page
values.
Generates the appropriate printer control command to print the number of
copies of your document. You can use these values:
•
•
File separators (FILESEP)
Creates a number of banner pages specified in this field. Refer to chapter
18 for more information about this field. You can use these values:
•
•
Form feed (FORMFEED)
1-255 — Prints from 1 to 255 copies
*SAME — Leaves the value unchanged
0-9 — Number of file separator pages to be generated
*SAME — Leaves the value unchanged
Generates a printer command to specify that the printer must use a page
shift value for predrilled paper. You can use these values:
•
•
•
*SAME — Leaves the value unchanged
*DEVD — Does not issue a shift command
*CONT — Does not issue a shift command
All other values generate a printer command for page shifting using the
value that is specified through the Predrilled shift support (SHIFT) global
value.
Printing Documents with XDPE/400 (9/2001)
11-3
Modifying spool files
Front side overlay
(FRONTOVL)
Generates the appropriate printer control command to merge an
electronic form stored on the printer with each page of data. You can use
these values:
•
name — Specifies the name of a front form to be printed with this
job. The name must follow these conventions:
—
In DJDE mode, the form name must contain six characters
followed by an optional .X extension. For example, TAXFRM.X
yields a printer control command to merge data with form
TAXFRM on the printer, while TAX02.X and MKTVALX23 are not
valid form name specifications and a Xerox printer control
command is not generated.
You can use a special form name of NONE.X to clear a previously
established form name.
—
In XES, PCL, or VIPP mode, the form name can contain from
one to eight characters.
NOTE: In VIPP mode, the form must reside on the printer
controller before it can be used by the printer. Refer to
chapter 21 for information about how to download a VIPP
form to the printer controller.
Job name (JOB)
Lines per inch (LPI)
Output priority (OUTPTY)
•
*NONE — Does not print a front form for this job. A value of *NONE
does not generate a Xerox control command.
•
*SAME — Leaves the value unchanged.
Creates a string from the job name, user, and job number attributes and
generates an XES command specifying the string as the printer job name.
This spool file attribute is used for XDPM (XES) processing only.
Specifies the line spacing setting on the printer, in lines per inch. This
spool file attribute is used for PCL processing only. You can use values
3, 4, 6 (default), 7.5, 8, 9, and 12.
Generates an XES command specifying the priority of this job:
Attribute valuePrinter job priority
1HIGH
8LOW
9HOLD
all other valuesNORMAL
This spool file attribute is used for XDPM (XES) processing only. You can
use these values:
•
•
•
1-9 — Specifies the priority of the spool file for processing
*SAME — Leaves the value unchanged
*JOB — Uses priority of the job that created the spool file
Printing Documents with XDPE/400 (9/2001)
11-4
Modifying spool files
Pages per side (MULTIUP)
Generates a printer command to activate the appropriate page formatting
instructions on the Xerox printer for 1-up, 2-up, 3-up (VIPP mode only), or
4-up printing. You can use these values:
•
*SAME — Leaves the value unchanged
•
1 — Prints one logical page on each physical page
•
2 — Prints two logical pages on each physical page
•
3 — (VIPP mode only) Prints three logical pages on each physical
page
•
4 — Prints four logical pages on each physical page
Depending on the printer mode, the MULTIUP attribute is used in this
manner:
•
In DJDE, XES, or PCL mode, Monitor Queue uses the MULTIUP
attribute and the Degree of page rotation (PAGRTT) attribute to
determine the page layout. PAGRTT cannot be changed in the spool
file. It must be specified using the printer file. Refer to chapter 10 for
details.
•
In VIPP mode, Monitor Queue uses the MULTIUP attribute to
determine the page layout.
Refer to chapter 25 for more information on “Multi-up printing.”
Print on both sides
(DUPLEX)
Generates the appropriate printer control command for duplex printing.
You can use these values:
•
•
•
*SAME — Leaves the value unchanged
*NO — Prints in simplex
*YES or *TUMBLE — Prints in duplex
Note these processing considerations:
•
For an XPPM printer, a spool file attribute value of *TUMBLE results
in a DUPLEX=YES DJDE. This may or may not yield tumble duplex
printing. Refer to your printer reference manual for more information.
•
For this parameter to be in effect for an NPS printer running NPS
version 1.6 or higher in PCL mode, or any version of NPS in VIPP
mode, duplex printing must be enabled using either the remote
output queue or the Virtual Printer on the NPS controller. If you are
unable to print in duplex, refer to chapter 26 for instructions on how
to correct the problem.
Examples of changing spool file attributes
This section provides examples demonstrating why you might change
spool file attributes before Monitor Queue processes the file.
Printing Documents with XDPE/400 (9/2001)
11-5
Modifying spool files
Example 1
In this example, an existing application is set to create a single copy of a
report. However, today (and today only) you need five copies of the
document. The application was run, and the spool file is held in an output
queue that Monitor Queue is monitoring. Monitor Queue was set up to
always generate printer control commands from spool file attributes.
Use the OS/400 CHGSPLFA command to change the COPIES spool file
attribute to 5 and release the spool file.
The system prints five copies of the document. Since the Xerox printer
generates the additional copies, you save the time required to transmit the
document five times. This method works for Xerox printers that have hard
disks.
Example 2
In this example, a Monitor Queue session was started to send documents
from an output queue to a Xerox 4235 printer in XDPM mode. You
urgently need a document in the queue.
In addition, the packet data field Monitor Queue is using is the User data
(USRDTA) attribute. The USRDTA attribute value of the document you
need is +JOB2 (Combined method with a packet JOB2), but Monitor
Queue was set up so that spool file attributes override any commands
included in user-defined packets.
Use the OS/400 CHGSPLFA command to change the Output priority
(OUTPTY) attribute of the needed spool file from 5 to 1.
When the job arrives at the printer, the job queue management software
on the Xerox 4235 prints this job ahead of any other jobs with lower job
priority that are already at the printer.
Example 3
In this example, several different packets of Xerox printer control
commands have been developed to format the output of a new
application. The application program has been set up to allow users to
specify Xerox printing characteristics using the Override Xerox Printer
File (OVRXPRTF) command.
When you run the application, specify the following:
•
Form type (FORMTYPE) as the packet data field (this is the
agreed-upon standard at your site)
•
The *DIRECT method of printer control generation
•
A packet name of RPT1
Since this is the wrong packet name for this job, you must correct the
error. Use standard OS/400 procedures to change the value of the Form
type (FORMTYPE) attribute of your spool file from #RPT1 to #RPT2.
Printing Documents with XDPE/400 (9/2001)
11-6
12.
12
DJDE command generation
This chapter describes how to create and insert dynamic job descriptor
entry (DJDE) control commands into the print data stream.
•
Sets of instructions describing how to process incoming data are
stored on the printer disks and are activated for specific jobs. These
instructions are organized as follows:
•
A Job Description Entry (JDE) describes how to process and print a
job. For example, a JDE may include an instruction to merge an
electronic form with the incoming data.
•
A Job Description Library (JDL) contains a library of JDEs and
provides default instructions to use if the JDE does not specify a
different instruction. For example, the JDL may specify a Page
Description Entry (PDE) to use to format the data if the JDE does not
specify one.
•
A Page Description Entry (PDE) specifies particular fonts and a page
layout to use. For example, instructions in a PDE may indicate the
number of logical pages to print on a physical page and where to
begin each logical page.
When you start an XPPM printer, the system activates a particular JDL.
DJDEs accompanying your print job can:
•
Change the JDE, JDL, or PDE used to print the job
•
Override specific instructions, such as increase the number of
copies to print
If you want to dynamically change the JDE, JDL, or PDE used to print your
job, you need to create a packet of DJDEs that includes the appropriate
command.
The XDPE/400 base software includes these DJDE resources to help you
configure and execute jobs to your DJDE printer:
•
Copies of sample JDL and JSL that can be used with XDPE/400 are
included in the JDL and JSL resource subfolders. They are named
XDPE.JDL and XDPE.JSL.
•
Landscape and portrait 1-, 2-, and 4-up PDEs are also supplied. See
“Indirect method” in this chapter for more information about the
PDEs supplied with XDPE/400.
Printing Documents with XDPE/400 (9/2001)
12-1
DJDE command generation
Using DJDE control commands
You can create commands for your job using one of these methods:
None
You can use the Always generate (ALWAYS) Monitor Queue parameter
to print a job without inserting any DJDE control commands that affect
document formatting.
Indirect method
In the Indirect method, Monitor Queue maps spool file attributes to DJDE
parameters and creates DJDE packets from these parameters. The
packets are then inserted into the print data stream.
You can use the Monitor Queue pass through option to print a job without
inserting a DJDE packet.
Direct and Combined
methods
In the Direct and Combined methods, you create a file of DJDE text.
Monitor Queue inserts this DJDE packet into the data stream before the
spool file is released to the printer writer.
Printing Documents with XDPE/400 (9/2001)
12-2
DJDE command generation
Indirect method
The Indirect method creates DJDE commands from spool file attributes.
When an OS/400 application program or print utility opens a printer file for
output, a spool file is created. The attributes of that spool file are created
from the printer file parameters.
Before the spool file is released to the printer writer, XDPE/400 processes
the spool file and creates DJDE commands.
When creating or changing your print job, it is better to configure it at the
printer file level instead of at the spool file level.
Table 12-1 shows the printer file parameters that map to the DJDE
commands.
Table 12-1.
Printer file parameters mapped to DJDE commands
IBM OS/400
printer file parameters
DJDE commands
created
FRONTMGN/BACKMGN
BEGIN=
ALIGN
END=
FORMFEED
SHIFT=
DRAWER
FEED=
FONT/PAGRTT/MULTIUP
FORMAT= or JDE= or PMODE=
DUPLEX
DUPLEX=
FRONTOVL
FORMS=
BACKOVL
BFORM= or FORMS=
COPIES
COPIES=
To prevent conflicts with the printer writer, which also processes spool file
attributes, the system converts several spool file attributes to their default
values. The spool file is then released to the printer writer. These
XDPE/400 spool default values are used:
•
•
•
•
•
COPIES=1
DUPLEX=*NO
FRONTOVL=*NONE
BACKOVL=*NONE
FORMTYPE=*STD
Printing Documents with XDPE/400 (9/2001)
12-3
DJDE command generation
Modifying printer file parameters
This section describes how to use the printer file parameters to define
DJDE commands.
You can modify the printer file parameters with any of these commands:
•
•
•
CRTPRTF to create a printer file
CHGPRTF to modify an existing printer file
OVRPRTF to override an existing printer file
For instructions on how to use the CRTPRTF, CHGPRTF, and OVRPRTF
commands, refer to OS/400 CL Reference and OS/400 Printer Device
Programming.
FRONTOVL
Specifies the electronic form to be used to print this job. If you want to use
a front overlay form, enter a six-character form name. XDPE/400
generates the FORM= parameter with the form name you specified. The
form must already exist on the printer. If you do not want a front overlay
form, enter *NONE.
If these conditions are true, a FORM DJDE using the contents of the front
overlay spool file attribute as the form name is inserted on the odd
numbered pages:
•
•
BACKOVL
The Front overlay global value include/exclude is *YES.
The front overlay field of the spool file attributes contains at least
one nonblank character that is a number or an alphabetic character.
Specifies the name of the electronic form to print on the reverse side of
each duplex page when printing this job. If you want to use a back overlay
form, enter a six-character form name. XDPE/400 generates the BFORM=
parameter with the form name you specified. The form must already exist
on the printer. If you do not want a back overlay form, enter *NONE.
If these conditions are true, a BFORM DJDE using the contents of the
Back overlay spool file attributes as the form name is inserted on the even
numbered pages.
DUPLEX
•
The Back overlay global value as BFORM is *NO.
•
The Back overlay global value include/exclude is *YES.
•
The back overlay field of the spool file attributes contains at least
one nonblank character that is a number or an alphabetic character.
Specifies whether to print the output on one side of the page (simplex) or
on both sides of the page (duplex). You can use these values:
•
*YES or *TUMBLE — XDPE/400 generates a DUPLEX=YES
parameter and prints in duplex
•
*NO — XDPE/400 generates a DUPLEX=NO parameter and prints in
simplex
Printing Documents with XDPE/400 (9/2001)
12-4
DJDE command generation
COPIES
Specifies the number of copies to print. To define COPIES, enter the
number of copies you want from 1 to 255 in the COPIES field.
NOTE: The Xerox printer can accept up to 32,767 copies, but the
AS/400 allows only a maximum value of 255.
XDPE/400 generates the COPIES DJDE with the specified number of
copies. If the value in the COPIES field is 1, the system does not generate
a COPIES DJDE.
FORMFEED
Specifies that the printer uses the page shift value for predrilled paper.
The page shift value is specified to the printer through the user interface.
Spool file attribute
DRAWER
*DEVD
No command generated
*CONT
No command generated
All others
Shift command with XDPE/400 global
values
Specifies the source drawer for paper that feeds into the printer. The
mapping of IBM values to Xerox paper trays is contained within the
XDPE/400 global values area. If you select a value other than those listed
here, the printer’s default drawer will be selected. You can use these
values:
•
•
•
•
•
•
ALIGN
DJDE command
*SAME — Does not change the global value
1 — Defines the XDPE/400 global value for drawer 1
2 — Defines the XDPE/400 global value for drawer 2
3 — Defines the XDPE/400 global value for drawer 3
4 — Defines the XDPE/400 global value for drawer 4
*E1 — Defines XDPE/400 global value for envelope drawer
Sets the DJDE packet termination mode. This specifies whether the
DJDEs created by XDPE/400 are terminated by an END; command. You
can use this parameter with the Indirect, Direct, and Combined methods.
If the Process banner page=*YES and the Data page source is not
*NONE, a DJDE is generated after the banner pages are generated. You
can use these values:
•
•
*NO — Creates a DJDE packet with END
*YES — Creates a DJDE packet with no END
Use the *NOEND option in CHGXPRTF or OVRXPRTF if either the
application program or the interface box inserts a DJDE packet into the
print data stream immediately after the DJDE packet created by
XDPE/400. If the *NOEND option is not selected, XDPE/400 inserts an
END into the data stream at the end of the DJDE packet created by
XDPE/400.
If a user-supplied packet immediately follows the XDPE/400 packet, the
user-supplied packet is not applied until the next page.
Printing Documents with XDPE/400 (9/2001)
12-5
DJDE command generation
FONT, PAGRTT, and
MULTIUP
FONT, PAGRTT, and MULTIUP specify which PDE to select from the list
of PDEs specified in the WRKGBLVAL command. This defines the
number of logical pages per physical page and the orientation of the page.
See “DJDE multi-up generation” in Chapter 25 for more information about
the PDEs supplied with XDPE/400.
FRONTMGN/BACKMGN
The BEGIN DJDE value is inserted into the print job stream on a
page-by-page basis if the Margins global value is *YES. If the Margins
global value is *NO, then the default printer setting is used.
If BEGIN DJDEs are inserted into the print data stream, a BEGIN DJDE,
using the Front margin values, is included on the odd numbered pages,
and a BEGIN DJDE, using the Back margin values, is included on the
even numbered pages.
A value of *DEVD (device default) for the FRONTMGN or BACKMGN
printer file parameter suppresses the creation of a BEGIN= DJDE for that
parameter.
Printing Documents with XDPE/400 (9/2001)
12-6
DJDE command generation
Direct method
When an OS/400 application program or print utility opens a printer file for
output, the system creates a spool file. The attributes of that spool file are
created from the printer file parameters. When the spool file is released
to the printer writer, these spool file attributes are converted to
printer-specific commands, either 5219 or 5225 printer types.
There is a separate printer writer for each device description in the
system. The printer writer knows the specific characteristics of the device
to which it is writing. Before the spool file is released to the printer writer,
XDPE/400 processes the DJDE text and creates a DJDE packet.
To prevent conflicts with the printer writer, which also processes spool file
attributes, the system converts six spool file attributes to their default
values before the spool file is released to the printer writer. These
XDPE/400 spool default values are used:
•
•
•
•
•
•
COPIES=1
DUPLEX=*NO
FRONTOVL=*NONE
BACKOVL=*NONE
PAGRTT=0
FORMTYPE=*STD
If the DJDE packet you are using to process your job contains values that
differ from the defaults, your job will print using the values from the
packet.
You can generate DJDE packets for use in the Direct method by using
either the DJDE menu-driven or text-based management tools. See
“Creating and managing DJDE packets” later in this chapter for more
information.
Default DJDE packet
XDPE/400 allows you to specify the action to take when the system does
not locate a DJDE packet. This is controlled using the Pass through option
(PASSTHRU) Monitor Queue parameter.
When specified, the DJDE packet called DEFAULT is invoked if the
requested packet is not found, or if *FORMTYPE is specified for the
Packet data (PACKETDATA) Monitor Queue parameter, and if the Form
type spool file attribute is *STD. You must create the default packet before
this feature can be used. If this packet is not found, the Default packet
option (DFTPKT) Monitor Queue parameter specifies the next action to
take.
For more information on default packet processing, see “Setting the
Packet data (PACKETDATA) parameter” in chapter 10.
Printing Documents with XDPE/400 (9/2001)
12-7
DJDE command generation
Combined method
This method combines the Direct and Indirect methods of DJDE text
generation. A DJDE packet is created using DJDE text from the
XDPEFLR/DJDE folder, then another DJDE packet is created from the
spool file attributes.
Application order of DJDE commands
You can use the Order of sequence (SEQUENCE) Monitor Queue
parameter to control the order in which the DJDE commands are created
from spool file attributes and DJDE packet parameters. This parameter
controls whether DJDE commands generated from spool file attributes
are inserted into the print data stream before or after the DJDE commands
retrieved from the DJDE packet. See your printer’s documentation for the
manner in which your printer implements those commands.
If sequence is set to *ATTRIB, the DJDEs that are generated from the
spool file attributes are inserted into the print data stream before the
DJDEs that are retrieved from the DJDE packet.
If sequence is set to *PACKET, DJDEs received from a DJDE packet are
inserted into the print data stream before the DJDEs generated from the
spool file attributes.
If page level DJDEs are created on the same page as top level DJDEs that
are created from logical processing tests, the page level commands are
inserted into the print data stream before the DJDE packet commands
from the logical processing test.
In DJDE jobs using the Combined method, the front and back overlay
forms specified in the spool file attributes are inserted after any specified
DJDE packet if these conditions are met:
•
You are running in *PAGE mode
•
You have specified *NO for the Back side overlay as BFORM
(DJDEBFR) global value
Printing Documents with XDPE/400 (9/2001)
12-8
DJDE command generation
Creating and managing DJDE packets
XDPE/400 provides several tools for creating and managing DJDE
packets. You can use either menu-driven DJDE packet management tools
or text-based management tools.
•
Menu-driven DJDE packet management:
—
—
•
Create DJDE packet (CRTDJDE) command
Change DJDE packet (CHGDJDE) command
Text-based management:
—
—
DJDE packet Text List utility (EDTDJDE)
OS/400 Source Entry Utility (SEU)
Packet name syntax
DJDE packet names must comply with these syntax rules:
•
•
•
•
The name can be from one to eight bytes long
The first byte of the name must be an alphabetic character
Bytes two through eight can be A-Z, 0-9, @, #, or $
Do not enclose the packet name within quotes or other characters
These are examples of valid DJDE packet names:
•
•
•
DJDETXT
AME@DJDE
NMDJDE12
NOTE: If you type lowercase letters, the name is saved in uppercase.
Using the Create DJDE packet menu
The Create DJDE packet (CRTDJDE) command allows you to generate
DJDE packets without having to know the entire DJDE command syntax.
This command creates some of the most commonly used DJDE
parameters.
Use the CRTDJDE command to create these DJDE options (the
corresponding keywords are shown in parentheses):
•
•
•
•
•
•
•
•
•
•
•
•
•
DJDE packet name (DJDE)
Printer job name (JDE)
Printer job library (JDL)
Number of copies to print (COPIES)
Print on both sides of sheet (DUPLEX)
Electronic form name (FORMS)
Page formatting setting (FORMAT)
Copy modification setting (MODIFY)
SPECIAL back form name (BFORM)
Distribution text (RTEXT)
Distribution form (RFORM)
Bin selection (FEED)
Text description (TEXT)
Printing Documents with XDPE/400 (9/2001)
12-9
DJDE command generation
For some DJDE creation parameters, you have the option of specifying
*NONE. This suppresses the creation of a DJDE for that option. This
option does not override the previously defined job description language
(JDL), or job descriptor entry (JDE) and DJDE options.
Packet creation procedure
Follow these steps to create a DJDE packet:
Step 1.
Enter CRTDJDE and press ENTER. The Create DJDE packet menu
displays.
Create DJDE packet (CRTDJDE)
Type choices, press Enter.
DJDE packet name . . . . . . . .
Name, F4 for list
Bottom
F3=Exit
F4=Prompt
F24=More keys
F5=Refresh
Printing Documents with XDPE/400 (9/2001)
F12=Cancel
F13=How to use this display
12-10
DJDE command generation
Step 2.
Enter the name of the DJDE packet and press ENTER. The Create DJDE
packet menu displays additional parameters.
Create DJDE packet (CRTDJDE)
Type choices, press Enter.
DJDE packet name . . . . . .
Printer job name . . . . . .
Printer job library . . . .
Number of copies to print .
Print on both sides of sheet
Electronic form name . . . .
Page formatting setting . .
Copy modification setting .
SPECIAL back form name . . .
Distribution text . . . . .
Distribution form . . . .
Bin selection . . . . . . .
Text ‘description’ . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
*NONE
*NONE
1
*NONE
*NONE
*NONE
*NONE
*NONE
*NONE
*NONE
*NONE
*BLANK
Name, F4 for list
JDE Name, *NONE
JDL id, *NONE
0-32767
*YES, *NO, *NONE
FRM id, *NONE
PDE id, *NONE
CME id, *NONE
FRM id, *NONE
RTEXT id, *NONE
FRM id, *NONE
MAIN, AUX, OPR, STK id...
Bottom
F3=Exit
F4=Prompt
F24=More keys
Step 3.
F5=Refresh
F12=Cancel
F13=How to use this display
Modify the parameters you want, following the conventions described in
the next section, and press ENTER.
Packet parameters
DJDE packet name (DJDE)
Specifies the name of the DJDE packet. The system stores the packet in
the XDPEFLR/DJDE folder. You can enter from one to eight characters.
Press F4 to display a list of existing DJDE packets.
Printer job name (JDE)
Specifies the name of the JDE used to print this job. The JDE refers to a
group of printer processing parameters that describe printing
requirements within a JDL. The JDL that contains this JDE is either the
JDL that is currently active on the printer or the JDL that is specified in the
Printer job library (JDL) DJDE packet parameter. You can enter from one
to six characters or *NONE, which suppresses the creation of a JDE
command.
Printer job library (JDL)
Specifies the PDL file that contains a collection of printing jobs (JDEs).
This JDL contains the JDE specified in the Printer job name (JDE) DJDE
packet parameter. You can use from one to six characters or *NONE,
which suppresses the creation of a JDL command.
Number of copies to print
(COPIES)
Specifies the number of copies to print of this report, from 0 to 32,767. A
value of zero (0) suppresses the creation of a COPIES= DJDE command.
The default is one (1).
Printing Documents with XDPE/400 (9/2001)
12-11
DJDE command generation
Print on both sides of sheet
(DUPLEX)
Specifies whether to print the pages of this job on both sides or one side
of a sheet. You can use these values:
•
•
•
*YES — Prints on both sides of the page (duplex)
*NO — Prints on one side of the page (simplex)
*NONE — Does not create a DUPLEX DJDE
Electronic form name
(FORMS)
Specifies the name of an electronic form to print on every page of this job.
You can enter from one to six characters or *NONE, which suppresses the
creation of a FORMS command.
Page formatting setting
(FORMAT)
Specifies the name of a page descriptor entry (PDE) used to set the page
formatting parameters for this job. These parameters include the location
of the starting print line of the page, font usage, and page orientation. You
can enter from one to six characters or *NONE, which suppresses the
creation of a FORMAT command.
Copy modification setting
(MODIFY)
Specifies the name of the copy modification entry (CME) used when
printing this job. A CME replaces the variable data on a page with fixed
data or can specify font changes within variable data. You can enter from
one to six characters or *NONE, which suppresses the creation of a
MODIFY command.
SPECIAL back form name
(BFORM)
Specifies the name of a form to print on the reverse side of duplex pages.
BFORM is used with DUPLEX=*YES to convert a simplex application into
a duplex application where the back side of a sheet is a fixed form. You
can enter from one to six characters or *NONE, which suppresses the
creation of a BFORM command.
NOTE: No variable data is merged with this form. If you specify a
BFORM and DUPLEX=*NO, the printer ignores the BFORM request.
Distribution text (RTEXT)
Specifies the name of a printer resident RTEXT (.TST) file to use when
printing this job. RTEXT prints distribution information (text and an
optional form) before every copy. The text or form can vary from copy to
copy, creating a distribution list for printing applications. You can enter
from one to six characters or *NONE, which suppresses the creation of a
RTEXT command.
Distribution form (RFORM)
Specifies the name of the electronic form to print with all RTEXT pages.
You can enter from one to six characters or *NONE, which suppresses the
creation of a RFORM command.
If you specify *NONE for RTEXT or leave it blank, and specify a form
name for RFORM, the RFORM form is ignored.
Printing Documents with XDPE/400 (9/2001)
12-12
DJDE command generation
Bin selection (FEED)
Specifies the sequence or method of paper selection to use when
selecting from the multiple paper sources available on Xerox printers. You
can use these values:
•
MAIN — Specifies the main set of trays with a FEED=MAIN
command.
•
AUX — Specifies the auxiliary set of trays with a FEED=AUX
command.
•
OPR — Specifies the operator control of the tray selection with a
FEED=OPR command.
•
Stock-Set-ID — Specifies the name of a stock set file resident on the
printer which defines a set of trays. The ID can be from one to six
characters.
•
*NONE — Does not create a FEED DJDE.
NOTE: STK ID does not appear with the F4 prompt, but does appear
on the menu.
Text description (TEXT)
Specifies a text string to store with the DJDE packet that you can use to
describe the DJDE packet. This string is intended for your information
only. You can use these values:
•
•
*BLANK — No text is retained
text — Allows up to 40 characters
Printing Documents with XDPE/400 (9/2001)
12-13
DJDE command generation
Examples of creating DJDE packets
This section provides two examples of creating DJDE packets.
Example 1
In this example, you develop a portrait-oriented application for a Xerox
4090 printer that requires 80 lines per page. The Monitor Queue uses a
default PDE that specifies 66 lines per page when you specify portrait
one-up printing via spool file attributes.
Along with the 80-line PDE, you must develop an electronic form that
matches the 80-line format. The name of the PDE file on the printer is
STFMT, and the electronic form is called SPEC1.
You must create a packet that contains the appropriate DJDEs to activate
the PDE and merge the form with the data. Use this procedure:
Step 1.
Sign on and, if necessary, add the XDPE/400 application library to the
library list for your user profile.
Step 2.
Enter CRTDJDE at any OS/400 command prompt. The Create DJDE
packet menu displays.
Create DJDE packet (CRTDJDE)
Type choices, press Enter.
DJDE packet name . . . . . . . .
Name, F4 for list
Bottom
F3=Exit
F4=Prompt
F24=More keys
F5=Refresh
Printing Documents with XDPE/400 (9/2001)
F12=Cancel
F13=How to use this display
12-14
DJDE command generation
Step 3.
Enter STMNTPKT as the name of your new packet and press ENTER.
You can use from one to eight characters for the name. The Create DJDE
Packet menu displays additional parameters.
Create DJDE Packet (CRTDJDE)
Type choices, press Enter.
DJDE packet name. . . . . . .
Printer job name . . . . . .
Printer job library . . . . .
Number of copies to print . .
Print on both sides of sheet.
Electronic form name. . . . .
Page formatting setting . . .
Copy modification setting . .
SPECIAL back form name. . . .
Distribution text . . . . . .
Distribution form . . . . .
Bin selection . . . . . . . .
Text selection. . . . . . . .
STMNTPKT
*NONE
*NONE
0
*NONE
*NONE
*NONE
*NONE
*NONE
*NONE
*NONE
*NONE
*BLANK
Name, F4 for list
JDE Name, *NONE
JDL id, *NONE
0-32767
*YES, *NO *NONE
FRM id, *NONE
PDE id, *NONE
CME id, *NONE
FRM id, *SAME
RTEXT id, *NONE
FRM id, *NONE
MAIN, AUX, OPR, STK id...
Bottom
F3=Exit
F4=Prompt
F24=More keys
F5=Refresh
F12=Cancel
F13=How to use this display
Step 4.
Enter SPEC1 as the Electronic form name.
Step 5.
Enter STFMT as the Page formatting setting.
Step 6.
Press ENTER.
The system stores the DJDE packet called STMNTPKT in the DJDE
subfolder of XDPEFLR.
To use this packet to print the output of the application, you must change
the printer file for your application. You can use the Change Xerox Printer
File (CHGXPRTF) command to specify the direct method of printer control
generation and the name of your new DJDE packet. Refer to chapter 10
for information about specifying the Direct method of command
generations.
Printing Documents with XDPE/400 (9/2001)
12-15
DJDE command generation
Example 2
In this example, each line mode application going to a particular output
queue uses a different printer file to specify a preprinted form. The form
stock is identified in the Form type (FORMTYPE) spool file attribute. You
want to replace these preprinted forms with electronic forms stored on the
printer.
It is too time consuming to change each printer file to specify an electronic
form name. Instead, you can create DJDE packets with names that match
the FORMTYPE values and specify the appropriate electronic form in
each packet.
The FORMTYPE value in a given printer file is called XYZFRM. An
electronic form that corresponds to this preprinted form has been
developed on the Xerox printer and is called XYZ. You need to create a
packet that matches the FORMTYPE. Use this procedure:
Step 1.
Sign on and, if necessary, add the XDPE/400 application library to the
library list for your user profile.
Step 2.
Enter CRTDJDE at any OS/400 command prompt.
Step 3.
Enter XYZFRM as the DJDE packet name. You can use from one to eight
characters for the name.
Step 4.
Enter XYZ as the Electronic form name and press ENTER.
Create DJDE Packet (CRTDJDE)
Type choices, press Enter.
DJDE packet name . . . . . .
Printer job name . . . . . .
Printer job library . . . . .
Number of copies to print . .
Print on both sides of sheet.
Electronic form name. . . . .
Page formatting setting . . .
Copy modification setting . .
SPECIAL back form name. . . .
Distribution list . . . . . .
Distribution form . . . . .
Bin selection . . . . . . . .
Text ‘description’. . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
XYZFRM
*NONE
*NONE
0
*NONE
XYZ
*NONE
*NONE
*NONE
*NONE
*NONE
*NONE
*BLANK
Name, F4 for list
JDE Name, *NONE
JDL id, *NONE
0-32767
*YES, *NO *NONE
FRM id, *NONE
PDE id, *NONE
CME id, *NONE
FRM id, *SAME
RTEXT id, *NONE
FRM id, *NONE
MAIN, AUX, OPR, STK id...
Bottom
F3=Exit
F4=Prompt
F24=More keys
F5=Refresh
Printing Documents with XDPE/400 (9/2001)
F12=Cancel
F13=How to use this display
12-16
DJDE command generation
The packet called XYZFRM now exists in the DJDE subfolder of
XDPEFLR. You can repeat this process for each different FORMTYPE
value.
To use these packets to print the jobs, make sure Monitor Queue is set up
to always use the Direct method of printer control generation and use the
FORMTYPE attribute as the packet data field. Refer to chapter 18 for
more information.
Using the Change DJDE packet menu
Use the Change DJDE packet (CHGDJDE) command to modify DJDE
packets created with the Create DJDE command. You can use this
command on a command line or within a program to change DJDE
packets. If prompted, press F1 to display the current values of the DJDE
commands.
Follow these steps to change a DJDE packet at the command prompt:
Step 1.
Enter CHGDJDE and press ENTER. The Change DJDE packet menu
displays.
Change DJDE packet (CHGDJDE)
Type choices, press Enter.
DJDE packet name . . . . . . . .
Name, F4 for current list
Bottom
F3=Exit
F4=Prompt
F24=More keys
F5=Refresh
Printing Documents with XDPE/400 (9/2001)
F12=Cancel
F13=How to use this display
12-17
DJDE command generation
Step 2.
Enter the name of the DJDE packet to change and press ENTER. The
Change DJDE packet menu displays additional parameters.
Change DJDE Packet (CHGDJDE)
Type choices, press Enter.
DJDE packet name. . . . . . .
Printer job name. . . . . . .
Printer job library . . . . .
Number of copies to print . .
Print on both sides of sheet.
Electronic form name. . . . .
Page formatting setting . . .
Copy modification setting . .
SPECIAL back form name. . . .
Distribution list . . . . . .
Distribution form . . . . .
Bin selection . . . . . . . .
Text ‘description’. . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
*SAME
*SAME
*SAME
*SAME
*SAME
*SAME
*SAME
*SAME
*SAME
*SAME
*SAME
*SAME
Name, F4 for list
JDE Name, *NONE, *SAME
JDL id, *NONE, *SAME
0-32767, *SAME
*YES, *NO, *SAME, *NONE
FRM id, *NONE, *SAME
PDE id, *NONE, *SAME
CME id, *NONE, *SAME
FRM id, *NONE, *SAME
RTEXT id, *NONE, *SAME
FRM id, *NONE, *SAME
MAIN, AUX, OPR, STK id...
Bottom
F3=Exit
F4=Prompt
F24=More keys
Step 3.
F5=Refresh
F12=Cancel
F13=How to use this display
Modify the parameters you want and press ENTER.
Refer to the conventions described in “Packet parameters” earlier in this
chapter.
NOTE: Use the *SAME option to obtain the same values as
previously defined with the CRTDJDE command.
Printing Documents with XDPE/400 (9/2001)
12-18
DJDE command generation
Using the DJDE packet Text List utility
You can use the DJDE packet Text List utility (EDTDJDE) to do the
following:
•
•
•
•
•
•
•
•
Display a list of DJDE text packets
Create DJDE text packets
Edit DJDE text packets
Copy DJDE text packets
Delete DJDE text packets
Display DJDE text packets
Print the contents of DJDE text packets
Rename DJDE text packets
The system stores the DJDE packets you create and maintain through
XDPE/400 in the XDPEFLR/DJDE folder.
NOTE: If the descriptive text is preceded by crt#, the packet was
created using the CRTDJDE CL command, and you can alter it using
the CHGDJDE or EDTDJDE command. If the descriptive text is
preceded by edt#, the packet was created or altered using the
EDTDJDE command, and you cannot update it using the CHGDJDE
CL command.
You can access the DJDE packet Text List utility through the XDPE/400
Main Menu. Enter EDTDJDE and press ENTER.
Printing Documents with XDPE/400 (9/2001)
12-19
DJDE command generation
The DJDE Text List menu displays. Use this menu to edit, copy, delete,
display, print, and rename DJDE text packets.
DJDE Text List
Starting characters
Position to . . . . .
Type option, then press Enter.
2 = Edit 3 = Copy 4 = Delete
Opt Packet
Description
_
_
_
_
_
_
_
_
_
_
5 = Display
6 = Print
7 = Rename
Revised
Bottom
F3=Exit
F4=Prompt
F11=Display names only
F5=Refresh
F12=Cancel
F6=Create
DJDE packets are listed by name along with the packet description and
the packet revision date. The Opt field allows you to choose the
processing function you wish to perform by entering the number that
corresponds to the desired function.
Pressing F11 will omit the Description and Revised columns from the
display, allowing you to view more packets on the screen. Pressing F11
again will redisplay these fields.
Printing Documents with XDPE/400 (9/2001)
12-20
DJDE command generation
Creating text packets
Use the Create DJDE Packet menu to create a new DJDE text packet
using the full-screen editor. Follow these steps:
Step 1.
At the DJDE Text List menu, press F6. The Create DJDE Packet menu
displays.
Create DJDE Packet
Type choices, press Enter.
Packet name . . . . . . . .
Text description . . . . .
F3=Exit
F5=Refresh
F12=Cancel
Step 2.
Enter the name of the DJDE packet you want to create in the Packet name
field. You must enter a name in this field; there is no default packet name.
Step 3.
Enter descriptive information in the Text description field for the packet.
Press ENTER to create the DJDE packet.
If the input is valid, XDPE/400 creates an empty text packet in the
XDPEFLR/DJDE folder and the full-screen editor displays.
Step 4.
Enter DJDE text. Refer to “Deleting text packets” in this chapter for
details.
Printing Documents with XDPE/400 (9/2001)
12-21
DJDE command generation
Editing text packets
Use the Edit DJDE Text menu to edit previously built DJDE packets. The
Edit DJDE Text menu provides a full-screen edit mode for the selected
DJDE packet. In edit mode, you use simple line-insert and line-delete
commands to insert and delete lines of DJDE text.
Follow these steps to edit a DJDE text packet:
Step 1.
At the DJDE Text List menu, enter 2 in the Opt field next to the DJDE
packet name you want to edit and press ENTER. The Edit DJDE Text
menu displays.
Edit DJDE Text
Packet: packet-name
...+....1....+....2....+....3....+....4....+....5....+....6....+....7.
**********************Beginning of data*****************************
xxxxxxx
xxxxxxx
xxxxxxx
xxxxxxx
xxxxxxx
xxxxxxx
xxxxxxx
xxxxxxx
xxxxxxx
xxxxxxx
xxxxxxx
xxxxxxx
***********************End of data**********************************
F3=Exit
Step 2.
Edit the DJDE text. Each line of DJDE text can contain up to 71
characters. You can enter or change text within the 71 columns. Specify
these line edit commands in the line-number column:
•
•
D or d for Delete Line
I or i for Insert Line
End each DJDE text line with a comma. A text line that does not end with
a comma is assumed to be the last record. As the last record, it and all
records following it are not sent to the printer.
Press ENTER to execute these commands. Lines marked D or d are
deleted, and blank lines are inserted after any line marked with an I or i
on the line-number column.
Printing Documents with XDPE/400 (9/2001)
12-22
DJDE command generation
Some don’ts to remember:
•
Do not enter values for SKIP, OFFSET, or PREFIX in the DJDE text.
These are XDPE/400 global IDEN values and are inserted
automatically when the DJDE packet is inserted into the print data
stream.
•
Do not enter the DJDE line ending semicolons (;) and command
terminating END in DJDE text. These are inserted automatically by
XDPE/400 at print time.
•
Do not continue DJDE commands from line to line.
Refer to your Xerox printer manuals for more information and for the
syntax of DJDE packets.
Step 3.
Press ENTER when you are done.
Step 4.
Press F3 to save the edited text. You will be asked if you want to save
your edits and if you want to return to editing your packet.
Printing Documents with XDPE/400 (9/2001)
12-23
DJDE command generation
Copying text packets
Use the Copy DJDE Text Packet menu to create a second copy of a
previously built DJDE packet. Follow these steps:
Step 1.
At the DJDE Text List menu, enter 3 in the Opt field next to each DJDE
packet you want to copy and press ENTER. The Copy DJDE Text Packet
menu displays.
Copy DJDE Text Packet
To rename copied DJDE text packet, type New Name, press Enter.
DJDE text packet
New name
DJDE text packet
New name
Bottom
F3=Exit
F5=Refresh
Step 2.
F12=Cancel
Enter the new name for the DJDE packet on the line to the right of the
name of each DJDE packet to copy and press ENTER.
You cannot copy a DJDE packet onto itself. If you try, an error message
displays, and the packet names that are not allowed are highlighted. You
cannot continue until you enter a different name.
Step 3.
If you are attempting to overwrite an existing packet, the Confirm Copy of
DJDE Text Packet menu displays. Choose Y if you want to overwrite the
existing packet with the new packet.
Printing Documents with XDPE/400 (9/2001)
12-24
DJDE command generation
Deleting text packets
Use the DJDE Text List Packet menu to delete one or more DJDE
packets.
At the DJDE Text List menu, enter 4 in the Opt field next to each DJDE
packet you want to delete and press ENTER.
A confirmation menu will display. Press F12 to cancel or ENTER to delete
the selected DJDE packets.
Displaying text packets
Use the Display DJDE Text menu to view the text of a previously built
DJDE packet.
At the DJDE Text List menu, enter 5 in the Opt field next to the DJDE
packet you want to display and press ENTER.
The Display DJDE Text menu displays. Press F3 or F12 to return to the
previous menu.
Printing the contents of text packets
Use the DJDE Text List menu to print the text of a previously built DJDE
packet.
At the DJDE Text List menu, enter 6 in the Opt field next to the DJDE
packet you want to print and press ENTER. The message, “DJDE text
packet name printed successfully” appears at the bottom of the DJDE
Text List menu.
Renaming text packets
Use the Rename DJDE Text Packet menu to rename an existing DJDE
text packet. Follow these steps:
Step 1.
At the DJDE Text List menu, enter 7 in the Opt field next to each DJDE
packet you want to rename and press ENTER. The Rename DJDE Text
Printing Documents with XDPE/400 (9/2001)
12-25
DJDE command generation
Packet menu displays with a list of the DJDE text packets you selected for
renaming.
Rename DJDE Text Packet
Type new name for DJDE text packet, press Enter.
DJDE text packet
New name
DJDE text packet
New name
Bottom
F3=Exit
F5=Refresh
Step 2.
F12=Create
Enter the new names for the DJDE text packets and press ENTER.
You cannot use a DJDE packet name that already exists. If you do, an
error message displays, and the duplicate names are highlighted. You
cannot continue until you enter a name that has not been used.
Using the OS/400 Source Entry Utility (SEU)
You can use the IBM Source Entry Utility (SEU) instead of the XDPE/400
EDTDJDE command to modify DJDE packets.
NOTE: Once you use SEU to create a packet, you cannot use
CHGDJDE to modify the packet; use SEU again.
Printing Documents with XDPE/400 (9/2001)
12-26
13.
13
XES command generation
This chapter describes how to create and insert Xerox Escape Sequence
(XES) control commands into the print data stream.
Using XES control commands
The generation of XES commands is restricted, depending on whether
Monitor Queue is in *JOB or *PAGE file processing mode. Use one of
these methods for generating XES commands:
None
Indirect method
You can use the Always generate (ALWAYS) Monitor Queue parameter
to print a job without inserting any XES control commands that affect
document formatting.
In the Indirect method, Monitor Queue maps printer file parameters to
XES control commands and inserts the commands into the print data
stream. The spool file is then released to the printer writer.
Direct method
In the Direct method, you first create a file of XES control commands,
called an XES packet. The system inserts these XES control commands
into the data stream before releasing the spool file to the printer writer.
Combined method
In the Combined method, you create a file of XES control commands, then
Monitor Queue maps the spool file attributes to these commands.
XDPE/400 inserts both sets of XES control commands into the print data
stream before releasing the spool file to the printer writer.
Printing Documents with XDPE/400 (9/2001)
13-1
XES command generation
File processing mode (PROCMODE) restriction
The File processing mode (PROCMODE) Monitor Queue parameter
determines how commands are inserted into your jobs. When
PROCMODE is *JOB, XDPE/400 maintains the prior XDPE/400 release
level with a reduced level of functionality. When *PAGE is specified for
PROCMODE, XDPE/400 uses the full level of functionality. Some
XDPE/400 commands are ineffective in *JOB mode.
Table 13-1 shows the values that are allowed with the File processing
mode (PROCMODE) Monitor Queue parameter.
Table 13-1
Parameters allowed with PROCMODE
Printer file parameters
1
*JOB
*PAGE
FORMFEED1
Yes
Yes
FRONTOVL
Yes (with cycle forms
command)
Yes
BACKOVL
Yes (with cycle forms
command)
Yes
DUPLEX
Yes
Yes
COPIES
Yes
Yes
OUTPUT PRIORITY
Yes
Yes
DRAWER1
Yes
Yes
FONT (identifier)
Yes
Yes
MULTIUP
No
Yes
PAGRTT
No
Yes
FRONTMGN/BACKMGN
Yes (only front margin)
Yes
This parameter may be overridden by the interface box.
Printing Documents with XDPE/400 (9/2001)
13-2
XES command generation
Indirect method
The Indirect method creates XES control commands from spool file
attributes.
When an OS/400 application program or print utility opens a printer file for
output, a spool file is created. The attributes of that spool file are created
from the printer file parameters.
Before the spool file is released to the printer writer, XDPE/400 processes
the spool file and creates XES control commands.
Table 13-2 shows the printer file parameters that map to the XDPE/400
XES features.
Table 13-2.
Printer file parameters mapped to XDPE/400 XES
features
IBM OS/400
printer file parameters
XDPE/400 XES features
FORMFEED
Predrilled paper shift
JOB
Job name
FRONTOVL
Forms Invocation
BACKOVL
Forms invocation
DUPLEX
Duplex mode selection
COPIES
Number of copies (for 4235)
OUTPUT PRIORITY
Job priority (for 4235)
DRAWER
Paper tray selection
FONT (identifier)
Generic XES packet
MULTIUP
Multi-up printing
PAGRTT
Multi-up printing
FRONTMGN
Margin setting
BACKMGN
Margin setting
NOTE: To prevent conflicts with the printer writer, which also
processes spool file attributes, XDPE/400 converts the spool file
attributes to their default values. The spool file is then released to the
printer writer.
Printing Documents with XDPE/400 (9/2001)
13-3
XES command generation
Modifying printer file parameters
The following sections describe the functions and use of the printer file
parameters to define XES parameters.
You can use any of these commands to modify the printer file parameters
shown in table 13-2:
•
•
•
CRTPRTF to create a printer file
CHGPRTF to modify an existing printer file
OVRPRTF to override an existing printer file
For instructions on how to use the CRTPRTF, CHGPRTF, and OVRPRTF
commands, refer to OS/400 CL Reference and OS/400 Printer Device
Programming.
FORMFEED
Creates a shift command for the 4235 and 4213 printers. Table 13-3
shows the options for the FORMFEED commands.
Table 13-3.
FORMFEED command options
Spool file attribute
XES command
*DEVD
No command generated
*CONT
Shift command with 0 values
All others
Shift command with XDPE/400 global
values
JOB
Constructs a job name for use in the XES command string from the Job
number, User name, and Job name fields of the JOB spool file attribute.
FRONTOVL
Activates an XES form for the 4700, 4235, and 4213 printers, or a
constant merge page load for 4030 printers on all odd side pages. The
XES form name can be one to eight characters in length and must have a
.FRM extension. Before an XES form can be used in a job, it must be
resident on the printer.
BACKOVL
Activates an XES form for the 4700, 4235, and 4213 printers, or a
constant page merge load for 4030 printers on all even side pages. The
XES form name can be one to eight characters in length and must have a
.FRM extension. Before an XES form can be used in a job, it must be
resident on the printer.
If the BACKOVL value is *FRONTOVL, the front form or constant merge
page is used.
For the 4030 XES printer, the form automatically downloads as a merged
page before the required page.
Enter *NONE for the BACKOVL parameter if you do not want to use an
electronic form.
Printing Documents with XDPE/400 (9/2001)
13-4
XES command generation
DUPLEX
Specifies whether to print the output on one side (simplex) or on both
sides (duplex) of the page. You can use these values:
•
*YES — XDPE/400 generates an XES duplex control command
•
*NO — XDPE/400 generates an XES simplex control command
•
*TUMBLE — XDPE/400 generates an XES tumble duplex control
command
See the Print on both sides of sheet (DUPLEX) XES packet parameter
later in this chapter for the difference between printing in duplex and
printing in tumble duplex.
NOTE: If you select *YES or *TUMBLE, along with a packet tray
specification, and are using the Flex i-data interface box, your job
may print simplex. Refer to chapter 26 for instructions to correct this
problem.
COPIES
Specifies the number of copies to print. To define COPIES, enter the
number of copies you want from 1 to 255 for the COPIES parameter.
XDPE/400 generates the XES COPIES control command with the
specified number of copies.
NOTE: Xerox printers can accept up to 32,767 copies, but the AS/400
only allows a maximum of 255. Use the Direct method if more than
255 copies are required.
For XES printers without a hard disk, the system transmits the enhanced
spool file(s) once for each copy desired.
OUTPUT PRIORITY
Specifies the job priority the printer uses to print the job. Table 13-4 shows
the OUTPUT-to-XES priority mapping.
Table 13-4.
OUTPUT-to-XES priority mapping
Spool file attribute
XES command
1
*HIGH
8
*LOW
9
*HOLD
All others
*NORM
Printing Documents with XDPE/400 (9/2001)
13-5
XES command generation
DRAWER
Specifies the source drawer from which paper is fed into the printer. The
XDPE/400 global values area contains the mapping of these IBM values
to Xerox paper trays. If you select a value other than those listed here, the
Data page source (DATASRC) Monitor Queue parameter value will be
used if one is specified; otherwise, if no DATASRC value is specified, the
printer’s default drawer will be selected. You can use these values:
•
•
•
•
•
•
1 — XDPE/400 global value for drawer 1
2 — XDPE/400 global value for drawer 2
3 — XDPE/400 global value for drawer 3
4 — XDPE/400 global value for drawer 4
*SAME — Leaves the value unchanged
*E1 — XDPE/400 global value for the envelope drawer
NOTE: If you are printing duplex and using the Flex i-data interface
box, you must synchronize both this DRAWER printer file parameter
and the Source tray (TRAY) packet parameter. Refer to chapter 26
for instructions on correcting any problems.
FONT (identifier)
Identifies a generic ASCII XES packet containing ASCII data. When a
generic packet is specified, XDPE/400 looks for a generic packet in the
XDPEFLR/GENXES directory. The ASCII file is wrapped by XDPE/400 in
one or more ASCII Transparency SCS commands and is merged with the
spool file output. Escape characters and all additional XES syntax rules
must be followed. XDPE/400 only reads and writes this file.
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.
For more information on processing generic packets, refer to “Generic
packets” later in this chapter.
MULTIUP/PAGRTT
MULTIUP prints multiple pages of output on one physical page. You can
use these values:
•
•
•
1 — One page of output is printed on each physical page
2 — Two pages of output are printed on each physical page
4 — Four pages of output are printed on each physical page
PAGRTT specifies the degree of text rotation in respect to the way the
page is loaded in the printer.
NOTE: When the ALWAYS and SEQUENCE Monitor Queue
parameters are *COMBINED and *ATTRIB, the Degree of page
rotation (PAGRTT) printer file parameter is overridden, and the
printer’s default orientation is used.
The MULTIUP and PAGRTT attributes work together to create the output
you want and are explained in detail in chapter 25, “Multi-up printing.”
FRONTMGN/BACKMGN
Specifies the offset origin from the edge on the front side of the page and
the back side of a page. The XES TOP and LEFT margin commands are
used with converted values and are inserted at the top of the page. Margin
values are converted into dots.
Printing Documents with XDPE/400 (9/2001)
13-6
XES command generation
Direct method
With the Direct method, a user-created XES packet is used by your
Monitor Queue session to create printer-specific XES commands, which
are then inserted into the spool file. With this method, the spool file
attributes that are used with the Indirect method are ignored. Refer to
chapter 8 for more information about configuring XDPE/400 for Direct
processing.
Default XES packet
XDPE/400 allows you to specify the action to take when the system does
not locate an XES packet. This is controlled using the Pass through option
(PASSTHRU) Monitor Queue parameter.
When specified, the XES packet called DEFAULT is invoked if the
requested packet is not found, or if *FORMTYPE is specified for the
Packet data (PACKETDATA) Monitor Queue parameter, and if the Form
type spool file attribute is *STD. You must create the default packet before
this feature can be used. If this packet is not found, the Default packet
option (DFTPKT) Monitor Queue parameter specifies the next action to
take.
For more information on default packet processing, see “Setting the
Packet data (PACKETDATA) parameter” in chapter 10.
Printing Documents with XDPE/400 (9/2001)
13-7
XES command generation
Combined method
The Combined method is a combination of the Direct and Indirect
methods of XES packet generation. XDPE/400 creates XES commands
using an XES command packet from the XDPEFLR/XES folder and the
XES commands created from the spool file attributes.
Application order of XES control commands
When Monitor Queue generates XES control commands in Combined
mode, the system compares the commands from the XDPEFLR/XES
folder with the commands generated from the spool file attributes. The
first occurrence of a duplicate command is deleted and is not written to
the spool file.
Monitor Queue controls the order in which the XES control commands are
received. Monitor Queue specifies whether to use commands generated
from the spool file attributes or XES control commands from the
XDPEFLR/XES folder. This mechanism is specified by the Order of
sequence (SEQUENCE) Monitor Queue parameter.
If the Order of sequence parameter is *ATTRIB, Monitor Queue uses the
XES control commands retrieved from the XDPEFLR/XES folder if a
parameter is specified by both the spool file attributes and the folder. This
means that XES control commands from the XDPEFLR/XES folder
override the XES control commands created from the spool file attributes.
If the Order of sequence parameter is *PACKET, Monitor Queue uses the
XES control commands whenever a parameter is specified by both the
folder file and the spool file attributes. This means that XES control
commands created from spool file attributes override XES control
commands from the XDPEFLR/XES folder.
Printing Documents with XDPE/400 (9/2001)
13-8
XES command generation
Creating and managing XES packets
The XES packet creation commands assist you in creating XES packet
control commands. You select XES control command options using a
command prompt menu. The system then creates an XES control
command packet with the selected options.
These XES packet creation commands are available:
•
•
•
CRTXES (Create Xerox Escape Sequence Packet)
CHGXES (Change Xerox Escape Sequence Packet)
DLTXES (Delete Xerox Escape Sequence Packet)
The following sections show you how to use these commands with the
available menus. You can also use these commands as CL commands by
providing the values for the keywords directly from the command line.
Creating XES packets
Use the CRTXES command to create XES control command packets
without having to know all about XES commands. This command creates
some of the most commonly used XES control commands.
You can create these XES options with the Create XES Packet command
(the corresponding commands are shown in parentheses):
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Printer control packet name (XES)
Job name (JOBNAME)
Operator text message (OTEXT)
Job priority (JPRY)
Number of copies (COPIES)
Forms sequence (FORMS)
Print on both sides of sheet (DUPLEX)
Pre-drilled paper (DRILLED)
Xerox 4235 page format (FORMAT)
Margin setting (MARGIN)
Page font selection (XESFONTS)
Source tray (TRAY)
Page offset (OFFSET)
Generic XES (GENXES)
Resource list name (RSCLIST)
Number of pages per side (PAGESPSIDE)
Multi-up packet name (XESMUP)
Printing Documents with XDPE/400 (9/2001)
13-9
XES command generation
Packet name syntax
XES packet names must comply with these syntax rules:
•
•
•
•
The name can be from one to eight bytes long
The first byte of the name must be an alphabetic character
Bytes two through eight can be A-Z, 0-9, @, #, or $
Do not enclose the name within quotes or other characters
These are examples of valid XES packet names:
•
•
•
XESTXT
NMXESA12
XES@301A
NOTE: If you type lowercase letters, the name is saved in uppercase.
Packet creation procedure
Follow these steps to create an XES packet:
Step 1.
Enter CRTXES and press ENTER. The Create XES Packet menu
displays.
Create XES Packet (CRTXES)
Type choices, press Enter.
Printer control packet name . .
Name, F4, for list
F3=Exit F4=Prompt F5=Refresh F10=Additional parameters
F13=How to use this display F24=More keys
Step 2.
Bottom
F12=Cancel
Enter the name of the XES packet and press ENTER. The Create XES
Packet menu displays additional parameters.
Printing Documents with XDPE/400 (9/2001)
13-10
XES command generation
Step 3.
Modify the parameters you want, following the conventions described in
the next section, and press ENTER.
Create XES Packet (CRTXES)
Type choices, press Enter.
Printer control packet name . .
Job name. . . . . . . . . . . . *GEN
Operator text message . . . . . *NONE
Name, F4 for list
Job priority . . .
Number of copies .
Forms sequence . .
+ for
Print on both sides
Pre-drilled paper .
*HIGH, *NORM, *LOW, *HOLD...
1-999, *NONE
Form name, *SKIP
. . . . . . *NORM
. . . . . .
. . . . . .
more values
of sheet. . *NO
. . . . . . *NO
*YES, *NO, *TUMBLE, *NONE
*YES, *NO, *NONE
Additional Parameters
Xerox 4235 page format
. . . *NONE
0-9, *NONE
More...
F3=Exit
F4=Prompt
F24=More keys
F5=Refresh
F12=Cancel
F13=How to use this display
Create XES Packet (CRTXES)
Type choices, press Enter.
Margin setting
Page height . . . . . . .
Top margin . . . . . . .
Bottom margin . . . . . .
Left margin . . . . . . .
Right margin . . . . . .
Page font selection
Font name . . . . . . . .
Font index . . . . . . .
Download font . . . . . .
Source tray . . . . . . . .
Page offset . . . . . . . .
Generic XES:
Packet name . . . . . . .
Invocation type . . . . .
Interface formatting off
.
.
.
.
.
.
.
.
.
.
*NONE
0
0
0
0
Number, *NONE
Number
Number
Number
Number
.
.
.
.
.
.
.
.
.
.
*NONE
0
*NO
*NONE
*NONE
0-9
*YES, *NO
*TRAY1, *TRAY2, *TRAY3...
*NONE, *YES
. . *NONE
. . *JOB
. . *NO
*NAME, F4 for list
*JOB, *PAGE
*YES, *NO
More...
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
F12=Cancel
Printing Documents with XDPE/400 (9/2001)
F13=How to use this display
13-11
XES command generation
Create XES Packet (CRTXES)
Type choices, press Enter.
Resource list name . . . . . . *NONE
Number of pages per side . . . *NONE
Multi-up packet name . . . . . *NONE
*NAME, F4 for list
1-32767, *NONE
Name, F4 for list
Bottom
F3=Exit F4=Prompt F5=Refresh F10=Additional parameters
F13=How to use this display F24=More keys
F12=Cancel
Packet parameters
Printer control packet name
(XES)
Job name (JOBNAME)
Operator text message
(OTEXT)
Specifies the name for the XES control packet you are creating. The
system stores the packet in the XDPEFLR/XES folder. You can use from
one to eight characters. Press F4 for a list of existing XES packets.
Specifies a name that displays on the XES job queue and prints on the
status sheet if a status sheet is printed. You can use these values:
•
*GEN — Uses the OS/400 spool file job name, user name, and spool
file number
•
job-name — Allows you to specify a character string from 1 to 32
characters
•
*NONE — Does not use the option
Specifies a message to alert the operator of special conditions. This
message displays before the job prints. Printing cannot proceed until the
operator presses the Continue key. You can use these values:
•
*NONE — Does not create message text.
•
text — Allows you to specify a character string from 1 to 40
characters. You can include lowercase characters in the text of this
message by enclosing them in quotes.
Printing Documents with XDPE/400 (9/2001)
13-12
XES command generation
Job priority (JPRY)
Sets the priority of this job within the printer job queue. You can use these
values:
•
•
•
•
•
*HIGH — Gives the job first priority
*NORM — Gives the job second priority
*LOW — Gives the job third priority
*HOLD — Holds the job in the queue
*NONE — Does not assign a priority to the job
Number of copies (COPIES)
Specifies the number of copies of this job to print. Valid values are *NONE
and from 1 to 999. A value of *NONE suppresses the XES multicopy
command. The default is one (1).
Forms sequence (FORMS)
Specifies the name of electronic forms to print, in a cyclical fashion, in a
job that consists of multiple variable pages. A form name of *SKIP causes
the printer to image a page without a form. You can use from one to eight
characters for each form name. You must enclose each form name within
single quotes, but do not include characters within the form name that are
not part of the form name, such as single or double quotes. You can enter
up to 10 forms.
NOTE: For Xerox 4030 printers, a merge page is loaded and invoked.
XES forms are indexed by XDPE/400 and your XES printer to allow the
use of multiple forms during a job. How forms are indexed can determine
how they are placed in a job. The logical processing feature of XDPE/400
allows you to control when and where a printer control packet is applied
using the When to apply (WHEN) parameter. This parameter also affects
the indexing and placement of forms:
•
An XES form applied as part of an XES packet or from printer file
parameters is assigned an index number of “1”. A form applied to the
top of a page (*TOP) by a logical processing test also assumes the
index number of “1” and replaces any previous form with an index of
“1”.
•
A form applied at the bottom of a page (*BOTTOM) by a logical
processing test assumes an index number of “2” and will be placed
on the next page regardless of any other forms that may already be
placed on that page.
For more information about logical processing, refer to chapter 23. For
more information about form indexing on XES printers, see the
documentation supplied with your XES printer.
Print on both sides of sheet
(DUPLEX)
Specifies whether to print on both sides or on one side of a sheet. You can
use these values:
•
•
•
•
*NO — Prints simplex
*YES — Prints duplex
*TUMBLE — Prints tumble duplex
*NONE — Does not use the option
Printing Documents with XDPE/400 (9/2001)
13-13
XES command generation
For portrait printing, when you specify *YES for DUPLEX, the result will
be duplex with long-edge binding, as shown in this figure:
For portrait printing, when you specify *TUMBLE for DUPLEX, the result
will be tumble duplex with short-edge binding, as shown in this figure:
For landscape printing, when you specify *YES for DUPLEX, the result will
be duplex with short-edge binding, as shown in this figure:
Printing Documents with XDPE/400 (9/2001)
13-14
XES command generation
For landscape printing, when you specify *TUMBLE for DUPLEX, the
result will be tumble duplex with long-edge binding, as shown in this
figure:
NOTE: If you select *YES or *TUMBLE, along with a packet tray
specification, and are using the Flex i-data interface box, your job
may print simplex. Refer to chapter 26 for instructions to correct this
problem.
Pre-drilled paper (DRILLED)
Instructs the printer to use the page shift value for predrilled paper. The
page shift value is specified through the Predrilled shift support (SHIFT)
global value. You can use these values:
•
•
•
Xerox 4235 page format
(FORMAT)
Specifies the preconfigured page format residing on the hard drive of the
4700 or 4235 printer. You can define a complete set of page makeup
parameters. You can use these values:
•
•
Margin setting (MARGIN)
*YES — Enables the shift option
*NO — Disables the shift option
*NONE — Does not use the option
0-9 — Identifies the format to use
*NONE — Does not use a format
Specifies the page dimension and the logical page boundaries. All values
are in units of 1/300. All margin values (top, bottom, left, and right) have
a default value of zero. If you do not enter a value, a value of zero is
automatically assigned. You can use these values:
•
page-height — Distance between the top edge and the bottom edge
of the page. If you select *NONE as the page height, a MARGIN
command is not generated.
•
top-margin — Distance from the top edge of the page to the top edge
of characters.
•
bottom-margin — Distance from the bottom edge of the paper to the
bottom of last line of text.
•
left-margin — Distance from the left edge of the page to where the
left side of the first character in each line is to be printed.
•
right-margin — Distance from the left edge of the page to where the
right side of the last character in each line is to be printed.
Printing Documents with XDPE/400 (9/2001)
13-15
XES command generation
Page font selection
(XESFONTS)
Identifies a specific font to be used as the initial font on the printed page.
You can use these values:
•
font-name — Specifies the name of a font that is resident on the
printer or downloaded to the printer prior to the job. Specify *NONE if
there is no initial font.
•
font-index — Specifies the XES font index to use.
•
download-font — Specifies whether the font is resident on the printer
(*NO) or is to be downloaded from the XDPEFLR/XESFONTS
subfolder (*YES).
If you are downloading a font from the XDPEFLR/XESFONTS subfolder,
the font name must be the same as the internal font name contained in
the header of the font on the printer. You do not need to specify the .FNT
file extension.
When you load a font that already exists on the printer, both copies are
kept. If you use this packet often, you could use up available printer
memory.
Source tray (TRAY)
Feeds paper from a specified tray. Tray selection may vary depending on
your printer setup.
If you select an invalid value, the Data page source (DATASRC) Monitor
Queue parameter value will be used if one is specified; otherwise, if no
DATASRC value is specified, the printer’s default drawer will be selected.
NOTE: If you are printing duplex and using the Flex i-data interface
box, you must synchronize both this TRAY packet parameter and the
DRAWER printer file parameter. Refer to chapter 26 for more
information if you have problems.
Page offset (OFFSET)
Offsets pages with a report. When used with logical processing, this
parameter allows you to cause a printed page to be offset from the others
in the stack. Note that to be implemented effectively, this parameter must
be inserted on a page-level basis as part of a logical processing test. You
can use these values:
•
•
*YES — Offsets the current page
*NONE — Specifies that no pages are offset
Printing Documents with XDPE/400 (9/2001)
13-16
XES command generation
Generic XES (GENXES)
Indicates you want to process a generic packet either once for the job, or
once for each printed page of the job. You can use these values:
•
packet-name — Specifies a one- to eight-character packet name,
which is located in the XDPEFLR/GENXES folder.
•
invocation-type — Specifies whether to insert the generic packet
once (*JOB mode) or on every page (*PAGE mode).
•
interface-formatting-off — Specifies whether to turn off page
formatting performed by the interface box. Applies to the idata Flex
and Agile 5250 Optima interface boxes.
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.
For information on creating generic packet files, refer to “Generic packets”
later in this chapter.
Resource list name
(RSCLIST)
Number of pages per side
(PAGESPSIDE)
Multi-up packet name
(XESMUP)
Allows for downloading of job or page level resources. The list is identical
in functionality to Monitor Queue’s list processing. The @ character is not
required if the resource list is specified within the packet.
Specifies the number of logical pages to be printed on each physical
page. This parameter works in conjunction with the Degree of page
rotation (PAGRTT) printer file parameter to produce the desired output.
Refer to chapter 25 for more information. You can use these values:
•
*NONE — Specifies normal (non-multi-up) printing
•
1-32,767 — Specifies the number of logical pages to be printed on
each physical page
Specifies the name of the multi-up packet that contains the relevant font
and positioning information for this job. A value must be entered for this
parameter if the Number of pages per side (PAGESPSIDE) parameter is
any value other than *NONE. Refer to chapter 25 for more information.
You can use this value:
•
name — A one- to eight-character alphanumeric value. The multi-up
packet specified must exist in the XDPEFLR/XESMUP directory.
Printing Documents with XDPE/400 (9/2001)
13-17
XES command generation
Example of creating XES packets
This example shows printing several form letters on a Xerox 4235 printer
in XDPM mode. The application generates the variable text of the letters,
but you want to print an electronic form on each page. You also want to
print the letters on special stock that the operator must load into the
printer before printing the job.
Although you can specify the electronic form with spool file attributes,
using an XES packet allows you to notify the printer operator about the
special stock. The electronic form is called LETR1.
Step 1.
Sign on and, if necessary, add the XDPE/400 application library to the
library list for your user profile.
Step 2.
Enter CRTXES at any OS/400 command prompt.
Create XES Packet (CRTXES)
Type choices, press Enter.
Printer control packet name . . SPECSTK
Job name. . . . . . . . . . . . *GEN
Operator text message . . . . . *NONE
Name, F4 for list
Job priority . . .
Number of copies .
Forms sequence . .
+ for
Print on both sides
Pre-drilled paper .
*HIGH, *NORM, *LOW...
0-999, *NONE
Form name, *SKIP
. . . . . . *NORM
. . . . . .
. . . . . .
more values
of sheet. . *NO
. . . . . . *NO
*YES, *NO, *TUMBLE, *NONE
*YES, *NO, *NONE
Additional Parameters
Xerox 4235 page format
. . . . *NONE
0-9, *NONE
More...
F3=Exit
F4=Prompt
F24=More keys
F5=Refresh
F12=Cancel
F13=How to use this display
Step 3.
Enter SPECSTK as the name of your new packet. You can use from one
to eight characters for the name.
Step 4.
Enter PLEASE LOAD SPECIAL EXPENSIVE STOCK! as the Operator
text message.
Step 5.
Enter LETR1 as the Forms sequence.
Printing Documents with XDPE/400 (9/2001)
13-18
XES command generation
Step 6.
Press ENTER. The system stores the SPECSTK packet in the XES
subfolder of XDPEFLR.
To use this packet to print the output of the application, you must change
the printer file for your application. Use the Change Xerox Printer File
(CHGXPRTF) command to specify the Direct method of printer control
generation and the name of your newly developed XES packet. Refer to
chapter 10 for more information.
Changing XES packets
Use the Change XES Packet (CHGXES) command to modify XES control
command packets created with the Create XES Packet command. You
can use this command on a command line or within a program to change
XES control command packets. If prompted, the existing values of the
XES control command packets are displayed.
NOTE: Press F10 to display the current values within the additional
parameters area. Press F9 to display a field without values or to
display all fields.
Follow these steps to modify an XES control command packet:
Step 1.
Enter CHGXES and press ENTER. The Change XES Packet menu
displays.
Change XES Packet (CHGXES)
Type choices, press Enter.
Printer control packet name . .
*NAME, F4 for list
Bottom
F3=Exit F4=Prompt F5=Refresh F10=Additional parameters
F13=How to use this display F24=More keys
Printing Documents with XDPE/400 (9/2001)
F12=Cancel
13-19
XES command generation
Step 2.
Enter the name of the XES packet you want to change and press ENTER.
The Change XES Packet menu displays additional parameters.
NOTE: Unless you press F9, the system displays only the XES
parameters selected by the Create XES control command.
Change XES Packet (CHGXES)
Type choices, press Enter.
Printer control packet name . .
Job name. . . . . . . . . . . .
Operator text message . . . . .
Job priority . . . . . . . . .
Number of copies. . . . . . . .
Forms sequence. . . . . . . . .
+ for more values
Print on both sides of sheet. .
Pre-drilled paper . . . . . . .
Xerox 4235 page format . . . .
Name, F4 for list
*SAME
*NONE
*SAME
*SAME
*SAME
*HIGH, *NORM, *LOW...
1-999, *NONE, *SAME
Form name, *SKIP...
*SAME
*SAME
*SAME
*YES, *NO, *TUMBLE...
*YES, *NO, *NONE, *SAME
0-9, *NONE, *SAME
More...
F3=Exit
F4=Prompt
F24=More keys
Step 3.
F5=Refresh
F12=Cancel
F13=How to use this display
Modify the parameters you want and press ENTER.
Refer to “Creating XES packets” earlier in this chapter for information
about the parameters.
NOTE: Use the *SAME option to obtain the same values as
previously defined with the CRTXES command.
Printing Documents with XDPE/400 (9/2001)
13-20
XES command generation
Deleting XES packets
Use the Delete XES Packet (DLTXES) command to delete an XES packet.
Follow these steps:
Step 1.
Enter DLTXES and press ENTER. The Delete XES Packet menu displays.
Step 2.
Enter the name of the XES packet you want to delete and press ENTER.
Delete XES Packet (DLTXES)
Type choices, press Enter.
Printer control packet name . .
NAME, F4 for list
Bottom
F3=Exit F4=Prompt F5=Refresh F10=Additional parameters
F13=How to use this display F24=More keys
Printing Documents with XDPE/400 (9/2001)
F12=Cancel
13-21
XES command generation
Generic packets
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.
How generic packets are processed
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.
Printing Documents with XDPE/400 (9/2001)
13-22
XES command generation
List processing
Use this method to specify such things as overriding specific printer
interface commands.
You can insert XES commands directly into the data stream, before the
banner page, by using list processing. List processing uses a resource list
you create using the Create Xerox Resource List (CRTXRSCLST)
command. A resource list can include the name of an XES generic packet.
Within the generic packet, you specify a file name which references an
ASCII file located in the XDPEFLR/GENXES subfolder.
The contents of an XES generic packet file used by list processing are
downloaded with resources and processed before the banner page is
processed. The specifications are used only once.
Refer to chapter 22 for more information on list processing.
Using the GENXES parameter
You can insert XES commands directly into the data stream, after the
banner page, and before the first printed page of the job, by specifying a
generic packet in the Generic XES packet (GENXES) parameter of the
Create XES Packet (CRTXES) command.
The contents of a generic packet specified in this manner are used either
once for the printed job or once each page of the printed job. You indicate
which method with the Invocation type subparameter of the GENXES
parameter.
The effect of parameters specified here is influenced by the following:
•
The setting of the Order of sequence (SEQUENCE) Monitor Queue
parameter
•
Logical processing specified for the job
•
A generic packet data downloaded with list processing
•
Internal XDPE/400 parameter resets
You can use generic packets in this manner when using either the Direct
or Combined method of processing.
For more information on using the GENXES parameter, refer to “Creating
XES packets” in this chapter.
Printing Documents with XDPE/400 (9/2001)
13-23
XES command generation
Using the FONT printer file parameter
You can insert XES commands directly into the data stream, after the
banner page, and before the first printed page of the job, by specifying a
generic packet using the FONT printer file parameter. The generic packet
name refers to an ASCII file of the same name located in the
XDPEFLR/GENXES subfolder.
The contents of a generic packet file specified in this manner are used
once.
The effect of parameters specified through the FONT printer file
parameter is influenced by the following:
•
The setting of the Order of sequence (SEQUENCE) Monitor Queue
parameter
•
Logical processing specified for the job
•
A generic packet data downloaded with list processing
•
Internal XDPE/400 parameter resets
You can use generic packets in this manner when using either the Indirect
or Combined method of processing.
For more information on using the FONT printer file parameter, refer to
“Modifying printer file parameters” in this chapter.
Creating a generic packet ASCII file
Use one of these methods to create a generic packet:
•
Create the generic packet using the OS/400 SEU. Transform the
source physical file member to an ASCII document using the Copy to
PC document command.
•
Create the generic packet using a PC editor, then store the file in the
XDPEFLR/GENXES shared folder directory.
Printing Documents with XDPE/400 (9/2001)
13-24
14.
14
XES color command generation
This chapter describes color processing and explains how to create and
use color packets for the Xerox 4700 color printer. Color processing
allows you to print documents with color by converting the IBM System
Network Architecture Character Set (SCS) Set Presentation Color (SPC)
commands in a spool file to Xerox 4700 XES color commands.
Color processing is enabled by referencing a Xerox color processing
palette packet. Color processing packets are created by the XDPE/400
Create Xerox Color Palette (CRTXCOL) command, and are referenced by
list processing. The color palette packet, along with the embedded IBM
SCS SPC commands, control the creation of the appropriate XES color
commands. Refer to chapter 22 for detailed information about how to use
the XDPE/400 list processing functions.
When color processing is started, the print data stream is searched for
IBM SCS SPC commands. Each SPC command is replaced by the
appropriate XES Ink Change command. An Assign Ink Color command is
inserted into the print data stream immediately before the first Ink Change
command is inserted. The Assign Ink Color command defines the ink
palette that is used by the subsequent Ink Change commands.
Note these considerations:
•
The Printer model (MODEL) Monitor Queue parameter must be
4700.
•
The File processing mode (PROCMODE) Monitor Queue parameter
must be *PAGE.
•
The Printer mode (MODE) Monitor Queue parameter must be
*XDPM.
•
You can only specify one color palette packet for each job.
•
Color processing cannot be used at the same time as multi-up
printing.
•
When you specify color processing, each character in a print line of
every page is tested to determine if it is the start of an IBM SCS SPC
command.
For more information about how SCS commands are processed in color
processing mode, refer to appendix C, “Processing notes.”
Printing Documents with XDPE/400 (9/2001)
14-1
XES color command generation
Creating XES color packets
Use the Create Xerox Color (CRTXCOL) command to create a color
palette packet in the XDPEFLR/COLOR folder. The values specified in
this command are the values of the colors that are in the XES Assign Ink
Color command.
To convert the IBM SCS SPC color commands to XES color commands,
there is an entry for every color that can be created with the CRTXCOL
command. These color names are defined in the IBM SCS SPC
commands and are available for use with the CRTXCOL command:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Brown
Blue
Red
Pink
Green
Turquoise
Yellow
Orange
Dark blue
Purple
Dark green
Dark turquoise
Mustard
Gray
Default
The IBM SCS SPC color names of white, black, neutral, and medium have
fixed values.
Packet name syntax
XES color packet names must comply with these syntax rules:
•
•
•
•
The name can be from one to eight bytes long
The first byte of the name must be an alphabetic character
Bytes two through eight can be A-Z, 0-9, @, #, or $
Do not enclose the name within quotes or other characters
These are examples of valid XES color packet names:
•
•
•
XCLR300
NMXCLR1
XCL@301A
NOTE: If you type lowercase letters, the name is saved in uppercase.
Printing Documents with XDPE/400 (9/2001)
14-2
XES color command generation
Packet creation procedure
Follow these steps to create a color palette packet:
Step 1.
Enter CRTXCOL and press ENTER. The Create a Color Palette Packet
menu displays.
Create a Color Palette Packet (CRTXCOL)
Type choices, press Enter.
Name, F4 for list
Color Palette packet name: . . .
Bottom
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
F12=Cancel
F13=How to use this display
Step 2.
Enter the name of the color palette packet and press ENTER. The first of
five Create a Color Palette Packet menu displays. You can use these
menus to assign values to the set of color names.
Step 3.
Modify the parameters you want. For more information, refer to “Packet
parameters” and “Packet default color values” in this chapter.
Printing Documents with XDPE/400 (9/2001)
14-3
XES color command generation
The remaining menus are shown on the following pages.
Create a Color Palette Packet (CRTXCOL)
Type choices, press Enter.
Color Palette packet
Brown:
Color model . .
Value #1 . . .
Value #2 . . .
Value #3 . . .
Blue:
Color model . .
Value #1 . . .
Value #2 . . .
Value #3 . . .
Red:
Color model . .
Value #1 . . .
Value #2 . . .
Value #3 . . .
name:
. . .
Name, F4 for list
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*RGB
0.3
0.06
0.017
*RGB, *XGL
-1-+2
-1-+2
-1-+2
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*RGB
0.04026
-.027
.3381
*RGB, *XGL
-1-+2
-1-+2
-1-+2
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*RGB
0.7982
-.019
0
*RGB, *XGL
-1-+2
-1-+2
-1-+2
More...
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
F12=Cancel
F13=How to use this display
Create a Color Palette Packet (CRTXCOL)
Type choices, press Enter.
Pink:
Color
Value
Value
Value
Green:
Color
Value
Value
Value
Turquoise:
Color
Value
Value
Value
model
#1 .
#2 .
#3 .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*RGB
.83266
-.039
.4142
*RGB, *XGL
-1-+2
-1-+2
-1-+2
model
#1 .
#2 .
#3 .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*RGB
-.078
.2521
.041
*RGB, *XGL
-1-+2
-1-+2
-1-+2
model
#1 .
#2 .
#3 .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*RGB
-.1458
.309
.7985
*RGB, *XGL
-1-+2
-1-+2
-1-+2
More...
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
F12=Cancel
Printing Documents with XDPE/400 (9/2001)
F13=How to use this display
14-4
XES color command generation
Create a Color Palette Packet (CRTXCOL)
Type choices, press Enter.
Yellow:
Color
Value
Value
Value
Orange:
Color
Value
Value
Value
Dark blue:
Color
Value
Value
Value
model
#1 .
#2 .
#3 .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*RGB
1.0557
.8865
-.083
*RGB, *XGL
-1-+2
-1-+2
-1-+2
model
#1 .
#2 .
#3 .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*RGB
.9501
.2511
.0048
*RGB, *XGL
-1-+2
-1-+2
-1-+2
model
#1 .
#2 .
#3 .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*RGB
0.009
.07
.555
*RGB, *XGL
-1-+2
-1-+2
-1-+2
More...
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
F12=Cancel
F13=How to use this display
Create a Color Palette Packet (CRTXCOL)
Type choices, press Enter.
Purple:
Color model
Value #1 .
Value #2 .
Value #3 .
Dark green:
Color model
Value #1 .
Value #2 .
Value #3 .
Dark turquoise:
Color model
Value #1 .
Value #2 .
Value #3 .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*RGB
.18
-.03
.394
*RGB, *XGL
-1-+2
-1-+2
-1-+2
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*RGB
-.025
.055
.023
*RGB, *XGL
-1-+2
-1-+2
-1-+2
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*RGB
-.1
.4
.7
*RGB, *XGL
-1-+2
-1-+2
-1-+2
More...
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
F12=Cancel
Printing Documents with XDPE/400 (9/2001)
F13=How to use this display
14-5
XES color command generation
Create a Color Palette Packet (CRTXCOL)
Type choices, press Enter.
Mustard:
Color
Value
Value
Value
Gray:
Color
Value
Value
Value
Default:
Color
Value
Value
Value
model
#1 .
#2 .
#3 .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*RGB
1.02
.72
.16
*RGB, *XGL
-1-+2
-1-+2
-1-+2
model
#1 .
#2 .
#3 .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*RGB
.5
0.0
0.0
*RGB, *XGL
-1-+2
-1-+2
-1-+2
model
#1 .
#2 .
#3 .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*RGB
1.0
0.0
0.0
*RGB, *XGL
-1-+2
-1-+2
-1-+2
Bottom
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
F12=Cancel
F13=How to use this display
Packet parameters
This section describes the color assignment parameters for each color
specified in this packet.
Color model
Value #1
XDPE/400 supports two color models:
•
RGB (red, green, and blue) — Specifies color in terms of the values
associated with the red, green, and blue color component values.
•
XGL (Xerox gray linear) — Specifies the white to black ratio values.
Specifies the first component value if the color model is RGB and
represents the luminance value for red. The values for this parameter
range from -1.5000000 to +2.000000.
If the color model is XGL, this value represents the ratio of black to white.
The values for XGL range from 1.000000 to 0.000000.
Value #2
Specifies the second component value for the RGB color model and
represents the luminance value for green.
The values for this parameter range from -1.5000000 to +2.000000.
Value #3
Specifies the third component value for the RGB color model and
represents the luminance value for blue.
The values for this parameter range from -1.5000000 to +2.000000.
Printing Documents with XDPE/400 (9/2001)
14-6
XES color command generation
Packet default color values
This section lists the default values for the XES color packets.
Brown
Defines the values for brown. The default values are:
Color model: *RGB
Value #1: 0.3
Value #2: 0.06
Value #3: 0.017
Blue
Defines the values for blue. The default values are:
Color model: *RGB
Value #1: 0.04026
Value #2: -0.027
Value #3: 0.3381
Red
Defines the values for red. The default values are:
Color model: *RGB
Value #1: 0.78982
Value #2: -0.019
Value #3: 0.0
Pink
Defines the values for pink. The default values are:
Color model: *RGB
Value #1: 0.83266
Value #2: -0.039
Value #3: 0.4142
Green
Defines the values for green. The default values are:
Color model: *RGB
Value #1: -0.078
Value #2: 0.2521
Value #3: 0.041
Turquoise
Defines the values for turquoise. The default values are:
Color model: *RGB
Value #1: -0.1458
Value #2: 0.309
Value #3: 0.7985
Yellow
Defines the values for yellow. The default values are:
Color model: *RGB
Value #1: 1.0557
Value #2: 0.8865
Value #3: -0.083
Orange
Defines the values for orange. The default values are:
Color model: *RGB
Value #1: 0.9501
Value #2: 0.2511
Value #3: 0.0048
Printing Documents with XDPE/400 (9/2001)
14-7
XES color command generation
Dark blue
Defines the values for dark blue. The default values are:
Color model: *RGB
Value #1: 0.009
Value #2: 0.07
Value #3: 0.555
Purple
Defines the values for purple. The default values are:
Color model: *RGB
Value #1: 0.18
Value #2: -0.03
Value #3: 0.394
Dark green
Defines the values for dark green. The default values are:
Color model: *RGB
Value #1: 0.025
Value #2: 0.055
Value #3: 0.023
Dark turquoise
Defines the values for dark turquoise. The default values are:
Color model: *RGB
Value #1: -0.1
Value #2: 0.4
Value #3: 0.7
Mustard
Defines the values for mustard. The default values are:
Color model: *RGB
Value #1: 1.02
Value #2: 0.72
Value #3: 0.16
Gray
Defines the values for gray. The default values are:
Color model: *XGL
Value #1: 0.5
Value #2: 0.0
Value #3: 0.0
Default
Specifies the attributes of the default color. The default values are:
Color model: *XGL
Value #1: 1.0
Value #2: 0.0
Value #3: 0.0
Printing Documents with XDPE/400 (9/2001)
14-8
XES color command generation
IBM color command names
For every IBM SCS SPC color command there is an IBM-assigned color
name. Table 14-1 shows the mapping of the one- and two-byte color
codes that make up part of the SPC commands their corresponding IBM
color names. Table 14-1 also lists the CRTXCOL keywords associated
with the color, the default color model, and the color values.
Note these considerations:
Table 14-1.
•
The color values for white and black are neutral. They are not in the
CRTXCOL command menu, because they are not changeable.
•
Except for dark turquoise, the default CRTXCOL command colors
match the colors of the 4700 II XES Palette of IBM Screen Colors.
•
There is no dark turquoise color in the 4700 II XES Palette of IBM
Screen Colors; a substitute color is used.
Color command names
IBM SPC color code
(hexadecimal value)
IBM color name
CRTXCOL
keyword
4700 RGB
values
4700 XGL
values
One byte: F8
Two byte: 000A
Orange
ORANGE
0.9501
0.2511
0.0048
Two byte: 0009
Dark blue
DRKBLUE
0.009
0.07
0.555
Two byte: 000B
Purple
PURPLE
0.18
-0.03
0.394
Two byte: 000C
Dark green
DRKGREEN
0.025
0.055
0.023
Two byte:000D
Dark turquoise
DRKTURQ
-0.1
0.4
0.7
One byte: F7
Neutral
1.0
Two byte: 0000,0008, or FF07
Black
1.0
Two byte: 000E
Mustard
MUSTARD
Two byte: 000F
Gray
GRAY
0.5
Two byte: FF00, FFFF
Current default
DEFAULT
1.0
One byte: F9
Two byte: 0007,FF08
White/color of medium
One byte: F0
Two byte: 0010
Brown
Printing Documents with XDPE/400 (9/2001)
1.02
0.72
0.16
0.0
BROWN
0.3
0.06
0.017
14-9
XES color command generation
Table 14-1.
Color command names (Continued)
IBM SPC color code
(hexadecimal value)
IBM color name
CRTXCOL
keyword
4700 RGB
values
One byte: F1
Two byte: 0001, FF)!
Blue
BLUE
0.04026
-0.027
0.3381
One byte: F2
Two byte: 0002, FF02
Red
RED
0.7982
-0.019
0.0
One byte: F3
Two byte: 0003, FF03
Pink/magenta
PINK
08.3266
-0.039
0.4142
One byte: F4
Two byte: 0004, FF04
Green
GREEN
-0.078
0.2521
0.041
One byte: F5
Two byte: 0005, FF05
Turquoise/Cyan
TURQ
-0.1458
0.309
0.7985
One byte: F6
Two byte: 0006, FF06
Yellow
YELLOW
1.0557
0.8865
-0.083
Printing Documents with XDPE/400 (9/2001)
4700 XGL
values
14-10
XES color command generation
Changing XES color packets
Use the Change a Color Palette Packet (CHGXCOL) command to modify
the XES color packet that you created with the CRTXCOL command.
NOTE: The values displayed on the CHGXCOL menus represent the
values you specified in the Options field of the CRTXCOL menus.
Follow these steps to change an XES color packet:
Step 1.
Enter CHGXCOL and press ENTER. The Change a Color Palette Packet
menu displays.
Change a Color Palette Packet (CHGXCOL)
Type choices, press Enter.
Color Palette packet name:
. . .
Name, F4 for list
Bottom
F3=Exit F4=Prompt
F24=More keys
Step 2.
F5=Refresh
F12=Cancel
F13=How to use this display
Enter the name of the color palette packet you want to change and press
ENTER.
The first of five Change a Color Palette Packet menus displays. You can
use these menus to reassign values to a set of color names.
The parameters are the same as the Create a Color Palette Packet
menus, but reflect any values you modified when you created the packet.
See “Creating XES color packets” earlier in this chapter for information on
the parameters.
Printing Documents with XDPE/400 (9/2001)
14-11
XES color command generation
Starting XES color processing
Follow these steps to start color processing for your job:
Step 1.
Log on to the system.
Step 2.
Add XDPE to the library list.
Step 3.
Create a color palette packet or modify an existing color palette packet to
use when printing your job.
This palette supplies the colors that Monitor Queue uses to convert the
IBM SCS SPC commands in your print data stream to XES color
commands.
Step 4.
Use the OS/400 SEU editor to create a resource download or processing
record list file.
The resource record list file should include the color palette packet entry
used when processing the print job (for example, COLOR/Name of your
color palette).
Step 5.
Enter CRTXRSCLST to convert the resource record list file that you
created in step 4 into the appropriate format to be used as a download or
processing list. Refer to chapter 22 for more information on list
processing.
Step 6.
Enable the list process by entering an at sign (@) in the Packet field of the
spool file to be printed, followed by the name of the list.
Step 7.
Start Monitor Queue with these parameters selected:
•
•
•
Printer option: 4700
Printer mode: *XDPM
File processing mode: *PAGE
Select any other options that are appropriate for your requirements.
Step 8.
Enter 6 in the Option field of the spool file and press ENTER.
This changes the status of your job to ready (*RDY) and releases the
spooled file for printing.
When Monitor Queue processes the spool file, the IBM SCS SPC
commands in the spool file are replaced with Xerox 4700 XES color
commands.
Printing Documents with XDPE/400 (9/2001)
14-12
15.
15
PCL command generation
This chapter describes how to create and insert PCL control commands
into the print data stream.
Using PCL control commands
PCL command generation is restricted depending on whether Monitor
Queue is in *JOB or *PAGE file processing mode. Use one of these
methods for generating PCL commands:
None
Indirect method
You can use the Always generate (ALWAYS) Monitor Queue parameter
to print a job without inserting any PCL control commands that affect
document formatting.
In the Indirect method, Monitor Queue maps printer file parameters to
PCL control commands and inserts the commands into the print data
stream. The spool file is then released to the printer writer.
Direct method
In the Direct method, you first create a file of PCL control commands,
called a PCL packet. XDPE/400 inserts these PCL control commands into
the data stream before releasing the spool file to the printer writer.
Combined method
In the Combined method, you create a file of PCL control commands and
Monitor Queue then maps the spool file attributes to these commands.
XDPE/400 inserts both sets of PCL commands into the print data stream
before releasing the spool file to the printer writer.
Printing Documents with XDPE/400 (9/2001)
15-1
PCL command generation
File processing mode (PROCMODE) restriction
The File processing mode (PROCMODE) Monitor Queue parameter
determines how commands are inserted into your jobs. When
PROCMODE is *JOB, XDPE/400 maintains the prior XDPE/400 release
level with a reduced level of functionality. When *PAGE is specified for
PROCMODE, XDPE/400 uses the full level of functionality. Some
XDPE/400 commands are ineffective in *JOB mode.
This table shows the values that are allowed with the File processing
mode (PROCMODE) Monitor Queue parameter.
Printer file parameters
*JOB
*PAGE
CHRID
No
Yes
COPIES
Yes
Yes
DRAWER
No
Yes
DUPLEX
Yes
Yes
FONT (identifier)
No
Yes
FORMFEED
Yes (only front shift)
Yes
FRONTMGN
Yes
Yes
BACKMGN
No
Yes
FRONTOVL
Yes
Yes
BACKOVL
No
Yes
LPI
No
Yes
MULTIUP
No
Yes
PAGRTT
No
Yes
PAGESIZE
No
Yes
Printing Documents with XDPE/400 (9/2001)
15-2
PCL command generation
Indirect method
The Indirect method creates PCL commands from spool file attributes.
When an OS/400 application program or print utility opens a printer file for
output, a spool file is created. The attributes of that spool file are created
from the printer file parameters.
Before the spool file is released to the printer writer, XDPE/400 processes
the spool file and creates PCL commands.
This table shows printer file parameters that map to the XDPE/400 PCL
features (when you press F11 at the CRTPRTF and CHGPRTF command
menus).
IBM OS/400
printer file parameters
XDPE/400 PCL features
COPIES
Number of copies
DRAWER
Paper tray selection
DUPLEX
Duplex mode selection
FONT (identifier)
Generic PCL packet
FORMFEED
Predrilled paper shift
FRONTMGN/BACKMGN
Margin setting
FRONTOVL/BACKOVL
Form invocation
LPI
Line spacing per inch
MULTIUP/PAGRTT
Multi-up printing
PAGESIZE
NPS printer tray selection
NOTE: To prevent conflicts with the printer writer, which also
processes spool file attributes, XDPE/400 converts the spool file
attributes to their default values. The spool file is then released to the
printer writer.
Printing Documents with XDPE/400 (9/2001)
15-3
PCL command generation
Modifying printer file parameters
This section describes the functions and use of the printer file parameters
to define PCL parameters. You can use any of these commands to modify
the printer file parameters:
•
•
•
CRTPRTF to create a printer file
CHGPRTF to modify an existing printer file
OVRPRTF to override an existing printer file
NOTE: For instructions on how to use the CRTPRTF, CHGPRTF, and
OVRPRTF commands, refer to OS/400 CL Reference and OS/400
Printer Device Programming.
COPIES
DRAWER
Specifies the number of copies to print. Enter the number of copies you
want from 1 to 255 in the COPIES parameter. XDPE/400 will retransmit
the enhanced user spool file the required number of times.
Specifies the source drawer from which paper is fed into the printer. The
XDPE/400 global values area contains the mapping of these IBM values
to Xerox paper trays. If a printer does not support a tray, the default tray
will automatically be used. You can use these values:
•
•
•
•
•
•
•
•
DUPLEX
1 — XDPE/400 global value for drawer 1
2 — XDPE/400 global value for drawer 2
3 — XDPE/400 global value for drawer 3
4 — XDPE/400 global value for drawer 4
5 — XDPE/400 global value for drawer 5
6 — XDPE/400 global value for drawer 6
*SAME — Leaves the value unchanged
*E1 — XDPE/400 global value for the envelope drawer
Specifies whether to print the output on one side (simplex) or on both
sides (duplex) of the page. You can use these values:
•
*YES — XDPE/400 generates a PCL duplex control command
•
*TUMBLE — XDPE/400 generates a PCL tumble duplex control
command
•
*NO — XDPE/400 generates a PCL simplex control command
For duplexing in landscape orientation, refer to the Duplex standard
(DUPLEXSTD) global value in chapter 6 of Section Two: Installing and
Customizing XDPE/400.
NOTE: If you are unable to print in duplex with an NPS printer, refer
to chapter 26 for instructions on how to correct the problem.
Printing Documents with XDPE/400 (9/2001)
15-4
PCL command generation
FONT (identifier)
Identifies a generic ASCII PCL packet containing ASCII data. XDPE/400
looks for a generic packet in the XDPEFLR/GENPCL directory. The ASCII
file is wrapped by XDPE/400 in one or more ASCII Transparency SCS
commands and is merged with the spool file output. Escape characters
and all additional PCL syntax rules must be followed. This attribute is only
used for generic packet processing if the Order of Sequence
(SEQUENCE) parameter is set to *ATTRIB; if SEQUENCE is set to
*PACKET, XDPE/400 will not recognize a generic packet specified
through this FONT attribute.
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.
For more information on how generic packets are processed, refer to
“Generic packets” later in this chapter.
FORMFEED
Generates the page shift values for predrilled paper. Use of the
FORMFEED spool file attribute is different from the IBM use of the option.
The page shift values are specified to the printer through the XDPE/400
global values user interface. This table shows the FORMFEED-to-PCL
command mapping.
Spool file attribute
PCL command
*DEVD
No command generated
*CONT
No command generated
All other values
Left registration with XDPE/400 global values
The XDPE/400 global values for front long and back long side offsets are
converted from dots to decipoints, and a Left Offset Registration PCL
command is used.
FRONTMGN
Specifies the offset, down and across, of the origin from the edge on the
front side of the paper. The offset values are specified with the Unit of
measure (UOM) parameter in the printer file. XDPE/400 generates an
MRP interface command (when using the *INTERNAL interface) or PCL
left and top margin commands (when using the *PCSUPP interface),
depending on the interface type.
The Offset down values are:
•
0 — No offset origin occurs.
•
offset-down — Specifies the offset of the origin from the top of the
page. If *CM is specified, the valid values range from 0 through
57.79. If *INCH is specified, the valid values range from 0 through
22.75. If a value is not specified, the default setting of 0,0 is used.
The Offset across values are:
•
0 — No offset origin occurs.
•
offset-across — Specifies the offset of the margin from the left side of
the page. If *CM is specified, the valid values range from 0 through
57.79. If *INCH is specified, the valid values range from 0 through
22.75. If a value is not specified, the default setting of 0 is used.
Printing Documents with XDPE/400 (9/2001)
15-5
PCL command generation
BACKMGN
Specifies the offset, down and across, of the origin from the edge on the
back side of the paper. The offset values are specified with the Unit of
measure (UOM) parameter in the printer file. XDPE/400 generates an
MRP interface command (when using the *INTERNAL interface) or PCL
left and top margin commands (when using the *PCSUPP interface),
depending on the interface type. You can use this value:
•
*FRONTMGN — Uses the offsets that are specified on the
FRONTMGN parameter
The Offset down values are:
•
0 — No offset origin occurs.
•
offset-down — Specifies the offset of the origin from the top of the
page. If *CM is specified, the valid values range from 0 through
57.79. If *INCH is specified, the valid values range from 0 through
22.75. If a value is not specified, the default setting of 0,0 is used.
The Offset across values are:
•
0 — No offset origin occurs.
•
offset-across — Specifies the offset of the margin from the left side
of the page. If *CM is specified, the valid values range from 0
through 57.79. If *INCH is specified, the valid values range from 0
through 22.75. If a value is not specified, the default setting of 0 is
used.
LPI
Specifies the line spacing setting on the printer, in lines per inch. You can
use values 3, 4, 6 (default), 7.5, 8, 9, and 12.
FRONTOVL
Activates a PCL macro on all odd page sides. The macro body name can
be one to eight characters in length and must represent a file that is in the
XDPEFLR/PCLMAC directory. The .X extension (required for earlier
XDPE/400 releases) for the macro name in the FRONTOVL parameter is
optional. The PCL commands that are in the macro body file must conform
to the rules of the PCL language.
You must delete specific commands from PCL forms, macro bodies, or
.PRN files that are created from a package, such as ELIXIR, before they
can be used as overlays on PCL printers. This table lists the PCL
commands that must be deleted.
PCL commands that
must be deleted
Meaning
&I#P
Page length
(esc) &I#A
Page size
(esc) &I#O
Page orientation
(esc) &I#H
Paper source
(esc) %-12345X
Universal Exit Language (UEL)
(esc) &r#F
Flush pages
(esc) &I#S
Simplex/Duplex
(esc) E
Printer reset
X'OC'
Page eject
Printing Documents with XDPE/400 (9/2001)
15-6
PCL command generation
The macro body is automatically downloaded as macro ID 82. Macro 82
is called for all odd numbered pages.
Enter *NONE in the FRONTOVL parameter if you do not want to use an
electronic form.
BACKOVL
Activates a PCL macro on all even page sides. The macro body name can
be one to eight characters in length and must represent a file that is in the
XDPEFLR/PCLMAC directory. The .X extension (required for earlier
XDPE/400 releases) for the macro name in the FRONTOVL parameter is
optional. The PCL commands that are in the macro body file must conform
to the rules of the PCL language.
The macro body is automatically downloaded as macro ID 83. Macro 83
is called for on all even numbered pages.
If the back overlay is *FRONTOVL, the front overlay macro 82 is used,
and additional macros are not loaded.
MULTIUP/PAGRTT
MULTIUP prints multiple pages of output on one physical page. You can
use these values:
•
•
•
1 — One page of output is printed on each physical page
2 — Two pages of output are printed on each physical page
4 — Four pages of output are printed on each physical page
PAGRTT specifies the degree of text rotation in respect to the way the
page is loaded in the printer.
The MULTIUP and PAGRTT parameters work together to create the
output you want and are explained in detail in chapter 25, “Multi-up
printing.”
PAGESIZE
Specifies the length and width of the page to be printed.
The page size is determined by a combination of the Lines per inch (LPI),
Characters per inch (CPI), and Page size (PAGESIZE) printer file
parameters. For example, a CPI of 10 and a Width (positions per line) of
85 will produce a page width of 8.5 inches; and an LPI of 6 with a Length
(lines per page) of 66 will produce a page length of 11 inches. With these
settings, XDPE/400 will specify USLetter as the page size of the job.
NOTE: The effect of this parameter varies depending on the PCL
printer used. Refer to “Xerox PCL printer tray selection” at the end of
this chapter for more information on tray selection methods for the
different PCL printers.
Printing Documents with XDPE/400 (9/2001)
15-7
PCL command generation
Direct method
With the Direct method, a user-created PCL packet is used by your
Monitor Queue session to create printer-specific PCL commands, which
are then inserted into the spool file. With this method, the spool file
attributes that are used with the Indirect method are ignored. Refer to
chapter 8 for more information about configuring XDPE/400 for Direct
processing.
Default Xerox PCL packet
XDPE/400 allows you to specify the action to take when the system does
not locate a Xerox PCL packet. This is controlled using the Pass through
option (PASSTHRU) Monitor Queue parameter.
When specified, the Xerox PCL packet called DEFAULT is invoked if the
requested packet is not found, or if *FORMTYPE is specified for the
Packet data (PACKETDATA) Monitor Queue parameter, and if the Form
type spool file attribute is *STD. You must create the default packet before
this feature can be used. If this packet is not found, the Default packet
option (DFTPKT) Monitor Queue parameter specifies the next action to
take.
For more information on default packet processing, see “Setting the
Packet data (PACKETDATA) parameter” in chapter 10.
Printing Documents with XDPE/400 (9/2001)
15-8
PCL command generation
Combined method
The Combined method is a combination of the Direct method and Indirect
method of Xerox PCL packet generation. The system creates PCL
commands using a Xerox PCL command packet from the XDPEFLR/PCL
folder and the PCL control commands created from the spool file
attributes.
Application order of PCL control commands
When Monitor Queue generates PCL control commands in Combined
mode, the system compares the commands from the XDPEFLR/PCL
folder with the commands generated from the spool file attributes. The
first occurrence of a duplicate command is deleted and is not written to
the spool file.
Monitor Queue controls the order in which the PCL control commands are
received. Monitor Queue specifies whether to use commands generated
from the spool file attributes or PCL control commands from the
XDPEFLR/PCL folder. This mechanism is specified by the Order of
sequence (SEQUENCE) Monitor Queue parameter.
If the Order of sequence parameter is *ATTRIB, Monitor Queue uses the
PCL control commands retrieved from the XDPEFLR/PCL folder if a
parameter is specified by both the spool file attributes and the folder. This
means that PCL control commands from the XDPEFLR/PCL folder
override the PCL control commands created from the spool file attributes.
If the Order of sequence parameter is *PACKET, Monitor Queue uses the
PCL control commands whenever a parameter is specified by both the
folder file and the spool file attributes. This means that PCL control
commands created from spool file attributes override PCL control
commands from the XDPEFLR/PCL folder.
Printing Documents with XDPE/400 (9/2001)
15-9
PCL command generation
Creating and managing Xerox PCL packets
Use the Xerox PCL packet creation commands to create Xerox PCL
commands that are generated by the XDPE/400 Monitor Queue. The
packets can be used in Direct mode or Combined mode. These PCL
packet creation commands are available:
•
•
•
•
CRTXPCL (Create Xerox PCL Packet)
CHGXPCL (Change Xerox PCL Packet)
DLTXPCL (Delete Xerox PCL Packet)
DSPXPCL (Display Xerox PCL Packet)
The following sections show you how to use these commands with the
available menus.
Creating Xerox PCL packets
Use the Create Xerox PCL Packet (CRTXPCL) command to specify these
options:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Printer control packet name (PCL)
Print on both sides of sheet (DUPLEX)
Pre-drilled paper (DRILLED)
Source tray (TRAY)
Page orientation (ORIENT)
Margin setting (MARGIN)
Font selection by attributes (FONT)
Page font selection by ID (FONTID)
Font selection by alphanumeric font name (FONTNAME)
PCL macro (PCLMAC)
Generic PCL (GENPCL)
Resource list name (RSCLIST)
Duplex side (DSIDE)
Lines per inch (LPI)
MRP internal interface mode (MRP)
Number of pages per side (PAGESPSIDE)
Multi-up packet name (PCLMUP)
Paper type (PAPERTYPE)
Job ticket processing (XTICKET)
Packet name syntax
Xerox PCL packet names must comply with these syntax rules:
•
•
•
•
The name can be from one to eight bytes long
The first byte of the name must be an alphabetic character
Bytes two through eight can be A-Z, 0-9, @, #, or $
Do not enclose the name within double quotes or other characters
These are examples of valid PCL packet names:
•
•
•
PCLTXT
NAME@PCL
NMPCLA12
NOTE: If you type lowercase letters, the name is saved in uppercase.
Printing Documents with XDPE/400 (9/2001)
15-10
PCL command generation
Packet creation procedure
Follow these steps to create a Xerox PCL packet:
Step 1.
Enter CRTXPCL and press ENTER. The Create Xerox PCL Packet menu
displays.
Create Xerox PCL Packet (CRTXPCL)
Type choices, press Enter.
Printer control packet name . . .
Name, F4 for list
Bottom
F3=Exit F4=Prompt F5=Refresh F10=Additional parameters
F13=How to use this display F24=More keys
F12=Cancel
NOTE: During command prompting, any of the current values that are
in the additional parameters area are given a conditional prompt.
Press F10 to display additional values. Press F9 to display fields
without values or to display all fields.
Step 2.
Enter the name of the Xerox PCL packet and press ENTER. The Create
Xerox PCL Packet menu displays additional parameters in three screens.
Printing Documents with XDPE/400 (9/2001)
15-11
PCL command generation
Step 3.
Modify the parameters you want, following the conventions described in
the next section, and press ENTER.
Create Xerox PCL Packet (CRTXPCL)
Type choices, press Enter.
Printer control packet name .
Print on both sides of sheet.
Pre-drilled paper . . . . . .
Source tray . . . . . . . . .
Page orientation . . . . . .
.
.
.
.
.
*NONE
*NONE
*NONE
*NONE
Name, F4 for list
*YES, *NO, *TUMBLE, *NONE
*YES, *NO, *NONE
*TRAY1, *TRAY2, *TRAY3...
*PORT, *LAND, *IPORT...
Additional parameters
Margin setting:
Page size .
Top margin .
Text length
Left margin
Right margin
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*NONE
*NONE
*NONE
*NONE
*NONE
*EXEC, *LETTER, *LEGAL...
1-1000, *NONE
1-1000, *NONE
1-1000, *NONE
1-1000, *NONE
More...
F3=Exit
F4=Prompt
F24=More keys
F5=Refresh
F12=Cancel
F13=How to use this display
Create Xerox PCL Packet (CRTXPCL)
(CRTXPCL )
Type choices, press Enter.
Font selection by attributes:
Symbol set . . . . . . . *NONE
Spacing . . . . . . . . . *NONE
Pitch . . . . . . . . . . *NONE
Height . . . . . . . . . *NONE
Style . . . . . . . . . . *NONE
Weight. . . . . . . . . . *NONE
Typeface. . . . . . . . . *NONE
Page font selection by ID . *NONE
Font name. . . . . . . . . . *NONE
PCL macro:
Macro name . . . . . . . . *NONE
Invocation type. . . . . . *OVERLAY
Generic PCL:
Packet name . . . . . . . *NONE
Invocation type. . . . . . *JOB
Character value, *ROMAN8...
*FIXED, *PS, *NONE
0.1-576, *NONE
0.25-999.75, *NONE
*UPRIGHT, *ITALIC...
*LIGHT, MEDIUM, BOLD...
*LP, *PICA, *ELITE...
1-32767, *NONE
Name, F4 for list
*EXEC, *CALL, *AUTO...
Name, F4 for list
*JOB, *PAGE
More...
F3=Exit
F4=Prompt
F24=More keys
F5=Refresh
Printing Documents with XDPE/400 (9/2001)
F12=Cancel
F13=How to use this display
15-12
PCL command generation
Create Xerox PCL Packet (CRTXPCL)
Type choices, press Enter.
Resource list name . . . . .
Duplex side . . . . . . . .
Lines per inch . . . . . . .
MRP internal interface mode
Number of pages per side . .
Multi-up packet name . . . .
Paper type . . . . . . . . .
Job ticket processing:
Extended ticket name . . .
Suppress PCL . . . . . . .
F3=Exit
F4=Prompt
F24=More keys
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*NONE
*NONE
*NONE
*NONE
*NONE
*NONE
*NONE
Name, F4 for list
*NEXT, *FRONT, *BACK, *NONE
00.10-99.99, *NONE
*MRP0, *MRP5, *MRP6, *NONE
1-32767, *NONE
Name, F4 for list
. .
. .
*NONE
*NO
Name, F4 for list
*NO, *YES
F5=Refresh
F12=Cancel
Bottom
F13=How to use this display
Packet parameters
Print on both sides of sheet
(DUPLEX)
Specifies whether to print on both sides or on one side of a sheet. With
XDPE/400 logical processing, packet switching on a page-to-page level
can allow for transitions to different duplex settings. You can use these
values:
•
•
•
•
*YES — Specifies duplex printing
*TUMBLE — Specifies tumble duplex printing
*NO — Specifies simplex printing
*NONE — Does not use the option
For duplexing in landscape orientation, refer to the Duplex standard
(DUPLEXSTD) global value in chapter 6 of Section Two: Installing and
Customizing XDPE/400.
NOTE: If you are unable to print in duplex with an NPS printer, refer
to chapter 26 for instructions on how to correct the problem.
Printing Documents with XDPE/400 (9/2001)
15-13
PCL command generation
Pre-drilled paper (DRILLED)
Allows you to make variations in the left margin for predrilled paper. The
XDPE/400 global values for the front and back long edges are converted
to decipoints and are used with a PCL Left Offset Registration command.
You can use these values:
•
*NO — Disables the shift option.
•
*YES — Enables the shift option. The system uses the shift value
you specified for the Predrilled shift support (SHIFT) global value.
•
*NONE — Does not use the option.
This parameter, combined with the source tray parameter, can be useful
when you are changing packets from page to page to increase the range
application.
Source tray (TRAY)
Selects the correct paper tray on a job or page level. If a printer does not
support a tray, the default tray will automatically be used. Tray selection
may vary depending on your printer setup.
NOTE: This parameter has no effect on NPS, DocuSP, or generic
printers. The effect of this parameter varies depending on the PCL
printer used. See “Xerox PCL printer tray selection” at the end of this
chapter for more information on tray selection methods for the
different PCL printers.
The DC265LP and DC255LP printers use *TRAY5 or *E for the Multi
Bypass Feeder (MBF).
Page orientation (ORIENT)
Allows page orientation changes. The PCL printer selects a rotated font
for the orientation. You can use these values:
•
*PORT — Selects portrait orientation.
•
*LAND — Selects landscape orientation.
•
*IPORT — Selects inverse portrait orientation.
•
*ILAND — Selects inverse landscape orientation.
•
*COR — Selects Computer Output Reduction. COR reduces output
to fit on a letter-sized page in landscape orientation. A 70%
reduction in the logical page size is accomplished with these
changes:
—
Substitution of smaller fonts:
•
•
•
•
14
15
20
27
pitch
pitch
pitch
pitch
for
for
for
for
10
12
15
17
pitch
pitch
pitch
pitch
fonts
fonts
fonts
fonts
—
Reduction of vertical line spacing to 70% of full size.
—
0.5-inch top and left margins.
Refer to the i-data Twinax XES/PCL Interface Controller for Xerox
Printers Programmer’s Guide for more information about this feature.
•
*NONE — Does not use the option.
Printing Documents with XDPE/400 (9/2001)
15-14
PCL command generation
Margin setting (MARGIN)
Assigns page margin settings. For selected Xerox printers, this parameter
is also used for paper selection:
•
For N32 and N24 printers, MARGIN works in conjunction with the
Paper type (PAPERTYPE) and Source tray (TRAY) packet
parameters, as well as with the physical paper size and paper type
loaded in the printer. If both MARGIN and PAPERTYPE are
specified, the paper tray you have defined on the printer for that
paper type must be the size specified by MARGIN.
•
For DC265LP and DC255LP printers, MARGIN works in conjunction
with the Source tray (TRAY) packet parameter, as well as with the
physical paper size and paper type loaded in the printer.
You can use these values:
•
Page size — Specifies the physical size of the page, which limits the
logical page. The margins and the text length are set to the defaults
for the size of the paper. Any unprinted data is printed. You can use
these values:
*EXEC — Specifies executive size paper (7.5 by 10.5 inches)
*LETTER — Specifies letter size paper (8.5 by 11 inches)
*LEGAL — Specifies legal size paper (8.5 by 14 inches)
*LEDGER — Specifies ledger size paper (11 by 17 inches)
*A4 — Specifies A4 size paper (210 by 297 mm)
*A3 — Specifies A3 size paper (297 by 420 mm)
*NONE — Does not use the option
The NPS and DocuSP printers use automatic tray selection based on
the page size.
•
Top margin — Sets the distance between the top of the printable
area and the top of the text, regardless of the paper orientation. The
top margin is defined as numbers of lines, or *NONE. You must
specify a value for Page orientation (ORIENT) in conjunction with
this parameter.
•
Text length — Sets the number of lines within which text may be
printed. Defined as numbers of lines, or *NONE.
•
Left margin — Sets the distance between the left edge of the text
and the left edge of the printable area, regardless of paper
orientation. The left margin is set as a column number, or *NONE.
You must specify a value for Page orientation (ORIENT) in
conjunction with this parameter.
•
Right margin — Sets the distance between the right edge of the text
and the right edge of the printable area, regardless of the paper
orientation. This right margin is set as a column number. The width
of the column is determined by the Horizontal Motion Index set by
the printer. *NONE can also be specified.
If margin errors are encountered when printing in *COMBINED with
*ATTRIB, refer to chapter 26, “Troubleshooting,” for instructions on
how to correct the problem.
Printing Documents with XDPE/400 (9/2001)
15-15
PCL command generation
Font selection by attributes
(FONT)
Selects the initial page font to be used for the page by PCL font attributes.
You must explicitly specify all seven attributes to make sure the font you
want matches a font that is resident on the printer. If an exact match is not
found, the default printer font is used.
The font selected is determined by the printer based on these attributes:
•
Symbol Set — An alphanumeric sequence representing a PCL
symbol set assignment. Values can be any character string or one of
these selected fixed values:
*ROMAN8 — Specifies the Roman 8 Symbol Set
*ISO8859L1 — Specifies the ISO 8859 Latin 1 Symbol Set
*PC8 — Specifies the PC 8 Symbol Set
*EURO1 — Specifies the Latin 1 Symbol Set with euro symbols for
western Europe
*EURO2 — Specifies the Latin 2 Symbol Set with euro symbols for
eastern Europe
*EURO3 — Specifies the Latin 5 Symbol Set with euro symbols for
Turkey
*NONE — Does not use the option
name — Specifies the actual PCL symbol set value as defined in the
PCL 5 Comparison Guide. For example, the value for the Latin/Cyrillic
symbol set containing the euro currency symbol is 3R.
•
Spacing — Sends a request to the printer for a proportionally-spaced
or fixed-pitch font. If proportional spacing is selected, but a
proportionally-spaced font is not available, the printer will designate
a fixed-pitch font. You can use these values:
*FIX — Specifies a fixed-pitch spaced font
*PS — Specifies a proportionally-spaced font
*NONE — Does not use the option
•
Pitch — Sends a request to the printer for the character spacing of
fixed-pitch fonts in characters per inch (CPI). If the pitch requested is
unavailable, the printer searches for the next larger size, or if not
available, the next smaller size. The value can be any decimal
number within the range 0.10 through 576 or *NONE.
•
Height — Sends a request to the printer for the character height of
the font in points (in 1/72nds of an inch). The value can be any
decimal number within the range 0.25 through 999.75 or *NONE.
•
Style — Sends a request for the posture of a character. You can use
these values:
*UPRIGHT — Specifies the upright font style
*CONDENSED — Specifies the condensed font style
*ITALIC — Specifies the italic font style
*ICOND — Specifies the condensed italic font style
*EXCOND — Specifies the extra condensed font style
*EXPAND — Specifies the expanded font style
*NONE — Does not use the option
Printing Documents with XDPE/400 (9/2001)
15-16
PCL command generation
•
Weight — Sends a request to the printer for the degree of bolding.
You can use these values:
*LIGHT — Specifies the light weight typeface
*MEDIUM — Specifies the medium weight typeface
*BOLD — Specifies the bold weight typeface
*EXBOLD — Specifies the extra bold weight typeface
*BLACK — Specifies the black weight typeface
*NONE — Does not use the option
•
Typeface — Sends a request to the printer for the design of the font.
Refer to the documentation supplied with your printer for more
information. You can use these values:
*LP — Specifies Line Printer
*PICA — Specifies Pica
*ELITE — Specifies Elite
*COUR — Specifies Courier
*HELV — Specifies Helvetica
*GOTHIC — Specifies Letter Gothic
*SCRIPT — Specifies Script
*PRESTIGE — Specifies Prestige (PElite)
*TIMERM — Specifies Times Roman
*UNIVERS — Specifies Universe
*ARIAL — Specifies Arial
*NONE — Does not use the option
NOTE: Not all fonts resident on your printer may contain the
euro symbol. Refer to the documentation supplied with your
printer for more information.
Page font selection by ID
(FONTID)
Allows you to use PCL fonts that are loaded on the printer.
The font can be downloaded and assigned to a font ID by an XDPE/400
Download PCL Fonts Resource command. The value can be any decimal
number between 1 and 32767, or *NONE.
The font can also be downloaded and assigned to a font ID by the Monitor
Queue list processing. Fonts downloaded in a Monitor Queue-processed
resource list are sequentially numbered starting at 8000 plus the font
position in the resource list. When assigning ID numbers, only fonts and
macros are counted in the resource list, and they are counted
sequentially, regardless of resource type. If this method is used to
download fonts, the font ID must be specified in the PCL packet.
Subsequent Monitor Queue resource list downloads will overwrite
like-numbered fonts from previous jobs.
NOTE: ID numbers reference fonts stored in the printer’s dynamic
memory. These fonts will be deleted when the printer is powered off.
Printing Documents with XDPE/400 (9/2001)
15-17
PCL command generation
Font selection by
alphanumeric font name
(FONTNAME)
PCL macro (PCLMAC)
Allows for the invocation of a pre-loaded font. Downloaded alphanumeric
fonts are permanently stored on the printer’s hard drive. They will be
preserved even when the printer is powered off. This parameter applies
to the N32 and N24 printers only. You can use these values:
•
name — Specifies the name assigned to the loaded font. The name
can be any alphanumeric value between 1 and 20 characters in
length.
•
*NONE — No command is generated.
Allows you to automatically download and activate a macro body that is in
the shared XDPEFLR/PCLMAC folder. The macro ID that is assigned and
used depends on the placement of the packet:
•
If a Xerox PCL packet is activated at the prepend time from the spool
file packet data location, macro 84 is assigned and used as the
macro in the Xerox PCL packet.
•
Macro 85 is used for page level packets at the top of the page.
•
Macro 86 is used for page level packets placed at the bottom of the
page.
If the name of the macro is numeric, XDPE/400 assumes that the macro
is permanently loaded on the printer. The numeric value is used as the
macro ID on activated PCL macro commands.
Macro bodies that are downloaded with the Monitor Queue list processing
are temporary macros that are accessible with the job that is downloaded
with them. To download macro bodies using Monitor Queue list
processing, see the Generic PCL (GENPCL) PCL packet parameter for
more information.
You must delete specific commands from PCL forms, macro bodies, or
.PRN files that are created from a package, such as ELIXIR, before they
can be used as overlays on PCL printers. This table lists the PCL
commands that must be deleted.
PCL command that must
be deleted
Meaning
&I#P
Page length
(esc) &I#A
Page size
(esc) &I#O
Page orientation
(esc) &I#H
Paper source
(esc) %-12345X
UEL (Universal Exit Language)
(esc) &r#F
Flush pages
(esc) &I#S
Simplex/duplex
(esc) E
Printer reset
X'0C'
Page eject
Printing Documents with XDPE/400 (9/2001)
15-18
PCL command generation
You can specify how to activate the macro using the Invocation type
subparameter:
•
*EXEC — Executes the macro (changing the page environment).
This value enables the PCL Invocation Type 2.
•
*CALL — Calls the macro (saving the page environment). This value
enables the PCL Invocation Type 3.
•
*AUTO — Enables the macro for automatic overlay on every page
(saves the page environment) of a job. This value enables the PCL
Invocation Type 4. If *AUTO is specified, the macro will be used on
every page of the job it is specified for regardless of any other macro
commands generated by other packets during the course of the job.
•
*OVERLAY — Calls the macro on every page until a new macro is
selected. If a macro is invoked by another packet during the course
of the job, that new macro is used. This value executes as a
modified PCL Invocation Type 3; which is an XDPE-enhanced
function.
Both *AUTO and *OVERLAY automatically invoke a macro on every page.
The primary difference between *AUTO and *OVERLAY is that *AUTO
will, when invoked, not allow any other macro to be called during the
course of a job.
If you wish to call a different PCL macro (using logical processing or some
other method) during the course of a job, you would use *OVERLAY. If
you want to use the same macro throughout, you could use *OVERLAY or
*AUTO. If you use *OVERLAY for this type of job, be sure no other macros
are called during the processing of the job.
Generic PCL (GENPCL)
Indicates you want to process a generic packet either once for the job, or
once for each printed page of the job. You can use these values:
•
packet-name — Specifies a one- to eight-character packet name,
which is located in the XDPEFLR/GENPCL folder
•
invocation-type — Specifies whether to insert the generic packet
once (*JOB mode) or on every page (*PAGE mode)
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.
For more information on how generic packets are processed, refer to
“Generic packets” later in this chapter.
If your generic PCL packet references a font or macro downloaded using
list processing, see “Downloading PCL fonts and macros using a resource
list” in chapter 22.
Resource list name
(RSCLIST)
Allows you to download job or page level resources. Note that the at
symbol (@) packet name prefix is not required. *NONE can also be
specified.
Printing Documents with XDPE/400 (9/2001)
15-19
PCL command generation
Duplex side (DSIDE)
Used with logical processing, allows you to send a form feed to start
printing on the next side of a page, the front side of a page, or the back of
a page when a new packet comes in the middle of a job. You can specify
these values:
•
•
•
•
*NEXT — Starts printing on the next side
*FRONT — Starts printing on the front side of the page
*BACK — Starts printing on the back of the page
*NONE — Does not use the option
If any value other than *NEXT or *NONE is used outside of logical
processing, all pages will start on the specified side, giving the
appearance of simplex.
Lines per inch (LPI)
Specifies the number of lines printed per inch. The value is an
approximate setting and depends on the interface type in use. This
parameter applies to all printers using the *PCSUPP interface setting. For
the *INTERNAL interface, a 42XX/MRP printer must be configured as a
3812/5219 device, Monitor Queue must be started using the printer
emulation setting of 5219 or *NOSCS, and *MRP5 must be specified for
the MRP internal interface (MRP) PCL packet parameter. You can use
these values:
•
number — Specifies a numeric value between 00.10 and 99.99
•
*NONE — Does not use the option
If you are using the *INTERNAL interface, the value you specify is
converted into units of 1440 and inserted into a Set Single Line Distance
SCS command. The 42XX/MRP interface uses an approximate value if
the interface is set to Computer Output Reduction (COR); that is, the
Xerox twinax interface function 10, Default orientation, is set to COR.
These examples show how the LPI value is converted into 1/1440 values:
•
If you specify 8.1, the unit value generated is 1440/8.1=177 or 8.13
LPI.
•
If you specify 8.08, the unit value generated is 1440/8.08=178.
If you are using the *PCSUPP interface, the value is converted into units
of 48 and inserted into a PCL Vertical Motion Index (VMI) command; for
example, if you specify 8.1, the unit value generated is 48/8.1=5.92.
MRP internal interface (MRP)
Specifically for use with the 42XX i-data internal interface box used with
the 4230, 4220, 4219, and 4215 printers, MRP allows the user to set the
i-data Y36 command through XDPE/400. The Y36 command determines
how the interface box handles IBM control codes that are sent to it.
If a value for MRP is entered in a PCL packet, that value overrides the
MRP value in the Monitor Queue for the duration of the job using that PCL
packet. When the job has finished processing, MRP is reset back to the
Monitor Queue value. If however, Monitor Queue has no MRP value set
and a value other than *NONE is entered in a PCL packet, the value from
the packet will stay active on the printer for all subsequent jobs until a job
comes along containing a PCL packet with a different MRP value.
Refer to the i-data Twinax XES/PCL Interface Controller for Xerox
Printers Programmer’s Guide for more information about this feature.
Printing Documents with XDPE/400 (9/2001)
15-20
PCL command generation
You must specify *NONE for this parameter if you are not using a 42XX
internal interface box. You can use these values:
•
*MRP0 — The interface box honors all IBM control codes that are
sent to it. This is the default setting for the 42XX internal interface
box.
With the 42XX i-data internal interface set to Y36,6, when sending a
PCL packet we recommend that you specify a value of *NONE for the
page size, which is set through the Margin setting (MARGIN)
parameter. To specify a setting other than *NONE for a PCL packet
page size, we recommend that you set the 42XX i-data internal
interface to Y36,0.
If an application you are using requires you to set the 42XX i-data
internal interface set to Y36,6 and use a value other than *NONE for
the PCL packet page size, your data will be printed one line lower
than expected on the first page of the job. You can fix this formatting
problem by using a generic PCL packet.
Follow this procedure to correct formatting on PCL jobs sent with the
42XX i-data internal interface set to Y36,6 and a value other than
*NONE set for the page size:
—
Create a generic PCL packet that contains the Vertical Cursor
Positioning PCL command:
Esc&a#V
where # is the number of decipoints (1/720 inch), which
represents the distance the data will be moved up the page.
—
•
*MRP5 — Suppresses all multibyte IBM control commands except
bolding. These page format commands will be honored:
—
—
—
—
—
Number of pages per side
(PAGESPSIDE)
Send this command once for the job by specifying *JOB for the
Invocation type subparameter of the Generic PCL (GENPCL)
parameter.
Carriage Return (CR)
Line Feed (LF)
Form Feed (FF)
print position (34-vvnn)
absolute line position (will be translated into CR + spaces)
•
*MRP6 — Suppresses page formatting in order to eliminate excess
blank pages and line feeds. Use this command only for jobs where
excess blank pages and line feeds are generated.
•
*NONE — XDPE/400 does not insert a Y36 command into the data
stream. If *NONE is selected, the 42XX internal interface box uses
its own MRP default of zero. All other interface boxes function
normally.
Specifies the number of logical pages to be printed on each physical
page. This parameter works in conjunction with the Degree of page
rotation (PAGRTT) printer file parameter to produce the desired output.
Refer to chapter 25, “Multi-up printing,” for more information. You can use
these values:
•
*NONE — Specifies normal (non-multi-up) printing
•
1-32767 — Specifies the number of logical pages to be printed on
each physical page
Printing Documents with XDPE/400 (9/2001)
15-21
PCL command generation
Multi-up packet name
(PCLMUP)
Specifies the name of the multi-up packet that contains the relevant font
and positioning information for this job. A value must be entered for this
parameter if the Number of pages per side (PAGESPSIDE) parameter is
any value other than *NONE. Refer to chapter 25, “Multi-up printing,” for
more information. You can use this value:
•
Paper type (PAPERTYPE)
name — A one- to eight-character alphanumeric value. The multi-up
packet specified must exist in the XDPEFLR/PCLMUP directory.
This parameter applies to the N32, N24, NPS, DocuSP, and generic XJT
printers only.
For N32 and N24 printers
PAPERTYPE selects the source tray based on the paper type.
PAPERTYPE works in conjunction with the Margin setting (MARGIN) and
Source tray (TRAY) packet parameters, as well as with the physical paper
size and paper type loaded in the printer. If both PAPERTYPE and
MARGIN are specified, the paper tray you have defined on the printer for
that paper type must match the size specified by MARGIN.
For more information on how the PAPERTYPE, MARGIN, and TRAY
packet parameters work together to select a tray for printing, see the
Alphanumeric ID Command discussion in the PCL 5 Comparison Guide.
For information on how the printer functions when the desired
combination of paper size and paper type are not available, refer to the
Xerox DocuPrint N24 and N32 Network Laser Printers Documentation
Set.
For NPS, DocuSP, and XJT generic printers
For all specific NPS, generic NPS, all specific DocuSP, generic DocuSP
and XJT generic printers PAPERTYPE generates a job ticket command
based on the values selected for this parameter.
PAPERTYPE values
You can use the following values for PAPERTYPE.
Value
N32 and N24 printers
NPS, DocuSP, and XJT generic printers
*BOND
Selects a tray loaded with bond
paper
Issues a paperType-preFinish job ticket
command with a user-defined value of “bond”
*CARDSTOCK
Selects a tray loaded with heavy
card stock
Issues a paperType-preFinish job ticket
command with a user-defined value of “cardstock”
*COLOR
Selects a tray loaded with
colored paper
Issues a paperType-opacity job ticket command
with a predefined value of “opaque”
*LABELS
Selects a tray loaded with labels
Issues a paperType-preFinish job ticket
command with a user-defined value of “labels”
*LETTERHEAD
Selects a tray loaded with
pre-printed letterhead paper
Issues a paperType-preFinish job ticket
command with a user-defined value of
“letterhead”
Printing Documents with XDPE/400 (9/2001)
15-22
PCL command generation
Value
N32 and N24 printers
NPS, DocuSP, and XJT generic printers
*PLAIN
Selects a tray loaded with plain
paper. This is the equivalent of
making no paper type selection
Issues a paperType-preFinish job ticket
command with a predefined value of “plain”
*PREPRINTED
Selects a tray loaded with
pre-printed forms
Issues a paperType-preFinish job ticket
command with a user-defined value of
“preprinted”
*PREPUNCHED
Selects a tray loaded with
pre-drilled paper
Issues a paperType-preFinish job ticket
command with a predefined value of “drilled”
*RECYCLED
Selects a tray loaded with
recycled paper
Issues a paperType-preFinish job ticket
command with a user-defined value of “recycled”
*TRANSPARENCY
Selects a tray loaded with
transparencies
Issues a paperType-opacity job ticket command
with a predefined value of “transparency”
*USERTYPE1
Selects a tray loaded with the
first user-defined paper type
Issues a paperType-preFinish job ticket
command with a user-defined value of
“usertype1”
*USERTYPE2
Selects a tray loaded with the
second user-defined paper type
Issues a paperType-preFinish job ticket
command with a user-defined value of
“usertype2”
*USERTYPE3
Selects a tray loaded with the
third user-defined paper type
Issues a paperType-preFinish job ticket
command with a user-defined value of
“usertype3”
*USERTYPE4
Selects a tray loaded with the
fourth user-defined paper type
Issues a paperType-preFinish job ticket
command with a user-defined value of
“usertype4”
*USERTYPE5
Selects a tray loaded with the
fifth user-defined paper type
Issues a paperType-preFinish job ticket
command with a user-defined value of
“usertype5”
*NONE
No paper type option is
generated
No paper type command is generated
Printing Documents with XDPE/400 (9/2001)
15-23
PCL command generation
Job ticket processing
(XTICKET)
Allows for the specification of extended job ticket processing
subparameters, which are valid for NPS, DocuSP and generic XJT
printers only. The subparameters are:
•
Extended ticket name — Specifies a one- to eight-character packet
name located in the XDPEFLR/XTICKET subfolder. This packet will
be inserted into the internal job ticket created by the XDPE/400
Monitor Queue.
•
Suppress PCL — Specifies whether to use PCL command
suppression. You can use these values:
*NO — Specifies no suppression of PCL commands within this job.
*YES — Specifies to suppress all PCL commands, except those
explicitly specified in the PCL packet or by packet processing. This is
used to suppress PCL commands that may conflict with job ticket
processing commands at the printer.
The Suppress PCL subparameter works in conjunction with the
Workstation customizing object (WSCST) Monitor Queue parameter.
If Suppress PCL is set to *YES and WSCST is set to *XDPEDFT or
*EURODFT, both HPT and XDPE/400- generated PCL commands
from spool file attributes will be suppressed.
If Suppress PCL is set to *YES and WSCST is set to a value other
than *XDPEDFT or *EURODFT, only XDPE/400- generated PCL
commands from spool file attributes will be suppressed. There will be
no affect on PCL commands generated from spool file attributes by
HPT and the user-generated WSCST.
Example of creating Xerox PCL packets
This example shows printing a form called XFORM1 on a Xerox 4220
printer in PCL mode. The variable text of the form is generated by the
application, but you want to print an electronic form on each page.
Step 1.
Sign on and, if necessary, add the XDPE/400 application library to the
library list for your user profile.
Step 2.
Enter CRTXPCL at any OS/400 command prompt.
Step 3.
Enter FORM1 as the name of your new packet. You can use from one to
eight characters.
NOTE: The additional parameters display only if you press F10.
Step 4.
Make sure OVERLAY is specified for the Invocation type.
Step 5.
Enter XFORM1 as the Macro name of the form.
Step 6.
Press ENTER. The system stores the FORM1 packet in the PCL subfolder
of XDPEFLR.
Printing Documents with XDPE/400 (9/2001)
15-24
PCL command generation
To use this packet to print the output of the application, you must change
the printer file for your application. Use the Change Xerox Printer File
(CHGXPRTF) command to specify the Direct method of printer control
generation and the name of your newly developed PCL packet. Refer to
chapter 10, “Creating and modifying printer files,” for more information.
Create Xerox PCL Packet (CRTXPCL)
Type choices, press Enter.
Printer control packet name .
Print on both sides of sheet.
Pre-drilled paper . . . . . .
Source tray . . . . . . . . .
Page orientation . . . . . .
.
.
.
.
.
FORM1
*NONE
*NONE
*NONE
*NONE
Name, F4 for list
*YES, *NO, *TUMBLE, *NONE
*YES, *NO, *NONE
*TRAY1, *TRAY2, *TRAY3...
*PORT, *LAND, *IPORT...
Additional parameters
Margin setting
Page size .
Top margin .
Text length
Left margin
Right margin
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*NONE
*NONE
*NONE
*NONE
*NONE
*EXEC, *LETTER, *LEGAL...
1-1000, *NONE
1-1000, *NONE
1-1000, *NONE
1-1000, *NONE
More...
F3=Exit
F4=Prompt
F24=More keys
F5=Refresh
Printing Documents with XDPE/400 (9/2001)
F12=Cancel
F13=How to use this display
15-25
PCL command generation
Create Xerox PCL Packet (CRTXPCL)
(CRTXPCL )
Type choices, press Enter.
Font selection by attributes:
Symbol set . . . . . . . *NONE
Spacing . . . . . . . . . *NONE
Pitch . . . . . . . . . . *NONE
Height . . . . . . . . . *NONE
Style . . . . . . . . . . *NONE
Weight. . . . . . . . . . *NONE
Typeface. . . . . . . . . *NONE
Page font selection by ID . *NONE
Font name . . . . . . . . . *NONE
PCL macro:
Macro name . . . . . . . . *NONE
Invocation type. . . . . . *OVERLAY
Generic PCL:
Packet name . . . . . . . *NONE
Invocation type. . . . . . *JOB
Character value, *ROMAN8...
*FIXED, *PS, *NONE
0.1-576, *NONE
0.25-999.75, *NONE
*UPRIGHT, *ITALIC...
*LIGHT, *MEDIUM, *BOLD...
*LP, *PICA, *ELITE, *COUR...
1-32767, *NONE
Name, F4 for list
*EXEC, *CALL, *AUTO, *OVERLAY
Name, F4 for list
*JOB, *PAGE
More...
F3=Exit
F4=Prompt
F24=More keys
F5=Refresh
F12=Cancel
F13=How to use this display
Create Xerox PCL Packet (CRTXPCL)
Type choices, press Enter.
Resource list name . . . . .
Duplex side . . . . . . . .
Lines per inch . . . . . . .
MRP internal interface mode
Number of pages per side . .
Multi-up packet name . . . .
Paper type . . . . . . . . .
Job ticket processing:
Extended ticket name . . .
Suppress PCL . . . . . . .
F3=Exit
F4=Prompt
F24=More keys
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*NONE
*NONE
*NONE
*NONE
*NONE
*NONE
*NONE
Name, F4 for list
*NEXT, *FRONT, *BACK, *NONE
00.10-99.99, *NONE
*MRP0, *MRP5, *MRP6, *NONE
1-32767, *NONE
Name, F4 for list
. .
. .
*NONE
*NO
Name, F4 for list
*NO, *YES
F5=Refresh
Printing Documents with XDPE/400 (9/2001)
F12=Cancel
Bottom
F13=How to use this display
15-26
PCL command generation
Changing Xerox PCL packets
Use the Change Xerox PCL Packet (CHGXPCL) command to modify
Xerox PCL packets created with the Create Xerox PCL Packet command.
NOTE: Press F10 to display the current values within the additional
parameters area. Press F9 to display fields without values or to
display all fields.
Follow these steps to modify a PCL control command packet:
Step 1.
Enter CHGXPCL and press ENTER. The Change Xerox PCL Packet
menu displays.
Change Xerox PCL Packet (CHGXPCL)
Type choices, press Enter.
Printer control packet name
Name, F4 for list
. . .
Bottom
F3=Exit
F4=Prompt
F24=More keys
F5=Refresh
F12=Cancel
F13=How to use this display
Step 2.
Enter the name of the Xerox PCL packet you want to change and press
ENTER. The Change Xerox PCL Packet menu displays additional
parameters in three screens.
Step 3.
Modify the parameters you want and press ENTER.
Printing Documents with XDPE/400 (9/2001)
15-27
PCL command generation
Refer to “Creating Xerox PCL packets” earlier in this chapter for
information about the parameters.
Change Xerox PCL Packet (CHGXPCL)
Type choices, press Enter.
Printer control packet name .
Print on both sides of sheet.
Pre-drilled paper . . . . . .
Source tray . . . . . . . . .
Page orientation . . . . . .
Margin setting:
Page size . . . . . . . .
Top margin . . . . . . . .
Text length . . . . . . .
Left margin . . . . . . .
Right margin . . . . . . .
.
.
.
.
.
*SAME
*SAME
*SAME
*SAME
Name, F4 for list
*YES, *NO, *TUMBLE, *NONE
*YES, *NO, *NONE
*TRAY1, *TRAY2, *TRAY3...
*PORT, *LAND, *IPORT...
.
.
.
.
.
*SAME
*SAME
*SAME
*SAME
*SAME
*EXEC, *LETTER, *LEGAL...
1-1000, *NONE, *SAME
1-1000, *NONE, *SAME
1-1000, *NONE, *SAME
1-1000, *NONE, *SAME
More...
F3=Exit
F4=Prompt
F24=More keys
F5=Refresh
F12=Cancel
F13=How to use this display
Change Xerox PCL Packet (CHGXPCL)
(CHGXPCL )
Type choices, press Enter.
Font selection by attributes:
Symbol set . . . . . .
Spacing . . . . . . . .
Pitch . . . . . . . . .
Height . . . . . . . .
Style . . . . . . . . .
Weight. . . . . . . . .
Typeface. . . . . . . . .
Page font selection by ID .
Font name . . . . . . . . .
PCL macro:
Macro name . . . . . . . .
Invocation type. . . . . .
Generic PCL:
Packet name . . . . . . .
Invocation type. . . . . .
*SAME
*SAME
*SAME
*SAME
*SAME
*SAME
*SAME
*SAME
*SAME
Character value, *ROMAN8...
*FIXED, *PS, *SAME, *NONE
0.10-576, *NONE, *SAME
0.25-999.75, *NONE, *SAME
*UPRIGHT, *ITALIC...
*LIGHT, *MEDIUM, *BOLD...
*LP, *PICA, *ELITE, *COUR...
1-32767, *NONE, *SAME
*SAME
*OVERLAY
Name, F4 for list
*EXEC, *CALL, *AUTO, *OVERLAY
*SAME
*JOB
Name, F4 for list
*JOB, *PAGE
More...
F3=Exit
F4=Prompt
F24=More keys
F5=Refresh
Printing Documents with XDPE/400 (9/2001)
F12=Cancel
F13=How to use this display
15-28
PCL command generation
Change Xerox PCL Packet (CHGXPCL)
Type choices, press Enter.
Resource list name . . . . .
Duplex side . . . . . . . .
Lines per inch . . . . . . .
MRP internal interface mode
Number of pages per side . .
Multi-up packet name . . . .
Paper type . . . . . . . . .
Job ticket processing:
Extended ticket name . . .
Suppress PCL . . . . . . .
F3=Exit
F4=Prompt
F24=More keys
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*SAME
*SAME
*SAME
*SAME
*SAME
*SAME
*SAME
Name, F4 for list
*NEXT, *FRONT, *BACK...
00.10-99.99, *NONE, *SAME
*MRP0, *MRP5, *MRP6, *NONE...
1-32767, *NONE, *SAME
Name, F4 for list
. .
. .
*SAME
*SAME
Name, F4 for list
*NO, *YES, *SAME
F12=Cancel
Bottom
F13=How to use this display
F5=Refresh
Printing Documents with XDPE/400 (9/2001)
15-29
PCL command generation
Deleting Xerox PCL packets
Use the Delete Xerox PCL Packet (DLTXPCL) command to delete Xerox
PCL packets without having to access the directory. Follow these steps:
Step 1.
Enter DLTXPCL and press ENTER. The Delete Xerox PCL Packet menu
displays.
Step 2.
Enter the name of the Xerox PCL packet you want to delete and press
ENTER.
Delete Xerox PCL Packet (DLTXPCL)
Type choices, press Enter.
Name, F4 for list
Printer control packet name . .
Bottom
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
Printing Documents with XDPE/400 (9/2001)
F12=Cancel
F13=How to use this display
15-30
PCL command generation
Displaying Xerox PCL packets
Use the Display XDPE PCL packet (DSPXPCL) command to display the
contents of a PCL packet. Follow these steps:
Step 1.
Enter DSPXPCL and press ENTER. The Display XDPE PCL packet menu
displays.
Display XDPE PCL packet (DSPXPCL)
Type choices, press Enter.
Printer control packet name . . .
Display output . . . . . . . . . *
Name, F4 for list
*, *PRINT
Bottom
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
F12=Cancel F13=How to use this display
Step 2.
Enter the name of the PCL packet you want to display.
Step 3.
To display the results on your screen, enter * for the Display output
parameter. To save the information to a spool file, enter *PRINT.
If *PRINT is selected, a spool file named DSPXPCL containing the
information is created and placed in your default output queue. You can
view or print the information.
Printing Documents with XDPE/400 (9/2001)
15-31
PCL command generation
Step 4.
Press ENTER. Depending on the value you entered for the Display output
parameter, the contents of the PCL packet will either display on your
screen or be saved to a spool file. A sample packet display follows.
Display XDPE PCL Packet (DSPXPCL)
Printer control packet name . . :SAMPKT
Packet version . .
Print on both sides
Pre-drilled paper .
Source tray . . . .
Page orientation .
. . . . .
of sheet.
. . . . .
. . . . .
. . . . .
.
.
.
.
.
:PV16
:*NO
:*NONE
:*TRAY4
:*LAND
PCL macro:
Macro name . . . . . . . . . :PCLMAC
Invocation type . . . . . . :*AUTO
Generic PCL:
Packet name . . . . . . . . :SHIFTPKT
Invocation type . . . . . . :*JOB
Resource list name . . . . . . :*NONE
Duplex side . . . . . . . . . . :*NONE
Lines per inch . . . . . . . . :*NONE
More...
F3=Exit
F12=Cancel
The Packet version parameter is an internal XDPE/400 PCL packet
parameter that indicates in which version of XDPE/400 the packet was
created or last changed. The values are:
PV20
PV21
PV22
Indicates XDPE/400 V2.0 or V2.1.0
Indicates XDPE/400 V2.1.1
Indicates XDPE/400 V2.1.2 and higher
Printing Documents with XDPE/400 (9/2001)
15-32
PCL command generation
If a parameter was not supported in the release the packet was created
in, the value field for that parameter will appear blank.
Display XDPE PCL packet (DSPXPCL)
Printer control packet name. . SAMPKT
Margin setting
Page size . .
Top margin .
Text length .
Left margin .
Right margin
Font selection
Symbol set
Spacing . .
Pitch . . .
Height . .
Style . . .
Weight . .
Typeface .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*LETTER
1
1
1
1
by attributes
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
.
.
.
.
.
.
.
*ROMAN8
*FIXED
10.0
10.0
*ITALIC
*BOLD
*COUR
Page font selection by ID
. . 813
More ...
F3=Exit
F12=Cancel
Display XDPE PCL packet (DSPXPCL)
Printer control packet name
. SAMPKT
MRP internal interface mode
Number of pages per side . .
Multi-up packet name . . . .
Font name . . . . . . . . .
Paper type . . . . . . . . .
.
.
.
.
.
*MRP0
*NONE
*NONE
*NONE
*BOND
Job ticket processing
Extended ticket name . . . NPSJOB
Suppress PCL . . . . . . . *NO
Bottom
F3=Exit
F12=Cancel
Printing Documents with XDPE/400 (9/2001)
15-33
PCL command generation
Working with Xerox PCL packet macro invocation types
Use the Work with XDPE PCL macros (WRKXPCLMAC) command to
display the macro invocation types in selected PCL packets. Follow these
steps:
Step 1.
Enter WRKXPCLMAC and press F4. The Work with XDPE PCL macros
menu displays.
Work with XDPE PCL macros (WRKXPCLMAC)
Type choices, press Enter.
Printer control packet name . . . *ALL
+ for more values
Conversion type or list . . . . . *DISPLAY
Name, F4 for list
*DISPLAY, *AUTOTOVER...
Bottom
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
F12=Cancel F13=How to use this display
Step 2.
Enter the name of a PCL packet, a list of packets, or *ALL for all PCL
packets located in your XDPEFLR/PCL subfolder.
Step 3.
Enter *DISPLAY to save the information to a spool file.
Step 4.
Press ENTER. A spool file named WRKXPCLMAC containing the
information is created and placed in your default output queue. You can
view or print the information. If a packet is selected that does not contain
a macro, it will not be included in the output. Figure 15-1 shows sample
output from WRKXPCLMAC.
NOTE: Because the *OVERLAY valid value has no corresponding
PCL Invocation Type, it is listed as having a PCL Invocation Type of
5, for which there is no corresponding PCL equivalent.
Printing Documents with XDPE/400 (9/2001)
15-34
PCL command generation
Figure 15-1. Sample output from WRKXPCLMAC
XDPE PCL Macro Usage page 1.
PCL
PCL
PCL
PCL
PCL
packet
packet
packet
packet
packet
INVOICE2
YEAREND
PAYABLE
IS220REP
SALESREP
with
with
with
with
with
macro
macro
macro
macro
macro
INVMAC2
MACR02
LISTFRM
IS220REP
SALESFRM
has
has
has
has
has
PCL
PCL
PCL
PCL
PCL
invocation
invocation
invocation
invocation
invocation
type
type
type
type
type
2
2
2
2
2
and
and
and
and
and
XDPE
XDPE
XDPE
XDPE
XDPE
invocation
invocation
invocation
invocation
invocation
type
type
type
type
type
*EXEC
*EXEC
*EXEC
*EXEC
*EXEC
PCL packet QUARTER with macro QTRSTMT has PCL invocation type 3 and XDPE invocation type *CALL
PCL packet XCR440
with macro XCRFRM
has PCL invocation type 3 and XDPE invocation type *CALL
PCL packet INVNTRY with macro REVMACRO has PCL invocation type 3 and XDPE invocation type *CALL
PCL
PCL
PCL
PCL
PCL
packet
packet
packet
packet
packet
SALESPER
CUSTSTAT
PURCHODR
PHONELST
PACKING
PCL packet PROGRAM
*OVERLAY
PCL packet TEST252
*OVERLAY
with
with
with
with
with
macro
macro
macro
macro
macro
RSREPT
REMITFRM
KDX200
USAGE
WAREHFRM
has
has
has
has
has
PCL
PCL
PCL
PCL
PCL
invocation
invocation
invocation
invocation
invocation
type
type
type
type
type
4
4
4
4
4
and
and
and
and
and
XDPE
XDPE
XDPE
XDPE
XDPE
invocation
invocation
invocation
invocation
invocation
type
type
type
type
type
*AUTO
*AUTO
*AUTO
*AUTO
*AUTO
with macro PROG1
has PCL invocation type 5 and XDPE invocation type
with macro SAMPMAC
has PCL invocation type 5 and XDPE invocation type
Printing Documents with XDPE/400 (9/2001)
15-35
PCL command generation
Changing PCL macro invocation types
After using the display utility and reviewing the differences between the
invocation types, you may determine that you need to convert your PCL
packets. Use the Work with XDPE PCL macros (WRKXPCLMAC)
command to change the PCL macro invocation type (PCLMAC) parameter
valid values in selected PCL packets. Follow these steps:
Step 1.
Enter WRKXPCLMAC and press ENTER. The Work with XDPE PCL
macros menu displays.
Work with XDPE PCL macros (WRKXPCLMAC)
Type choices, press Enter.
Printer control packet name . . . *ALL
+ for more values
Conversion type or list . . . . . *DISPLAY
Name, F4 for list
*DISPLAY, *AUTOTOVER...
Bottom
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
F12=Cancel F13=How to use this display
Step 2.
Enter the name of a PCL packet, a list of packets, or *ALL for all PCL
packets located in your XDPEFLR/PCL subfolder.
Step 3.
If you want to change the PCL invocation type in the selected packets
from *OVERLAY to *AUTO, enter *OVERTOAUTO. To change the PCL
invocation type from *AUTO to *OVERLAY, enter *AUTOTOOVER.
Step 4.
Press ENTER.
Printing Documents with XDPE/400 (9/2001)
15-36
PCL command generation
Generic packets
The XDPE/400 generic packet feature allows you to insert data created
outside of XDPE/400 into your print jobs. This can be any type of data,
including text, PCL commands, and PCL resources (such as macros) or
any combination of these.
A generic packet is an ASCII file stored in the XDPEFLR/GENPCL
subfolder. XDPE/400 downloads the unmodified ASCII file contents
directly into the data stream. The file contents do not have to be
XDPE/400-specific.
Before using generic packets, be aware of these considerations:
•
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 OS/400 writer-generated
commands can affect the way a command in a generic packet will
work.
If you use generic packets, you must reset all appropriate
parameters, either within the generic packet or in a generic packet in
the beginning of the next page. Thoroughly test your job before
putting it into production, and again after you make any changes to
XDPE/400 parameters for that job.
Refer to chapter 26 for more information on resetting parameters.
•
Generic packets inserted at the bottom of a page using logical
processing will overprint the last print line of the page. To correct this
situation, the text that is positioned in the generic packet needs to be
positioned with a Vertical Cursor Position command. This will force
the text to be positioned in the correct position on the page.
•
When printing to a network printer using constant back forms with a
generic packet larger than 255 bytes, the job either ends with “out of
memory” messages or prints garbage. To correct this situation, use a
generic packet that calls a macro containing the back form. Refer to
method 2 in “Building the generic PCL packet (BACKFRM)” later in
this chapter.
Creating a generic packet ASCII file
Use one of the following two methods to create a generic packet.
Using a DOS editor
The DOS editor you use must support hex output.
Step 1.
Create a text file containing the data (text, PCL commands, etc.) you want
to use.
Step 2.
Use the IBM PC Support or Client Access facility to copy the text file to
the XDPEFLR/GENPCL subfolder.
Printing Documents with XDPE/400 (9/2001)
15-37
PCL command generation
Using the Source Entry Utility
Step 1.
Create a source member containing the data (text, PCL commands, etc.)
you want to use.
Step 2.
Use the Copy to PC Document (CPYTOPCD) command to convert the
source member to an ASCII document and copy it to the
XDPEFLR/GENPCL subfolder.
NOTE: When creating a generic packet, some DOS editors may place
a line feed at the end of each line of the generic packet. This line feed
will appear as:
Hex '0D0A'
(Carriage Return Line Feed)
NOTE: You may want to delete this extra line feed to avoid any
additional text displacement.
Inserting generic packets
You can use numerous methods to insert generic packets into your print
job. The method you use depends on the type of processing required for
the job and the location in the job where you want your generic packet
inserted. You can insert a generic packet:
•
At the beginning of a job (before the XDPE/400-generated banner
page) using list processing
•
At the beginning of a job (after the XDPE/400-generated banner
page) using the Generic PCL (GENPCL) PCL packet parameter or
the Font identifier (FONT) printer file parameter
•
At the top or bottom of a page using logical processing
Each of these processing methods is described in the following sections.
List processing
You can insert PCL commands directly into the data stream, before the
XDPE/400-generated banner page, by using list processing. Use this
method to specify such things as overriding specific twinax printer
interface commands.
List processing uses a resource list you create using the Create Xerox
resource list (CRTXRSCLST) command. Your resource list should include
the name of a generic PCL packet. The generic packet name refers to an
ASCII file of the same name located in the XDPEFLR/GENPCL subfolder.
The contents of a generic PCL packet file used by list processing are
downloaded with resources and processed before the
XDPE/400-generated banner page is processed. The settings specified in
the generic packet are used only once.
Refer to chapter 22 for more information on list processing.
Printing Documents with XDPE/400 (9/2001)
15-38
PCL command generation
PCL packet through GENPCL PCL packet parameter
You can insert PCL commands directly into the data stream, after the
banner page and before the first printed page of the job, by specifying a
generic packet using the Generic PCL (GENPCL) PCL packet parameter.
Using the Invocation type subparameter, you can specify whether the
contents of a generic packet are used once for the printed job, or once on
each page of the printed job.
You can use this method with either the Direct or Combined processing
method.
PCL packet through FONT printer file parameter
You can insert PCL commands directly into the data stream, after the
banner page and before the first printed page of the job, by specifying a
generic packet using the Font identifier (FONT) printer file parameter. The
generic packet name refers to an ASCII file of the same name located in
the XDPEFLR/GENPCL subfolder. The contents of a generic packet file
specified in this manner are used only once.
You can use this method with either the Indirect or Combined processing
method.
Logical processing
Logical processing allows you to insert a PCL packet into your print job.
This PCL packet can call a generic packet. The packet is inserted
dynamically, depending on the variable data in your job.
In addition, you have the option of inserting the contents of the packet at
the top of the intended page or at the bottom. Generally, data inserted at
the top of a page affects that page, while data inserted at the bottom of a
page affects the output on the next page. Refer to the PCL 5 Printer
Language Technical Reference Manual for information on the
implementation of PCL commands.
Refer to chapter 23 for more information on using logical processing.”
Printing Documents with XDPE/400 (9/2001)
15-39
PCL command generation
Example of using a generic packet for constant back forms
This example uses generic packets to print jobs using constant back
forms.
On any duplex printer, the ability to associate a constant back page with
a print job for a duplex application is a frequent, conventional requirement
for such items as:
•
•
Claim Forms
Account Statements
To implement constant back pages within XDPE/400, several objects are
required. An XDPE/400 logical processing test is required along with two
XDPE/400 PCL packets: one for the page level options for the job level
(or front page side) and one for the merging of the back page. The logical
processing test is referenced within an XDPE/400 list invoked from the job
level PCL packet.
Figure 15-2 shows the order in which these objects are referenced. The
same object names that are used in this figure also are used throughout
this section to show a consistent example for creating constant back
pages. Note that FRONTFRM and ADJUST are optional.
Figure 15-2. Constant back job elements
Printing Documents with XDPE/400 (9/2001)
15-40
PCL command generation
Building the job level PCL packet (BFJOBPCL)
The job level PCL packet will have options relating to the front side of the
application. Duplexing and a list reference are required, with an electronic
form, tray, and margins as optional packet entries. For this example, a
front page down adjustment is required after the top margin is entered into
the PCL packet.
This command creates a PCL packet containing the required and optional
objects from the previous figure:
CRTXPCL
PCL(BFJOBPCL)
DUPLEX(*YES)
ORIENT(*PORT)
MARGIN(*NONE 3)
PCLMAC(FRONTFRM)
GENPCL(ADJUST *PAGE)
RSCLIST(BFRSCLST)
As well as the required options, this packet invokes the optional generic
PCL packet ADJUST, which handles vertical alignment adjustments by
including the PCL command (esc)*p#Y. It also calls the optional form
FRONTFRM, which is placed on the front page. If you do not want to use
one or both of these options, omit the command(s).
Building the XDPE/400 resource list (BFRSCLST)
An XDPE/400 resource list must be built, which references the logical
processing test. Using the AS/400 editor (Source Entry Utility), create a
member within a source physical file. The following member is an example
of a list that contains only a logical processing reference:
LPP/BFLPP
An additional entry would be present if the macro invocation style (method
2 in “Building the generic PCL packet”) is used to apply the constant back
page. The macro is assigned an ID by XDPE/400. This ID is required
within the generic PCL sequence. XDPE/400 uses an ID of 8000 for the
first resource (font or macro) loaded from a list, then it increments by one
for each following resource.
PCLMAC/name of the PCLMAC entry
Once the member has been saved, use CRTXRSCLST to copy the source
member into the resource list subdirectory within XDPE/400’s shared
folders. This command entry creates a resource list from the source file
(XDPEASDEMO/PICKRLST) member called BFRSCLST:
CRTXRSCLST
SRCFILE(XDPEASDEMO/PICKRLST)
SRCMBR(BFRSCLST)
LIST(BFRSCLST)
FLR(*RSCLIST)
Printing Documents with XDPE/400 (9/2001)
15-41
PCL command generation
Creating the logical processing test (BFLPP)
XDPE/400 logical processing corresponds to PDL logical processing. The
matching of constant text or a change in the contents of a page location
will cause a condition to be true and an action to take place. Once an
XDPE/400 logical processing test is true, an XDPE/400 packet, named
within the test, is acted upon. The action can occur at the top or bottom of
a page.
For our BFORM example, the PCL packet, called BFMRGPCL, will be
processed at the bottom of the page. The test is required regardless of the
print data, hence a change criteria is used. The difference between the
test string entered into the command and the print data will cause the test
to be true. Once the test is true, the PCL is applied to the bottom of each
until a new bottom condition is invoked. The BFORM test only needs to be
used once, at the starting page of the BFORM application.
The CRTXLPP command menu with the required parameters is illustrated
below.
Create a Xerox LPP (CRTXLPP)
Type choices, press Enter.
Logical processing packet name
Test type . . . . . . . . . .
Test expression . . . . . . .
Test string . . . . . . . . .
Test position . . . . . . . .
Test page range:
starting page . . . . . .
ending page . . . . . . .
Line range:
starting line . . . . . .
ending line . . . . . . .
When to apply . . . . . . . .
Application duration . . . .
Printer control packet name .
Text ’description’ . . . . .
BACK FORM
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
BFLPP
*CHANGE
*EQ
xx
1
Name, F4 for list
*MATCH, *CHANGE
*EQ, *NE
1
1
1-1000000000, *FIRST
1-1000000000, *END
1-256, *ALL
1
1-256, *FIRST
1-256, *END
1
*BOTTOM
*TOP, *BOTTOM
*CONT
*ONCE, *CONT
BFMRGPCL
Character value
LOGICAL PROCESSING FOR MERGING
F12=Cancel
Bottom
F13=How to use this display
The Test expression (EXPRESSION) parameter is ignored when
*CHANGE is specified for the Test type (TYPE) parameter.
The Test page range (PAGERANGE) subparameter values must be
changed if you restart a print job with constant back pages. For more
information, see “Restarting a PCL constant back print job” in chapter 23.
Printing Documents with XDPE/400 (9/2001)
15-42
PCL command generation
Building the BFORM merge PCL packet (BFMRGPCL)
The PCL invoked on the bottom of each page contains only a generic PCL
entry. The generic PCL packet is the document library object containing
PCL or text, for the constant back page. The method of creation is outlined
in the following section. The document library object must be contained
within the folder XDPEFLR/GENPCL.
This command creates a PCL packet containing the required options:
CRTXPCL
PCL(BFMRGPCL)
GENPCL(BACKFRM *PAGE)
Building the generic PCL packet (BACKFRM)
The following procedures outline two methods for creating the generic
PCL packet. Method 1 creates a generic PCL packet containing the back
form. Method 2 creates a generic PCL packet that calls a macro
containing the back form.
Use method 2 when the resulting generic packet created with method 1
would be greater than 255 bytes in size, and you will be using it for remote
or network printing. Using generic packets larger than 255 bytes can
produce unpredictable results.
To create generic packets, use a PC editor that supports hex input.
Method 1
Step 1.
Create a file that contains this PCL command:
X'0C'(esc)&f5X
Step 2.
Perform a DOS copy, with the binary switch, using the following as input:
•
The file created in step 1
•
A FORMFIXed PCL .PRN file from Elixir, Lytrod Software, a
Windows application, or a self-created set of commands and text
data
Use the GENPCL directory as the destination location.
Step 3.
Use the generic PCL file (BACKFRM) within the BFORM merge PCL
packet (BFMRGPCL).
Printing Documents with XDPE/400 (9/2001)
15-43
PCL command generation
Method 2
Instead of containing all the page data for the back side, the generic PCL
packet can include only a macro call-out invoking a pre-loaded or
resource list loaded PCL macro. The form feed control byte
(X'0C'(esc)&f5X) must precede the macro invocation sequence
(esc)&f0s#y3x1S).
The following example shows how to use a macro call-out invoking a
pre-loaded PCL macro.
Step 1.
Create a file that contains this PCL command:
X'0C'(esc)&f5X (esc)&f0s#y3x1S
where # is the macro ID of the pre-loaded macro
If you are using a resource list to download this macro, see “Downloading
PCL fonts and macros using a resource list” in chapter 22.
Step 2.
Perform a DOS copy, with the binary switch, using the file created in step
1 as input. Use the GENPCL directory as the destination location. For this
example, the generic PCL packet is named BACKFRM2.
Step 3.
Use this generic PCL file (BACKFRM2) within the BFORM merge PCL
packet (BFMRGPCL).
The AS/400 printer file
The XDPE/400 job level packet is placed within the AS/400 printer file
object used to generate the spool file. Either the formtype or user data
fields or page info fields can be used. This command creates a
XDPEASDEMO/PICKLIST printer file using the user data field for the
XDPE/400 PACKETDATA field:
CRTPRTF
FILE(XDPEASDEMO/PICKLIST)
USRDTA('#BFJOBPCL')
Printing Documents with XDPE/400 (9/2001)
15-44
PCL command generation
Xerox PCL printer tray selection
This section provides tray selection methods and considerations for the
different Xerox PCL printers. Xerox PCL printers can be broken down into
these main groups:
•
•
•
•
DC265LP and DC255LP printers
N32 and N24 printers
NPS and DocuSP printers
All other PCL printers
Tray selection methods are different for each printer group, depending on
the command generation method being used. Table 15-1 provides a quick
overview of the tray selection methods by printer group and command
generation method. Tray selection methods for each printer group are
discussed in greater detail in the following sections.
NOTE: The Combined method uses a combination of Direct and
Indirect processing. The Combined method using Order of sequence
*ATTRIB is functionally the same as the Direct method. The
Combined method using Order of sequence *PACKET is functionally
the same as the Indirect method.
Since each group uses different inputs to determine which tray to print
from, your applications may need to be changed when switching from one
type of printer to another.
l
Table 15-1.
PCL printer tray selection methods
Printers
Direct mode
Indirect mode
DC265LP/DC255LP
Tray number, page size
Tray number
N32/N24
Tray number, page size, paper type
Tray number
NPS and DocuSP
Page size, extended job ticket
(color, weight, type commands)
Page size
All Generic printers
Not supported
Not supported
All other PCL printers
Tray number
Tray number
NOTE: Generic printer devices other than *DOCUSP, *NPS, and
*XJT use the printer’s defined default paper tray. To override paper
tray selection a generic PCL packet is required.
Printing Documents with XDPE/400 (9/2001)
15-45
PCL command generation
DC265LP and DC255LP printer tray selection
Tray selection for the DC265LP and DC255LP printers is based on the
tray number and/or page size.
Direct mode
In Direct mode, the DC265LP and DC255LP printers use the Margin
setting (MARGIN) packet parameter in conjunction with the Source tray
(TRAY) packet parameter, as well as with the physical paper size and
paper type loaded in the printer to select the paper for a job. Xerox
recommends using the MARGIN packet parameter for paper selection.
As an alternative, these printers can use the Separator page source
(BANNERSRC) and Data page source (DATASRC) Monitor Queue
parameters to select the paper tray.
Any tray selection by the TRAY packet parameter will override any tray
selected by the BANNERSRC and DATASRC Monitor Queue parameters.
For information on how tray selection precedence and printer defaults are
handled for the DC265LP and DC255LP printers, refer to the Xerox
Document Centre 240/255/265 Network Laser Printers Reference Guide.
Indirect mode
In Indirect mode, the DC265LP and DC255LP printers use the Source
drawer (DRAWER) printer file parameter to determine the paper tray. Or
paper tray selection can be performed using the Separator page source
(BANNERSRC) and Data page source (DATASRC) Monitor Queue
parameters.
Any tray selection by the DRAWER printer file parameter will override any
tray selected by the BANNERSRC and DATASRC Monitor Queue
parameters.
Printing Documents with XDPE/400 (9/2001)
15-46
PCL command generation
N32 and N24 printer tray selection
Tray selection for the N32 and N24 printers is based on the tray number,
page size, or paper type (which is defined on the printer), or a combination
of these.
Direct mode
In Direct mode, the N32 and N24 printers use a combination of Paper type
(PAPERTYPE), Margin setting (MARGIN), and Source tray (TRAY)
packet parameters to select the paper for a job. If MARGIN and/or
PAPERTYPE is specified in conjunction with TRAY, the size and type of
the intended tray must match the parameters specified for the job.
Therefore, Xerox recommends using the MARGIN and PAPERTYPE
packet parameters for paper selection.
Paper tray selection can also be performed using the Separator page
source (BANNERSRC) and Data page source (DATASRC) Monitor
Queue parameters.
Any tray selection by the TRAY packet parameter will override any tray
selected by the BANNERSRC and DATASRC Monitor Queue parameters.
Indirect mode
In Indirect mode, the N32 and N24 printers use the Source drawer
(DRAWER) printer file parameter to determine the paper tray. Or paper
tray selection can be performed using the Separator page source
(BANNERSRC) and Data page source (DATASRC) Monitor Queue
parameters.
Any tray selection by the DRAWER printer file parameter will override any
tray selected by the BANNERSRC and DATASRC Monitor Queue
parameters.
Printing Documents with XDPE/400 (9/2001)
15-47
PCL command generation
NPS and DocuSP printer tray selection
NPS and DocuSP printers use automatic tray selection based on the page
size, not the tray number. In order for a job to print on an NPS or DocuSP
printer, the page size of the job must match a page size set on the printer.
XDPE/400 inserts a paperType-size command in the Monitor
Queue-generated internal job ticket created for each job. The method
used by XDPE/400 to determine the page size of a job depends on the
command generation method used for the job.
XDPE/400 supports these NPS printers:
•
•
•
•
•
•
•
•
4890 NPS
4850 NPS
4635 NPS
4090 NPS
4050 NPS
180 NPS
92C NPS
DP96NPS
XDPE/400 supports this DocuSP printer:
•
DP65
Direct mode
There are two methods of tray selection when running in Direct mode:
•
Tray selection based on page size
•
Tray selection based on the type, weight, and color attributes
defined in your extended job ticket
When tray selection is based on page size, the page size is determined
by the Margin setting (MARGIN) packet parameter. The page size
selected will be the page size for the job. If no value is selected for the
Direct mode, the printer’s default page size will be used. If no value is
selected for the Combined/ Attribute mode, the page size is determined
using the same method as described in the next section, “Indirect and
Combined/Packet modes.”
Xerox recommends that you specify a valid page size for the Page size
subparameter in the default PCL packet and in all your user-created PCL
packets by entering this command:
CHGXPCL
PCL(packet-name)
MARGIN(page-size)
If you are using the extended job ticket feature, paper tray selection can
also be specified by entering paper type, weight, and color commands in
your extended job ticket packet. Any commands entered in your packet
must not conflict with the specified page size. See chapter 16 for more
information on extended job ticket packets.
NOTE: The internal job ticket contains the paperType-size command.
Therefore, if you are using an extended job ticket packet, do not add
the paperType-size command to it. Your printer may react adversely
to the duplicate command.
Printing Documents with XDPE/400 (9/2001)
15-48
PCL command generation
Indirect mode
In Indirect mode, the page size is determined by a combination of the
Lines per inch (LPI), Characters per inch (CPI), and Page size
(PAGESIZE) printer file parameters.
Since many printer files use the QSYS/QSYSPRT printer file for the
default page size values, we recommend that you configure
QSYS/QSYSPRT with a valid page size supported by your printer.
The following examples demonstrate how the LPI, CPI, and PAGESIZE
printer file parameters work together to calculate the length and width of
the page. With the settings in both examples, XDPE/400 will specify letter
as the page size for the job.
Example 1
An LPI of 6 with a Length (lines per page) of 66 will produce a page length
of 11 inches as follows:
66/6 = 11 inches
And a CPI of 10 and a Width (positions per line) of 85 will produce a page
width of 8.5 inches as follows:
85/10 = 8.5 inches
Example 2
An LPI of 8 with a Length of 88 will produce a page length of 11 inches as
follows:
88/8 = 11 inches
And a CPI of 15 and a Width of 127 will produce a page width of 8.5 inches
as follows:
127/15 = 8.5 inches
Converting from millimeters to inches
Because NPS and DocuSP printers use millimeters as the unit of measure
to determine the page size, you will need to use these formulas to specify
the correct width and length of your job. (Note that 25.4 is the
inch-to-millimeters conversion factor.)
Length in mm = integer part of
((length in lines / lines per inch) x 25.4) + 0.5
Width in mm = integer part of
((width in characters / characters per inch) x 25.4) + 0.5
Printing Documents with XDPE/400 (9/2001)
15-49
PCL command generation
Printer tray selection for other PCL printers
Tray selection for these PCL printers is based on the tray number.
Excluding the DC265LP, DC255LP, N32, N24, NPS, and DocuSP
printers, XDPE/400 supports these PCL printers:
•
•
•
•
•
•
•
4520
4517
4512
4230
4220
4219
4215
Direct mode
In Direct mode, these printers use the Source tray (TRAY) packet
parameter to select the correct paper tray on a job or page level. If a
printer does not support a tray, the default tray will automatically be used.
Tray selection may vary depending on your printer setup.
As an alternative, these printers can use the Separator page source
(BANNERSRC) and Data page source (DATASRC) Monitor Queue
parameters to select the paper tray.
Any tray selection by the TRAY packet parameter will override any tray
selected by the BANNERSRC and DATASRC Monitor Queue parameters.
Indirect mode
In Indirect mode, these printers use the Source drawer (DRAWER) printer
file parameter to select the correct paper tray. Or paper tray selection can
be performed using the Separator page source (BANNERSRC) and Data
page source (DATASRC) Monitor Queue parameters.
Any tray selection by the DRAWER printer file parameter will override any
tray selected by the BANNERSRC and DATASRC Monitor Queue
parameters.
Printing Documents with XDPE/400 (9/2001)
15-50
16.
16
Xerox job ticket packet generation
This chapter describes how to create and use XDPE/400 extended job
ticket packets for setting up complex print jobs to take advantage of a
wide range of printing, finishing, and job management options available
on NPS, DocuSP, and generic XJT printers.
The extended job ticket feature functions on NPS, DocuSP, and XJT
generic printers in PCL mode with job ticket processing enabled on the
printer controller.
For a list of options available on your NPS, DocuSP, and XJT generic
printers, refer to Xerox Production Systems Job Ticket Programming
Guide.
Job ticket processing
A job ticket is a series of required and optional user-generated
commands. Each command contains an instruction or set of instructions
related to a specific print job requirement, which forms a record. The
commands contained in the job ticket are inserted at the beginning of an
XDPE/400-generated spool file.
In XDPE/400, the Monitor Queue automatically generates an internal job
ticket containing several job ticket commands for NPS, DocuSP, and
generic XJT printers. This internal job ticket provides standard printing
capabilities. To expand your printing capabilities, you can create an
extended job ticket packet containing user-generated commands using
the Create Xerox Job Ticket (CRTXTCK) command and insert the packet
into the Monitor Queue-created job ticket using the Create Xerox PCL
Packet (CRTXPCL) command.
To use an extended job ticket packet, the packet name must be entered
in the Extended ticket name subparameter field of the Job ticket
processing parameter on the third screen of the CRTXPCL or CHGXPCL
command screens. In addition, Monitor Queue must be set up to process
the PCL packet.
Monitor Queue does not support extended job ticket packet processing or
PCL suppression using the Indirect command generation method. See the
Always generate (ALWAYS) Monitor Queue parameter in chapter 18 for
more information.
Printing Documents with XDPE/400 (9/2001)
16-1
Xerox job ticket packet generation
Internal job ticket commands
The Monitor Queue-generated internal job ticket contains these
commands:
•
•
•
•
•
•
•
•
%XRXbegin: 100.132
%XRXdisposition: PRINT
%XRXPDLformat: PDL-version
%XRXsenderName:user-id
%XRXtitle:spool-file-name
%XRXrequirements:plex
%XRXpaperType-size:
%XRXend
NOTE: The requirements:plex command is valid for NPS printers
only. This command is generated from either the Print on both sides
of sheet (DUPLEX) PCL packet parameter or the Print on both sides
(DUPLEX) spool file attribute, and therefore contains a value of either
simplex or duplex.
The PDLformat: PDL-version command is dependent on the printer
type. For NPS printers, HP is the generated PDL version. For DocuSP
printers, HP 5 is the generated PDL version.
The paperType-size command is generated from either the Margin setting
(MARGIN) PCL packet parameter or the Page size (PAGESIZE),
Characters per inch (CPI), and Lines per inch (LPI) spool file attributes.
One of these two commands also will be generated by the Monitor Queue
if a paper type specification is made in the PCL packet:
•
•
%XRXpaperType-preFinish
%XRXpaperType-opacity
See the Paper type (PAPERTYPE) PCL packet parameter in chapter 15
for the PAPERTYPE values.
Since these commands are automatically generated by the XDPE/400
Monitor Queue, you do not need to include them in your extended job
ticket packet.
NOTE: It is the responsibility of the user to know and understand the
job ticket command syntax and usage. For more information, refer to
the Xerox Production Systems Job Ticket Programming Guide.
Printing Documents with XDPE/400 (9/2001)
16-2
Xerox job ticket packet generation
Processing conflicts
NPS, DocuSP, and generic XJT printers may react adversely to duplicate
commands. When a command is encountered in both the internal job
ticket and the extended job ticket packet, both commands may be
ignored. This may occur with these Monitor Queue-generated commands:
•
•
requirements:plex
paperType-size
This may also occur with these Monitor Queue-generated commands if a
paper type specification is made in the PCL packet:
•
•
paperType-preFinish
paperType-opacity
Refer to the Paper type (PAPERTYPE) PCL packet parameter in chapter
15 for a list of PAPERTYPE values.
Because these four commands can be automatically created in the
internal job ticket by the Monitor Queue, it is recommended that they be
selected using a PCL packet or spool file attributes, not with a
user-created extended job ticket packet.
Order of precedence
Because the extended job ticket is inserted at the beginning of the print
job, commands generated from a PCL packet or spool file attributes may
take precedence over similar commands in an extended job ticket packet,
regardless of the Order of sequence (SEQUENCE) Monitor Queue
parameter. To ensure that your job prints as intended, it is recommended
that you block duplicate commands using the Suppress PCL (XTICKET)
PCL packet parameter or the Attribute include/exclude flag (INHIBLST)
global value.
For detailed information on job ticket commands, refer to the Xerox
Production Systems Job Ticket Programming Guide or the Xerox
DocuPrint Network Printer Series Guide to Managing Print Jobs.
Printing Documents with XDPE/400 (9/2001)
16-3
Xerox job ticket packet generation
Separator page considerations
XDPE/400 separator pages affect the manner in which your extended job
ticket cover and exception page commands are processed. If you are
using banner and/or trailer pages, covers and exception pages are
handled as follows:
•
If you specify a cover command in your extended job ticket packet,
the front cover will be inserted before the banner page(s) and the
back cover will be inserted after the trailer page(s).
•
If you specify exception page commands in your extended job ticket
packet, or any command that is page number dependent, the page
count will be off by however many banner pages are used. For
example, if two banner pages are used with each job, the first
banner page is considered page 1, the second banner page is page
2, the first data page is page 3, the second data page is page 4, etc.
XDPE/400 separator pages are considered to be part of the job by the
printer, just like covers and exception pages. If you want to print covers
without the insertion of separator pages, you need to disable the
separator pages by specifying *NO for the Process separator page
(BANNER) Monitor Queue parameter. If you want to use exception pages,
you can either disable separator pages or take them into account when
creating your exception page commands.
Printing Documents with XDPE/400 (9/2001)
16-4
Xerox job ticket packet generation
Creating and managing extended job ticket packets
Use the extended job ticket packet commands to create and manage
extended job ticket packets to be inserted into the internal job ticket
record created by the XDPE/400 Monitor Queue. These extended job
ticket packet commands are available:
•
CRTXTCK — Creates extended job ticket packets
•
CHGXTCK — Changes, displays, and prints extended job ticket
packets
•
DLTXTCK — Deletes extended job ticket packets
The following sections show you how to use these commands.
Rules for creating extended job ticket packets
Follow these rules when entering commands into an extended job ticket
packet. It is the responsibility of the user to know and understand job
ticket command syntax and usage. For detailed information, refer to Xerox
Production Systems Job Ticket Programming Guide.
•
Enter one command per line.
•
Each line must end with a carriage return and line feed. This will be
done automatically when using the extended job ticket packet
commands.
•
Enter each command without the %XRX prefix. This prefix will be
added to each command during Monitor Queue processing.
•
Blank lines are allowed.
•
Enter an asterisk (*) in the first position on a line to indicate that the
line is a comment.
NOTE: For information concerning duplicate command problems or
precedence of commands, see “Processing conflicts” and “Order of
precedence” earlier in this chapter.
Printing Documents with XDPE/400 (9/2001)
16-5
Xerox job ticket packet generation
Creating extended job ticket packets
The Create Xerox Job Ticket (CRTXTCK) command is used to create a
new extended job ticket packet.
The extended job ticket packet commands use the IBM Source Entry
Utility (SEU) editor for creating, editing, printing, and displaying extended
job ticket packets. Other text editors can be used as long as the editor
appends a carriage return and line feed to the end of each line. If you
choose to use a different text editor, make sure the extended job ticket
packet resides in the XDPEFLR/XTICKET subfolder.
NOTE: It is the responsibility of the user to know and understand the
IBM SEU editor. For information on using the SEU editor, refer to
Source Entry Utility User’s Guide and Reference.
Follow these steps to create a Xerox extended job ticket packet.
Step 1.
Enter CRTXTCK and press ENTER. The Create Xerox Job Ticket
(CRTXTCK) command screen displays.
Create Xerox Job Ticket (CRTXTCK)
Type choices, press Enter.
Extended ticket name . . . . . .
F3=Exit
F4=Prompt
F24=More keys
Step 2.
F5=Refresh
________
F12=Cancel
Name, F4 for list
Bottom
F13=How to use this display
Enter a packet name in the Extended ticket name (XTICKET) field and
press ENTER. Valid packet names are one to eight characters. An SEU
session is launched for you to enter your job ticket commands.
Printing Documents with XDPE/400 (9/2001)
16-6
Xerox job ticket packet generation
Step 3.
When you have entered all your job ticket commands, use the F3 function
key to exit the edit screen. Upon exiting the edit screen, an OS/400 exit
screen appears. Do not change any of the parameters on this screen.
Simply press the Enter key to continue.
If necessary, these two parameters may be changed on the exit screen:
•
Return to editing — Allows you to return to the SEU editing session
that you just left.
•
Print member — Allows you to print the extended job ticket packet
source that you just created.
CAUTION: Unexpected results may occur if any other parameters are
changed on the exit screen.
Step 4.
A prompt will appear asking if you would like to save the packet in the
XDPEFLR/XTICKET subfolder. Type Y to save the packet in XTICKET.
Type N if you do not want to save the packet.
If a packet with the same name exists in XTICKET, you will be prompted
to enter a different packet name under which to save the packet or you
can press F3 or F12 to exit without saving the packet.
Printing Documents with XDPE/400 (9/2001)
16-7
Xerox job ticket packet generation
Changing, displaying, and printing extended job ticket
packets
Use the Change Xerox Job Ticket (CHGXTCK) command to edit, display,
or print an extended job ticket packet created with the Create Xerox Job
Ticket command.
Step 1.
Enter CHGXTCK and press ENTER. The Change Xerox Job Ticket
command screen displays.
Change Xerox Job Ticket (CHGXTCK)
Type choices, press Enter.
Extended ticket name . . . . . .
Ticket option . . . . . . . . .
________
*EDIT
F3=Exit
F4=Prompt
F24=More keys
F12=Cancel
F5=Refresh
Name, F4 for list
*EDIT, *DISPLAY, *PRINT
Bottom
F13=How to use this display
Step 2.
Enter the name of the job ticket packet you want to change, display, or
print.
Step 3.
Enter the ticket option of your choice (*EDIT, *DISPLAY, or *PRINT) and
press ENTER. If you choose *EDIT or *DISPLAY, an SEU session will be
launched displaying the requested packet. If you choose *PRINT, a copy
of the packet data will be written to a spool file.
Printing Documents with XDPE/400 (9/2001)
16-8
Xerox job ticket packet generation
Step 4.
If you choose *EDIT, update the packet and use the F3 function key to exit
the edit screen. Upon exiting the edit screen, an OS/400 exit screen
appears. Do not change any of the parameters on this screen. Simply
press the Enter key to continue.
If necessary, these two parameters may be changed on the exit screen:
•
Return to editing — Allows you to return to the SEU editing session
that you just left.
•
Print member — Allows you to print the extended job ticket packet
source that you just created.
CAUTION: Unexpected results may occur if any other parameters are
changed on the exit screen.
Step 5.
A prompt will appear asking if you would like to save the packet in the
XDPEFLR/XTICKET subfolder. Type Y to save the changes to the packet
in XTICKET. Type N if you do not want to save the changes to the packet.
Xerox job ticket packet parameters
Extended ticket name
(XTICKET)
Ticket option (TCKOPT)
Specifies the name of the extended job ticket packet located in the
XDPEFLR/XTICKET folder.
Specifies the option you want to use on the extended job ticket packet.
You can use these values:
•
*EDIT — Opens the extended job ticket packet for editing.
•
*DISPLAY — Displays the contents of the extended job ticket packet.
•
*PRINT — Writes a copy of the extended job ticket source data to a
spool file. If this option is selected, a spool file named QPSUPRTF,
which contains the packet information, is created and placed in your
default output queue for printing.
Printing Documents with XDPE/400 (9/2001)
16-9
Xerox job ticket packet generation
Deleting extended job ticket packets
Use the Delete Xerox Job Ticket (DLTXTCK) command to delete Xerox
job ticket packets.
Step 1.
Enter DLTXTCK and press ENTER. The Delete Xerox Job Ticket
command screen displays.
Step 2.
Enter the name of the job ticket packet you want to delete in the Extended
ticket name (XTICKET) field and press ENTER.
Delete Xerox Job Ticket (DLTXTCK)
Type choices, press Enter.
Extended ticket name . . . . . .
F3=Exit
F4=Prompt
F24=More keys
F5=Refresh
Printing Documents with XDPE/400 (9/2001)
________
F12=Cancel
Name, F4 for list
Bottom
F13=How to use this display
16-10
17.
17
VIPP command generation
This chapter describes how to create, insert, or reference these VIPP or
PostScript command elements in the print data stream.
•
VIPP command — A VIPP command describes how the printer
should process the data stream. VIPP commands control the page
composition of a job.
•
VIPP Native Mode Prefix (NMP) record — An NMP record is a VIPP
command that is preceded by the prefix %%XGF. NMP records are
used within the data stream to dynamically invoke VIPP resources or
features.
•
Job Descriptor Ticket (JDT) — A JDT is a printer control file that
contains one or more VIPP commands. The JDT must reside on the
printer controller. In addition, the spool file must identify the name of
the JDT to be used by the printer to process the data stream.
•
PostScript Data Structuring Conventions (DSC) packet — A
PostScript DSC packet is an object that contains DSC statements. A
DSC statement is preceded by the prefix %% and followed
immediately by a DSC command (with no space between the prefix
and the command). DSC statements are instructions that you want
the PostScript document manager to apply to the entire job.
Refer to the Xerox Variable Data Intelligent PostScript PrintWare (VIPP)
Reference Manual for detailed information about VIPP commands, NMP
records, and JDTs. Refer to the PostScript Language Reference Manual
for information about DSC statements.
Before you use VIPP command generation for the first time, make sure
that you have:
•
Completed the installation process described in Section Two:
Installing and Customizing XDPE/400. This process includes
downloading the separator page JDT called XDPSPR.JDT to the
printer controller.
•
Addressed all network and, if applicable, duplex printing setup
requirements for VIPP mode printers as described in chapter 20,
“Remote/Network printing,” of this manual.
Printing Documents with XDPE/400 (9/2001)
17-1
VIPP command generation
VIPP functionality supported
XDPE/400 supports the following VIPP functions:
•
XDPE/400 supports only VIPP line mode. VIPP native mode is not
supported.
•
XDPE/400 supports these VIPP record formats:
—
—
Variable length format
Variable length format with Printer Carriage Control (PCC)
NOTE: All OS/400 spool files use variable length record formats
with and without PCC.
•
XDPE/400 supports only these VIPP presentation modes:
—
—
Listing
Record processing entry (RPE)
VIPP database presentation mode currently is not supported.
•
XDPE/400 supports only line printer record types. All data for an
output line is contained in a single record.
General processing requirements and considerations
Note the following requirements and considerations when processing
VIPP files with XDPE/400:
•
During spool file processing, XDPE/400 only identifies the name of
the JDT to be used by the printer for the data stream; XDPE/400
does not insert the contents of the JDT into the data stream. To be
used by the printer, all VIPP resources, including JDTs, must be
resident on the printer controller.
Every time you create or change a VIPP resource, you must
download the resource to the printer. Refer to chapter 21 for
instructions on downloading VIPP resources to the printer controller.
•
The value of the File processing mode (PROCMODE) Monitor
Queue parameter must be *PAGE.
•
Input spool files, such as Data Description Specification (DDS) or
Office Vision formatted files, that contain embedded SCS page
formatting commands may cause unpredictable results if they
contain other than simple positioning commands. For example, the
first tab in a line may be processed; however, all subsequent tabs
may not be processed.
•
List processing support of VIPP-enabled printers is limited to
N-series printers. The list processing feature does not support
resource downloads or the use of generic files for DocuSP and NPS
printers in VIPP mode.
Printing Documents with XDPE/400 (9/2001)
17-2
VIPP command generation
Generating VIPP command elements
Use one of these methods for creating, inserting, and referencing VIPP
command elements:
Indirect method
In the Indirect method, Monitor Queue maps the input spool file attributes
and inserts the corresponding VIPP commands and NMP records into the
spool file. XDPE/400 also inserts DSC packet statements identified by the
FONT ID printer file parameter into the spool file. In addition, XDPE/400
inserts a null VIPP Start line mode (STARTLM) command into the spool
file. The spool file is then released to the writer.
Direct method
In the Direct method, you first create a JDT that contains VIPP commands
describing how to process the spool file. You then download the JDT to
the printer controller.
JDTs also can be edited on the printer controller, or edited on other
systems and then downloaded to the printer controller.
During spool file processing, XDPE/400 inserts a VIPP Start line mode
(STARTLM) command into the spool file. The STARTLM command
identifies the name of the JDT to be used by the printer. XDPE/400 also
inserts DSC packet statements identified by the FONT ID printer file
parameter into the spool file. The spool file is then released to the writer.
Combined method
In the Combined method, you first create a JDT that contains VIPP
commands describing how to process the spool file. You then download
the JDT to the printer controller.
JDTs also can be edited on the printer controller, or edited on other
systems and then downloaded to the printer controller.
During spool file processing, XDPE/400 inserts a VIPP STARTLM
command into the spool file. The STARTLM command identifies the name
of the JDT to be used by the printer.
In addition, Monitor Queue maps the input spool file attributes and inserts
the corresponding VIPP commands and NMP records into the spool file.
XDPE/400 also inserts DSC packet statements identified by the FONT ID
printer file parameter into the spool file. The spool file is then released to
the writer.
Printing Documents with XDPE/400 (9/2001)
17-3
VIPP command generation
Indirect method
The Indirect method creates and inserts VIPP commands and NMP
records and imbeds the contents of PostScript DSC packets by using the
spool file attributes.
When an OS/400 application program opens a printer file for output, a
spool file is created. The attributes of that spool file are created using the
printer file parameters.
Before the spool file is released to the OS/400 writer, XDPE/400
generates and inserts VIPP commands, NMP records, and DSC
statements in the spool file based on the printer file parameters.
XDPE/400 inserts these elements in the following manner:
•
XDPE/400 inserts VIPP commands after the VIPP file start command
(%!) and before the null VIPP STARTLM command.
•
XDPE/400 inserts NMP records following the null VIPP STARTLM
command.
•
XDPE/400 places a copy of the contents of the DSC packet after the
VIPP file start command (%!) and before the VIPP STARTLM
command. The contents of the DSC packet will precede all
generated VIPP commands.
Table 17-1 shows the printer file parameters that map to XDPE/400 VIPP
features.
Table 17-1.
Printer file parameters mapping to VIPP command elements
OS/400 printer
file parameters
XDPE/400 VIPP
features
VIPP command, NMP record, or DSC statements inserted
BACKOVL
Forms invocation
NMP record containing VIPP SETBFORM command
COPIES
Number of copies
VIPP SETCYCLECOPY command and NMP record containing
VIPP SETCYCLECOPY command
DUPLEX
Duplex selection
NMP record containing VIPP DUPLEX_on,
TUMBLEDUPLEX_on, or DUPLEX_off command
FONT ID
PostScript DSC
Set of DSC processing statements
FORMFEED
Predrilled paper shift
NMP record containing VIPP SHIFT command
FRONTMGN
Margin setting
NMP record containing VIPP SETMARGIN command
FRONTOVL
Forms invocation
NMP record containing VIPP SETFORM command
MULTIUP
Multi-up printing
VIPP TWOUP or SETMULTIUP command
PAGRTT
Degree of page
rotation
NMP record containing VIPP PORT, LAND, IPORT, or ILAND
command
Printing Documents with XDPE/400 (9/2001)
17-4
VIPP command generation
Modifying printer file parameters
You can modify the printer file parameters with any of these OS/400
commands:
•
•
•
CRTPRTF to create a printer file
CHGPRTF to modify an existing printer file
OVRPRTF to override an existing printer file
For instructions on how to use the CRTPRTF, CHGPRTF, and OVRPRTF
commands, refer to OS/400 CL Reference and OS/400 Printer Device
Programming.
Printer file parameters for the VIPP Indirect method
This section describes how to use the printer file parameters to create,
insert, or reference VIPP or PostScript command elements.
BACKOVL
Specifies the name of the electronic form to print on the reverse side of
each duplex page when printing this job. You can use these values:
•
form-name — Specify a one- to eight-character form name. The form
must already exist on the printer controller. XDPE/400 generates an
NMP record that contains the VIPP SETBFORM command and the
name of the form that you specified.
•
For information about how to create VIPP forms, see “Using the
XDPE/400 VIPP resource commands” later in this chapter. Refer to
chapter 21 for instructions on downloading VIPP forms to the printer
controller.
NOTE: During spool file processing, XDPE/400 automatically
appends an extension of .frm to the name of the form that you
specify with this printer file parameter.
•
COPIES
*NONE or *FRONTOVL — Specify *NONE or *FRONTOVL if you do
not want XDPE/400 to generate an NMP record containing a VIPP
SETBFORM command.
Specifies the number of copies to print. You can use a value from 1 to 255.
XDPE/400 generates both a VIPP SETCYCLECOPY command and an
NMP record containing the VIPP SETCYCLECOPY command. Each
command indicates the number of copies you specified.
NOTE: The collation mode for your copies is based on the VIPP
COLLATE_on and COLLATE_off command settings. COLLATE_on is
the VIPP default. The VIPP default values are defined in xgf.def,
which is located in the /usr/xgf/src/ directory on the printer controller.
Printing Documents with XDPE/400 (9/2001)
17-5
VIPP command generation
DUPLEX
Specifies whether to print the output on one side of the page (simplex) or
on both sides of the page (duplex).
NOTE: For this parameter to be in effect for an NPS printer running
in VIPP mode, duplex printing must be enabled using either the
remote output queue or the Virtual Printer on the NPS controller.
Refer to chapter 20, “Remote/Network printing,” for instructions on
how to enable duplex printing.
You can use the values in the following table. XDPE/400 generates an
NMP record that contains the corresponding VIPP command identified in
the table.
DUPLEX printer
file value
FONT ID
VIPP command generated by
XDPE/400
*YES
DUPLEX_on
*TUMBLE
TUMBLEDUPLEX_on
*NO
DUPLEX_off
Identifies the name of a packet containing a set of PostScript DSC
statements. Specify only the numerical portion of the packet name;
XDPE/400 assumes that the first 3 characters of the packet name are
‘FID’. Refer to “Creating VIPP resources or PostScript DSC packets” later
in this chapter for information about the naming conventions and required
subfolder storage location in XDPEFLR for DSC packets.
XDPE/400 looks for a DSC packet in the XDPEFLR/MISLIB folder that has
a name containing ‘FID’ as the first 3 characters and the numerical value
that you specified. For example, if you specify a value of 9065 for the
FONT ID parameter, XDPE/400 will look for the object named FID9065. If
the value you specify contains any leading zeroes, XDPE/400 will ignore
the leading zeroes. For example, if you specify a value of 005, XDPE/400
will look for the object named FID5.
XDPE/400 then places a copy of the contents of the DSC packet after the
VIPP file start command (%!) for the data stream. For more information
about DSC packets, refer to “PostScript DSC packets” later in this
chapter.
FORMFEED
Specifies that the printer uses the page shift value for predrilled paper.
You can use these values:
•
Any value other than *CONT or *DEVD — Specify a valid OS/400
value other than *CONT or *DEVD (such as *AUTOCUT, *CUT,
*CONT2) if you want XDPE/400 to generate an NMP record that
contains a VIPP SHIFT command. XDPE/400 uses the Predrilled
shift support (SHIFT) global values when generating the VIPP SHIFT
command parameters. Refer to chapter 6 in Section Two: Installing
and Customizing XDPE/400 for information about the Predrilled shift
support (SHIFT) global values.
Printing Documents with XDPE/400 (9/2001)
17-6
VIPP command generation
This table shows how XDPE/400 maps each Predrilled shift support
(SHIFT) global value to each VIPP SHIFT parameter:
SHIFT global value
VIPP SHIFT
command parameter
Front side - long edge
Xfront
Back side - long edge
Xback
Front side - short edge
Yfront
Back side - short edge
Yback
XDPE/400 assumes that the VIPP SETUNIT command in your JDT is
either set to DOT3 (1/300 inch) or, if no SETUNIT command is
specified, uses the VIPP default value of DOT3. If your JDT specifies
any other SETUNIT value (such as pels or inches) or if you have
changed the VIPP default value, you will have to adjust the Predrilled
shift support (SHIFT) global values to the appropriate conversion
values.
FRONTMGN
•
*CONT — Specify *CONT if you want XDPE/400 to generate an
NMP record that contains a VIPP SHIFT command using all zero
values for the horizontal (X) and vertical (Y) shift values for the front
and back pages.
•
*DEVD — Specify *DEVD if you do not want XDPE/400 to generate
an NMP record containing a VIPP SHIFT command.
Specifies the offsets from the edge of the page where printing begins (left
and top) and ends (bottom and right). You can use these values:
•
offset-down and offset-across — Specify an offset-down and
offset-across value if you want XDPE/400 to generate an NMP
record containing the VIPP SETMARGIN command. This table
shows how XDPE/400 maps each FRONTMGN value to the VIPP
SETMARGIN command parameters.
FRONTMGN printer file
value
VIPP SETMARGIN
command parameter
offset-down
top and bottom
offset-across
left and right
XDPE/400 automatically converts the FRONTMGN values, which are
in inches or centimeters, into dots before generating the VIPP
SETMARGIN command.
•
*DEVD — Specify *DEVD if you do not want XDPE/400 to generate
an NMP record containing a VIPP SETMARGIN command.
Printing Documents with XDPE/400 (9/2001)
17-7
VIPP command generation
FRONTOVL
Specifies the electronic form to be used to print this job. You can use
these values:
•
form-name — Specify a one- to eight-character form name. The form
must already exist on the printer controller. XDPE/400 generates an
NMP record that contains a VIPP SETFORM command and the
name of the form that you specified.
NOTE: In duplex mode, the form specified using this parameter
will print on every page side where there is variable text unless a
back overlay is specified using the BACKOVL parameter.
For information about how to create VIPP forms, see “Using the
XDPE/400 VIPP resource commands” later in this chapter. Refer to
chapter 21 for instructions on downloading forms to the printer
controller.
NOTE: During spool file processing, XDPE/400 automatically
appends an extension of .frm to the name of the form that you
specify with this printer file parameter.
•
MULTIUP
*NONE — Specify *NONE if you do not want XDPE/400 to generate
an NMP record containing a VIPP SETFORM command.
Specifies the number of logical pages to be printed on one physical page.
You can use these values:
•
•
•
•
1
2
3
4
—
—
—
—
Print
Print
Print
Print
one page of output on each physical page
two pages of output on each physical page
three pages of output on each physical page
four pages of output on each physical page
Refer to chapter 25 for information about how the MULTIUP value is used
during multi-up printing.
NOTE: If you specify a MULTIUP value greater than 1 using the
Indirect method, XDPE/400 will ignore any value specified for the
PAGRTT parameter. See chapter 25 for more information.
Printing Documents with XDPE/400 (9/2001)
17-8
VIPP command generation
PAGRTT
Specifies the degree of text rotation in respect to the way the page is
loaded in the printer. XDPE/400 generates an NMP record that contains
the corresponding VIPP orientation command. You can use the values
shown in this table:
*
PAGRTT value
1
VIPP command
generated by
XDPE/400
Orientation
produced
0
PORT
Portrait
90
LAND
Landscape
180
IPORT
Inverted portrait
270
ILAND
Inverted landscape
*AUTO, *DEVD, or
*COR
PORT or LAND1
Portrait or
landscape
See note below.
NOTE: If you specify *AUTO, *DEVD, or *COR, XDPE/400
uses the page width, page length, characters per inch, and
lines per inch to determine whether the page is in portrait or
landscape orientation. If the calculated width is less than or
equal to the length, XDPE/400 assumes that the orientation
is portrait. Otherwise, XDPE/400 assumes that the
orientation is landscape.
Printing Documents with XDPE/400 (9/2001)
17-9
VIPP command generation
Direct method
In the Direct method you create a VIPP JDT, download the JDT to the
printer controller, and specify the name of the JDT for your print job. For
information about how to create JDTs, refer to “Using the XDPE/400 VIPP
resource commands” later in this chapter. Refer to chapter 21 for
information about how to download JDTs to the printer controller.
Before the spool file is released to the OS/400 writer, XDPE/400
generates and inserts the name of the JDT in the spool file based on the
spool file attribute value specified for the Packet data (PACKETDATA)
Monitor Queue parameter. This is either the User data (USRDTA) spool
file attribute or the Form type (FORMTYPE) spool file attribute.
XDPE/400 also places DSC statements in the spool file if the FONT ID
printer file parameter is specified.
XDPE/400 inserts these elements in the following manner:
•
XDPE/400 obtains the name of the JDT to be used by the printer.
XDPE/400 automatically appends an extension of .jdt to the JDT
name and then inserts the JDT name with the extension in the VIPP
STARTLM command in the spool file.
If a JDT name is not specified, XDPE/400 inserts a null VIPP
STARTLM command in the spool file. The printer will use the VIPP
default values in xgf.def in the /usr/xgf/src/ directory on the printer
controller to process the file.
•
XDPE/400 places a copy of the contents of the DSC packet after the
VIPP file start command (%!) and before the VIPP STARTLM
command.
Modifying printer file parameters
You can modify the printer file parameters with any of these OS/400
commands:
•
•
•
CRTPRTF to create a printer file
CHGPRTF to modify an existing printer file
OVRPRTF to override an existing printer file
For instructions on how to use the CRTPRTF, CHGPRTF, and OVRPRTF
commands, refer to OS/400 CL Reference and OS/400 Printer Device
Programming.
Printer file parameter for the VIPP Direct method
You can use the FONT ID printer file parameter with the VIPP Direct
method to identify the name of a packet containing a set of PostScript
DSC statements. See the FONT ID discussion under “Printer file
parameters for the VIPP Indirect method” for detailed information about
how to use this printer file parameter.
Printing Documents with XDPE/400 (9/2001)
17-10
VIPP command generation
Processing considerations and requirements
Note these considerations and requirements when you are using the
Direct method:
•
As a general rule when coding your JDT, you should place VIPP
commands that print on the page (such as SETBFORM) after global
page formatting commands such as plex type, orientation, media
selection, etc.
•
If the file will be sent to an NPS printer and you specify the VIPP
SETMEDIA or SETPAGESIZE command in your JDT, you also must
specify the name of the file that contains the corresponding DSC
statements by using the FONT ID printer file parameter. For more
information about DSC statements, refer to the Xerox Variable Data
Intelligent PostScript Printware (VIPP) Reference Manual. The
Xerox DocuPrint Network Printer Series Guide to Managing Print
Jobs within the Xerox DocuPrint Network Printer Series
Documentation Set also provides information about DSC statements
for NPS printers.
NOTE: The SAMPLE file in the XDPE/400 application library
contains members DSCMEDIA and DSCSIZE. These members
are samples that show how to specify page size or media
selection for PostScript printers. You can use these samples as
templates when creating your own DSC statements for your
jobs.
•
XDPE/400 does not perform any validation edits on the contents of
your VIPP JDT or PostScript DSC packets. You are responsible for
ensuring that the contents of each JDT or DSC packet follow the
conventions and guidelines described in the VIPP Reference Manual
or the PostScript Language Reference Manual.
Combined method
The Combined method is a combination of the Direct method and the
Indirect method. You can use the Combined method to generate, insert,
or reference VIPP command elements for the data stream. You also can
use the Combined method to insert the contents of DSC packets by using
the FONT ID printer file parameter.
XDPE/400 generates a VIPP STARTLM command specifying the name of
the JDT to be used by the printer. XDPE/400 then generates VIPP
commands and Native Mode Prefix (NMP) records and inserts DSC
statements based on the spool file attributes described earlier for the
Indirect method.
Printing Documents with XDPE/400 (9/2001)
17-11
VIPP command generation
Application order of VIPP commands
Since VIPP requires that a STARTLM command with a JDT name be the
first VIPP command in a spool file, any Indirect attributes specified will
override any VIPP commands specified in the referenced JDT.
NOTE: In VIPP mode, the value specified for the Order of sequence
(SEQUENCE) Monitor Queue parameter has no effect on the
application order of VIPP commands.
Processing considerations and requirements
Note these considerations and requirements when you are using the
Combined method:
•
If you specify a COPIES value in the spool file attributes, you also
must specify the maximum number of copies in your JDT using the
VIPP SETCYCLECOPY command.
•
The Combined method currently is not supported for VIPP multi-up
printing when using the spool file attributes if a JDT is specified.
Refer to chapter 25 for information about how you can produce VIPP
multi-up printing if you use the Combined method as your command
generation method.
•
If the file will be sent to an NPS printer and you specify the VIPP
SETMEDIA or SETPAGESIZE command in your JDT, you also must
specify the name of the file that contains the corresponding DSC
statements by using the FONT ID printer file parameter. For more
information about DSC statements, refer to the Xerox Variable Data
Intelligent PostScript Printware (VIPP) Reference Manual. The
Xerox DocuPrint Network Printer Series Guide to Managing Print
Jobs within the Xerox DocuPrint Network Printer Series
Documentation Set also provides information about DSC statements
for NPS printers.
NOTE: The SAMPLE file in the XDPE/400 application library
contains members DSCMEDIA and DSCSIZE. These members
are samples that show how to specify page size or media
selection for PostScript printers. You can use these samples as
templates when creating your own DSC statements for your
jobs.
•
XDPE/400 does not perform any validation edits on the contents of
your VIPP JDT or PostScript DSC packets. You are responsible for
ensuring that the contents of each JDT or DSC packet follow the
conventions and guidelines described in the Xerox Variable Data
Intelligent PostScript Printware (VIPP) Reference Manual or the
PostScript Language Reference Manual.
Printing Documents with XDPE/400 (9/2001)
17-12
VIPP command generation
PostScript DSC packets
The XDPE/400 DSC packet feature allows you to insert a copy of the
contents of an object containing PostScript DSC statements into your
print jobs. The contents do not have to be XDPE/400-specific.
A DSC packet is an ASCII object that is stored in the XDPEFLR/MISLIB
subfolder with the name FIDnnnnn (where nnnnn is a user-assigned
number). Refer to “Using the XDPE/400 VIPP resource commands” later
in this chapter for information about the required subfolder storage
location in XDPEFLR for DSC packets.
You identify the name of the object that contains the DSC statements to
be inserted by using the FONT ID printer file parameter. During spool file
processing, XDPE/400 will place a copy of the object’s contents after the
VIPP file start command (%!) and before the first VIPP command.
Creating a PostScript DSC packet
You can create a PostScript DSC packet by using the Create VIPP
Resource (CRTVIPRSC) command. For information about how to use
CRTVIPRSC, see “Using the XDPE/400 VIPP resource commands” later
in this chapter.
XDPE/400 does not perform any validation edits on the contents of your
DSC packet. You are responsible for ensuring that the DSC statements
within the packet follow the conventions and guidelines described in the
PostScript Language Reference Manual.
Inserting DSC packets through the FONT ID printer file
parameter
You can insert PostScript DSC directly into the data stream by specifying
the name of a DSC packet using the Font identifier (FONT ID) printer file
parameter. The DSC packet name refers to an ASCII object of the
corresponding name located in the XDPEFLR/MISLIB folder.
You can use this method with either the Direct, Indirect or Combined
command generation method.
Printing Documents with XDPE/400 (9/2001)
17-13
VIPP command generation
Samples provided by XDPE/400
XDPE/400 provides a number of VIPP or PostScript samples that can
assist you in the setup and definition of the VIPP command elements.
Table 17-2 identifies the name, location, and purpose of each sample
provided.
Table 17-2.
VIPP and PostScript samples provided by XDPE/400
Resource name
XDPE/400 location
Contents
Members
DSCMEDIA and
DSCSIZE
SAMPLE file in the
XDPE/400 application
library
Sample DSC media and DSC page size statements
that can be used as templates when creating DSC
statements for print jobs
XDPSMP.FRM
XDPEFLR/FORMLIB folder
Sample front form
Note that XDPEFLR/FORMLIB also contains a front
form called XDPIVP.FRM. XDPIVP.FRM is used by
XDPE/400 when you run the installation verification
procedure.
XDPBCK.FRM
XDPEFLR/FORMLIB folder
Sample back form
XDPLPJOB.FRM
XDPEFLR/FORMLIB folder
Sample job-level form for LPP testing
XDPLPPGE.FRM
XDPEFLR/FORMLIB folder
Sample page-level form for LPP testing
XDPSMP.JDT
XDPEFLR/JDTLIB folder
Sample JDT
XDPLPJOB.JDT
XDPEFLR/JDTLIB folder
Sample job-level JDT for LPP testing
XDPLPPGE.JDT
XDPEFLR/JDTLIB folder
Sample page-level JDT for LPP testing
XGF.DEF
XDPEFLR/MISLIB folder
Sample VIPP default file
Note that these defaults may differ from the defaults
defined for xgf.def in /usr/xgf/src/ on your printer.
Printing Documents with XDPE/400 (9/2001)
17-14
VIPP command generation
Using the XDPE/400 VIPP resource commands
Before the printer can use a VIPP resource as part of a job, the VIPP
resource must be created and then downloaded to the appropriate
directory on the printer controller. Before a PostScript DSC packet can be
used as part of a job, the packet must be created and stored in the MISLIB
subfolder of XDPEFLR.
This section describes the XDPE/400 VIPP commands available that
allow you to create, edit, display, print, or delete these types of resources:
•
•
•
•
•
•
VIPP JDTs
VIPP forms
VIPP segments
VIPP encoding tables
VIPP core and setup files
PostScript DSC packets
Refer to chapter 21 for instructions on downloading VIPP resources to the
printer controller.
NOTE: You cannot use the VIPP resource commands for creating or
editing font (.psf) or image (.tif) files. However, you can download
existing font and image files using the Download VIPP Resource
(DNLDVIP*) commands. For more information see chapter 21.
Creating VIPP resources or PostScript DSC packets
Use the Create VIPP Resource (CRTVIPRSC) command to create a new
VIPP resource or PostScript DSC packet. The CRTVIPRSC command
uses the IBM Source Entry Utility (SEU) editor for creating the resource
or packet.
NOTE: It is your responsibility to know and understand the IBM SEU
editor. For information on using the SEU editor, refer to Source Entry
Utility User’s Guide and Reference.
Other text editors can be used as long as the editor appends a carriage
return and line feed to the end of each line. If you choose to use a different
text editor, make sure the VIPP resource or PostScript DSC packet
resides in these folders:
Resource or packet type
XDPE/400 folder location
VIPP JDTs
XDPEFLR/JDTLIB
VIPP forms and segments
XDPEFLR/FORMLIB
VIPP encoding tables
XDPEFLR/ENCODING
VIPP core and setup files, and
PostScript DSC packets
XDPEFLR/MISLIB
Printing Documents with XDPE/400 (9/2001)
17-15
VIPP command generation
Follow these steps to create a VIPP resource or DSC packet:
Step 1.
Enter CRTVIPRSC and press ENTER. The Create VIPP resource
(CRTVIPRSC) command screen displays.
Create VIPP Resource (CRTVIPRSC)
Type choices, press Enter.
VIPP resource name . . . . . . .
Folder specification . . . . . .
____________
*JDT
F3=Exit
F4=Prompt
F24=More keys
F12=Cancel
F5=Refresh
Name
*JDT, *FRM, *ENC, *MIS
Bottom
F13=How to use this display
Step 2.
Enter the appropriate values for each screen parameter. Refer to
“Resource creation parameters” later in this chapter for the valid values
for each parameter.
Step 3.
Press ENTER. An SEU session is launched for you to enter your VIPP
resource commands or DSC statements.
XDPE/400 will not perform any validation edits on the contents of your
VIPP resource or DSC packet. You are responsible for ensuring that the
contents of each VIPP resource or PostScript DSC packet follows the
conventions and guidelines described in the Xerox Variable Data
Intelligent PostScript Printware (VIPP) Reference Manual or the
PostScript Language Reference Manual.
Step 4.
When you have entered all your commands or statements, select the F3
function key to exit the edit screen. Upon exiting the edit screen, an
OS/400 exit screen appears. Typically, you do not need to change any of
the parameters on this screen. Simply press ENTER to continue.
Printing Documents with XDPE/400 (9/2001)
17-16
VIPP command generation
If necessary, these two parameters may be changed on the exit screen:
•
Print member — Allows you to print the resource or packet contents
that you just created.
•
Return to editing — Allows you to return to the SEU editing session
that you just left.
CAUTION: Unexpected results may occur if any other parameters are
changed on the exit screen.
Step 5.
A prompt will appear asking if you would like to save the resource or
packet in the specified subfolder.
•
•
Type Y to save the resource or packet to the specified subfolder.
XDPE/400 then attempts to save the resource or packet:
—
If the save operation is successful, XDPE/400 displays a
message indicating the name of the resource or packet and the
subfolder in which it was saved.
—
If a resource or packet with the same name already exists in the
subfolder, you will be prompted to enter a different name under
which to save the resource or packet, or you can press F3 or
F12 to exit without saving the resource or packet.
—
If the save operation is not successful, XDPE/400 displays an
error message.
Type N if you do not want to save the resource or packet. XDPE/400
displays a message indicating that the resource or packet was not
saved.
Resource creation parameters
VIPP resource name
(VIPRSC)
Specifies the name of the VIPP resource you want to create. The format
of the VIPP resource name is as follows:
resource.ext
where
•
resource is a user-defined name for the VIPP resource or PostScript
DSC packet.
—
For VIPP resources, the resource name can be one- to
eight-characters in length. The name must follow these
conventions:
•
The first character must be alphabetic.
•
The remaining one- to seven-characters can consist of the
following characters: A through Z, 0 through 9, _, @, #, or $.
Printing Documents with XDPE/400 (9/2001)
17-17
VIPP command generation
—
•
For PostScript DSC packets, the resource name can be four- to
eight-characters in length. The name must follow these
conventions:
•
The first 3 characters must be FID.
•
The remaining one- to five-characters must be a numeric
value. You should avoid specifying leading zeroes in the
value. For example, specify 656 rather than 00656.
.ext indicates the resource extension. The extension follows these
conventions:
—
For VIPP resources other than encoding tables and PostScript
DSC packets, the extension can be one- to three-alphanumeric
characters. Make sure that you specify the appropriate
extension for the VIPP resource type:
VIPP resource type
—
Valid extension
JDTs
.jdt
forms
.frm
segments
.seg
VIPP core and setup files
any other extension
For VIPP encoding tables and PostScript DSC packets, do not
specify an extension.
Do not enclose the VIPP resource or PostScript DSC packet name within
double quotes or other characters.
NOTE: If you enter the VIPP resource name in lowercase letters,
XDPE/400 will save the name in uppercase letters.
These are examples of valid VIPP resource or DSC packet names:
•
•
•
•
•
ACCTG.FRM
GL_VIPP.JDT
[email protected]
FID16
FID9065
Printing Documents with XDPE/400 (9/2001)
17-18
VIPP command generation
Folder specification
(FLRSPC)
Specifies the folder in which the VIPP resource or DSC packet will reside.
You can use these values:
•
*JDT — Stores the resource in the JDTLIB subfolder of XDPEFLR.
•
*FRM — Stores the resource in the FORMLIB subfolder of
XDPEFLR.
•
*ENC — Stores the resource in the ENCODING subfolder of
XDPEFLR.
•
*MIS — Stores the resource or packet in the MISLIB subfolder of
XDPEFLR.
Make sure that you store your resource in the folder that is appropriate for
the resource type, as shown below:
Resource or packet type
XDPE/400 folder location
VIPP JDTs
XDPEFLR/JDTLIB
VIPP forms and segments
XDPEFLR/FORMLIB
VIPP encoding tables
XDPEFLR/ENCODING
VIPP core and setup files, and
PostScript DSC packets
XDPEFLR/MISLIB
Printing Documents with XDPE/400 (9/2001)
17-19
VIPP command generation
Example of creating a new VIPP resource
This example shows how to create and store a new VIPP JDT called
GL_VIPP.JDT.
Step 1.
Sign on and, if necessary, add the XDPE/400 application library to the
library list for your user profile.
Step 2.
Enter CRTVIPRSC at any OS/400 command prompt.
Step 3.
Enter GL_VIPP.JDT as the name of your new VIPP JDT.
Step 4.
Enter *JDT as the name of the subfolder. For example:
Create VIPP Resource (CRTVIPRSC)
Type choices, press Enter.
VIPP resource name . . . . . . .
Folder specification . . . . . .
GL_VIPP.JDT
*JDT
F3=Exit
F4=Prompt
F24=More keys
F12=Cancel
F5=Refresh
Printing Documents with XDPE/400 (9/2001)
Name
*JDT, *FRM, *ENC, *MIS
Bottom
F13=How to use this display
17-20
VIPP command generation
Step 5.
Press ENTER. XDPE/400 launches an SEU session in which you can
enter your VIPP commands for the JDT. For example:
Columns . . . :
1 71
Edit
XDPE214/XTICKET
SEU==>
GL_VIPP
FMT ** ...+... 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+... 7
*************** Beginning of data *************************************
'''''''
'''''''
'''''''
'''''''
'''''''
'''''''
'''''''
'''''''
'''''''
'''''''
'''''''
'''''''
'''''''
'''''''
'''''''
****************** End of data ****************************************
F3=Exit
F4=Prompt
F16=Repeat find
Step 6.
F5=Refresh
F9=Retrieve
F17=Repeat change
F10=Cursor
F11=Toggle
F24=More keys
When you have entered all your VIPP commands for the JDT, select F3
to exit the edit screen. Upon exiting the edit screen, an OS/400 exit screen
appears.
Printing Documents with XDPE/400 (9/2001)
17-21
VIPP command generation
Do not change any of the parameters on this screen. Press ENTER to
continue.
Exit
Type choices, press Enter.
Change/create member . . . . . . .
Member . . . . . . . . . . . . .
File . . . . . . . . . . . . . .
Library . . . . . . . . . . . .
Text . . . . . . . . . . . . . .
Resequence member . . . . . . . .
Start . . . . . . . . . . . . .
Increment . . . . . . . . . . .
Y
Y=Yes, N=No
GL_VIPP
Name, F4 for list
XTICKET
Name, F4 for list
XDPE212
Name
_______________________________________
Y
0001.00
01.00
Y=Yes, N=No
0000.01-9999.99
00.01-99.99
. . . . . . . . . . .
N
Y=Yes, N=No
Return to editing . . . . . . . . .
N
Y=Yes, N=No
Go to member list . . . . . . . . .
N
Y=Yes, N=No
Print member
F3=Exit
F4=Prompt
F5=Refresh
Printing Documents with XDPE/400 (9/2001)
F12=Cancel
17-22
VIPP command generation
Step 7.
A prompt will appear asking if you would like to save the resource in the
subfolder specified in the FLRSPC parameter:
XDPE/400 VIPP Resource
Y
Would you like to save this resource to the
specified folder?
Y = Yes
N = No
F3=Exit
F12=Cancel
Type Y. The system will store GL_VIPP.JDT in the JDTLIB subfolder of
XDPEFLR. Once GL_VIPP.JDT is successfully stored, the system will
display a message indicating that GL_VIPP.JDT has been saved to the
JDTLIB subfolder.
NOTE: Before this VIPP resource can be used by a print application,
you must download the resource to the printer controller. Refer to
chapter 21 for instructions on how to download a new resource to the
printer controller.”
Printing Documents with XDPE/400 (9/2001)
17-23
VIPP command generation
Editing, displaying, or printing a VIPP resource or
PostScript DSC packet
Use the Change VIPP Resource (CHGVIPRSC) command to edit, display,
or print either VIPP resources or PostScript DSC packets created with the
Create VIPP Resources command.
Follow these steps to edit, display, or print a VIPP resource or DSC
packet:
Step 1.
Enter CHGVIPRSC and press ENTER. The Change VIPP Resource
(CHGVIPRSC) command screen displays.
Change VIPP Resource (CHGVIPRSC)
Type choices, press Enter.
VIPP resource name . . . . . . .
Process option . . . . . . . . .
Folder specification . . . . . .
____________
*EDIT
*JDT
F3=Exit
F4=Prompt
F24=More keys
F12=Cancel
F5=Refresh
Name
*EDIT, *DISPLAY, *PRINT
*JDT, *FRM, *ENC, *MIS
Bottom
F13=How to use this display
Step 2.
Enter the name of the VIPP resource or DSC packet you want to edit,
display, or print.
Step 3.
Specify the type of function you want to perform:
Step 4.
•
*EDIT to edit a VIPP resource or DSC packet
•
*DISPLAY to display the contents of a VIPP resource or DSC packet
•
*PRINT to write the contents of the VIPP resource or DSC packet to
a spool file for printing
Enter the name of the folder in which the resource or packet currently
resides.
Printing Documents with XDPE/400 (9/2001)
17-24
VIPP command generation
Step 5.
Press ENTER. Depending on the option that you specified in step 3,
XDPE/400 performs these functions:
•
If you specified *EDIT, XDPE/400 launches an SEU session in which
you can edit your resource commands or DSC statements. See
“Editing VIPP resources or DSC packets” below for more information
about how to use this option.
•
If you specified *DISPLAY, XDPE/400 displays the contents of the
requested resource or packet. Once you finish browsing the
contents, select F3 to end the SEU session.
•
If you specified *PRINT, XDPE/400 writes the data from the
requested resource or packet to a spool file named QPSUPRTF in
your default output queue.
Editing VIPP resources or DSC packets
If you select the *EDIT option on the Change VIPP Resources
(CHGVIPRSC) command screen and press ENTER, XDPE/400 launches
an SEU editing session in which you can change the contents of your
resource or packet.
NOTE: XDPE/400 will not perform any validation edits on your
changes. You are responsible for ensuring that the contents of each
VIPP resource or PostScript DSC packet follows the conventions and
guidelines described in the Xerox Variable Data Intelligent PostScript
Printware (VIPP) Reference Manual or the PostScript Language
Reference Manual.
When you have entered all your changes, select the F3 function key to
exit the edit screen. Upon exiting the edit screen, an OS/400 exit screen
appears. Typically, you do not need to change any of the parameters on
this screen. Simply press ENTER to continue.
If necessary, these two parameters may be changed on the exit screen:
•
Print member — Allows you to print the resource or packet contents
that you just created.
•
Return to editing — Allows you to return to the SEU editing session
that you just left.
CAUTION: Unexpected results may occur if any other parameters are
changed on the exit screen.
Printing Documents with XDPE/400 (9/2001)
17-25
VIPP command generation
A prompt will appear asking if you would like to save the changed
resource or packet in the specified subfolder.
•
Type Y to save the changed resource or packet to the specified
subfolder. XDPE/400 displays a message indicating the name of the
resource or packet and the subfolder in which it was saved.
•
Type N if you do not want to save your changes. XDPE/400 displays
a message indicating that the changed resource or packet was not
saved.
Even though you change a VIPP resource using the CHGVIPRSC
command, your changed resource will not be used by a print job until you
download the new version of the VIPP resource to the printer controller.
Refer to chapter 21 for instructions on how to download a VIPP resource
to the printer controller.”
Printing Documents with XDPE/400 (9/2001)
17-26
VIPP command generation
Deleting a VIPP resource or DSC packet
Use the Delete VIPP Resource (DLTVIPRSC) command to delete a VIPP
resource or PostScript DSC packet that was created with the Create VIPP
Resources (CRTVIPRSC) command.
Follow these steps to delete a VIPP resource or DSC packet:
Step 1.
Enter DLTVIPRSC. The Delete VIPP Resource (DLTVIPRSC) command
screen displays.
Delete VIPP Resource (DLTVIPRSC)
Type choices, press Enter.
VIPP resource name . . . . . . .
Folder specification . . . . . .
____________
*JDT
F3=Exit
F4=Prompt
F24=More keys
F12=Cancel
F5=Refresh
Name
*JDT, *FRM, *ENC, *MIS
Bottom
F13=How to use this display
Step 2.
Enter the name of the VIPP resource or DSC packet you want to delete.
Step 3.
Enter the name of the folder in which the resource or packet currently
resides. You can use these values:
•
•
•
•
*JDT — Selects the JDTLIB subfolder of XDPEFLR
*FRM — Selects the FORMLIB subfolder of XDPEFLR
*ENC — Selects the ENCODING subfolder of XDPEFLR
*MIS — Selects the MISLIB subfolder of XDPEFLR
Press ENTER to delete the resource or packet.
Step 4.
XDPE/400 will display a message indicating whether the delete operation
was successful.
Printing Documents with XDPE/400 (9/2001)
17-27
VIPP command generation
Printing Documents with XDPE/400 (9/2001)
17-28
18.
18
Using Monitor Queue
This chapter describes Monitor Queue, the XDPE/400 function that
processes application spool files for printing. These topics about the
operation of Monitor Queue are covered:
•
•
•
•
•
•
•
Monitor Queue operation
Starting a Monitor Queue session
Displaying a Monitor queue session
Changing a Monitor Queue session
Ending a Monitor Queue session
Resetting a Monitor Queue session
Monitor Queue messages
NOTE: To start, change, end, or reset a Monitor Queue session, your
user ID must be entered in the system directory and have *JOBCTL
and *SPLCTL special authorities. Refer to “Creating an XDPE/400
user profile” in Chapter 5 of Section Two: Installing and Customizing
XDPE/400 for instructions on enrolling a user in the system directory.
If you are running your system at security level 40 or higher, see the
“Security requirements” in Chapter 4 of Section Two: Installing and
Customizing XDPE/400 before starting a Monitor Queue session.
Refer to chapter 19 for more information about managing your print jobs.
Refer to chapter 20 for more information about printing over networks.
Printing Documents with XDPE/400 (9/2001)
18-1
Using Monitor Queue
Monitor Queue operation
Once your application has created a spool file and placed it on an output
queue, start a Monitor Queue session for that queue. Each Monitor Queue
session monitors a specific output queue. To monitor more than one
output queue at a time, you can have multiple Monitor Queue sessions
running concurrently. The number of Monitor Queue sessions you can run
is based on available resources. Each session can be set up
independently and can use the same print device or different devices. If
multiple Monitor Queue sessions are sharing a device using the same
output queue, only one writer can be started for that queue. All other
Monitor Queue sessions must have *NONE for the Printer writer (WTR)
Monitor Queue parameter.
When you start a Monitor Queue session, the Monitor Queue creates a
working output queue in the XDPE/400 application library. The working
output queue is given the same name as the monitored output queue. For
example, if the output queue you are monitoring is named PROD1,
Monitor Queue will create an output queue named PROD1 in the
XDPE/400 application library. Figure 18-1 shows the processing flow of
three Monitor Queue sessions running concurrently.
When a spool file with a status of *RDY is placed in the monitored output
queue, Monitor Queue moves the file to the working output queue in the
XDPE/400 application library. This is where the file is processed. Monitor
Queue offers two types of file processing modes, *JOB and *PAGE, which
are specified by the File processing mode (PROCMODE) Monitor Queue
parameter.
Figure 18-1. Multiple Monitor Queue sessions
Printing Documents with XDPE/400 (9/2001)
18-2
Using Monitor Queue
When the file processing mode is *JOB, Monitor Queue creates a prepend
file containing job level commands and banner page data, a spool file
containing the original print data, and a postpend file containing printer
reset commands.
In *PAGE mode, Monitor Queue creates a single spool file that integrates
job and page level commands, banner page data, and the print data from
your original spool file. *PAGE mode is necessary for all higher
processing functions, such as logical processing, and is the
recommended mode. See the File processing mode (PROCMODE)
Monitor Queue parameter description later in this chapter for more
information about which method to use. Also see chapter 19 for more
information about *JOB and *PAGE processing modes.
Depending on how your Monitor Queue session is configured, the spool
file(s) will either be moved to a remote/network output queue, written to a
printer, or remain in the queue in the XDPE/400 application library.
Multiple sessions of Monitor Queue can run at the same time, each one
monitoring a different output queue and sending data to a different printer.
Monitor Queue does not use any more of the system resources than
necessary. For example, if there are no spool files to be processed,
Monitor Queue enters into an idle state until a print job arrives at the
output queue.
Printing Documents with XDPE/400 (9/2001)
18-3
Using Monitor Queue
Starting a Monitor Queue session
Each time you enter the Start Monitor Queue (STRMONQ) command, one
Monitor Queue session is started. Follow these steps to start a Monitor
Queue session:
Step 1.
Enter STRMONQ and press ENTER. The Start Monitor Queue menu
displays.
Start Monitor Queue (STRMONQ)
Type choices, press Enter.
Output queue .
Library . .
Printer writer
Interface box
Printer model
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*LIBL
Name
Name, *LIBL, *CURLIB
Name, *NONE
*FLEX, *USAII, *SOLIMAR...
4050, 4090, 4135, 4235...
Bottom
F3=Exit F4=Prompt F5=Refresh F10=Additional parameters
F13=How to use this display F24=More keys
F12=Cancel
Step 2.
Enter the appropriate option for each field and press ENTER.
Step 3.
Press F9 or press ENTER. The following three Start Monitor Queue
menus will be displayed.
Printing Documents with XDPE/400 (9/2001)
18-4
Using Monitor Queue
Step 4.
Modify the parameters you want, following the conventions described in
the next session, and press ENTER.
Start Monitor Queue (STRMONQ)
Type choices, press Enter.
Output queue . . . .
Library . . . . .
Printer writer . . .
Interface box . . .
Printer model . . .
Printer emulation .
Software version . .
Printer mode . . . .
Xerox interface mode
Set interface mode .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*LIBL
5225
*V1R1
*XPPM
*NORMAL
*YES
Name
Name, *LIBL, *CURLIB
Name, *NONE
*FLEX, *USAII, *SOLIMAR...
4050, 4090, 4135, 4235...
5225, 5219, *NOSCS
*V1R1, *V1R2, *V1R5
*XPPM, *XDPM, *PCL, *VIPP
*NORMAL, *PASSTHRU
*YES, *NO
Additional Parameters
File processing mode . . .
Pass option . . . . . . .
Pass through option . . .
*PAGE
*CONT
*PRINT
*PAGE, *JOB, *AUTO
*CONT, *SINGLE
*PRINT, NOPRINT
More...
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
F12=Cancel
F13=How to use this display
Start Monitor Queue (STRMONQ)
Type choices, press Enter.
Packet data . . . . . . .
Always generate . . . . .
Order of sequence . . . .
File separators . . . . .
Process separator page. .
Separator page source . .
Data page source . . . .
Default packet option . .
Leading RSTACK option . .
Trailing RSTACK option .
Queue for packet messages
Library . . . . . . .
Form type options:
Form type . . . . . .
Message option . . . .
Wait time between files .
*USRDTA
*NONE
*PACKET
*FILE
*BOTH
*NONE
*NONE
*NO
*YES
*NO
*USER
*LIBL
*USRDTA, *FORMTYPE, *PAGEINFO
*NONE, *INDIRECT, *DIRECT...
*PACKET, *ATTRIB
0-9, *FILE
*YES, *NO, *BOTH, *TRLR
*NONE, *MAIN, *AUX, *AUTO...
*NONE, *MAIN, *AUX, *AUTO...
*YES, NO
*YES, NO
*YES, NO
Name, *USER, *SYSOPR, *NONE
Name, *LIBL, *CURLIB
*ALL
*NOMSG
1
Form type, *ALL, *STD
*NOMSG, *MSG
0-60 seconds
More...
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
Printing Documents with XDPE/400 (9/2001)
F12=Cancel
F13=How to use this display
18-5
Using Monitor Queue
Start Monitor Queue (STRMONQ)
Type choices, press Enter.
Multi-part printing . . . . . .
Save output queue . . . . . . .
Library. . . . . . . . . . .
Device class . . . . . . . . .
Remote/Network output queue . .
Library . . . . . . . . . . .
Workstation customizing object
Library . . . . . . . . . . .
MRP internal interface mode . .
*NO
*OUTQ
*OUTQLIB
*LCL
*LIBL
*XDPEDFT
*LIBL
*NONE
*YES, *NO
Name, *OUTQ
Name, *OUTQLIB, *LIBL...
*LCL, *RMT, *NET
Name
Name, *LIBL, *CURLIB
Name, *XDPEDFT, *EURODFT
Name, *LIBL, *CURLIB
*MRP0, *MRP5, *MRP6, *NONE
Bottom
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
F12=Cancel
F13=How to use this display
Monitor Queue parameters
Output queue (OUTQ)
Specifies the name of the monitored output queue. You cannot use the
STRMONQ command to start a monitor session for an output queue that
is already being monitored.
CAUTION: When specifying an output queue to be monitored using
the Output queue (OUTQ) Monitor Queue parameter, do not use an
output queue in the XDPE/400 application library, or an output queue
that is used as a remote/network output queue.
Library
Specifies the name of the library in which the output queue is located. You
can use these values:
•
*LIBL — Uses the library list to locate the output queue.
•
*CURLIB — Uses the current library for the job to locate the output
queue. If a current library is not specified for the job, QGPL is used.
•
name — Specifies the name of the library in which the output queue
resides.
Printing Documents with XDPE/400 (9/2001)
18-6
Using Monitor Queue
Printer writer (WTR)
Interface box (INTERFACE)
Specifies the name of the printer writer or device description file assigned
to Monitor Queue. This specifies the printer to use to print the spool file.
You can either specify the name of a printer writer or *NONE. If *NONE is
specified, XDPE/400 will process the spool files without writing them to a
printer. When specifying *NONE, note these considerations:
•
To use this option, File processing mode (PROCMODE) must be
*PAGE and Wait time between files (WAITTIME) must be 0 (zero).
•
Processed spool files are placed in the XDPE/400 internal output
queue in the XDPE/400 application library. For example, if the
monitored output queue is PRT505, XDPE/400 places the processed
spool files in a queue named PRT505 in the XDPE/400 application
library.
•
It is the user’s responsibility to start a writer to this output queue.
XDPE/400 does not automatically start a writer to this queue.
Specifies the interface used to connect the Xerox printer to the AS/400.
Refer to tables 18-1 and 18-2 for the valid combinations of interface
boxes, printer models, and printer modes. You can use these values:
•
*AGILE — Specifies an AGILE interface box.
•
*BARR — Specifies a BARR interface box.
•
*FLEX — Specifies a Xerox FLEX or i-data interface box.
•
*INTERNAL — Specifies that the interface is internally located in the
Xerox printer.
•
*MPI — Specifies an MPI interface box.
•
*PCSUPP — Specifies that the printer is attached to a PC parallel
port, or connected on a network.
•
*SMART — Specifies a SMART interface box. This interface is valid
only for 4235 XPPM printers.
•
*SOLIMAR — Specifies a SOLIMAR interface box.
•
*USAII — Specifies a SPUR USA interface box.
•
*X3X — Specifies a 3X twinax print station interface box.
Printing Documents with XDPE/400 (9/2001)
18-7
Using Monitor Queue
Printer model (MODEL)
Specifies the model number of the Xerox printer. You can use these
values:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Printer emulation
(PRTTYPE)
Software version (VERSION)
9790
9700
8790
8700
4890
4890NPS
4850
4850NPS
4700
4635NPS
4520
4517
4512
4450
4235
4230
4220
4219
4215
4213 (model II)
4135
4090
4090NPS
4050
4050NPS
4030
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
3700
180LPS
180NPS
92CLPS
92CNPS
DC265LP
DC255LP
DP96
DP96NPS
DP65
N4025
N3225
N2825
N2125
N2025
N40
N32
N24
N17
*DOCUSP
*LCDS
*NPS
*PCL
*VIPP
*XJT
Specifies the printer type that the Xerox printer emulates. Also, enables
you to specify if the Monitor Queue should not generate SCS commands.
You can use these values:
•
5225 — Emulates the IBM 5225 printer
•
5219 — Emulates the IBM 5219 printer
•
*NOSCS — Specifies that the Monitor Queue will not generate SCS
commands
Specifies the software version of the Xerox 4235 printer. You can use
these values:
•
*V1R1 — Specifies that the printer operating system is operating at
version 1, release 1
•
*V1R2 — Specifies that the printer operating system is operating at
version 1, release 2
•
*V1R5 — Specifies that the printer operating system is operating at
version 1, release 5 or above
Printing Documents with XDPE/400 (9/2001)
18-8
Using Monitor Queue
Printer mode (MODE)
Specifies the mode in which the printer will operate. You can use these
values:
•
*XPPM — Uses a DJDE data stream for a Xerox centralized printer
•
*XDPM — Uses an XES data stream for a Xerox decentralized
printer
•
*PCL — Uses a PCL data stream for a Xerox PCL printer
•
*VIPP — Uses a VIPP data stream for a Xerox PostScript printer
Tables 18-1 and 18-2 show the supported configuration for
XDPE/400-supported printers by printer type.
Table 18-1.
Interface devices for XDPE/400-supported XPPM and XDPM printers
Mode
4235, 3700
4700, 4213, 4030 II
4450
9790, 9700, 8790, 8700, 4890,
4850, 4635, 4135, 4090, 4050,
180 LPS, 92C LPS, DP96,
*LCDS
XPPM
Flex, Agile, Smart,
3X (4235 only)
—
INTERNAL
Spur USAII, Solimar, BARR
XDPM
Flex, Agile, MPI,
PCSUPP, 3X (4235 only)
Flex, Agile, MPI,
PCSUPP
—
—
Table 18-2.
Interface devices for XDPE/400-supported PCL and PostScript printers
4230, 4220, 4219,
4215, *PCL
Mode
4520, 4517, 4512,
DC265LP,
DC255LP, *PCL
4890 NPS, 4850 NPS,
4635 NPS, 4090 NPS,
4050 NPS, 180 NPS,
92C NPS, DP96 NPS,
DP65, N32, N24,
*DOCUSP, *NPS, *XJT
N4025, N3225, N2825,
N2125, N2025, N40,
N17, *VIPP
PCL
PCSUPP,
INTERNAL
PCSUPP
PCSUPP
—
PostScript
—
—
PCSUPP
PCSUPP
Xerox interface mode
(XINTMODE)
Determines whether XDPE/400 processes the data stream by converting
it into metacode for the printer. This option only applies to these areas:
•
•
The Xerox 4450 printer, when the interface is *INTERNAL
When the interface is *BARR
Printing Documents with XDPE/400 (9/2001)
18-9
Using Monitor Queue
You can use these values:
•
*NORMAL — Converts the data stream to metacode.
During normal mode processing, the 4450 printer generates internal
printer commands from the OS/400 print stream commands.
XDPE/400 does the following:
•
—
Detects and processes page orientation commands (PMODE
DJDEs).
—
Alters the internal page formatting specification (FONT DJDE) to
match the new page.
—
Overrides any externally generated global page formatting rules
(FORMAT DJDEs).
—
Converts the page rotation spool file attribute to a PMODE
DJDE. This DJDE directs page formatting for the 4450 printer.
*PASSTHRU — Does not convert the data stream to metacode.
BEGIN and FONT commands are generated for the printer.
During pass through mode processing, the 4450 printer does not
generate internal printer commands. XDPE/400 passes the external
printer commands without modification and uses the standard page
rotation and multiple up spool file attributes to generate page
formatting commands.
Set interface mode
(INTFINIT)
File processing mode
(PROCMODE)
Specifies whether XDPE/400 sets the Flex twinax interface box into
XPPM or XDPM mode at the start of a Monitor Queue session. You can
use these values:
•
*YES — Sets the appropriate printer mode in Flex interface box at
the start of the session according to the Printer mode (MODE)
parameter
•
*NO — No printer mode set up commands are sent to the FLEX
interface box
Specifies the spool file processing mode that the Monitor Queue session
runs in. You can use these values:
*PAGE — Creates a single integrated spool file for each spool file to be
processed. You must specify *PAGE if you will be running in VIPP mode.
•
*JOB — Creates a separate spool file that is sent ahead of the user
file. This mode is provided for compatibility with the previous version
of XDPE/400.
In this processing mode, a Monitor Queue session must be started
with the WAITTIME parameter value equal to 1 or more seconds.
•
*AUTO — Automatically selects the *PAGE or *JOB mode,
depending on the spool processing guidelines. For example, if page
level processing is required, *PAGE is automatically selected as the
processing mode.
In this processing mode, a Monitor Queue session must be started
with the WAITTIME parameter value equal to 1 or more seconds.
Printing Documents with XDPE/400 (9/2001)
18-10
Using Monitor Queue
When selecting the file processing mode, note these considerations:
•
You cannot save a USER ASCII file after printing it with XDPE/400 if
Monitor Queue is started in *PAGE mode, even if the OS/400 SAVE
spool file attribute is *YES. Start Monitor Queue in *JOB mode
instead, and set the SAVE spool file attribute to *YES.
•
*JOB mode or *AUTO mode requires that the wait time between
spool files must be a non-zero number. The time limit can be from 1
to 60 seconds.
•
Monitor Queue checks the progress of printing in *PAGE mode only
if the wait time is not zero. Monitor Queue always checks the printing
process while in *JOB mode or *AUTO mode.
•
You cannot change the processing mode once a Monitor Queue
session has started.
•
A WAITTIME of zero is recommended. This will enable the Monitor
Queue and printer writer to execute concurrently, thereby increasing
printer throughput.
Refer to chapter 19, “Managing print operations,” for more information.
Pass option (PASS)
Specifies the search mode that Monitor Queue uses to search the output
queue. You can use these values:
•
*SINGLE — Specifies that Monitor Queue makes one pass through
the output queue that is processing the designated spool files.
Monitor Queue makes a list of the available spool files on the output
queue at the start of a Monitor Queue session and processes them
one at a time.
When the list of available spool files is processed, the Monitor Queue
session automatically ends. If a spool file is added to the output
queue after the session starts, it is not processed.
•
*CONT — Specifies that Monitor Queue continues to monitor the
output queue until Monitor Queue is stopped. Monitor Queue is
stopped when you enter the ENDMONQ command.
When a Monitor Queue session starts, Monitor Queue makes a list of
available spool files on that output queue and processes them one by
one. When the spool files are processed, Monitor Queue makes
another list of available spool files on the output queue. If a spool file
is added to the output queue after the previous list is created by
Monitor Queue, it is processed in the next pass.
Printing Documents with XDPE/400 (9/2001)
18-11
Using Monitor Queue
Pass through option
(PASSTHRU)
Specifies whether Monitor Queue prints a spool file if the spool file
attribute referenced by the PACKETDATA Monitor Queue parameter is
either blank or specifies a packet that is not found.
For information on VIPP processing, refer to the VIPP special packet data
(SPECPACK) parameter on the Work with Global Values (UPDTGLOBAL)
screen in chapter 6.
•
*PRINT — Specifies that the job will be printed. If the field is blank,
the job will be printed without a packet. For more information on
default packet processing, see “Setting the Packet data
(PACKETDATA) parameter” in chapter 10. If Monitor Queue cannot
find the packet specified in the Packet data field, it will look for a
packet named DEFAULT in the appropriate subfolder. If DEFAULT is
not found, refer to the Default packet option (DFTPKT) Monitor
Queue parameter for the next action.
•
*NOPRINT — Specifies that the job will not be printed and will be left
in the original output queue with a status of hold (HLD).
The default packet will be used if the PACKETDATA Monitor Queue
parameter is *FORMTYPE and the Form type spool file attribute is *STD.
This will occur regardless of the value specified for PASSTHRU.
Packet data (PACKETDATA)
Specifies the spool file attribute from which to retrieve
DJDE/XES/PCL/VIPP packet name information or XDPE/400 options. If
the spool file attribute specified by this parameter is left blank, no packet
will be used to process the job. For more information about how these
types of jobs are processed, see “Setting the Packet data (PACKETDATA)
parameter” in Chapter 10.
For information on VIPP processing, refer to the VIPP special packet data
(SPECPACK) parameter on the Work with Global Values (UPDTGLOBAL)
screen in chapter 6.
DJDE, XES, and PCL packet names for *USRDTA and *FORMTYPE can
be from 1 to 8 characters. All characters following the eighth character will
be ignored. VIPP packet names can be from 1 to 10 characters.
•
*USRDTA — Uses the User data field of the spool file attributes as a
source.
•
*FORMTYPE — Uses the Form type field of the spool file attributes
as a source.
•
*PAGEINFO — Specifies that the PAGESIZE, LPI, CPI, and page
rotation attributes of the spool file attributes are used as a source.
For DJDE, XES, and PCL, this option is valid only in Direct or
Combined modes with a DFTPKT value of *YES.
Monitor Queue constructs a DJDE, XES, PCL, or VIPP packet name
by examining the page information attributes of a spool file. The
following table shows the attributes that are used to construct an
8-character packet name.
Printing Documents with XDPE/400 (9/2001)
18-12
Using Monitor Queue
Attribute
Number of
characters
Value
Character
value
Page rotation
1
*AUTO
0
90
180
270
X
P
J
I
L
Page width
3
n/a
3 characters
CPI
2
n/a
2 characters
LPI
2
n/a
2 characters
For example, if page rotation is *COR, page width is 132, CPI is 10,
and LPI is 6, then the packet name is constructed as follows:
*AUTOX
Page width=132132
CPI=1010
LPI=606
Packet name=X1321006
Always generate (ALWAYS)
The Always generate (ALWAYS) parameter, along with the contents of
the Packet data (PACKETDATA) field, determines the method of
command generation used for a print job.
You can use these values:
•
*NONE — Sends the spool file directly to be printed without printer
commands.
•
*INDIRECT — Creates printer commands from spool file attributes.
•
*DIRECT — Creates printer commands from a printer control packet
specified for the spool file, ignoring the spool file attributes.
•
*COMBINED — Creates printer commands from spool file attributes
and a printer control packet and combines them both in a new spool
file.
Refer to the appropriate command generation chapter for more
information on each command generation method.
Refer to table 10-1 in chapter 10, “Creating and modifying printer files,”
for the relationship between the contents of the Packet data field and the
Always generate parameter of the Start Monitor Queue (STRMONQ)
command.
Printing Documents with XDPE/400 (9/2001)
18-13
Using Monitor Queue
Order of sequence
(SEQUENCE)
Specifies which source printer control commands will be inserted first into
the print data stream, spool file attributes, or XDPEFLR packets.
NOTE: This parameter has no effect in VIPP mode or on extended job
ticket commands.
When a duplicate command occurs, the last occurrence may override the
previous occurrence. See the documentation for your printer for the
manner in which these commands are implemented.
You can use these values:
File separators (FILESEP)
•
*PACKET — Specifies that printer control commands from XDPEFLR
packets are inserted into the print data stream first
•
*ATTRIB — Specifies that printer control commands created from
the spool file attributes are inserted into the print data stream first
Specifies the number of separator (banner and trailer) pages that will be
printed before and/or after each job. The type of separator pages used,
either AS/400-generated or XDPE/400-generated, is determined by the
Process separator page (BANNER) Monitor Queue parameter. If the
number of file separators is 0, no separator pages will be produced by
either XDPE/400 or the OS/400 writer.
You can use these values:
Process separator page
(BANNER)
•
*FILE — Uses the File separators (FILESEP) spool file attribute in
the spool file being processed for the number of separator pages to
generate
•
0-9 — Specifies the number of separator pages to print for all spool
files processed during this Monitor Queue session
Specifies the type of separator pages to be printed with your jobs, either
AS/400-generated or XDPE/400-generated.
XDPE/400 provides both banner and trailer page separators. Banner
pages are separators that are generated at the beginning of a spool file.
Trailer pages are separators that are generated at the end of a spool file.
Unless specifically stated, all references to separator pages apply to both
banner and trailer pages.
NOTE: The OS/400 printer writer generates banner pages only.
The number of separator pages produced depends on either the File
separators (FILESEP) spool file attribute or the File separators (FILESEP)
Monitor Queue parameter. You can use these values:
•
*YES — Directs the Monitor Queue to produce only banner pages
and suppresses the printing of a banner page by the OS/400 printer
writer.
If this value is selected and the Printer mode (MODE) parameter is
XPPM, XDPE/400 inserts a SIDE=NUFRONT DJDE command into
the print data stream after the last banner page.
•
*NO — Monitor Queue does not create any separator pages. Banner
pages are produced by the OS/400 printer writer.
Printing Documents with XDPE/400 (9/2001)
18-14
Using Monitor Queue
•
*BOTH — Directs the Monitor Queue to produce both banner and
trailer pages and suppresses the printing of a banner page by the
OS/400 printer writer.
•
*TRLR — Directs the Monitor Queue to produce only trailer pages
and suppresses the printing of a banner page by the OS/400 printer
writer.
For duplex jobs, if *BOTH or *TRLR is selected and the Printer mode
(MODE) parameter is XPPM, XDPE/400 will insert a
SIDE=NUFRONT DJDE command into the print data stream before
the first trailer page.
Refer to Section Two: Installing and Customizing XDPE/400 for a
description of the separator pages that Monitor Queue generates, and a
discussion of your options for changing separator pages.
Separator page source
(BANNERSRC)
Specifies the source tray for the selection of separator pages, both
banners and trailers. Tray selection may vary depending on your printer
setup. If a printer does not support a tray, the default tray will
automatically be used.
NOTE: This parameter has no effect on NPS, DocuSP, and generic
printers. The effect of this parameter varies depending on the PCL
printer used. Refer to “Xerox PCL printer tray selection” in Chapter 15
for more information on tray selection methods for the different PCL
printers. Refer to chapter 17 for information about how to specify
source drawers in VIPP mode. Also, in VIPP mode, the separator
page source tray selection is specified in XDPSPR.JDT. Refer to
Chapter 6 in Section Two: Installing and Customizing XDPE/400 for
detailed information about customizing XDPSPR.JDT.
If BANNER is *YES, *BOTH, or *TRLR and BANNERSRC is not *NONE,
XDPE/400 generates a printer control sequence to select the source of
paper used to print separator pages. If *NONE is specified, no printer
commands to select the separator pages source are created, and the
printer uses the current default value.
Data page source
(DATASRC)
Specifies the source tray for the selection of data pages. If a printer does
not support a tray, the default tray will automatically be used.
NOTE: This parameter has no effect on NPS, DocuSP, and generic
printers. The effect of this parameter varies depending on the PCL
printer used. Refer to “Xerox PCL printer tray selection” in chapter 15
for more information on tray selection methods for the different PCL
printers. Refer to chapter 17 for information about how to specify
source drawers in VIPP mode.
If BANNER is *YES, *BOTH, or *TRLR and DATASRC is not *NONE,
XDPE/400 generates a printer control sequence to select the source of
paper used to print the data pages. If *NONE is specified, XDPE/400 does
not create printer commands to select data source.
When running with the Indirect or Combined method, the value for the
Source drawer (DRAWER) printer file parameter takes precedence over
the value selected for this parameter.
Printing Documents with XDPE/400 (9/2001)
18-15
Using Monitor Queue
Default packet option
(DFTPKT)
When a packet specified in a printer file is not found, XDPE/400 searches
for a default packet. This parameter indicates the action to take if the
default printer command packet is not found.
NOTE: This parameter has no effect in VIPP mode.
You can use these values:
Leading RSTACK option
(LEDRSTK)
Trailing RSTACK option
(TRLRSTK)
•
*YES — Monitor Queue prints the spool file without generating
printer commands from the packet
•
*NO — Monitor Queue displays a message that the packet was not
found and does not print the spool file
Specifies whether to add an RSTACK string at the beginning of every
XPPM print job. If a report separation is not specified in the startup JSL,
the control from the previous job is carried forward to the next print job.
You can use these values:
•
*YES — Inserts an RSTACK string at the beginning of each report
•
*NO — Does not insert an RSTACK string at the beginning of each
report
Specifies whether to add an RSTACK string at the end of an XPPM print
job. The printer can print all of the pages and copies of the last job without
requiring an ENDJOB printer command. You can use these values:
•
*YES — Inserts a trailing RSTACK string after the end of each report
•
*NO — Does not insert a trailing RSTACK string
NOTE: The 4235 printer in XPPM mode does not require a trailing
RSTACK.
Queue for packet messages
(MSGQ)
Specifies the name of the message queue to which the Monitor Queue
sends a message if the following occurs:
•
A printer command packet is not found
•
Spool file processing for a given form type is complete
XDPE/400 also sends a message to the XDPEMSGQ message queue.
You can use these values:
•
message-queue-name — Sends messages to the user-specified
message queue
•
*USER — Sends messages to the message queue of the user who
started the Monitor Queue session
•
*SYSOPR — Sends messages to the system operator message
queue
•
*NONE — No messages will be sent to a user-specified message
queue or to the XDPE/400 message queue
Printing Documents with XDPE/400 (9/2001)
18-16
Using Monitor Queue
Library
Form type options
(FORMTYPE)
Indicates the library to use for sending packet error messages. You can
use these libraries:
•
*LIBL — Uses the library list to locate the message queue.
•
*CURLIB — Uses the current library for the job to locate the
message queue. QGPL is used if a current library is not specified for
the job.
•
name — Specifies the name of the library in which the message
queue resides.
Allows you to process spool files for all form types or only for specified
form types. If a spool file is in ready state but does not have the specified
form type, it is not processed.
You can use the CHGMONQ command to change the Form type option to
process without having to stop and restart the session.
There are two subparameters for the Form type options (FORMTYPE)
parameter, Form type and Message option.
Form type — Indicates the spool files to process. For example, to
process files that contain the form named BLUE.FRM, enter BLUE.FRM
as the form type. You can use these values:
•
*ALL — Processes all ready spool files in the output queue,
regardless of their form type. With this option, Monitor Queue does
not send a completion message after processing all available spool
files.
•
*STD — Processes ready spool files that contain the form type
*STD.
•
form-type — Processes ready spool files that contain the form type
you specify.
Message option — Indicates whether to send a message when
processing for the specified form type is complete. You can use these
values:
•
*MSG — Sends a message when Monitor Queue finishes processing
spool files with a specified form type
•
*NOMSG — Does not send a message when processing is complete
NOTE: If you do not end the Monitor Queue session and the Pass
option (PASS) parameter is *CONT, additional spool files are
processed as they become available for printing, and a message is
resent after the list is processed.
Wait time between files
(WAITTIME)
Determines whether the Monitor Queue waits between the processing of
spool files and if so, how many seconds it should wait before it checks to
see if the last file has completed processing by the printer writer. You can
use these values:
•
•
0-60 — If File processing mode (PROCMODE) is *PAGE
1-60 — If File processing mode (PROCMODE) is *JOB or *AUTO
For more information on WAITTIME values, refer to “WAITTIME
processing notes” later in this chapter.
NOTE: The WAITTIME value must be 0 for a network printer.
Printing Documents with XDPE/400 (9/2001)
18-17
Using Monitor Queue
Multi-part printing (XMPT)
Indicates whether multi-part printing support is required for a Monitor
Queue session. You can use these values:
•
*YES — Indicates that multi-part printing is required for this Monitor
Queue session
•
*NO — Indicates that multi-part printing is not required for this
session
To control multi-part printing, you must start the Monitor Queue session
in *PAGE processing mode with zero wait time. *PAGE mode ensures the
spool file is printed in the order the entries are listed in the multi-part
packet. A zero wait time ensures XDPE/400 processes each entry in the
multi-part packet immediately.
Save output queue
(SAVEOUTQ)
Specifies the name of the queue to which the Monitor Queue stores the
application spool files. You can use these values:
•
*OUTQ — Stores the printed spool files in the same output queue
that is being monitored. When this value is specified, *OUTQLIB
must be specified for Library.
•
name — Stores the printed spool files in the user-specified output
queue.
This parameter only works if *YES is specified for the SAVE spool file
attribute. All spool files that are created by Monitor Queue are
automatically deleted after printing.
NOTE: To print, then save a USER ASCII file, you must start Monitor
Queue in *JOB mode.
Library
Device class (DEVCLS)
Indicates the library to use for storing all printed spool files. You can use
these values:
•
*OUTQLIB — Specifies the library where the output queue being
monitored is located
•
*LIBL — Uses the library list to locate the spool file output queue
•
*CURLIB — Uses the current spool file library to locate the spool file
output queue
•
name — Specifies the name of the library in which the queue resides
Specifies the class of printing device, whether it is printing locally or
printing over a network. You can use these values:
•
*LCL — Specifies printing to a locally-attached twinax printer.
•
*RMT — Specifies printing to a remote output queue.
•
*NET — Specifies transformation of the data stream via Host Print
Transform and printing to a network-attached printer via TCP/IP.
After the data is transformed into ASCII data and the SCS
commands are transformed into PCL or VIPP commands, the
Monitor Queue sends print output to the remote/network output
queue for processing by the remote writer.
Printing Documents with XDPE/400 (9/2001)
18-18
Using Monitor Queue
Remote/Network output
queue (RMTOUTQ)
Specifies the name of a remote output queue where you want XDPE/400
to send the processed spool files for printing. If a remote output queue is
not specified, XDPE/400 places the processed spool files in the internal
output queue in the XDPE/400 application library.
NOTE: If a remote output queue is specified, XDPE/400 does not
automatically start a writer to that output queue. You must start a
remote writer. Refer to chapter 20, “Remote/Network printing,” for
more information.
Library
Workstation customizing
object (WSCST)
Specifies the name of the library in which the output queue was created.
You can use these values:
•
name — Specifies the name of the library in which the output queue
resides.
•
*LIBL — Uses the library list to locate the output queue.
•
*CURLIB — Uses the current library for the job to locate the output
queue. If a current library is not specified for the job, QGPL is used.
For network printing, this parameter specifies the workstation customizing
object that contains the Host Print Transform table to be used for this
Monitor Queue session. You can use these values:
•
name — Specifies the name of a user-created workstation
customizing object. It is recommended that the XDPE/400 default
WSCST (*XDPEDFT) or euro-capable PCL default WSCST
(*EURODFT) be used.
CAUTION: The use of a user-created workstation customizing
object during a Monitor Queue session may produce
unpredictable results.
•
*XDPEDFT — Uses one of the XDPE/400 default workstation
customizing objects in the XDPE/400 application library. The default
WSCST options are:
WSCST
XWSCSTN32
Printers
•
45XX, 42XX, DC265LP, DC255LP,
N32, and N24 printers in PCL mode
•
NPS and DocuSP printers when the
XTICKET Suppress PCL option is
set to *NO
XWSCSTSUP
NPS and DocuSP printers when the
XTICKET Suppress PCL option is set to
*YES
XWSCST4220
All other network PCL printers
XWSCSTVIPP
Printers in VIPP mode
Printing Documents with XDPE/400 (9/2001)
18-19
Using Monitor Queue
•
*EURODFT — Uses one of the euro-capable PCL default
workstation customizing objects in the XDPE/400 application library.
The default WSCST options are:
WSCST
EWSCSTN32
Library
MRP internal interface mode
(MRP)
Printers
•
N32 and N24 printers
•
NPS printers when the XTICKET
Suppress PCL option is set to *NO
EWSCSTSUP
NPS printers when the XTICKET
Suppress PCL option is set to *YES
EWSCST4220
All other network PCL printers
Specifies the name of the library where the workstation customizing
object is located. If no value is entered, *LIBL is used. You can use these
values:
•
name — Specifies the name of the library in which the workstation
customizing object resides
•
*LIBL — Uses the library list to locate the workstation customizing
object
•
*CURLIB — Uses the current library for the job to locate the
workstation customizing object
Specifically for use with the 42XX i-data internal interface box used with
the 4230, 4220, 4219, and 4215 printers, MRP allows the user to set the
i-data Y36 command through XDPE/400. The Y36 command determines
how the interface box handles IBM control codes that are sent to it. You
must specify *NONE for this parameter if you are not using a 42XX
internal interface box.
If a value for MRP is entered in a PCL packet, that value overrides the
MRP value in the Monitor Queue for the duration of the job using that PCL
packet. When the job has finished processing, MRP is reset back to the
Monitor Queue value. If however, Monitor Queue has no MRP value set
and a value other than *NONE is entered in a PCL packet, the value from
the packet will stay active on the printer for all subsequent jobs until a job
comes along containing a PCL packet with a different MRP value.
Refer to the i-data Twinax XES/PCL Interface Controller for Xerox
Printers Programmer’s Guide for more information about this feature.
You can use these values:
•
*MRP0 — The interface box honors all IBM control codes that are
sent to it. This is the default setting for the 42XX internal interface
box.
•
*MRP5 — Suppresses all multibyte IBM control commands except
bolding. These page format commands will be honored:
—
—
—
—
—
Carriage Return (CR)
Line Feed (LF)
Form Feed (FF)
Print position (34-vvnn)
Absolute line position (will be translated into CR + spaces)
Printing Documents with XDPE/400 (9/2001)
18-20
Using Monitor Queue
•
*MRP6 — Suppresses page formatting in order to eliminate excess
blank pages and line feeds. This command should only be used for
jobs where excess blank pages and line feeds are generated.
•
*NONE — XDPE/400 does not insert a Y36 command into the data
stream. If *NONE is specified, the 42XX internal interface box uses
the MRP default of zero. All other interface boxes function normally.
WAITTIME processing notes
If WAITTIME is 0 (zero), the Monitor Queue processes a spool file, places
it in the internal output queue, and immediately begins processing the
next spool file. The Monitor Queue is able to process spool files
independently of the printer writer, and is not limited by the processing
speed of the printer or the writer.
When WAITTIME is any number other than 0 (zero), the Monitor Queue
places the current spool file on the internal output queue and issues a wait
for the number of seconds specified in the WAITTIME parameter. When
the wait has expired, the Monitor Queue looks in the output queue. If the
spool file is still there, another wait is issued and, after that expires, the
Monitor Queue checks again. This continues until the spool file has been
removed from the output queue by the printer writer. When the spool file
is no longer in the output queue, the Monitor Queue begins processing the
next spool file. This means, especially for a lengthy print job, none of the
following processes can take place until the current print job has finished
printing by the printer:
•
•
•
Any processing for the next XDPE/400 spool file
Any changes you have made to XDPE/400 global values
A command to end Monitor Queue
It is recommended that a non-zero WAITTIME be used only under these
conditions:
•
•
If File processing modes (PROCMODE) is *JOB or *AUTO
If you are instructed to do so by Xerox Technical Support
If you need to use a non-zero WAITTIME, you should calculate the
optimum WAITTIME for your specific application. The value of the
WAITTIME parameter can greatly affect performance. A WAITTIME value
that is too small causes excessive checking of large spool files and is an
unnecessary waste of processing. An excessively large WAITTIME value
can greatly decrease throughput as the Monitor Queue can be waiting for
a job that has already been printed.
If the size of the spool files being processed varies not more than one
standard deviation, the optimum WAITTIME value is half of the average
time needed to print a spool file. If the size of the spool files is highly
variable, this method is not effective. A smaller number should be used
because a WAITTIME that is larger than optimum slows processing more
than one that is smaller.
Using the CHGMONQ command, you can use WAITTIME to apply a break
to a Monitor Queue session in *PAGE processing mode with a zero wait
time. If you use the CHGMONQ command to change the wait time to any
number other than zero, Monitor Queue immediately starts to check the
integrated spool file that was last created. It does not process another
spool file until the last integrated spool file is printed. From then on it only
processes one spool file at a time and waits between files to check the
printing progress.
Printing Documents with XDPE/400 (9/2001)
18-21
Using Monitor Queue
Examples of starting a Monitor Queue session
This section contains examples of starting Monitor Queue sessions that
meet specific operational needs.
Example 1
In this example, you have replaced your old production 5225 printer with
a new Xerox 4850 printer and installed XDPE/400. You want to direct one
of the output queues previously directed to the 5225 printer to the Xerox
printer. This output queue was used to print accounting reports on
standard green bar paper. The printer file used to create these spool files
was changed to specify an electronic green bar form stored on the Xerox
printer. You do not know which field, if any, was used as the packet data
field.
Start a Monitor Queue session for this output queue and printer. Use the
default values for startup parameters, with the exception of this change:
Always generate*INDIRECT
Monitor Queue automatically generates DJDEs from the spool file
attributes, regardless of what is in the USRDTA or FORMTYPE attributes.
The green bar form merges with the data at the printer.
Example 2
In this example, the spool files going to the output queue for your Xerox
printer all specify a printer control generation method in the USRDTA
field. You want to override formatting decisions as much as possible at the
last minute (that is, after the spool file is on the output queue), regardless
of what has been specified in the packet data field.
Start a Monitor Queue session for this output queue. Use the default
values for startup parameters, with the exception of this change:
Always generate*COMBINED
Spool file attributes always translate into printer control commands and
take precedence over any packet specified in the USRDTA attribute.
Example 3
In this example, the spool files going to a particular output queue have a
text entry in the FORMTYPE attribute, but there is no # preceding it.
Previously, the FORMTYPE attribute indicated a special form needed to
be loaded onto the printer for the job. A set of Xerox printer control
packets were developed whose names correspond to the possible
FORMTYPE values. (Each packet calls an electronic form stored on the
printer that corresponds to the preprinted form formerly used to print the
job.)
Start a Monitor Queue session for this output queue. Use the default
values for startup parameters, with the exception of these changes:
Packet data*FORMTYPE
Always generate*DIRECT
The jobs print using the electronic versions of the forms.
Printing Documents with XDPE/400 (9/2001)
18-22
Using Monitor Queue
Example 4
In the previous example, you cannot use the COPIES attribute to increase
the number of copies of a particular job once the spooled file gets to the
output queue. You would like to do this, but you do not want anyone to
make an entry in the FRONTOVL attribute and override the electronic
form name specified in the packet.
End the previous Monitor Queue session. Restart it using the default
startup values, with the exception of these changes:
Packet data*FORMTYPE
Always generate*COMBINED
Order of sequence*ATTRIB
You can increase the number of copies using spool file attributes, but the
electronic form name in the packet takes precedence if there is a name in
the FRONTOVL attribute.
Example 5
In all of the previous examples, the Monitor Queue has operated with a
time delay between print jobs, which it used to check the printing process.
The Monitor Queue can operate without the time delay as long as you
start the session using a *PAGE file processing mode and a zero wait
time.
End the previous Monitor Queue session. Restart it using the default
startup values, with the exception of these changes:
File processing mode*PAGE
Wait time between files0
With a zero wait time between files, the Monitor Queue does not check the
printing process. Instead, it continues to process the available user spool
files. This allows the Monitor Queue to process files while continuing to
print the previous job. The printer does not have to wait while the Monitor
Queue processes the file.
Printing Documents with XDPE/400 (9/2001)
18-23
Using Monitor Queue
Displaying a Monitor Queue session
Use the Display XDPE Monitor Queue (DSPMONQ) command to display
the Monitor Queue properties that were entered to start the Monitor
Queue session.
To display the Monitor Queue properties, enter DSPMONQ and press
ENTER. The Display XDPE Monitor Queue screens display.
Display XDPE Monitor Queue (DSPMONQ)
Queue: PCLOUTQ
Library: APPLIB
Printer writer . . .
Interface box . . . .
Printer model . . . .
Printer emulation . .
Software version. . .
Printer mode . . . .
Xerox interface mode
Set interface mode .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
:*NONE
:*PCSUPP
:DC265LP
:5219
:*V1R1
:*PCL
:*NORMAL
:*YES
File processing mode
Pass option . . . . .
Pass through option .
Packet data . . . . .
Always generate . . .
Order of sequence . .
File separators . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
:*PAGE
:*CONT
:*PRINT
:*USRDTA
:*DIRECT
:*PACKET
:1
More ...
F3=Exit
F12=Cancel
Printing Documents with XDPE/400 (9/2001)
18-24
Using Monitor Queue
Display XDPE Monitor Queue (DSPMONQ)
Queue: PCLOUTQ
Library: APPLIB
Process separator page .
Separator page source . .
Data page source . . . .
Default packet option . .
Leading RSTACK option . .
Trailing RSTACK option .
Queue for packet messages
Library . . . . . . . .
Form type options:
Form type . . . . . . .
Message option . . . .
Wait time between files .
Multi-part printing . . .
Save output queue . . . .
Library . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
:*YES
:*NONE
:*NONE
:*NO
:*YES
:*NO
:CQ99999
:QUSRSYS
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
:*ALL
:*NOMSG
:0
:*NO
:PCLOUTQ
:INTSTLIB
More ...
F3=Exit
F12=Cancel
Display XDPE Monitor Queue (DSPMONQ)
Queue: PCLOUTQ
Library: APPLIB
Device class . . . . . . . . . .:*NET
Remote/Network output queue . . :L265Q
Library . . . . . . . . . . . :INTSTLIB
Workstation customizing object. :*XDPEDFT
Library . . . . . . . . . . . :*LIBL
MRP internal interface mode . . :*NONE
Bottom
F3=Exit
F12=Cancel
Printing Documents with XDPE/400 (9/2001)
18-25
Using Monitor Queue
Changing a Monitor Queue session
You can use the Change Monitor Queue (CHGMONQ) command to
change specified processing options without having to stop and restart
the Monitor Queue session.
When you start a Monitor Queue session where the Form type options
(FORMTYPE) Monitor Queue parameter is set to a value other than *ALL
or *STD, XDPE/400 processes all spool files with that form type. For
example, you can start a Monitor Queue session and specify BLUE.FRM
as the form type. During the Monitor Queue session, you can change the
form type to process RED.FRM files instead.
In this example, XDPE/400 completes the spool file search for the first
form type, BLUE.FRM, then begins searching the files for the new form
type, RED.FRM. Monitor Queue continues to process spool files for
RED.FRM until you change the form type again, or end the Monitor Queue
session.
Follow these steps to change a Monitor Queue session:
Step 1.
Enter CHGMONQ and press ENTER. The Change Monitor Queue menu
displays.
Change Monitor Queue (CHGMONQ)
Type choices, press Enter.
Output queue . . . . . . .
Name
Bottom
F3=Exit F4=Prompt
F5=Refresh
F13=How to use this display
Step 2.
F10=Additional parameters
F24=More keys
F12=Cancel
Enter the name of the Output queue being monitored during the Monitor
Queue session and press F10.
The Change Monitor Queue menu displays additional parameters.
Change the parameters you want and press ENTER.
Printing Documents with XDPE/400 (9/2001)
18-26
Using Monitor Queue
Refer to “Starting a Monitor Queue session” in this chapter for information
about the output queue and other available options.
Change Monitor Queue (CHGMONQ)
Type choices, press Enter.
Output queue
. . . . . .
Name
Additional Parameters
Pass option . . . . . .
Pass through option . .
Packet data . . . . . .
Always generate . . . .
Order of sequence . . .
File separators . . . .
Process separator page.
Separator page source .
Data page source . . .
Default packet option .
Leading RSTACK option .
Trailing RSTACK option.
.
.
.
.
.
.
.
.
.
.
.
.
*SAME
*SAME
*SAME
*SAME
*SAME
*SAME
*SAME
*SAME
*SAME
*SAME
*SAME
*SAME
*CONT, *SINGLE, *SAME
*PRINT, *NOPRINT, *SAME
*USRDTA, *FORMTYPE...
*NONE, *INDIRECT, *DIRECT...
*PACKET, *ATTRIB, *SAME
*0-9, *FILE
*YES, *NO, *BOTH, *TRLR...
*NONE, *MAIN, *AUX, *AUTO...
*NONE, *MAIN, *AUX, *AUTO...
*YES, *NO, *SAME
*YES, *NO, *SAME
*YES, *NO, *SAME
More...
F3=Exit
F4=Prompt
F24=More keys
F5=Refresh
Printing Documents with XDPE/400 (9/2001)
F12=Cancel
F13=How to use this display
18-27
Using Monitor Queue
Ending a Monitor Queue session
Use the End Monitor Queue (ENDMONQ) command to terminate one or
all Monitor Queue sessions.
When Monitor Queue is ended with a command, and you want to use the
output queue and the printer writer previously assigned to XDPE/400, you
must start the printer writer manually.
Follow these steps to end a Monitor Queue session:
Step 1.
Enter ENDMONQ and press ENTER. The End Monitor Queue menu
displays.
Step 2.
Enter the appropriate value for each parameter, following the conventions
described in the next section, and press ENTER.
End Monitor Queue (ENDMONQ)
Type choices, press Enter.
Output queue. . . . . . . .
Order of Sequence . . . . . *SPOOL
Name, *ALL
*LIST, *SPOOL, *COPY, *IMMED
Bottom
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
Printing Documents with XDPE/400 (9/2001)
F12=Cancel
F13=How to use this display
18-28
Using Monitor Queue
Parameters
Output queue (OUTQ)
Specifies the name of the output queue to stop monitoring. You can use
these values:
•
•
End schedule (SCHED)
name — Specifies the output queue that was started
*ALL — Specifies all instances of Monitor Queue
Specifies how a Monitor Queue session is ended.
NOTE: If WAITTIME is 0 (zero), *IMMED is the only valid value.
You can use these values.
•
*COPY — Specifies that Monitor Queue stops making multiple
copies by ending retransmission at the end of the current copy.
•
*IMMED — Specifies that the XDPE/400 will stop monitoring the
output queue immediately. The spool file that is processing at the
time stops immediately, and the user file is returned to the
application output queue.
If you specify *IMMED to end a Monitor Queue session, the current
print job stops immediately. The application spool file is reassigned
to the original output queue that is being monitored.
If a Monitor Queue session is stopped immediately, the integrated
spool file is left on the output queue in the Ready status and is not
deleted. You do not need to process that same file after you initiate
an immediate end to a Monitor Queue session. The application spool
file is not lost when a session is immediately ended, and your spool
file is reassigned to the original output queue with a status of Hold.
•
*SPOOL — Specifies that Monitor Queue finishes processing the
current spool file before ending. Once the current spool file is
printed, Monitor Queue does not process any more spool files, even
if they are eligible for printing.
•
*LIST — Specifies that Monitor Queue finishes processing the output
queue list. Once all the spool files from the current list are printed,
the Monitor Queue session ends.
Non-zero WAITTIME
If you have a non-zero WAITTIME and use the ENDMONQ command with
the *IMMED option to end a Monitor Queue session, XDPE/400
recognizes the request, but will not end until the current spool file has
been processed by the printer writer. For all other modes of SCHED, if
WAITTIME is not zero, the Monitor Queue session will not end until all
processed spool files have been written to the printer.
Printing Documents with XDPE/400 (9/2001)
18-29
Using Monitor Queue
Clearing multiple Monitor Queue sessions
If the Monitor Queue will not end, perform these steps:
Step 1.
Enter the IBM Work With Active Job (WRKACTJOB) command.
Step 2.
Page forward to the QSPL subsystem section.
Step 3.
For Monitor Queue, select option 4 (END) and Press F4 (prompt) for
OPTION, select (*IMMED), then press ENTER.
Step 4.
If the OS/400 writer remains active, repeat step 3 for the OS/400 writer
listed in the QSPL subsystem section.
Step 5.
Clean up the XDPE/400 multiple session database by entering this
command:
RMVM
FILE(library/XDPEMQSESS)
MBR(output-queue)
where
library
The name of the XDPE/400 application library is
XDPEvrm, where
•
•
•
output-queue
v is the version number
r is the release number
m is the modification number
Output queue being monitored.
Printing Documents with XDPE/400 (9/2001)
18-30
Using Monitor Queue
Resetting a Monitor Queue session
Use the Reset Monitor Queue (RSTMONQ) command to reset a Monitor
Queue session that ended abnormally. Each time you use this command,
one or all of the active Monitor Queue sessions is reset.
NOTE: Before you use this command, try to end the Monitor Queue
sessions with the ENDMONQ command or the procedure for clearing
multiple Monitor Queue sessions. Resetting an output queue that was
not ended explicitly with the ENDMONQ command can produce
unexpected errors.
Follow these steps to reset a Monitor Queue session:
Step 1.
Enter RSTMONQ and press ENTER. The Reset Monitor Queue menu
displays.
Step 2.
Enter the appropriate option for the Output queue parameter and press
ENTER. Refer to “Ending a Monitor Queue session” in this chapter for
information about the Output queue parameter.
Reset Monitor Queue (RSTMONQ)
Type choices, press Enter.
Name, *ALL
Output queue . . . . . . . .
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
Printing Documents with XDPE/400 (9/2001)
F12=Cancel
F13=How to use this display
18-31
Using Monitor Queue
Monitor Queue messages
Before you start a Monitor Queue session that was previously ended,
check the Monitor Queue XDPEMSGQ message file to make sure that the
ENDMONQ command completed successfully.
To check the XDPEMSGQ file, enter this command and press ENTER:
DSPMSG XDPEMSGQ
Refer to Chapter 26, “Troubleshooting” for information on “Monitor Queue
solutions”.
Printing Documents with XDPE/400 (9/2001)
18-32
19.
19
Managing print operations
This chapter describes the methods Monitor Queue uses to process print
jobs, and the facilities you can use to learn the status of those jobs.
Monitor Queue processing modes
The Monitor Queue operates in one of these three basic processing
modes, as specified by the File processing mode (PROCMODE) Monitor
Queue parameter:
•
•
•
*JOB mode
*JOB
*PAGE
*AUTO
When Monitor Queue operates in *JOB processing mode, it creates a
spool file that contains job level printer commands and banner page data.
This spool file is sent to the printer ahead of the user spool file. Optionally,
a third spool file can be created and sent to the printer to mark the end of
a print job.
For example, Monitor Queue can perform the following sequence:
a.
*PAGE mode
Create a spool file (XPREPEND) that contains some or all of the items
in this order:
—
Leading printer and interface commands, such as RSTACK
string in XPPM
—
Printer resources, such as fonts and forms
—
Banner page data
—
DJDE, XES, and PCL printer commands
b.
Process your spool file after the XPREPEND file
c.
Optionally create a spool file that contains trailing printer commands,
such as RSTACK string in XPPM mode, or RESET commands in
XDPM or PCL mode
When Monitor Queue operates in *PAGE processing mode, a single
integrated spool file that contains printer commands and user spool file
data is created. This integrated spool file can contain some or all of the
items in this order:
•
Leading printer and interface commands, such as RSTACK string in
XPPM mode or the PostScript begin file (%!) command in VIPP
mode
•
Printer resources, such as fonts and forms
•
Banner page data
•
DJDE, XES, PCL, VIPP, and PostScript printer commands
•
Monitor Queue-generated SCS commands
•
User file data (modified or unmodified)
Printing Documents with XDPE/400 (9/2001)
19-1
Managing print operations
•
Trailer page data
•
Trailing printer or interface commands such as the RSTACK string in
XPPM mode, RESET commands in XDPM or PCL mode, or the
PostScript end-of-file (%%EOF) command in VIPP mode
In this mode, the Monitor Queue can insert printer commands in these
three optional areas:
•
•
•
*AUTO mode
Before the user spool data (for the job setup information)
On a page boundary (to facilitate page level commands)
After the user spool data (to reestablish the printer settings for the
next spool job)
When Monitor Queue operates in *AUTO processing mode, the Monitor
Queue automatically determines whether to operate in *JOB mode or
*PAGE mode.
*JOB mode processing
Figure 19-1 shows how Monitor Queue (operating in *JOB mode)
intervenes in the standard OS/400 process to insert Xerox printer control
commands into the data stream going to the printer.
Figure 19-1. How Monitor Queue works with spool files in *JOB mode
Printing Documents with XDPE/400 (9/2001)
19-2
Managing print operations
•
Monitor Queue searches its assigned output queue (PRT4213) for
spool files with a RDY (ready) status.
•
Monitor Queue finds a ready spool file called INVRPT2 and moves it
to an output queue in the XDPE/400 application library that is also
called PRT4213. This internal XDPE/400 output queue is on HOLD.
The spool file is given an output priority of 5.
•
In its internal output queue, Monitor Queue builds a file called
XPREPEND with an output priority of 2. The file is on HOLD.
•
Monitor Queue generates or retrieves the appropriate Xerox printer
control commands and places them in the XPREPEND file.
•
If this output is going to a Xerox printer operating in XDPM mode, or
if a trailing RSTACK is requested while in XPPM mode, Monitor
Queue may create a file called XPOSTPEND with an output priority
of 8. The file is on HOLD. The XPOSTPEND file contains an XES or
DJDE command to reset the Xerox printer.
•
Monitor Queue releases its internal output queue. The printer writer
processes the XPREPEND, user data (INVRPT2), and XPOSTPEND
files in order of their output priority.
The printer writer processes some of the same spool file attributes as
Monitor Queue, such as the COPIES attribute. This may result in
redundant and possibly conflicting processing. Therefore, after
Monitor Queue translates a spool file attribute into a Xerox printer
control command, that spool file attribute is set to the default value.
For example, if COPIES=5 on the spool file, Monitor Queue
generates the Xerox printer control command to create five copies on
the Xerox printer and then changes the spool file attribute to
COPIES=1. This prevents the printer writer from transmitting the job
to the printer 5 times, resulting in 25 copies.
•
If the Xerox printer does not have a disk unit, XDPE/400 instructs the
printer writer to perform multiple transmissions of the required spool
files correlating to the user copy count.
•
The system deletes the XPREPEND and XPOSTPEND files from the
internal output queue once the print job is complete.
•
If the SAVE attribute in INVRPT2 is *YES, then Monitor Queue
returns INVRPT2 to the original output queue with a status of SAV
(save), which was set by the printer writer. If SAVE=*NO, then the
printer writer also deletes INVRPT2.
Printing Documents with XDPE/400 (9/2001)
19-3
Managing print operations
Examples of *JOB mode spool file status
This section provides examples of how status and other information
changes as Monitor Queue processes a spool file.
Example 1 (*JOB mode)
Figure 19-2 shows how the Work with All Spool Files entry for a spool file
called INVRPT2 changes during processing.
Figure 19-2. Work with All Spool Files (INVRPT2/*JOB)
•
Line A shows the entry as soon as the spool file is ready on user
output queue PRT4213.
•
Line B shows the entry after Monitor Queue moves INVRPT2 to its
internal output queue. The system changes the output queue library
to the XDPE/400 application library and the USRDTA field to
XEROX.
•
Line C shows the entry after Monitor Queue releases its internal
output queue to the printer writer. The status column changes to
WTR.
•
Line D shows that INVRPT2 was returned to the original output
queue with a status of SAV. This means the File save attribute of
INVRPT2 must have been set to *SAVE. The User Data attribute
(and any other attribute values that were changed) is returned to the
original value.
The prepend and postpend files that Monitor Queue creates on its internal
output queue show up on the Work with All Spool Files screen of the user
who started the Monitor Queue session. In this example, user
YOURNAME did not start Monitor Queue so these files do not display.
Printing Documents with XDPE/400 (9/2001)
19-4
Managing print operations
Example 2 (*JOB mode)
Figure 19-3 shows how the Work with All Spool Files entry for a spool file
called CUSTSTMT changes as the Monitor Queue processes it.
Figure 19-3. Work with All Spool Files (CUSTSTMT/*JOB)
•
Line A shows the entry as soon as the spool file is ready on user
output queue PRT4850.
•
Line B shows the entry after Monitor Queue moves CUSTSTMT to its
internal output queue. The system changes the output queue library
to the XDPE/400 application library and the USRDTA field to
XEROX.
•
Line C shows that CUSTSTMT was returned to the original output
queue with a status of HLD. This means an error condition occurred
while Monitor Queue was creating the necessary prepend and
postpend files. The User Data attribute (and any other attribute
values that were changed) is returned to the original value. The
system cannot print this file until the error situation is corrected, and
the file is released to Monitor Queue again.
Printing Documents with XDPE/400 (9/2001)
19-5
Managing print operations
*PAGE mode processing
Figure 19-4 shows how Monitor Queue (operating in *PAGE mode)
intervenes in the standard OS/400 process to insert Xerox printer control
commands into the data stream going to the printer.
Figure 19-4.
How Monitor Queue works with spool files in *PAGE mode
Monitor Queue searches its assigned output queue (PRT4213) for spool
files with a RDY (ready) status.
•
Monitor Queue finds a ready spool file called INVRPT2 and moves it
to an output queue in the XDPE/400 application library that is also
called PRT4213. This internal XDPE/400 output queue status is HLD
(on hold).
•
Monitor Queue builds a new spool file from the original spool file.
Depending on the Wait time between files (WAITTIME) Monitor
Queue parameter, this spool file will either keep the original spool
file name of INVRPT2 or be called XPREPEND.
•
Monitor Queue generates or retrieves the appropriate Xerox printer
control (job level) commands and places them in the
XDPE/400-created spool file.
•
If this output is going to a Xerox printer operating in XDPM mode, or
if a trailing RSTACK is requested while in XPPM mode, Monitor
Queue may add postpend commands, such as the XES command to
reset the Xerox printer.
Printing Documents with XDPE/400 (9/2001)
19-6
Managing print operations
•
Monitor Queue adds page level commands, the original INVRPT2
print data, and the job level reset commands to the
XDPE/400-created spool file.
•
Monitor Queue releases the hold on its internal output queue. The
printer writer processes this integrated file.
The printer writer processes some of the same spool file attributes as
Monitor Queue, such as the COPIES attribute. This may result in
redundant and possibly conflicting processing. Therefore, after
Monitor Queue translates a spool file attribute into a Xerox printer
control command, that attribute is set to the default value. For
example, if COPIES=5 on the spool file, Monitor Queue generates the
Xerox printer control command to create five copies on the Xerox
printer and then changes the spool file attribute to COPIES=1. This
prevents the printer writer from transmitting the job to the printer 5
times, resulting in 25 copies.
•
If the Xerox printer does not have a disk unit, XDPE/400 instructs the
printer writer to perform multiple transmissions of the required spool
files correlating to the user copy count.
•
The system deletes the XDPE/400-created spool file from the
internal output queue once the print job is complete.
•
If the SAVE attribute in the original INVRPT2 is *YES, then Monitor
Queue returns it to the original output queue with a status of HLD (on
hold) or to the Save output queue (SAVEOUTQ) if specified in the
STRMONQ command with a status of HLD (on hold). If SAVE is *NO,
then the system also deletes the original INVRPT2.
Printing Documents with XDPE/400 (9/2001)
19-7
Managing print operations
Examples of *PAGE mode spool file status
This section provides examples of how status and other information
changes as Monitor Queue processes a spool file.
Example 1 (*PAGE mode with waittime=0)
Figure 19-5 shows how the Work with All Spool Files entry for a spool file
called INVRPT2 changes during processing.
Figure 19-5. Work with All Spool Files (WAITTIME=0)
•
Line A shows the entry as soon as the spool file is ready on user
output queue PRT4213.
•
Line B shows the entry after Monitor Queue moves INVRPT2 to its
internal output queue. The system changes the output queue library
to the XDPE/400 application library and the USRDTA field to
XEROX.
•
Line C shows that XDPE/400 creates a spool file using the name of
the original spool file, which in this case is called INVRPT2. When
XDPE/400 is finished creating INVRPT2, the file is sent to the printer
destination.
If the original spool file, in this case INVRPT2, is returned to the original
output queue with a status of HLD, this means that either the Save file
attribute of INVRPT2 was set to *YES or an error condition may have
occurred while Monitor Queue was processing the spool file.
If an error condition occurred, the system cannot print INVRPT2 until the
error situation is corrected, and the file is released to Monitor Queue
again. In this case, an error message will be sent to the XDPE/400
message queue informing the user about the error condition.
Spool files processed by XDPE/400 in *PAGE mode with a WAITTIME of
zero are owned by the user of the original (unprocessed) spool file.
Printing Documents with XDPE/400 (9/2001)
19-8
Managing print operations
Example 2 (*PAGE mode with non-zero waittime)
Figure 19-6 shows how the Work with All Spool Files entry for a spool file
called INVRPT2 changes during processing.
Figure 19-6. Work with All Spool Files (non-zero WAITTIME)
•
Line A shows the entry as soon as the spool file is ready on user
output queue PRT4213.
•
Line B shows the entry after Monitor Queue moves INVRPT2 to its
internal output queue. The system changes the output queue library
to the XDPE/400 application library and the USRDTA field to
XEROX.
•
Line C shows that XDPE/400 creates a spool file called XPREPEND
from the original spool file. When XDPE/400 is finished creating
XPREPEND, the file is sent to the printer destination.
If the original spool file, in this case INVRPT2, is returned to the original
output queue with a status of HLD, this means that either the Save file
attribute of INVRPT2 was set to *YES or an error condition may have
occurred while Monitor Queue was processing the spool file.
If an error condition occurred, the system cannot print INVRPT2 until the
error situation is corrected, and the file is released to Monitor Queue
again. In this case, an error message will be sent to the XDPE/400
message queue informing the user about the error condition.
Spool files processed by XDPE/400 in *PAGE mode with non-zero
WAITTIME are owned by the user who started the Monitor Queue
session, not by the owner of the original (unprocessed) spool file.
In this example, the original spool file is owned by YOURNAME and the
Monitor Queue session was started by YOURNAME. Therefore, the
XPREPEND file created by XDPE/400 is also owned by YOURNAME. If
the Monitor Queue session had been started by another user, for example
MONQUSR, the XPREPEND file created by XDPE/400 would be owned
by MONQUSR, not YOURNAME.
Printing Documents with XDPE/400 (9/2001)
19-9
Managing print operations
Working with Monitor Queue jobs
Use the Work With XDPE Monitor Queue (WRKMONQJOB) command to
access options from a list of Monitor Queue jobs that are currently
running. You can do the following:
•
Change the properties of a Monitor Queue session
•
Hold the writer that is associated with Monitor Queue
•
End a Monitor Queue session using the ENDWTR command, and
send a status message
•
Display the properties that are associated with the current Monitor
Queue session
•
Release the Monitor Queue job that was previously put on hold
NOTE: *JOBCTL and *SPLCTL special authorities are required to use
the WRKMONQJOB command.
The following is an example of the Work With XDPE Monitor Queue
screen that appears when you enter the WRKMONQJOB command:
Work With XDPE Monitor Queue
Position to . . . .
Starting characters
Type options, then press Enter.
1=XDPE jobs
2=Change
3=Hold
4=End
5=Display
6=Release
7=XDPE messages 8=Application output queue 9=XDPE output queue
10=Remote queue
Opt
Library/Queue
Writer
QUSRSYS/PRTO1
PRT4215
Status
Current/Last Job
DEQW
Bottom
Parameters or command
===>
F3=Exit F4=Prompt F5=Refresh
Printing Documents with XDPE/400 (9/2001)
F9=Retrieve
F12=Cancel
F22=Printers
19-10
Managing print operations
Field descriptions
This section explains the fields displayed on the Work With XDPE Monitor
Queue screen.
Opt
Library/Queue
Accepts the input for the options to be performed against the
corresponding Monitor Queue job. You can use these values:
•
Option 1 — Displays the active jobs running in the QSPL subsystem.
•
Option 2 — Changes the properties of a Monitor Queue session.
•
Option 3 — Holds the writer and suspends the printing of the current
spool file by a Monitor Queue. When the spool file is released, it will
print from the start of the job that was put on hold.
•
Option 4 — Ends a Monitor Queue session (with ENDMONQ).
•
Option 5 — Displays the Monitor Queue properties that were used to
start a session.
•
Option 6 — Releases a Monitor Queue job that was put on hold.
•
Option 7 — Displays the messages in the XDPE/400 message
queue.
•
Option 8 — Displays a list of spool files on the application output
queue.
•
Option 9 — Displays a list of spool files on the internal XDPE/400
output queue.
•
Option 10 — Displays a list of spool files on the remote XDPE/400
output queue.
Specifies the name of the output queue that Monitor Queue is currently
monitoring.
Writer
Specifies the writer to which the job that is currently being monitored will
be printed.
Status
Provides the status of Monitor Queue. If status is blank, it indicates no
Monitor Queue session is running. You need to reset that Monitor Queue.
These values may be displayed:
Current/Last Job
•
DEQW — The job is waiting for spool files (s) to be available for
processing
•
DLYW — The job is being delayed for an interval of time
•
END — The job ended with the *IMMED option
•
EOJ — The job is ending
•
HLD — The job is being held
•
PRTW — The job is waiting for output to a printer to be completed
•
RUN — The job is currently running and processing the spool file
•
LCKW — The job is waiting for a lock to be released
Identifies the job that Monitor Queue is currently processing or that it
processed last.
Printing Documents with XDPE/400 (9/2001)
19-11
Managing print operations
Job accounting
XDPE/400 supports the AS/400 Job Accounting function. Job Accounting
monitors the number of pages actually printed during the course of a job,
and the user running the job. Note these considerations when using this
feature in *PAGE mode:
•
The page count reported by XDPE/400 may vary slightly from the
actual number of physical pages printed depending on the amount of
resources downloaded and the settings for separator pages.
•
For jobs using multi-up processing, XDPE/400 logs the number of
physical pages printed, not the number of logical pages processed.
Printing Documents with XDPE/400 (9/2001)
19-12
20.
20
Remote/Network printing
This chapter contains information for using TCP/IP and HPT with
XDPE/400. XDPE/400 allows printing to three different device classes:
local (non-network), remote (via TCP/IP), and network (via TCP/IP and
HPT). Figure 20-1, shown on the next page, illustrates each of these
device classes.
•
Local — Prints to a printer connected directly to an AS/400 via a
twinax interface box.
•
Remote — Uses TCP/IP to print over a network. The remote device
class supports the same printer/interface twinax box configurations
that are used for local (non-network) printing.
•
Network — Uses TCP/IP in conjunction with an IBM feature called
Host Print Transform (HPT). The HPT feature included with
XDPE/400 allows printing to ASCII format printers without a twinax
interface box.
In order to connect to TCP/IP, you must have knowledge of the OS/400
implementation of TCP/IP and its uses, and have established your IP
connectivity. This chapter explains how to specify the TCP/IP connection
to XDPE/400 and how to tell XDPE/400 to route spool files using TCP/IP.
For additional information on AS/400 communications and TCP/IP
connectivity, refer to the related IBM publications.
Printing Documents with XDPE/400 (9/2001)
20-1
Remote/Network printing
Figure 20-1. Local, remote, and network printing
Printing Documents with XDPE/400 (9/2001)
20-2
Remote/Network printing
Supported printer/interface box configurations
This section provides information about local, remote, and network printer
configurations.
Local and remote printer configurations
Table 20-1 shows the printer configurations supported when *LCL and
*RMT are specified for the Device class (DEVCLS) Monitor Queue
parameter.
Table 20-1.
Interface devices for local and remote XDPE/400-supported printers
4700, 4213,
4030 II
4450
4230, 4220,
4219, 4215
9790, 9700, 8790, 8700, 4890,
4850, 4635, 4135, 4090, 4050,
180 LPS, 92C LPS, DP96,
*LCDS
Flex, Agile, Smart,
3X (4235 only)
—
INTERNAL
—
Spur USAII, Solimar, BARR
XDPM
Flex, Agile, MPI,
PCSUPP,
3X (4235 only)
Flex, Agile,
MPI,
PCSUPP
—
—
—
PCL
—
—
—
PCSUPP,
INTERNAL
—
Mode
4235, 3700
XPPM
Network printer configurations
These printers are supported for network printing and must be connected
without a twinax interface box. Printers running in PCL mode:
•
4890 NPS
•
180 NPS
•
4850 NPS
•
92C NPS
•
4635 NPS
•
DC265LP
•
4520
•
DC255LP
•
4517
•
DP96NPS
•
4512
•
DP65
•
4230
•
N32
•
4220
•
N24
•
4219
•
*DOCUSP
•
4215
•
*PCL
•
4090 NPS
•
*XJT
•
4050 NPS
•
*NPS
Printing Documents with XDPE/400 (9/2001)
20-3
Remote/Network printing
Printers running in VIPP mode:
•
4890 NPS
•
N4025
•
4850 NPS
•
N3225
•
4635 NPS
•
N2825
•
4635 NPS
•
N2125
•
4635 NPS
•
N2025
•
4050 NPS
•
N40
•
180 NPS
•
N32
•
92C NPS
•
N24
•
DP96NPS
•
N17
•
DP65
•
*VIPP
To specify a network printer, these values must be specified for the
Monitor Queue parameters:
•
The Interface box (INTERFACE) parameter must be *PCSUPP.
•
The Printer mode (MODE) parameter must be set to *PCL for PCL
mode printers and *VIPP for VIPP mode printers.
•
The Wait time between files (WAITTIME) parameter must be 0.
•
The Device class (DEVCLS) parameter must be *NET.
Setting up duplex printing on NPS printers (PCL or VIPP
mode)
If you plan to print duplex copies on an NPS printer running NPS version
1.6 or higher in PCL mode, or any version of NPS in VIPP mode, you need
to provide job level instructions to NPS to indicate that the printer can print
in duplex. NPS will print duplex copies only if the duplex parameter is
specified either on the LPR command or on the Virtual Printer on the NPS
controller.
The LPR command is generated internally by OS/400 using the remote
output queue attributes.
NOTE: Once you specify duplex copies, all jobs, including simplex
jobs, will print at the duplex speed.
Printing Documents with XDPE/400 (9/2001)
20-4
Remote/Network printing
Specifying the duplex parameter in the remote output
queue
To specify the duplex parameter in the remote output queue, perform
these steps:
Step 1.
End the remote writer by issuing the ENDWTR command.
Step 2.
Add the Destination Option 'C(duplex)' to the remote queue by issuing this
command. (Enter the Destination Option in mixed-case, exactly as
shown.)
CHGOUTQ
OUTQ(library-name/outq-name)
DESTOPT('C(duplex)')
where
library-name
The name of the XDPE/400 application library.
outq-name
The name of the remote output queue.
If the remote output queue has other values already defined for the
Destination Option, you must specify the new value and any other
value(s) in DESTOPT. Each value must be separated by at least one
space. For example, if the Destination Option “XAIX” is already specified
for the remote output queue, and now you want to specify the duplex
parameter, you would issue this command:
CHGOUTQ
OUTQ(library-name/outq-name)
DESTOPT('C(duplex) XAIX')
Specifying a Virtual Printer
To create a Virtual Printer for duplex on the NPS printer controller,
perform one of these actions:
•
If your OS/400 output queue is defined with Destination Option
'C(duplex)', issue this command:
Create Virtual Printer printer-name
where printer-name is the name of your Virtual Printer.
•
If your OS/400 output queue is not defined with Destination Option
'C(duplex)', issue these commands:
Create Virtual Printer printer-name
Change Virtual Printer printer-name Plex duplex
where printer-name is the name of your Virtual Printer.
Printing Documents with XDPE/400 (9/2001)
20-5
Remote/Network printing
Considerations
Using generic packets (XES and PCL modes)
For remote and network printing, do not use a generic packet that is larger
than 255 bytes; doing so can produce unpredictable results. Refer to
chapter 13, “XES command generation,” or chapter 15, “PCL command
generation,” for more information about how to create and use generic
packets.
Interfaces
If you are using TCP/IP without HPT, note these considerations when
using the Flex i-data interface box:
•
When using a Flex i-data interface controller on a network-attached
printer with TCP/IP, you must set the translation mode at the
interface, rather than through XDPE/400. The translation mode must
be set before a Monitor Queue session is started.
•
There are two translation modes supported for XDPE/400. Use this
function command to set the mode:
%Y70,mode%
where
mode
Is either “2” for XPPM mode or “1” for XDPM mode
%
User-defined i-data flex escape character
For more information, see the i-data XES/PCL Interface Controller for
Xerox Printers User's Guide.
Printing Documents with XDPE/400 (9/2001)
20-6
Remote/Network printing
Using Host Print Transform with TCP/IP
Host Print Transform (HPT) is an IBM AS/400 utility that converts SCS
EBCDIC spool files to ASCII spool files without losing the printer control
commands embedded in the spool files. XDPE/400 uses HPT internally to
transform the spool files for use with ASCII format printers.
To perform the transformation, XDPE/400 uses a workstation customizing
object containing a transformation table. The table identifies the EBCDIC
SCS commands in the spool file and converts them to ASCII format. The
converted data is written to the *USERASCII spool file and placed in the
sending output queue, to be sent over a network, via TCP/IP.
Customizing Host Print Transform
XDPE/400 allows you to specify a user-created workstation customizing
object. It is recommended that the XDPE/400 default workstation
customizing objects be used. Using a user-created workstation
customizing object may produce unpredictable results.
CAUTION: Do not modify the workstation customizing objects
included with XDPE/400 without first making a copy. You may be
asked to remove a user-coded workstation customizing object when
requesting software support.
Source copies of the transform tables included with XDPE/400 are located
in the SAMPLE database file in the XDPE/400 application library. The
default members are named XWSCSTxxxx and the euro-capable
members are named EWSCSTxxxx, where xxxx is the printer type. Use
these transform tables as templates — do not modify them. Refer to
OS/400 Workstation Customization Programming for more information
about how to create and use these objects.
Printing Documents with XDPE/400 (9/2001)
20-7
Remote/Network printing
Setting up TCP/IP support
This section describes how to set up TCP/IP to print to network printers.
The steps include:
•
Creating a sending output queue using the CRTOUTQ command.
This sending output queue specifies the destination and output
queue to send the processed spool files.
•
Starting the remote writer using the STRRMTWTR command to send
the files from the sending queue to the destination through TCP/IP.
•
Starting a Monitor Queue session using the STRMONQ command to
process files in a monitored queue and place them in the sending
queue.
Creating the sending TCP/IP output queue
Step 1.
To create the sending TCP/IP output queue, enter CRTOUTQ and press
ENTER. The Create Output Queue menu displays.
Create Output Queue (CRTOUTQ)
Type choices, press Enter.
Output queue . . . . . . .
Library . . . . . . . .
*CURLIB
Maximum spooled file size:
_
Number of pages . . . . .
*NONE
Starting time . . . . . .
Ending time . . . . . . .
+ for more values
Order of files on queue . .
*FIFO
Remote system . . . . . . .
*NONE
F3=Exit F4=Prompt F5=Refresh
F13=How to use this display
Step 2.
Name
Name, *CURLIB
Form type, *ALL, *STD
Time
Time
*FIFO, *JOBNBR
F10=Additional parameters
F24=More keys
F12=Cancel
Enter the name of the output queue you want to create and press F9. The
Create Output Queue menu displays additional parameters.
Printing Documents with XDPE/400 (9/2001)
20-8
Remote/Network printing
Step 3.
Modify the required parameters, following the conventions described in
the next section, and press ENTER.
NOTE: If, after creating the output queue, you experience problems
printing either multiple copies or duplexed copies of a job, refer to
chapter 26 for instructions on how to fix these problems.
Create Output Queue (CRTOUTQ)
Type choices, press Enter.
Output queue . . . . . . . .
Library
. . . . . . . . .
Maximum spooled file size: _
Number of pages . . . . . .
Starting time . . . . . . .
Ending time . . . . . . . .
+ for more values
Order of files on queue . . .
Remote system . . . . . . . .
SNDQUE01
*CURLIB
Name
Name, *CURLIB
*NONE
Number, *NONE
Time
Time
*FIFO
*NONE
*FIFO, *JOBNBR
Remote printer queue
. . . .
*USER
Writers to autostart
. . . .
*NONE
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
Printing Documents with XDPE/400 (9/2001)
F12=Cancel
1-10, *NONE
More...
F13=How to use this display
20-9
Remote/Network printing
Create Output Queue (CRTOUTQ)
Type choices, press Enter.
Queue for writer messages
Library . . . . . . . . .
Connection type . . . . . . .
Destination type . . . . . .
Transform SCS to ASCII . . .
Manufacturer type and model .
Workstation customizing object
Library . . . . . . . . .
Internet address . . . . . .
VM/MVS class . . . . . . . .
Forms Control Buffer . . . .
Destination options . . . . .
QSYSOPR
*LIBL
*IP
*OS400
*NO
*IBM42011
*NONE
Name
Name, *LIBL, *CURLIB
*SNA, *IP
*OS400, *OS400V2, *PSF2...
*YES, *NO
A
*NONE
*NONE
A, B, C, D, E, F, G...
Character value, *NONE
Text 'description'
*BLANK
. . . . .
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
Name, *NONE
Name, *LIBL, *CURLIB
F12=Cancel
More...
F13=How to use this display
Create Output Queue (CRTOUTQ)
Type choices, press Enter.
Additional Parameters
Display any file . .
Job separators . . .
Operator controlled
Data queue . . . . .
Library . . . . .
Authority to check .
Authority . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*NO
0
*YES
*NONE
*OWNER
*CHANGE
*NO, *YES, *OWNER
0-9, *MSG
*YES, *NO
Name, *NONE
Name, *LIBL, *CURLIB
*OWNER, *DTAAUT
Name, *USE, *ALL...
Bottom
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
Printing Documents with XDPE/400 (9/2001)
F12=Cancel
F13=How to use this display
20-10
Remote/Network printing
Required parameters for CRTOUTQ
This section describes the parameters required for using TCP/IP with
XDPE/400. All other parameters use their default value. Refer to the
OS/400 CL Reference for complete information on using this command
with TCP/IP.
Output queue (OUTQ)
Enter the name of the sending output queue you are creating. This queue
cannot be one monitored by any Monitor Queue session.
Library
Enter the name of the library where the output queue will be created. This
must be a library other than the XDPE/400 application library. You can
use these values:
Remote system (RMTSYS)
Remote printer queue
(RMTPRTQ)
name
Specifies the name of the library in which the output queue
resides.
*CURLIB
Uses the current library for the job to locate the output
queue. If a current library is not specified for the job, QGPL
is used.
Enter *INTNETADR to indicate you will be specifying an IP address.
Enter the name of the destination where the files are to be sent.
If the destination is an AS/400 output queue, enter the queue name
preceded by the library name, as in:
library-name/printer-queue-name
Example:
RMTLIB/RMTSYSQ
If you do not specify a library name, OS/400 will look for the queue in the
QUSRSYS library. If the queue is not found there, the spooled file is
routed to the QPRINT output queue in the QGPL library.
If the destination is not an AS/400, the name is system dependent, and
may be the name of a device, the name of an output queue, or the name
of a Virtual Printer. For example:
•
If you are running in PCL or VIPP mode and the file destination is an
NPS printer, this parameter must specify the name of a Virtual
Printer.
•
If you are running in PCL or VIPP mode and the file destination is a
DocuSP printer, this parameter must specify the name of a DocuSP
queue.
If the name must be in lowercase or mixed case, enclose the name in
single quotes, as in:
'OSRmtQ'
Connection type (CNNTYPE)
Destination type
(DESTTYPE)
Transform SCS to ASCII
(TRANSFORM)
Enter *IP for Internet Protocol.
Enter *OS400 if the destination is an AS/400. If you are sending your
output to a device other than another AS/400, such as a network-attached
printer, or to a system not matching any of the other special values, you
can specify *OTHER. Refer to OS/400 TCP/IP Configuration and
Reference for more information.
Enter *NO. XDPE/400 will perform the transformation internally.
Printing Documents with XDPE/400 (9/2001)
20-11
Remote/Network printing
Internet address
(INTNETADR)
Enter the Internet address of the destination system to which files will be
sent.
NOTE: Before you can specify an IP host name for use with
XDPE/400, you may have to assign the address in the OS/400 Host
Table. For details on this command refer to OS/400 TCP/IP
Configuration and Reference.
Authority (AUT)
Enter *CHANGE to allow other users to start a Monitor Queue.
Starting the sending writer
Use the Start Remote Writer (STRRMTWTR) command to start the
sending queue writer. The maximum number of writers that can be
connected to the remote output queue is ten.
Step 1.
To start the writer for the sending output queue you created with the
CRTOUTQ command in the previous section, enter STRRMTWTR and
press ENTER. The Start Remote Writer menu appears.
Start Remote Writer (STRRMTWTR)
Type choices, press Enter.
Output queue . . . . . .
Library . . . . . . .
Queue for writer messages
Library . . . . . . .
Form type options:
Form type . . . . . . .
Message option . . . .
*LIBL
*OUTQ
Name,
Name,
Name,
Name,
*ALL
*LIBL, *CURLIB
*OUTQ, *REQUESTER
*LIBL, *CURLIB
*ALL
*NOMSG
Form type, *All, *STD, *FORMS
*NOMSG, *INQMSG, *MSG...
Bottom
F3=Exit F4=Prompt
F24=More keys
Step 2.
F5=Refresh
F12=Cancel
F13=How to use this display
Enter the name of the remote output queue you wish to start the writer for
and press F10. The Start Remote Writer menu displays additional
parameters.
Printing Documents with XDPE/400 (9/2001)
20-12
Remote/Network printing
Step 3.
Modify the required parameters, following the conventions described in
the next section, and press ENTER.
Start Remote Writer (STRRMTWTR)
Type choices, press Enter.
Output queue . . . . . .
Library . . . . . . .
Queue for writer messages
Library . . . . . . .
Form type options:
Form type . . . . . . .
Message option . . . .
.
.
.
.
SNDQUE01
*LIBL
*OUTQ
Name,
Name,
Name,
Name,
*ALL
*LIBL, *CURLIB
*OUTQ, *REQUESTER
*LIBL, *CURLIB
.
.
*ALL
*NOMSG
Form type, *All, *STD, *FORMS
*NOMSG, *INQMSG, *MSG...
Additional Parameters
Writer . . . . . . . . . .
Auto-end options:
Automatically end writer
If yes, when to end . . .
*OUTQ
Name, *OUTQ, *SYSGEN
*NO
*NORDYF
*NO, *YES
*NORDYF, *FILEEND
Bottom
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
F12=Cancel
F13=How to use this display
Required parameters for STRRMTWTR
This section describes the parameters required for using TCP/IP with
XDPE/400. All other parameters use their default values.
Output queue (OUTQ)
Library
Enter the name of the sending output queue you created using the
CRTOUTQ command. You can use these values:
name
Specifies the name of the sending output queue to start the writer
for.
*ALL
Starts the writer for all sending output queues.
Specifies the name of the library where the sending output queue resides.
You can use these values:
*LIBL
Uses the library list to locate the output queue.
*CURLIB
Uses the current library for the job to locate the output
queue. If a current library is not specified for the job, QGPL
is used.
name
Specifies the name of the library where the output queue
resides.
Printing Documents with XDPE/400 (9/2001)
20-13
Remote/Network printing
Ending the remote writer
The writer used for the TCP/IP sending output queue does not end
automatically. Use the ENDWTR command to end the writer after all files
processed by the Monitor Queue session have been received by the
destination. The procedure for ending the TCP/IP remote writer is
identical to the procedure for ending a local writer.
Starting a Monitor Queue session
The procedure for starting a Monitor Queue session to a remote or
network print device is similar to starting a Monitor Queue session to a
local print device, with the following required parameters. These
parameters require specific values for remote and network printing.
Interface box (INTERFACE)
File processing mode
(PROCMODE)
Specify *PCSUPP if you are using HPT with TCP/IP. If you are using
TCP/IP only, specify the interface type that is appropriate for your
configuration.
Enter *PAGE. TCP/IP will not function in *JOB mode.
Wait time between files
(WAITTIME)
Enter 0. TCP/IP will not function properly if WAITTIME is any value other
than 0.
Device class (DEVCLS)
Specify the class of printing device, whether it is printing locally or printing
over a network. The default value is *LCL, which specifies local printing.
Enter *RMT if you want to print to a network-attached twinax printer via
TCP/IP.
Enter *NET if you are printing to an ASCII format printer via TCP/IP. In
both cases, the Monitor Queue sends print output to the Remote/Network
output queue for processing by the remote writer.
Remote/Network output
queue (RMTOUTQ)
Enter the name of the output queue you created using the Create Output
Queue (CRTOUTQ) command. When a Remote/Network output queue is
specified, XDPE/400 places the processed spool files in the output queue
specified with this parameter, not the XDPE/400 internal output queue in
the XDPE/400 application library. When printing over a network using
TCP/IP or TCP/IP and HPT, a value must be entered for this parameter.
When you specify a remote/network output queue, either in the Monitor
Queue or as part of a multi-part job, do not specify an output queue that
is monitored by a Monitor Queue session. If the specified output queue is
monitored by a Monitor Queue session, the spool file will be placed on the
XDPE/400 internal output queue in the XDPE/400 application library.
Library
Specify the name of the library in which the output queue was created.
Printing Documents with XDPE/400 (9/2001)
20-14
Remote/Network printing
Workstation customizing
object (WSCST)
For network printing, this parameter specifies the workstation customizing
object that contains the Host Print Transform table to be used for this
Monitor Queue session. It is recommended that either the XDPE/400
default WSCST (*XDPEDFT) or euro-capable default WSCST
(*EURODFT) be used. Both *XDPEDFT and *EURODFT use one of the
XDPE/400 default workstation customizing objects in the XDPE/400
application library. See the Workstation customizing object (WSCST)
Monitor Queue parameter in chapter 18 for a list of the WSCST options.
NOTE: The use of a user-created workstation customizing object
during a Monitor Queue session may produce unpredictable results.
Library
Specify the name of the library where the workstation customizing object
is located. If no value is entered, *LIBL is used.
Refer to chapter 18 for more information on these parameters.
Changing a Monitor Queue session
When using the Change Monitor Queue (CHGMONQ) command during a
TCP/IP Monitor Queue session, note these considerations:
•
The sending output queue (RMTOUTQ) can be changed during a
Monitor Queue session.
•
Wait time between files (WAITTIME) cannot be changed. WAITTIME
must be 0 (zero).
•
Device class (DEVCLS) cannot be changed. You cannot switch
between TCP/IP, TCP/IP with HPT, or local printing during a Monitor
Queue session.
All other functionality is unaffected. You can use the Display Monitor
Queue (DSPMONQ) command to view these settings without changing
them. Refer to chapter 18 for more information on these parameters.
Printing Documents with XDPE/400 (9/2001)
20-15
Remote/Network printing
Remote/Network resource downloading
Use either of these methods to download resources to your
remote/network printer:
NOTE: These methods are not valid for NPS or DocuSP printers
running in either PCL or VIPP mode. Refer to chapter 21 for
instructions about how to download PCL or VIPP resources.
•
Specify the output queue of the remote/network printer with the
Output queue/Library (OUTQ) parameter for the download resource
command used.
•
Specify an output queue that is monitored by a Monitor Queue
session with the Output queue/Library (OUTQ) parameter for the
download resource command used. The output queue of the
remote/network printer must be specified in that Monitor Queue
session using the Remote/Network output queue (RMTOUTQ)
Monitor Queue parameter.
The resources will be placed in the remote/network output queue for
the printer without being processed by XDPE/400.
NOTE: For the resources to be received by the printer, an
OS/400 writer must be started to the remote/network output
queue.
Printing Documents with XDPE/400 (9/2001)
20-16
21.
21
Resource management
This chapter shows you how to manage printer resources using
XDPE/400. XDPE/400 allows you to download resources manually using
download resource commands, or you can download resources
semi-automatically using resource lists. Table 21-1 shows the printer
resources that you can download.
Table 21-1.
Downloadable printer resources
Command
Resource type
XDPEFLR subfolder
Printer type
DNLDFNTRSC
DJDE fonts
FONTS
XPPM (DJDE)
DNLDFRMRSC
DJDE forms
FORMS
XPPM (DJDE)
DNLDIMGRSC
DJDE images
IMAGES
XPPM (DJDE)
DNLDLGORSC
DJDE logos
LOGOS
XPPM (DJDE)
DNLDJDLRSC
DJDE JDL objects
JDL
XPPM (DJDE)
DNLDPDLRSC
DJDE PDL objects
PDL
XPPM (DJDE)
DNLDFSLRSC
DJDE FSL source
FSL
XPPM (DJDE)
DNLDJSLRSC
DJDE JSL source
JSL
XPPM (DJDE)
DNLDXESFNT
XES fonts
XESFONTS
XDPM (XES)
DNLDXESFRM
XES forms
XESFORMS
XDPM (XES)
DNLDPCLMAC
PCL macros
PCLMAC
XPCL (PCL)
DNLDPCLFNT
PCL fonts
PCLFONTS
XPCL (PCL)
DNLDVIPENC
VIPP encoding tables
ENCODING
PostScript (VIPP) —
N-series printers only
DNLDVIPFNT
VIPP fonts
MISLIB
PostScript (VIPP) —
N-series printers only
DNLDVIPFRM
VIPP forms and
segments
FORMLIB
PostScript (VIPP) —
N-series printers only
DNLDVIPIMG
VIPP images
IMGLIB
PostScript (VIPP) —
N-series printers only
DNLDVIPJDT
VIPP JDTs
JDTLIB
PostScript (VIPP) —
N-series printers only
Printing Documents with XDPE/400 (9/2001)
21-1
Resource management
Table 21-1.
Downloadable printer resources (Continued)
Command
DNLDVIPRSC
Resource type
XDPEFLR subfolder
VIPP forms and
segments
FORMLIB
VIPP images
IMGLIB
VIPP JDTs
JDTLIB
VIPP encoding tables
ENCODING
PostScript fonts, VIPP
core and setup files
MISLIB
Printing Documents with XDPE/400 (9/2001)
Printer type
PostScript (VIPP) —
NPS and DocuSP
printers only
21-2
Resource management
Copying resources to the XDPEFLR resource folder
Your resources must be on the AS/400 in the appropriate XDPEFLR
subfolder. Use the following procedures to copy resources from an
AS/400 database file or from a PC to the appropriate XDPEFLR subfolder.
Copying resources from an AS/400 database file
The resources you use with XDPE/400 must be in the appropriate
XDPE/400 subfolders. To copy resources from an AS/400 database file to
a subfolder, use the CL CPYTOPCD command. Follow this procedure:
Enter this command and press F4:
CPYTOPCD
FROMFILE(library-name/file-name)
FROMMBR(member-name)
TOFLR('XDPEFLR/subfolder-name')
TODOC(document-name)
TRNFMT(*TEXT|*NOTEXT)
TRNTBL(name|*CURLIB|*LIBL|*DFT|*NONE)
For more information on the CPYTOPCD command, refer to the OS/400
CL Reference.
TRNFMT
The TRNFMT keyword determines if the file is terminated with a carriage
return/line feed (CR/LF) sequence when transferred to the folder. This
keyword also determines if the file is translated. You can use these
values:
•
*TEXT — Deletes trailing spaces and appends an ASCII CR/LF to
the end of each database record. Use this keyword for source
resources that must be translated.
Select this option when creating text resources as text resource
records, job source languages (JSLs), and forms source languages
(FSLs). JSLs and FSLs must be terminated by an ASCII CR, LF, or
CR/LF when they are downloaded to a Xerox printer.
•
TRNTBL
*NOTEXT — Does not insert a CR/LF at the end of each record. Use
this keyword for object format resources that must not be translated,
such as images and logos.
The TRNTBL keyword selects the translation table used to translate the
database characters to the correct encoding for use in the subfolder. The
TRNTBL keyword has no meaning unless the TRNFMT keyword is *TEXT.
You can use these values:
•
*DFT — Translates the data in the database file from EBCDIC to
ASCII
Text resources, JSLs, and FSLs must be in ASCII format when they
are downloaded to a Xerox printer.
•
*NONE — Specifies no translation
Use this option with object format resources, such as logos and JDLs.
Printing Documents with XDPE/400 (9/2001)
21-3
Resource management
Copying resources from a PC
To use resources that are on a PC, you must first copy them to the
appropriate XDPE/400 folders on the AS/400.
Use the IBM Client Access shared folder facility to copy the resources.
Shared folders let the PC access files in folders on the AS/400 as if they
were in a directory on the fixed disk of the PC. The resources in a PC file
must be in a format that the Xerox printer can read.
You must have the correct access rights to work with the XDPEFLR folder.
For more information on using AS/400 Client Access, refer to the OS/400
setup manual for your type of PC.
Follow these steps to copy the resources from the PC to the AS/400:
Step 1.
Enter this PC command to assign a drive letter to the AS/400 folder:
I:FSPC ASSIGN d: XDPEFLR
where:
Step 2.
I:
Indicates the system drive letter that is automatically assigned to
QIWSFLR folder on the AS/400. This is the default drive for PC
Support and is assigned automatically when you execute STARTPCS
to begin PC Support.
d:
Indicates any PC drive letter that is currently not being used, such as
E: or F:. This drive letter must be in the range of D: to L:.
Enter this DOS copy command to place a resource in an XDPE/400 folder:
COPY file-name D:subfolder
where:
file-name
Specifies the name of the DOS file copied to the AS/400.
subfolder
Specifies the name of the subfolder to which the resource is
copied. There is a separate subfolder for each type of
resource that XDPE/400 supports.
The subfolders and types of resources in them are listed in table 21-1,
shown earlier in this chapter.
Printing Documents with XDPE/400 (9/2001)
21-4
Resource management
Downloading resources manually (DJDE, XES, and PCL
modes)
You can use the Xerox resource management options to manually
download DJDE, XES, and PCL resources from an AS/400 to the printer.
Each type of resource is downloaded with a separate command. The
command you use to download your resources depends on the type of
resource you are downloading, and the type of printer to which you are
downloading the resources. Each resource is downloaded as a spool file.
Example of downloading resources manually
Follow these steps to access the Xerox resource management options:
Step 1.
Enter WRKXRSC and press ENTER. The Work with Xerox Resource
menu displays.
WRKXRSC
Work with Xerox Resource
System: XXXXXXXX
Select one of the following:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
Download
font resource
form resource
image resource
logo resource
JDL resource
PDL resource
FSL source
JSL source
XES font
XES form
Xerox PCL macro body
Xerox PCL font
DNLDFNTRSC
DNLDFRMRSC
DNLDIMGRSC
DNLDLGORSC
DNLDJDLRSC
DNLDPDLRSC
DNLDFSLRSC
DNLDJSLRSC
DNLDXESFNT
DNLDXESFRM
DNLDPCLMAC
DNLDPCLFNT
Selection or command
===>
F1=Help
F3=Exit
Step 2.
F4=Prompt
F9= Retrieve
F12=Cancel
F16=Major menu
Type the number of the download option you want and press ENTER. A
menu for the selected option displays.
Printing Documents with XDPE/400 (9/2001)
21-5
Resource management
Step 3.
Type the appropriate options for each field and press ENTER.
NOTE: All download commands have the same fields, except for PCL
macro and PCL font. PCL macro has a Macro id assignment (MID)
parameter with a range of 1 to 32,000 (except for 80 to 89). PCL font
has a Font id assignment (FID) parameter with a range of 1 to 32,000.
The download resource options are described in detail in the following
section.
Download Font Resource (DNLDFNTRSC)
Type choices, press Enter.
Font file name
Output queue .
Library . .
Interface type
Printer model
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*LIBL
Name, F4 for list
Name
Name, *LIBL, *CURLIB
*FLEX, *USAII, *SOLIMAR...
4050, 4090, 4135, 4235...
Bottom
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
F12=Cancel
F13=How to use this display
Parameters
Resource file name
Specifies the name of the resource to be downloaded. The resource must
be in the subfolder that corresponds to the resource type selection. This
file may also contain the name of a resource list to be downloaded. For
the resource list name, the first character must be an at sign (@). Refer
to chapter 22 for more information about list processing.
Output queue (OUTQ)
Specifies the name of the output queue to which the resource download
spool file is written. If Monitor Queue is controlling the printing on the
printer to which the resource is downloaded, use the name of the output
queue that Monitor Queue is monitoring.
If Monitor Queue is not controlling the printing, specify the output queue
that has the printer writer started for the printer you want.
Printing Documents with XDPE/400 (9/2001)
21-6
Resource management
Library
Interface type (INTERFACE)
Specifies the name of the library that contains the output queue. You can
use these values:
•
*LIBL — Uses the library list to locate the message queue.
•
*CURLIB — Uses the current library for the job to locate the
message queue. If a current library is not specified for the job, QGPL
is used.
•
name — Specifies the name of the library that contains the message
queue.
Specifies the name of the interface box used to connect the Xerox printer
to the AS/400 system. You can use these values:
*FLEX
*SMART
*AGILE
*USAII
*SOLIMAR
*BARR
*INTERNAL
*X3X
*MPI
Printer model (MODEL)
Specifies the model number of the Xerox printer to download the
resource. Press F4 to display a list of supported printer models. You can
use these values:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
9790
9700
8790
8700
4890
4850
4450
4235
4135
4090
4050
4030
3700
180LPS
92CLPS
DP96
*LCDS
Printing Documents with XDPE/400 (9/2001)
21-7
Resource management
Downloading PCL macros
Use the PCL Macro Resource (DNLDPCLMAC) command to add a
permanent macro resource to the Xerox resource PCL printer.
You can use the assigned ID to reference the macro within a Xerox PCL
packet or within a PCL data stream.
Numeric ID numbers reference macros stored in the printer’s dynamic
memory. These macros will be deleted when the printer is powered off.
NOTE: For NPS printers, macros can only be downloaded as part of
a print job, not manually using the DNLDPCLMAC command.
PCL macro parameters
This section describes the parameters of a PCL macro.
Macro file name (PCLMAC)
A required parameter that specifies the name of the file in the
XDPEFLR/PCLMAC folder that contains the macro file that will be
downloaded. The file name can be up to eight characters. No file
extension should be present. An example of a valid name for a macro
resource file is LB01A.
Output queue (OUTQ)
A required parameter that specifies a qualified name for the output queue.
It also specifies the library where the output queue is located.
Interface type (INTERFACE)
Specifies the name of the interface box used to connect the Xerox printer
to the AS/400 system. You can use these values:
Printer model (MODEL)
•
*INTERNAL — Specifies that the interface is internal to the Xerox
printer, and is valid for the 4230, 4220, 4219, and 4215 printers.
•
*PCSUPP — Specifies that the printer is interfaced to the AS/400
through the parallel interface of the computer or network-attached by
means of Client Access or PC support. This value is valid for the
4520, 4517, 4512, 4230, 4220, 4219, 4215, DC265LP, DC255LP,
DP65, N32, N24, *PCL, *DOCUSP, and *XJT printers.
A required parameter that specifies one of these printer model numbers
to use.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
4520
4517
4512
4230
4220
4219
4215
DC265LP
DC255LP
DP65
N32
N24
*DOCUSP
*PCL
*XJT
Printing Documents with XDPE/400 (9/2001)
21-8
Resource management
Macro id assignment (MID)
Specifies the ID number to use in subsequent PCL macro management
commands. You can use the ID number of the macro to select it for
printing within a PCL packet. The ID number can be a any value between
1 and 79, or 90 and 32,000 (the numbers 80 through 89 are used by
XDPE/400 for PCL packet macro processing).
CAUTION: ID numbers reference macros stored in the printer’s
dynamic memory. These macros will be deleted when the printer is
powered off.
The Macro id assignment (MID) and Macro name (MACRONAME) PCL
macro parameters are mutually exclusive.
Macro name (MACRONAME)
Specifies the macro name to use in subsequent PCL macro management
commands. The name can be any alphanumeric value between 1 and 20
characters in length. Downloaded alphanumeric macros are permanently
stored on the printer’s hard drive. They will be preserved even when the
printer is powered off. This parameter applies only to the N32 and N24
printers.
The Macro id assignment (MID) and Macro name (MACRONAME) PCL
macro parameters are mutually exclusive.
Using macros with PCL printers
XDPE/400 PCL resource processing with the DNLDPCLMAC command
allows you to download a macro body that is in the XDPEFLR/PCLMAC
folder. You can assign and use a macro ID later in a Xerox PCL packet or
in a generic PCL packet.
You must delete specific commands from PCL forms, macro bodies, or
PRN files that were created from a package, such as ELIXIR, before they
can be used as overlays on PCL printers.
This table shows the PCL commands that need to be removed.
PCL command that
must be deleted
Meaning
&I#P
Page length
(esc) &I#A
Page size
(esc) &I#O
Page orientation
(esc) &I#H
Paper source
(esc) %-12345X
UEL (Universal Exit Language)
(esc) &r#F
Flush pages
(esc) &I#S
Simplex/duplex
(esc) E
Printer reset
X'0C'
Page eject
Printing Documents with XDPE/400 (9/2001)
21-9
Resource management
Downloading PCL fonts
Use the Download PCL Fonts Resource (DNLDPCLFNT) command to add
a permanent font resource to the Xerox PCL printer.
You can use the assigned ID to reference the font within a Xerox PCL
packet or within a PCL data stream.
Numeric ID numbers reference fonts stored in the printer’s dynamic
memory. These fonts will be deleted when the printer is powered off.
NOTE: For NPS printers, fonts can only be downloaded as part of a
print job, not manually using the DNLDPCLFNT command.
PCL font parameters
This section describes the parameters of a PCL font.
Font file name (PCLFONTS)
A required parameter that specifies the name of the file in the
XDPEFLR/PCLFONTS folder that contains the font definition to be
downloaded. The file name can be up to eight characters followed by an
extension, which is optional. However, extension FLJ will be added if one
is not present. You can specify these extensions:
•
•
•
FLJ
HPL
HPP
PCLFONTS can also specify a list name, preceded by the at sign (@), that
contains the names of multiple resources to be downloaded. For example,
@LISTNAME would be a valid list name. A list can contain a mixture of
resources, such as PCL macros and PCL fonts, but the list file must be
placed in the folder corresponding to the resource download command
being used. For example, the DNLDPCLFNT command will look for the list
in the XDPEFLR/PCLFONTS folder, even if it contains different types of
resource entries.
Output queue (OUTQ)
A required parameter that specifies a qualified name for the output queue.
Also specifies the library where the output queue is located.
Interface type (INTERFACE)
Specifies the name of the interface box used to connect the Xerox printer
to the AS/400 system. You can use these values:
•
*INTERNAL — Specifies that the interface is internal to the Xerox
printer, and is valid for the 4230, 4220, 4219, and 4215 printers.
•
*PCSUPP — Specifies that the printer is interfaced to the AS/400
through the parallel interface of the computer or network-attached by
means of Client Access or PC support. This value is valid for the
4520, 4517, 4512, 4230, 4220, 4219, 4215, DC265LP, DC255LP,
DP65, N32, N24, *PCL, *DOCUSP, and *XJT printers.
Printing Documents with XDPE/400 (9/2001)
21-10
Resource management
Printer model (MODEL)
A required parameter that specifies one of these printer model numbers:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Font id assignment (FID)
4520
4517
4512
4230
4220
4219
4215
DC265LP
DC255LP
DP65
N32
N24
*DOCUSP
*PCL
*XJT
Specifies the ID number to use in subsequent PCL font management
commands. You can use the ID number of the font to select the font for
printing in a PCL packet. The ID number can be a value between 1 and
32000.
NOTE: ID numbers reference fonts stored in the printer’s dynamic
memory. These fonts will be deleted when the printer is powered off.
The Font id assignment (FID) and Font name (FONTNAME) PCL font
parameters are mutually exclusive.
Font name (FONTNAME)
Specifies the font name to use in subsequent PCL font management
commands. You can use the name of the font to select it for printing within
a PCL packet. The name can be any alphanumeric value between 1 and
20 characters in length. Downloaded alphanumeric fonts are permanently
stored on the printer’s hard drive. They will be preserved even when the
printer is powered off. This parameter applies only to the N32 and N24
printers.
The Font id assignment (FID) and Font name (FONTNAME) PCL font
parameters are mutually exclusive.
Printing Documents with XDPE/400 (9/2001)
21-11
Resource management
Downloading resources manually (NPS and DocuSP
printers in VIPP mode)
The Download VIPP Resource (DNLDVIPRSC) command downloads one
or more VIPP or PostScript resources to the VIPP printer controller on the
NPS and DocuSP printers. For information on downloading resources
manually to an N-series printer, refer to the next section “Downloading
resources manually (N-series printers in VIPP mode).” XDPE/400
performs the download using an automated File Transfer Protocol (FTP)
process.
NOTE: To use DNLDVIPRSC, OS/400 TCP/IP must be properly
configured on your AS/400 system. In addition, you must have write
authority for the printer controller to which you will download
resources.
During the download process, XDPE/400 creates a spool file, named
XDPEFTPLOG, to log OS/400 and FTP messages received by XDPE/400.
This file is automatically displayed at the end of the XDPE/400 FTP
download process. XDPEFTPLOG also can be found in your default
output queue.
You will need to review this log for any error messages to verify that the
process completed successfully. The log consists of two parts:
•
The first part shows the results of the FTP script creation process. If
there is an error message in the script processing for a resource,
XDPE/400 will not attempt to download the resource.
•
The second part shows the results of the FTP execution by
XDPE/400.
Printing Documents with XDPE/400 (9/2001)
21-12
Resource management
Downloading VIPP or PostScript resources
Use the Download VIPP resource (DNLDVIPRSC) command to download
these VIPP or PostScript resources to the printer controller via FTP:
•
•
•
•
•
•
•
fonts
forms
images
JDTs
segments
encoding tables
core and setup files
Follow these steps to download a VIPP resource. See “Resource
download parameters” below for the requirements for each command
parameter.
Step 1.
Enter DNLDVIPRSC. The Download VIPP Resource (DNLDVIPRSC)
command screen displays.
Download VIPP Resource (DNLDVIPRSC)
Type choices, press Enter.
VIPP resource name
Printer controller
Printer controller
Remote system . .
F3=Exit
F4=Prompt
F24=More keys
Step 2.
. . . . .
user ID .
password
. . . . .
.
.
.
.
.
.
.
.
F5=Refresh
____________
________
Character value
Character value
Character value
__________________
F12=Cancel
Bottom
F13=How to use this display
Enter the appropriate values for each screen parameter. Refer to
“Resource download parameters” below for the valid values for each
parameter.
Printing Documents with XDPE/400 (9/2001)
21-13
Resource management
Step 3.
Press ENTER.
XDPE/400 will attempt to download the requested VIPP or PostScript
resource to the selected printer. When processing completes, XDPE/400
will automatically display a log, called XDPEFTPLOG, that contains all
messages generated during the download process. For example:
Display Spooled File
File . . . . . :
XDPEFTPLOG
Page/Line
1/1
Control . . . . .
Columns
1 - 78
Find . . . . . .
*...+....1....+....2....+....3....+....4....+....5....+....6....+....7....+...
5769SS1 V4R4M0 990521
SEU SOURCE LISTING
SOURCE FILE . . . . . . . QTEMP/FTPSRC
MEMBER . . . . . . . . . FTPLOG
SEQNBR*...+... 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+... 7
/*====================================================================
SCRIPT PROCESSING PROGRAM ERROR LOG
/*====================================================================
No errors were encountered during script processing.
/*====================================================================
FTP JOB LOG
/*====================================================================
Output redirected to a file.
Input read from specified override file.
Connecting to remote host 12.345.678.901 using port 21.
220 tahoep2 FTP server (UNIX(r) System V Release 4.0) ready.
Enter login ID (xe99999):
331 Password required for root.
230 User root logged in.
Enter an FTP subcommand.
> binary
200 Type set to I.
More...
F3=Exit
F12=Cancel
F19=Left
F20=Right
F24=More keys
This log consists of two parts:
Step 4.
•
The SCRIPT PROCESSING PROGRAM ERROR LOG identifies any
processing errors that occurred while building the script for the FTP
(such as log file open errors). If an error is identified in the SCRIPT
PROCESSING PROGRAM ERROR LOG, XDPE/400 will not execute
the FTP.
•
The FTP JOB LOG provides messages about the execution of the
FTP.
Review both parts of XDPEFTPLOG to ensure that no severe errors
occurred, no errors occurred during downloading, and processing
completed successfully.
NOTE: If you successfully downloaded any PostScript fonts or VIPP
core files and setup files, they will be located in the /usr/xgfc/mislib/
directory on the printer controller. You will have to manually move
them to the correct directory for your printer.
Printing Documents with XDPE/400 (9/2001)
21-14
Resource management
Resource download parameters
VIPP resource name
(VIPRSC)
Specifies the name of the VIPP or PostScript resource to be downloaded.
The format for the VIPP resource name is as follows:
resource.ext
where
•
resource is the name of the VIPP or PostScript resource. The name
can be up to eight characters.
Two wild card characters can be used to represent one or more
characters in the resource name:
—
asterisk (*) — Represents one or more characters. For example,
if you specify a resource name of A*6, XDPE/400 would process
any of these members:
A56
ALLO6
ACCTG006
—
question mark (?) — Represents one character. For example, if
you specify a resource name of ACCTG6?, XDPE/400 would
process any of these members:
ACCTG60
ACCTG61
ACCTG6P
•
.ext is the extension for the resource. XDPE/400 uses the extension
of the VIPP resource name to identify the subfolder where the
resource resides in XDPEFLR and where the resource will reside on
the printer controller. The subfolder name is used as the
subdirectory name on the printer controller in the /usr/xgfc/directory.
The extensions and their related subfolders and subdirectories
appear in this table.
Extension
VIPP or PostScript
resource type
Folder location used
by XDPE/400
Destination printer
directory location
.frm or .seg
forms or segments
XDPEFLR/FORMLIB
/usr/xgfc/formlib/
.tif or .jpg
images
XDPEFLR/IMGLIB
/usr/xgfc/imglib/
.jdt
JDTs
XDPEFLR/JDTLIB
/usr/xgfc/jdtlib/
none
encoding tables
XDPEFLR/ENCODING
/usr/xgfc/encoding/
Any other extension
PostScript fonts
XDPEFLR/MISLIB
/usr/xgfc/mislib/
XDPE/400 converts and processes all alphabetical characters in a VIPP
resource name as uppercase characters on the AS/400 but downloads the
names in lowercase characters to the printer controller. For example, if
you specify a resource name called acctg61.jdt in DNLDVIPRSC,
XDPE/400 processes the resource as ACCTG61.JDT, but downloads the
resource as acctg61.jdt to /usr/xgfc/jdtlib/.
Printing Documents with XDPE/400 (9/2001)
21-15
Resource management
Print controller user ID
(PRTCTLID)
Specifies the printer controller user ID to be used by XDPE/400 to
download the resources to the printer controller using FTP. This user ID
must have write authority on the printer controller.
This value can be up to eight mixed-case characters. Quotation marks are
not required to maintain the case of the characters.
Print controller password
(PRTCTLPW)
Specifies the password for the printer controller user ID to be used for the
FTP session. To maintain security, your input to this field will not display
as you are entering it.
This value can be up to eight mixed-case characters. Quotation marks are
not required to maintain the case of the characters.
Remote system (RMTSYS)
Specifies the system name as defined on the AS/400, or the TCP/IP
address of the printer controller to which the resource(s) will be
downloaded. For example:
RMTSYS
111.222.333.444
Printing Documents with XDPE/400 (9/2001)
21-16
Resource management
Downloading resources manually (N-series printers in VIPP
mode)
The following commands are used for manually downloading the various
types of VIPP or PostScript resources to the N-series printers. Each type
of resource is downloaded with a separate command. The command you
use to download your resources depends on the type of resource you are
downloading. Each resource is downloaded as a spool file.
Resource type
Download command
fonts
DNLDVIPFNT
forms
DNLDVIPFRM
images
DNLDVIPIMG
JDTs
DNLDVIPJDT
encoding tables
DNLDVIPENC
Refer to the “Downloading resources automatically” section in this chapter
to download resources semi-automatically using resource lists for the
VIPP or PostScript resources.
Example of downloading resources manually
The next section describes the download resource parameters for the
N-series printers.
Download VIPP JDT (DNLDVIPJDT)
Type choices, press Enter.
JDT resource name . . . . .
Output queue . . . . . . . .
Library . . . . . . . . .
Interface type . . . . . . .
Printer model . . . . . . .
*LIBL
*PCSUPP
Name, F4 for list
Name
Name, *LIBL, *CURLIB
*PCSUPP
N17, N2025, N2125, N24...
Bottom
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
Printing Documents with XDPE/400 (9/2001)
F12=Cancel
F13=How to use this display
21-17
Resource management
Resource download parameters
JDT resource name
Specifies the name of the resource to be downloaded, for instance,
JDTLIB subfolder if the processing mode is VIPP. The resource must be
in the subfolder that corresponds to the resource type selection. This file
may also contain the name of a resource list to be downloaded. Refer to
chapter 22 for more information about list processing.
Resource types, commands, extensions, and related subfolders and
subdirectories appear in this table.
Command
VIPP or PostScript
resource type
Extension
Folder location used
by XDPE/400
Destination printer
directory location
DNLDVIPFRM
.frm or .seg
forms or segments
XDPEFLR/FORMLIB
/usr/xgfc/formlib/
DNLDVIPIMG
.tif or .jpg
images
XDPEFLR/IMGLIB
/usr/xgfc/imglib/
DNLDVIPJDT
.jdt
JDTs
XDPEFLR/JDTLIB
/usr/xgfc/jdtlib/
DNLDVIPENC
none
encoding tables
XDPEFLR/ENCODING
/usr/xgfc/encoding/
DNLDVIPFNT
Any other
extension
PostScript fonts
XDPEFLR/MISLIB
/ps/fonts/
Output queue (OUTQ)
Specifies the name of the output queue to which the resource download
file is written. If Monitor Queue is controlling the printing on the printer to
which the resource is downloaded, use the name of the output queue that
Monitor Queue is monitoring.
If Monitor Queue is not controlling the printing, specify the output queue
that has the printer writer started for the printer you want.
Library
Interface type (INTERFACE)
Specifies the name of the library that contains the output queue. You can
use these values:
•
*LIBL — Uses the library list to locate the message queue.
•
*CURLIB — Uses the current library for the job to locate the
message queue. If a current library is not specified for the job, QGPL
is used.
•
name — Specifies the name of the library that contains the message
queue.
Specifies the name of the interface box used to connect the Xerox printer
to the AS/400 system. You can use this value:
•
Printer model (MODEL)
*PCSUPP
Specifies the model number of the Xerox printer to download the
resource. Press F4 to display a list of supported printer models. You can
use these values:
•
•
•
•
•
N4025
N3225
N2825
N2125
N2025
Printing Documents with XDPE/400 (9/2001)
•
•
•
•
•
N40
N32
N24
N17
*VIPP
21-18
Resource management
Downloading resources automatically
By using Monitor Queue, you can list the resources to download instead
of having to download them separately. This capability is enabled by
XDPE/400 list processing.
NOTE: List processing support of VIPP-enabled printers is limited to
N-series printers. The list processing feature does not support
resource downloads for DocuSP and NPS printers in VIPP mode.
You can use list processing to enable the automatic resource
downloading with either the download commands (DNLDxxxRSC,
DNLDVIPxxx) or through the packet data field of the spool file attributes.
To enable list processing resource downloading with a download
command, you must first create a list of resources. Instead of providing a
resource name in the download command, supply the name of the
resource list.
To enable list processing resource downloading from the spool file
attributes, store the resource list name in the packet data field of the spool
file attributes. Refer to chapter 22 for more information about list
processing.
4213 environment saving
The 4213 printer allows you to allocate a portion of printer memory to save
the environment of an emulation mode (XES, LJ2D, and LJ3D) without
reconfiguring the printer. The current emulation mode can be overridden
by embedding Mode Switch (=MCK=) command strings in the beginning
of your data stream. XDPE/400 inserts MCK commands into the data
stream to switch the emulation to XES for all XES resources processed.
If you do not enable Environment Saving on the printer, all XES resources
are removed from the 4213 printer once the emulation is switched from
XES. For detailed information on Environment Saving, refer to the “Using
the menus” chapter of the Xerox 4213 Laser Printing Systems User
Guide.
Printing Documents with XDPE/400 (9/2001)
21-19
Resource management
Using euro fonts with your PCL print jobs
The common unit of currency for the European Economic and Monetary
Union (EMU) is the euro. The euro currency symbol is €. This section
describes the steps needed to set up your system to support PCL euro
fonts.
To incorporate euro fonts into your print jobs, you need to make changes
in each of these areas:
•
•
Your AS/400 system
XDPE/400 and your Xerox PCL printer
The following sections describe how to make these changes.
Changes to your AS/400 system
This section lists the changes that need to be made to your AS/400
system in order to support the use of euro fonts.
•
OS/400 Language Support — The AS/400 National Language
Support euro software must be installed on your system with your
National Language Version Feature Codes that include euro support.
This software contains the translation tables used for keyboard
EBCDIC code pages, printer EBCDIC code pages, workstation
customization ASCII code pages, as well as for other tasks unrelated
to printing. For additional information, refer to the OS/400 National
Language Support and the OS/400 International Application
Development publications.
•
Application support — Contact your software vendor to determine if
your applications are euro compliant and to find out what EBCDIC
code pages support the euro currency symbol.
•
Terminal configuration
•
Printer file configuration
The following sections provide the procedures needed to configure your
terminal and printer file.
Terminal configuration
To include the euro currency symbol in your print data, your OS/400
system must be configured for you to be able to enter the euro symbol
from your terminal.
Data entry of the euro currency symbol must be enabled by modifying the
appropriate device descriptions.
Use the OS/400 Change display device command, CHGDEVDSP, to
change the value of the keyboard language type parameter, KBDTYPE,
to one of the new euro keyboard types. This needs to be done for all
locally-attached twinax display devices and all PCs connected to your
AS/400 through the Client Access facility. In addition, some twinax
devices may require hardware upgrades that support these devices. For
more information on euro requirements for twinax devices, contact your
hardware vendor. For more information on euro support for PC devices,
refer to your OS/400 Client Access/400 documentation.
Printing Documents with XDPE/400 (9/2001)
21-20
Resource management
The following table lists only the most common euro keyboard types.
Additional euro keyboard types can be found as follows:
•
For all AS/400 users, refer to the OS/400 Roadmap to Euro Support
at this URL: http://www.as400.ibm.com/euro/roadmap.htm
•
For AS/400 users running OS/400 4.5.0 or higher, refer to the update
to the OS/400 Roadmap to Euro Support at this URL:
http://www.as400.ibm.com/euro/support.htm
The keystroke combination for the euro currency symbol, €, is Alt+e.
Euro keyboard type
Country
AGE
Austria/Germany
BLM
Belgium Multinational
BRE
Brazilian Portuguese
CAM
Canadian French Multinational
DME
Denmark
FAE
France (azerty)
FNE
Finland/Sweden
ICE
Iceland
ITE
Italian
NEE
Netherlands
NWE
Norway
PRE
Portugal
SFM
Switzerland/French Multinational
SGM
Switzerland/German Multinational
SPE
Spain
SSE
Spanish speaking
SWE
Sweden
UKE
United Kingdom
USE
United States/Canada
Printing Documents with XDPE/400 (9/2001)
21-21
Resource management
Printer file configuration
For the euro currency symbol to be supported in spool files created with
your print data, you must configure your printer files to handle euro
characters. You can configure your printer files in one of two ways:
•
By specifying the name of a euro-supported code page and
character set in your printer file
•
Setting the AS/400 System value to use a specified euro code page
and character set and specifying the System special value
(*SYSVAL) in your printer file
Choose the method you want to use; each method is described in the
following sections.
The character set for the euro currency symbol is 695 for the euro code
pages in the following table. The table lists only the most common euro
code page values. Additional PCL euro code pages and character sets
can be found as follows:
•
For all AS/400 users, refer to the OS/400 Roadmap to Euro Support
at URL: http://www.as400.ibm.com/euro/roadmap.htm
•
For AS/400 users running OS/400 4.5.0 or higher, refer to the update
to the OS/400 Roadmap to Euro Support at URL:
http://www.as400.ibm.com/euro/support.htm
Euro code page
Country
1140
United States, Canada, Netherlands,
Portugal, Brazil, Australia, New Zealand
1141
Austria, Germany
1142
Denmark, Norway
1143
Finland, Sweden
1144
Italy
1145
Spain, Latin America (Spanish)
1146
United Kingdom
1147
France
1148
Belgium, Canada, Switzerland
1149
Iceland
Printing Documents with XDPE/400 (9/2001)
21-22
Resource management
Specifying the name of a code page and character set
The printer file used to create a spool file with the euro currency symbol
must specify both an EBCDIC code page and a character set that support
the euro currency symbol.
The EBCDIC code page value specified in the printer file must be
compatible with the selected euro keyboard type that was used to create
the data. This applies to all user-created printer files, OS/400 printer files
such as QSYS/QSYSPRT, and printer files included in your applications
by the application software vendors.
Change the Character identifier (CHRID) parameter in your printer file to
reflect the appropriate euro code page and character set. Do this for each
printer file that requires the euro currency symbol. Refer to chapter 10 for
information on modifying your printer files.
Using *SYSVAL to specify the code page and character
set
Follow these steps to set the AS/400 System value to use a specified euro
code page and character set:
Step 1.
Use the Change System Value command, CHGSYSVAL, to enter a new
system value of QCHRID.
Step 2.
Set QCHRID to the appropriate euro code page and character set values.
Step 3.
Specify *SYSVAL for the Character identifier (CHRID) parameter in your
printer file to indicate that you want to use the System value to determine
the code page and character set values. Repeat this step for each printer
file using the euro currency symbol.
Printing Documents with XDPE/400 (9/2001)
21-23
Resource management
XDPE/400 and your Xerox PCL printer
This section describes the procedures for configuring XDPE/400 and your
printer to use euro fonts. How you configure XDPE/400 and your printer
depends on how your printer handles fonts. Xerox N32, N24, and NPS
printers support resident euro fonts, while all other Xerox PCL printers
only support downloadable euro fonts. Procedures for each type of printer
are listed below.
Printer resident fonts
The N32, N24, and NPS PCL printers support printer resident euro fonts.
To enable XDPE/400 to use printer resident euro fonts, follow these
steps.
Step 1.
Verify that your printer is at the required software version. See the “Printer
requirements” section in chapter 4 of Section Two: Installing and
Customizing XDPE/400 for the printer software versions required for
printer resident euro fonts.
Step 2.
Ensure that your applications use XDPE/400 with *COMBINED or
*DIRECT mode.
Step 3.
Create a PCL packet specifying *EURO1, *EURO2, or *EURO3 for the
Symbol Set attribute of the Font selection by attributes (FONT) packet
parameter. For more information on PCL symbol sets that contain the
euro currency symbol, see the PCL 5 Comparison Guide or refer to
Hewlett Packard C4210A Developer's Reference Guide at URL:
http://www.hp.com/pond/euro/indexes/dimm.html
NOTE: The symbol set for the font selected must be compatible with
the EBCDIC code page specified in the printer file and the selected
euro keyboard type.
Step 4.
Specify *EURODFT for the Workstation customizing object (WSCST)
Monitor Queue parameter. *EURODFT uses one of the euro-capable PCL
default workstation customizing objects and ASCII code pages in the
XDPE/400 application library. The ASCII code pages can be found in the
SAMPLE file in member EWSCSTxxxx at tag :DFTASCCP.
NOTE: The ASCII code page must be compatible with the font symbol
set, the EBCDIC code page specified in the printer file, and the
selected euro keyboard type.
Printing Documents with XDPE/400 (9/2001)
21-24
Resource management
Downloaded fonts
Follow these steps for all Xerox PCL printers that support downloadable
fonts.
Step 1.
Ensure that your applications use XDPE/400 with *COMBINED or
*DIRECT mode.
Step 2.
Use the Download PCL Fonts Resource (DNLDPCLFNT) command to
download the PCL euro fonts to your printer.
NOTE: The font selected must be compatible with the EBCDIC code
page specified in the printer file and the selected euro keyboard type.
or
Add the PCL euro fonts to your Xerox resource list(s). Refer to chapter 22
for more information.
Step 3.
Create a PCL packet specifying either the font ID number of the
downloaded font for the Page font selection by ID (FONTID) packet
parameter or the font name of the downloaded font for the Font selection
by alphanumeric font name (FONTNAME) packet parameter.
Step 4.
Specify *EURODFT for the Workstation customizing object (WSCST)
Monitor Queue parameter. *EURODFT uses one of the euro-capable PCL
default workstation customizing objects and ASCII code pages in the
XDPE/400 application library. The ASCII code pages can be found in the
SAMPLE file in member EWSCSTxxxx at tag :DFTASCCP.
NOTE: The ASCII code page must be compatible with the font symbol
set, the EBCDIC code page specified in the printer file, and the
selected euro keyboard type.
Printing Documents with XDPE/400 (9/2001)
21-25
Resource management
Euro font considerations
If you are using multi-up printing and require euro fonts, consider the
following:
•
Multi-up packets can only be used in *DIRECT or *COMBINED
mode.
•
The PC/Support translation table (PCSLIB) global value must specify
an EBCDIC to ASCII translation table that supports the euro
currency symbol.
•
PCSLIB must be compatible with the EBCDIC code page specified in
your printer file.
•
PCSLIB must be compatible with the selected keyboard type.
•
For network printing, PCSLIB must be compatible with the ASCII
code page in the workstation customizing object.
Printing Documents with XDPE/400 (9/2001)
21-26
22.
22
List processing
This chapter shows you how to use the list processing functions of
XDPE/400. List processing allows you to:
•
Download resources
•
Invoke logical processing tests
•
Include generic files
•
Select the mode of printer command generation and the printer
control packet or JDT
NOTE: List processing support of VIPP-enabled printers is limited to
N-series printers. The list processing feature does not support
resource downloads or the use of generic files for DocuSP and NPS
printers in VIPP mode.
A list is a source physical file member that you have converted into an
XDPE/400 resource list using the CRTXRSCLST command. The source
member list contains the names of objects and the subfolders where they
are stored.
Printing Documents with XDPE/400 (9/2001)
22-1
List processing
Creating a list source member
A list starts as a source file member. The record length of the source file
must be 92. A source member record or line contains these items of
information, separated by a slash (/):
•
The name of the directory or subfolder that has the object to be
processed, or the type of printer commands required (also called
packet mode keyword: DJDE, XES, PCL, or JDTLIB)
•
The name of the object (with file extension, if required), or the same
information required in the packet data field of the spool file
attributes
The packet mode keyword is DJDE if the processing mode is XPPM, XES
if the processing mode is XDPM, PCL if the processing mode is for a
Xerox PCL printer, or JDTLIB if the processing mode is VIPP. The packet
flag that indicates the printer command generation type can be a plus sign
(+) for the Combined method, a number sign (#) for the Direct method, or
no prefix (defaults to the Always generate (ALWAYS) Monitor Queue
parameter). The packet name is either XDPE, for Indirect packet
generation, or the name of a printer control packet.
A list can contain a mix of resources, including fonts, forms, and images.
The list can be in any order. The resources that are downloaded are not
necessarily related to the folder with the resource list. All lists used during
Monitor Queue processing must be in the RSCLIST subfolder.
NOTE: Resource downloads are not currently supported by VIPP.
JDTs specified in a list will be called from the JDTLIB subfolder.
Specify resources using uppercase letters only; XDPE/400 recognizes
downloaded resources only in uppercase.
This is an example of a list used to download resources:
FONTS/L0112B.FNT
FONTS/L01233C.FNT
FORMS/INVOICE.FRM
LOGOS/COMPANY.LGO
This is an example of a list used by Monitor Queue to download print
resources, invoke a logical processing test, and print in Indirect mode:
FONTS/L0112B.FNT
FORMS/XVGB.FRM
FORMS/INVOICE.FRM
LPP/TEST05
DJDE/XDPE
This is an example of a list used by Monitor Queue to download print
resources to print in Direct mode:
FONTS/L0112B.FNT
FORMS/XVGB.FRM
FORMS/INVOICE.FRM
DJDE/#JOB1
Printing Documents with XDPE/400 (9/2001)
22-2
List processing
This table shows the objects that can be referenced in a list.
Printer resource
1
Subfolder
Resource file
extension
DJDE fonts
FONTS
FNT
DJDE forms
FORMS
FRM
DJDE images
IMAGES
IMG
DJDE logos
LOGOS
LGO
DJDE FSLs
FSL
FSL
DJDE JDLs
JDL
JDL
DJDE JSLs
JSL
JSL
DJDE packet
DJDE
No extension
XES fonts
XESFONTS
FNT
XES forms
XESFORMS
FRM
XES packet
XES
No extension
XES generic packet
GENXES
Optional
PCL fonts
PCLFONTS
FLJ
PCL macros
PCLMAC
No extension
PCL packet
PCL
No extension
PCL generic packet
GENPCL
Optional
VIPP encoding tables
ENCODING
Optional
VIPP fonts
MISLIB
Optional
VIPP forms
FORMLIB
Optional
VIPP images
IMGLIB
Optional
VIPP JDT packet
JDTLIB
No extension 1
Logical processing packet
LPP
No extension
XDPE/400 automatically adds an extension of .JDT to all VIPP JDT packet
names.
These resources must be on the AS/400 in the appropriate XDPEFLR
subfolder. Use the PC Support facility to copy resources that are on a PC
to the AS/400.
Use standard OS/400 commands to access the XDPEFLR folder and read
it directly. Each type of resource is stored in a separate subfolder. Place
objects in the subfolders by copying them from either an AS/400 database
file or from a PC directory.
Printing Documents with XDPE/400 (9/2001)
22-3
List processing
Creating a Xerox resource list
Follow these steps to create a resource list for XDPE/400:
Step 1.
Use the OS/400 Source Entry Utility (SEU) editor to create a file of
resources.
The record length of the source file must be 92 characters. Make sure
there are no blanks before the first nonblank character of each list entry,
and no embedded blanks in the list. Delete all null, nonlist records from
the file.
Step 2.
Enter CRTXRSCLST and press F4. The Create Xerox Resource List
menu displays, as shown on the next page.
Step 3.
Enter the appropriate option for each field, following the conventions
described in the next section, and press ENTER.
Create Xerox Resource List (CRTXRSCLST)
Type choices, press Enter.
Source file . . . . . . . .
Library . . . . . . . . .
Source member . . . . . . .
List name . . . . . . . . .
Folder . . . . . . . . . . . *RSCLIST
Name
Name
Name
Character value
Name, *COLOR, *DJDE...
Bottom
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
Printing Documents with XDPE/400 (9/2001)
F12=Cancel
F13=How to use this display
22-4
List processing
Parameters
Source file (SRCFILE)
Library
Source member (SRCMBR)
List name (LIST)
Folder (FLR)
Specifies the name of the source file that contains the file member used
to create the resource list.
Specifies the name of the library that contains the source file.
Specifies the file member that contains the prototypical resource list. The
contents of this member are used to create the object form of the resource
list.
Specifies the eight-character name of the list to create.
Specifies the subfolder in XDPEFLR that contains the resource list. You
can use these subfolders:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
COLOR
DJDE
ENCODING
FONTS
FORMLIB
FORMS
FSL
GENPCL
GENXES
IMAGES
IMGLIB
JDL
JDTLIB
JSL
•
•
•
•
•
•
•
•
•
•
•
•
•
LOGOS
LPP
MISLIB
PCL
PCLFONTS
PLCMAC
PCLMUP
PDL
RSCLIST
XES
XESFONTS
XESFORMS
XESMUP
If the resource list is used by Monitor Queue, it must be in the RSCLIST
subfolder. If the resource list is used by the WRKXRSC/DNLDxxxRSC
command, it must be stored in the subfolder specified in the resource field
of the download list.
Printing Documents with XDPE/400 (9/2001)
22-5
List processing
Configuring a list processing job
You can specify a list using these methods:
•
As the resource name in a DNLDxxxRSC command
•
As a packet name in the packet data field in the spool file attributes
of a job printed by Monitor Queue
•
In an XES or Xerox PCL packet
To use a list in a DNLDxxxRSC command, enter the list file name,
preceded by an at sign (@) in the resource file name. The download
command processes the list.
To use list processing as part of printing a job, perform one of these
options:
•
Use the IBM CHGPRTF command to specify the list file name,
including the at sign (@) prefix, in the packet data field; use this
format:
@list-name
•
For XES or PCL processing, use one of these XDPE/400 commands
to specify the list file name in the Resource list name (RSCLIST)
parameter.
—
—
—
—
CRTXES
CHGXES
CRTXPCL
CHGXPCL
Printing Documents with XDPE/400 (9/2001)
22-6
List processing
Example of using list processing to download resources
This example describes how to use list processing to download resources
to a 4090 printer.
Creating a source list of resources
Use the standard AS/400 SEU editor to create a source list containing
these entries:
FORMS/INVOICE.FRM
FORMS/STMT1.FRM
FORMS/STMT2.FRM
FORMS/STMT3.FRM
FORMS/EOMRPT.FRM
LOGOS/COMPANY.LGO
Save the list as member ACCTFRMS in file LISTS of library XEROX.
Creating a Xerox resource list
Create a Xerox resource list using this procedure:
Step 1.
Sign on and, if necessary, add the XDPE/400 application library to the
library list for your user profile.
Step 2.
Enter CRTXRSCLST at any OS/400 command prompt and press ENTER.
The Create Xerox Resource List menu appears, as shown on the next
page.
Step 3.
Enter LISTS as the name of the resource list source file you have created.
Step 4.
Enter XEROX as the name of the library in which the source file resides.
Step 5.
Enter ACCTFRMS as the name of the source member that contains the
specific list you want to place in the XDPEFLR subfolder.
Step 6.
Place the list you create in any subfolder of XDPEFLR. The subfolder you
use determines which downloading program you will use to download the
resources.
Since the resources in this example are primarily forms, store the list of
resource names in the FORMS subfolder of XDPEFLR, by entering
*FORMS.
Printing Documents with XDPE/400 (9/2001)
22-7
List processing
Step 7.
Enter ACCTFRMS as the name for the list file within the XDPEFLR
subfolder.
Since the source file name in the example is only 8 characters, use that
for the name of the list within the FORMS subfolder of XDPEFLR.
Step 8.
Press ENTER.
Create Xerox Resource List (CRTXRSLST)
Type choices, press Enter.
Source file. .
Library . .
Source member.
List name. . .
Folder . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*RSCLIST
Name
Name
Name
Character value
Name, *COLOR, *DJDE...
Bottom
F3=Exit
F4=Prompt
F24=More keys
F5=Refresh
Printing Documents with XDPE/400 (9/2001)
F12=Cancel
F13=How to use this display
22-8
List processing
Downloading the resources
Since the resource list is stored in the FORMS subfolder of XDPEFLR,
you must use the forms downloading command to download the
resources listed, as follows:
Step 1.
Start the printer writer for your Xerox 4090, if necessary, against the
output queue to which you will send the listed resources for downloading.
If there is a Monitor Queue session already started for the 4090 printer,
you can direct the output of the resource downloader to that output queue.
Step 2.
Access the XDPE/400-supplied Download Form Resource menu using
one of these methods:
•
Enter WRKXRSC at any OS/400 command prompt and select 2 from
the menu of downloading options.
•
Enter DNLDFRMRSC at any OS/400 command prompt.
Download Form Resource (DNLDFRMRSC)
Type choices, press Enter.
Font file name
Output queue .
Library . .
Interface type
Printer model
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Name, F4 for list
Name
Name
*FLEX, *USAII, *SOLIMAR...
4050, 4090, 4135, 4235...
.
.
.
.
.
Bottom
F3=Exit
F4=Prompt
F24=More keys
F5=Refresh
F12=Cancel
F13=How to use this display
Step 3.
Enter @ACCTFRMS as the list file name in the Form file name parameter.
Step 4.
Enter the name of the output queue to which the 4090 printer is attached
(either directly or through Monitor Queue).
Step 5.
Enter the name of the library in which the output queue resides.
Step 6.
Enter the model number of the Xerox printer to which you are downloading
the resource.
Printing Documents with XDPE/400 (9/2001)
22-9
List processing
Step 7.
Enter the name or type of interface that attaches the printer to the AS/400.
Step 8.
Press ENTER.
XDPE/400 creates a spool file containing the listed resources and the
appropriate printer control commands to direct the 4090 printer to store
them on one of its system disks. The printer writer (or Monitor Queue)
processes this spool file and sends the data to the printer.
Multiple printer list support
XDPE/400 allows you to create a resource list that you can send to
different types of printers. You can use a resource list that contains
references to both XPPM and XDPM resources and send resources to
both types of printers. You enable this feature with the Multiple-printer
resource list (MPRLST) global value.
If MPRLST is *NO, XDPE/400 checks the resource download list for
resource types that are incompatible with the printer mode being used. If
XDPE/400 finds an incompatible resource, that resource is ignored.
If the resource list is used by Monitor Queue, the printer mode is
determined by the Printer mode (MODE) Monitor Queue parameter. If the
resource list is used by a download CL command, the printer mode is
determined by the name of the folder with the resource list.
For example, if the resource list is in the XDPEFLR/FONTS folder, the
printer mode is assumed to be XPPM. If the resource list is in the
XDPEFLR/XESFONTS folder, the printer mode is assumed to be XDPM.
If MPRLST is *YES, XDPE/400 creates resource lists without examining
the printer mode.
Printing Documents with XDPE/400 (9/2001)
22-10
List processing
Downloading PCL fonts and macros using a resource list
PCL fonts and macros downloaded using a resource list are sequentially
numbered starting with 8000. When assigning ID numbers, only fonts and
macros are counted in the resource list. The following sample resource
list demonstrates this numbering method.
Resource
Font ID
PCLFONTS/FONT1.FLJ
8000
Macro ID
PCL/PCLPKT
PCLMAC/FORM1
PCLFONTS/FONT2.FLJ
PCLMAC/FORM2
8001
8002
8003
LPP/LPPPKT
Note that subsequent Monitor Queue resource list downloads will
overwrite like-numbered macros from previous jobs.
Printing Documents with XDPE/400 (9/2001)
22-11
List processing
Printing Documents with XDPE/400 (9/2001)
22-12
23.
23
Logical processing
This chapter describes how to create and use logical processing packets.
With logical processing, you can search print data for specific text strings.
You can use the detection of these text strings to control the insertion of
printer control packets into the print data stream. For example, printer
control packets can change:
•
•
•
Format information
Page orientation from landscape to portrait
Forms on a page-to-page basis
NOTE: When running in VIPP mode, XDPE/400 only identifies the
name of the JDT to be used by the printer for the data stream;
XDPE/400 does not insert the contents of the JDT into the data
stream. To be used by the printer, all VIPP resources, including JDTs,
must be resident on the printer controller.
Logical processing is controlled by logical processing packets (LPP). The
use of logical processing packets is specified by list processing. For more
information on list processing, see chapter 22.
Whenever list processing encounters a list record with a type of LPP
entry, the name portion of the record is assumed to be an LPP name, and
a logical processing test is created from the specified logical processing
packet.
Each logical processing packet defines test criteria and a processing
action. The information you specify with the Create a Xerox LPP
(CRTXLPP) command defines a test. Figure 23-1 shows the information
you specify to define the test criteria.
The test compares the data that you specified in the logical processing
packet with the data in the print data stream. This test process results in
a true test or a false test.
Whether a test is true or false depends on the selected values (*CHANGE
and *MATCH) of the Test type (TYPE) parameter, the selected values of
the Test expression (EXPRESSION) parameter, and the contents of the
print data stream.
Printing Documents with XDPE/400 (9/2001)
23-1
Logical processing
Figure 23-1. Test information
Create a Xerox LPP (CRTXLPP)
Type choices, press Enter.
Information
that specifies
how to test.
Information
that specifies
where to test.
Information
that specifies
what to do if
the test packet
is true.
Logical processing packet name
Test type . . . . . . . . . .
Test expression . . . . . . .
Test string . . . . . . . . .
Test position . . . . . . . .
Test page range:
starting page . . . . . .
ending page . . . . . . .
Line range:
starting line . . . . . .
ending line . . . . . . .
When to apply . . . . . . . .
Application duration . . . .
Printer control packet name .
Text ’description’ . . . . .
*MATCH_
*EQ
Name, F4 for list
*MATCH, *CHANGE
*EQ, *NE
*ALL
1-256, *ALL
*FIRST
*END_
1-1000000000, *FIRST
1-1000000000, *END
*FIRST
*END
*TOP
*ONCE
1-256, *FIRST
1-256, *END
*TOP, *BOTTOM
*ONCE, *CONT
Character value
*BLANK
Bottom
F3=Exit F4=Prompt
F24=More keys
*CHANGE value
F5=Refresh
F12=Cancel
F13=How to use this display
A test is true if you selected *CHANGE as the Test type (TYPE) parameter
and the Test string is not the same as the print data. When a test is true,
the print data tested is used to replace the contents of the Test string.
A test is false if you selected *CHANGE as the Test type (TYPE)
parameter and the print data is the same as the Test string.
*MATCH value
A test is true if these conditions occur:
•
The print data is the same as Test string, and the value of the Test
expression (EXPRESSION) parameter is *EQ.
•
The print data is not the same as the Test string, and the selected
value of the Test expression parameter is *NE.
A test is false if these conditions occur:
•
The print data is not the same as the Test string, and the value of the
Test expression (EXPRESSION) parameter is *EQ.
•
The print data is the same as the Test string, and the selected value
of the Test expression parameter is *NE.
Whenever a true test occurs, the printer control packet specified by the
Printer control packet name (PACKET) parameter is retrieved from the
appropriate DJDE, XES, or PCL subfolder in the XDPEFLR folder. Only
two printer control packets can be inserted on each logical page: one for
the top processing and one for the bottom processing. Refer to appendix
C for additional logical processing notes.
Printing Documents with XDPE/400 (9/2001)
23-2
Logical processing
Logical processing considerations
This section describes the considerations and restrictions that apply to
logical processing.
Refer to appendix C for information on the use of SCS commands and
logical processing.
Restarting a PCL constant back print job
When restarting a print job with constant back pages, you must change
the Starting page and Ending page subparameter values specified for the
Test page range (PAGERANGE) parameter to match the Starting page
subparameter value specified for the Page range to print (PAGERANGE)
spool file attribute. Once the job has finished reprinting, the Starting page
and Ending page subparameter values specified for the Test page range
(PAGERANGE) parameter must be changed back to 1 and 1,
respectively.
For example, if the Starting page and Ending page subparameters for the
Page range to print (PAGERANGE) spool file attribute are set to 2 and 5,
respectively, then the Starting page and Ending page subparameters for
the Test page range (PAGERANGE) parameter must be set to 2 and 2,
respectively. The Ending page subparameter for the Page range to print
(PAGERANGE) spool file attribute does not affect constant back page
processing.
Logical processing considerations and restrictions
These LPP considerations and restrictions apply:
•
Logical processing is not supported when the Always generate
(ALWAYS) Monitor Queue parameter is set to *INDIRECT.
•
You can use logical processing only if the File processing mode
(PROCMODE) Monitor Queue parameter is *AUTO or *PAGE.
•
You cannot use logical processing when you are using multi-up
printing on printers that support XES or PCL.
•
Multi-up printing on printers that support VIPP is controlled by the
JDT and can be used with logical processing.
•
Multi-up printing on printers that support DJDEs is controlled by the
JSL and can be used with logical processing. If an LPP results in a
DJDE being inserted into the middle of a logical page, an error will
occur.
NOTE: When using multi-up printing, true logical processing
tests cause printer control packets to be inserted into the print
data stream at the end of logical pages. This can also result in
printer control packets being inserted in the middle of a physical
page.
Printing Documents with XDPE/400 (9/2001)
23-3
Logical processing
•
When the page test range of an LPP is before the current page of the
spooled file that is being processed, the LPP is removed from the list
of LPPs being processed. The LPP is deleted and is not referenced
again.
•
Only the first occurrence of a true LPP test, one for top and one for
bottom processing, is tested on a page. Once a true test is
encountered for that page, one for top processing and one for
bottom processing, it is not tested again. The LPP tests will continue
on the next page.
•
When printing XES jobs, you cannot specify that a generic packet be
inserted at the bottom of a page.
•
If a logical processing test includes *ONCE as the application
duration and you are calling a PCL packet containing a macro, you
should specify *CALL rather than *OVERLAY for PCL macro
(PCLMAC) PCL packet parameter. When you use *OVERLAY, the
macro is continuously used.
•
For DJDE, XES, and PCL jobs, do not use COPIES in a packet
called as a result of a logical processing test. Logical processing
tests page by page; the COPIES printer control command is effective
only at the job level.
•
When a value other than 1 to *END is specified for the Page range to
print attribute of a spool file, the corresponding change may need to
be made to the logical processing packet.
Printing Documents with XDPE/400 (9/2001)
23-4
Logical processing
Duplex printing
Some printer control commands may cause a duplex print job to print in
simplex when inserted as part of a true logical processing test where
*ONCE is specified for the Application duration (DURATION) logical
processing packet parameter. Table 23-1 lists the DJDE, XES, and PCL
packet parameters that may cause this to occur. Refer to chapter 26 for
information on the VIPP packet parameters that may cause this same
problem to occur.
Table 23-1.
DJDE, XES, and PCL packet parameters that affect duplex printing
Printer mode
DJDE
XES
XES (4235 printer)
PCL
Parameter name
Parameter value(s)
SPECIAL back form name (BFORM)
All values
Number of copies to print (COPIES)
All values
Print on both sides of sheet (DUPLEX)
*NO
Bin selection (FEED)
All values
Printer job name (JDE)
All values
Printer job library (JDL)
All values
Distribution text (RTEXT)
All values
Print on both sides of sheet (DUPLEX)
*NO, *YES, *TUMBLE
Source tray (TRAY)
All values
4235 page format (FORMAT)
2-9
Print on both sides of sheet (DUPLEX)
*NO
Source tray (TRAY)
*TRAY2, *TRAY3, *TRAY4
Source tray (TRAY)
All values
Page orientation (ORIENT)
All values
Margin setting: Page size (MARGIN)
All values
Duplex side (DSIDE)
*FRONT, *BACK
Printing Documents with XDPE/400 (9/2001)
23-5
Logical processing
Placement of XES forms
XES forms are indexed by XDPE/400 and your XES printer to allow the
use of multiple forms during a job. How forms are indexed can determine
how they are placed in a job. The logical processing feature of XDPE/400
allows you to control when and where a printer control packet is applied
using the When to apply (WHEN) parameter. This parameter also affects
the indexing and placement of forms:
•
An XES form applied as part of an XES packet or from printer file
parameters is assigned an index number of “1”. A form applied to the
top of a page (*TOP) by a logical processing test also assumes the
index number of “1” and replaces any previous form with an index of
“1”.
•
A form applied at the bottom of a page (*BOTTOM) by a logical
processing test assumes an index number of “2” and will be placed
on the next page regardless of any other forms that may already be
placed on that page.
For more information about form indexing on XES printers, see the
documentation supplied with your XES printer.
Performance considerations
When you specify logical processing, every print line on every page that
is specified in a logical processing test is tested until a true test condition
is met. This can consume greater than normal amounts of processor time.
By restricting the amount of data in the test range by using the Test
position, Test page range, and Line range parameters, processing time
can be greatly reduced. Full pages that are outside the test range are
skipped without being tested. Data in partially-skipped pages is skipped
on a character-by-character basis.
Printing Documents with XDPE/400 (9/2001)
23-6
Logical processing
Creating logical processing packets
This section describes how to create logical processing packets using the
Create a Xerox LPP (CRTXLPP) command.
Packet name syntax
Logical processing packet names must comply with these syntax rules:
•
The name can be from one to eight bytes long
•
The first byte of the name must be A-Z or 0-9
•
Bytes two through eight can be A-Z, 0-9, @, #, or $
•
Do not enclose the name within quotes or other characters
NOTE: If you enter lowercase letters, the AS/400 system changes
them to uppercase letters.
Printing Documents with XDPE/400 (9/2001)
23-7
Logical processing
Packet creation procedure
Follow these steps to create a logical processing packet:
Step 1.
Enter CRTXLPP and press ENTER. The Create a Xerox LPP menu
displays.
Create a Xerox LPP (CRTXLPP)
Type choices, press Enter.
Logical processing packet name
Test type . . . . . . . . . . .
*MATCH_
Name, F4 for list
*MATCH, *CHANGE
Bottom
F3=Exit F4=Prompt
F24=More keys
Step 2.
F5=Refresh
F12=Cancel
F13=How to use this display
Enter the name of the logical processing packet and the Test type, and
press ENTER. The Create a Xerox LPP menu displays additional
parameters.
Printing Documents with XDPE/400 (9/2001)
23-8
Logical processing
Step 3.
Modify the parameters you want, following the conventions described in
the next section, and press ENTER.
Create a Xerox LPP (CRTXLPP)
Type choices, press Enter.
Logical processing packet name
Test type . . . . . . . . . .
Test expression . . . . . . .
Test string . . . . . . . . .
Test position . . . . . . . .
Test page range:
starting page . . . . . .
ending page . . . . . . .
Line range:
starting line . . . . . .
ending line . . . . . . .
When to apply . . . . . . . .
Application duration . . . .
Printer control packet name .
Text ’description’ . . . . .
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
*MATCH
*EQ
Name, F4 for list
*MATCH, *CHANGE
*EQ, *NE
*ALL
1-256, *ALL
*FIRST
*END
1-1000000000, *FIRST
1-1000000000, *END
*FIRST
*END
*TOP
*ONCE
1-256, *FIRST
1-256, *END
*TOP, *BOTTOM
*ONCE, *CONT
Character value
*BLANK
F12=Cancel
Bottom
F13=How to use this display
Packet parameters
Logical processing packet
name (LPP)
Specifies the name of the logical processing test packet to be created.
The logical processing packet is stored in the XDPEFLR/LPP folder. The
logical processing packet name can be from one to eight characters in
length.
Test type (TYPE)
Specifies the type of criteria to apply when searching for strings. The
result of a string comparison, the Test type, and the Test expression
determines if a logical processing test is true. You can use these values:
•
*MATCH — Uses the Test expression parameter to determine the
type of test to be performed.
•
*CHANGE — Specifies that the comparison is true if the string being
tested is different from the Test string. Each time a string tests true,
the value of the string that tested true is picked up by the Test string,
and is used for testing until the next true test is encountered. If the
string that is currently being tested in the print data stream is shorter
than the Test string in the logical processing packet, the print data
stream string is extended with blanks until the strings are the same
length.
See table 23-2 for the results of each type of test.
Printing Documents with XDPE/400 (9/2001)
23-9
Logical processing
Test expression
(EXPRESSION)
Specifies how to evaluate a string comparison. The Test expression
parameter is not used if the Test type parameter is *CHANGE. You can
use these values:
•
*EQ — Specifies that the LPP test is true if the test string is equal to
the comparison string in the spool file. Otherwise, the test is false.
•
*NE — Specifies that the LPP test is true if the test string is not
equal to the comparison string in the spool file. Otherwise, the test is
false.
Table 23-2 shows the result of a test for both the Test type and Test
expression parameters. If the test is true, the printer control packet is
applied to the page. If the test is not true, the printer control packet is not
applied to the page.
Table 23-2.
Test type
*CHANGE
*MATCH
Test string (STRING)
Test position (POSITION)
Test page range
(PAGERANGE)
Test results
Test
expression
Strings
equal
Strings not
equal
n/a
False
True
*EQ
True
False
*NE
False
True
Identifies the test string used in the test. The string can range from 1 to
32 characters in length and can include hexadecimal digits. For
*CHANGE, the initial string used for the change comparison is the LPP
test string.
Tests the character position within lines that are being processed. You
can use these values:
•
*ALL — Specifies that every character position is checked
•
1-256 — Specifies the character position of the first character to be
tested
Specifies the set of pages in the print job to be tested. The starting page
specifies which page is tested first. If the starting page specified is larger
than the number of pages in the job, no pages are tested. The ending
page specifies which page is tested last. Full pages that are outside the
test range are skipped without being tested.
You can use these values for the starting page subparameter:
•
*FIRST — Specifies that the test begins on the first page in the spool
file
•
1-1000000000 — Specifies the page where the text begins
You can use these values for the ending page subparameter:
•
*END — Specifies that the test begins on the last page of the spool
file to be tested
•
1-1000000000 — Specifies the page where the text ends
Printing Documents with XDPE/400 (9/2001)
23-10
Logical processing
Line range (LINERANGE)
Specifies the set of lines on each page to test. You can use these values
for the starting line subparameter:
•
*FIRST — Specifies that the test starts on the first line of each page
•
1-256 — Specifies a specific line where the test will start
You can use these values for the ending line subparameter:
•
*END — Specifies that the test ends on the last line of each page
•
1-256 — Specifies a specific line where the test will end
NOTE: For logical processing jobs, the Overflow line number
(OVRFLW) printer file parameter must be greater than or equal to the
ending line subparameter of the Line range (LINERANGE) logical
processing packet parameter.
When to apply (WHEN)
Application duration
(DURATION)
Specifies when and where to insert the printer control packet. You can use
these values:
•
*TOP — Inserts a printer control packet before the first character on
the first line of the page
•
*BOTTOM — Inserts a printer control packet after the last character
on the last line of the page; not supported for VIPP mode
Indicates how many times a specified printer control packet is applied in
a print data stream. You can specify one of these values:
•
*ONCE — Applies a specified printer control packet to the page
where the test was true. After the application of the packet, the print
environment that existed at the beginning of the job is restored.
If you use *ONCE, the options in the printer control packet are applied
to the page where the test was true. XDPE/400 then resets the job by
reinserting the original job level commands into the data stream. If
you have invoked an option through a printer control packet that did
not have a value set at the job level, the option is not turned off at the
job reset, but is carried forward to all pages in the job.
Printing Documents with XDPE/400 (9/2001)
23-11
Logical processing
To use *ONCE effectively, you should create a reset printer control
packet at the job level that contains all the values you want applied to
the job at reset. This makes all options in the printer control packet
called by the LPP subordinate to the reset packet at the time of reset.
For example, the LPP printer control packet may make XDPE/400
change to landscape orientation for one page of the job. To change
back to portrait orientation at job reset, the reset printer control
packet must specify this value. These steps describe how to create
and implement this reset packet:
•
Packet control packet name
(PACKET)
1.
Note all values in the XES or PCL packet specified for *ONCE
invocation by the LPP packet.
2.
Create an XES or PCL packet containing the values you would
like to change at reset.
3.
Add this reset packet to the resource list used to invoke the LPP
packet.
*CONT — Applies a specified printer control packet to the page
where the test was true and to all subsequent pages until another
packet is invoked due to a successful logical processing test or until
the end of the job. If a subsequent printer control packet is
processed, it replaces any previous *CONT packet.
Specifies the name of the printer control packet to insert into the print data
stream.
When specifying the name of a VIPP JDT packet, type in the packet name
without an extension. XDPE/400 automatically adds an extension of .JDT
to all JDT packet names. Note that XDPE/400 only identifies the name of
the JDT to be used by the printer for the data stream; XDPE/400 does not
insert the contents of the JDT into the data stream. To be used by the
printer, all VIPP resources, including JDTs, must be resident on the
printer controller.
Text ‘description’ (TEXT)
Lets you enter descriptive text that is stored with the logical processing
packet. This field is for user information only. You can use these values:
•
*BLANK — Specifies that no text is saved.
•
text — Allows you to specify a character string from 1 to 40
characters, enclosed within quotes.
Printing Documents with XDPE/400 (9/2001)
23-12
Logical processing
Changing logical processing packets
Follow these steps to change a logical processing packet:
Step 1.
Enter CHGXLPP and press ENTER. The Change a Xerox LPP menu
displays.
Change a Xerox LPP (CHGXLPP)
Type choices, press Enter.
Name, F4 for list
Logical processing packet name:
Bottom
F3=Exit F4=Prompt
F24=More keys
Step 2.
F5=Refresh
F12=Cancel
F13=How to use this display
Enter the name of the logical processing packet, and press ENTER. The
Change a Xerox LPP menu displays the parameters for the specified
logical processing packet.
Printing Documents with XDPE/400 (9/2001)
23-13
Logical processing
Step 3.
Modify the parameters you want and press ENTER. Refer to “Packet
parameters” for more information.
Change a Xerox LPP (CHGXLPP)
Type choices, press Enter.
Logical processing packet name
Test type . . . . . . . . . .
Test expression . . . . . . .
Test string . . . . . . . . .
Test position . . . . . . . .
Test page range:
starting page . . . . . . .
ending page . . . . . . . .
Line range:
starting line . . . . . . .
ending line . . . . . . . .
When to apply . . . . . . . .
Application duration . . . .
Printer control packet name .
Text ’description’ . . . . .
*SAME
*SAME
*SAME
*SAME
Name, F4 for list
*MATCH, *CHANGE, *SAME
*EQ, *NE, *SAME
1-256, *ALL, *SAME
*SAME
*SAME
1-1000000000, *FIRST, *SAME
1-1000000000, *END, *SAME
*SAME
*SAME
*SAME
*SAME
*SAME
*SAME
1-256, *FIRST, *SAME
1-256, *END, *SAME
*TOP, *BOTTOM, *SAME
*ONCE, *CONT, *SAME
Character value, *SAME
Bottom
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
Printing Documents with XDPE/400 (9/2001)
F12=Cancel
F13=How to use this display
23-14
Logical processing
Starting logical processing
Follow these steps to start logical processing:
Step 1.
Log on to the system.
Step 2.
Add XDPE/400 to the library list.
Step 3.
Create a logical processing packet.
Step 4.
Create a resource download or processing record list file. Using the
AS/400 SEU editor, create a resource record list file that includes the
logical processing packet entry to be used when processing this print job
(for example, LPP/name of your logical processing packet).
Step 5.
Convert the resource record list file that you created in step 4 into the
appropriate format to be used as a download or processing list. Enter this
command:
CRTXRSCLST
Refer to chapter 22 for more information on list processing.
Step 6.
Enable the list process by entering the at sign (@) in the Packet field of
the spool file to be printed, followed by the name of the list.
NOTE: For logical processing jobs, the Overflow line number
(OVRFLW) printer file parameter must be greater than or equal to the
ending line subparameter of the Line range (LINERANGE) logical
processing packet parameter.
Step 7.
Start Monitor Queue, with this parameter selected:
File processing mode: *PAGE
Select other options that are appropriate for your requirements.
Step 8.
Release the spooled file for printing.
To print your job, you must change the status from hold (*HLD) to ready
(*RDY). To do this, enter 6 in the Option field of the spool file, and press
ENTER.
When Monitor Queue processes the spool file, tests that are specified by
the logical processing packets will begin. If any true test conditions are
encountered, printer control packets are inserted into the print data
stream.
Printing Documents with XDPE/400 (9/2001)
23-15
Logical processing
Printing Documents with XDPE/400 (9/2001)
23-16
24.
24
Multi-part printing
This chapter describes multi-part printing, the XDPE/400 function that
allows you to combine the features of high-quality laser output and the
merging of electronic forms to create multi-part forms.
Traditionally, multiple-part forms, such as invoices or sales orders, were
printed on preprinted multi-part form stock using impact printers. Since
the actual printing was done with impact printers, all parts of the form were
printed at the same time, although not with the same clarity or intensity as
the top part. If you needed additional copies of each part of the form, you
had to separate the parts and photocopy them.
While laser printers can only print one page at a time, each part of a
multiple-part form is produced with the same clarity and quality as the first
part. Using XDPE/400, you can merge text with electronic forms.
Each part of the multi-part job can be can be generated using different
printer control packets and different methods of command generation. In
addition, each part of the multi-part job can be sent to a specific output
queue.
Printing Documents with XDPE/400 (9/2001)
24-1
Multi-part printing
Figure 24-1 provides an example of how XDPE/400 processes a
multi-part job.
Figure 24-1. Sample XDPE/400 multi-part job
You create a complete spool file in its self-contained environment for each
part of the form. In this sample three-part customer order form, each part
of the form is used for a specific purpose:
•
•
•
The first part is used in the sales department
The second part is used in the shipping department
The third part is sent to the customer
In this example, the spool file contained order data for two different
customer orders. There are two pages in the spool file, one for each
customer order. The first time the spool file is processed, part 1 for each
of the two orders is printed on a printer in the sales department. The
second time the spool file is processed for part 2, the same data is used,
but printed on a different form by a printer in the shipping department. Part
3 is printed using the same data, but on a printer using special stock for
the customer copies.
Printing Documents with XDPE/400 (9/2001)
24-2
Multi-part printing
Creating a multi-part packet
It is recommended that you create your multi-part packets using CL
programs. Using this method, if you wish to change a multi-part packet,
you can simply change the CL program you used to create it and run the
program again.
If you do not want to use CL programs to create or change your multi-part
packets, note these considerations for using the Change Multi-part
Packet (CHGXMPT) command:
•
If you change any field of a multi-part packet, you must retype at
least one character in each field of each part.
•
If you change any field of a multi-part packet, and that packet spans
more than one screen, you must retype at least one character in
each field of each part for all of the fields on that screen before
pressing the PAGE UP or PAGE DOWN keys. This must be done for
every screen.
•
If you delete one part of a multi-part packet, you must move all
entries that display below that entry up one level by retyping them.
For example, if you have six parts in a multi-part packet and you
delete the fourth entry, you must retype the fifth entry in the fourth
entry fields, the sixth entry in the fifth entry fields, and delete the
characters on the lines where the sixth entry was.
CAUTION: Failure to follow this procedure can result in the output
queue/library values for each part in the multi-part packet being
replaced by *XDPEQUE and *XDPELIB.
Follow these steps to create a multi-part packet:
Step 1.
Enter CRTXMPT and press ENTER. The Create Multi-part Packet menu
displays.
Printing Documents with XDPE/400 (9/2001)
24-3
Multi-part printing
For multi-part printing, Monitor Queue locates the Multi-part packet name
(XMPT) you enter on this menu, then processes the spool file once for
every packet name you list on this menu for Printer control packet list
(PRTPKT). If an Output queue and Library is specified, XDPE/400 places
the processed spool file in that output queue. If none is specified,
XDPE/400 uses the internal output queue in the XDPE/400 application
library.
Create Multi-part Packet (CRTXMPT)
Type choices, press Enter.
Multi-part packet name. . . . . .
Printer control packet list:
Printer control packet . . . .
Output queue . . . . . . . . . *XDPEQUE
Library . . . . . . . . . . .
*XDPELIB
+ for more values _
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
F12=Cancel
Name, F4 for list
Character value
Name, *XDPEQUE
Name, *XDPELIB
F13=How to use this display
Step 2.
Enter the name of the multi-part packet you are creating and press
ENTER. This is the name specified in the packet data field of the spool
file.
Step 3.
Enter the names of the packets to use for printing each part of your
multi-part spool file. You can use the name of any existing packet. The
largest number of packets you can use for one multi-part spool file is 10.
For each packet you can also specify an output queue and library. If an
Output queue and Library is specified, XDPE/400 places the processed
spool file in that output queue. If none is specified, XDPE/400 uses the
internal output queue in the XDPE/400 application library, or the
Remote/network output queue, if one is specified.
NOTE: The processing of each part by its packet follows standard
XDPE/400 printer control as determined by the values specified for
the PACKETDATA and ALWAYS Monitor Queue parameters. Refer
to the “Choosing a command generation method” section in
Chapter 8 for more information.
Printing Documents with XDPE/400 (9/2001)
24-4
Multi-part printing
Considerations
This section provides considerations that apply to multi-part packets.
Specifying output queues
Note these considerations when specifying output queues for printer
control packets in a multi-part packet:
•
You can specify an output queue and library for each part of a
multi-part job. If no output queue and library are specified,
XDPE/400 uses the internal output queue in the application library. If
you specify an output queue, a library must also be specified.
•
When spool files are sent to output queues other than the XDPE/400
default output queue or a Remote/network output queue specified in
the Monitor Queue, it is the user’s responsibility to start writers for
those output queues they specify in the multi-part packet.
•
Because only one printer/interface box configuration can be
specified for each Monitor Queue session, all of the output queues
you specify in a multi-part job must support this configuration. If
*NET is specified for the Device class (DEVCLS) Monitor Queue
parameter, all of the output queues specified must support HPT. If
the Device class (DEVCLS) value is *LCL or *RMT, all of the output
queues specified must support printing without HPT.
Printing Documents with XDPE/400 (9/2001)
24-5
Multi-part printing
Example of a multi-part packet
This example illustrates the creation of a multi-part packet named
INVOICE.
Create Multi-part Packet (CRTXMPT)
Type choices, press Enter.
Multi-part packet name. . . . . .
Printer control packet list:
Printer control packet . . . .
Output queue . . . . . . . . .
Library . . . . . . . . . . .
Printer control packet . . . .
Output queue . . . . . . . . .
Library . . . . . . . . . . .
Printer control packet . . . .
Output queue . . . . . . . . .
Library . . . . . . . . . . . .
+ for more values _
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
Name, F4 for list
INVOICE
#PKT1
PRTQUE025
SALESLIB
XDPE
*XDPEQUE
*XDPELIB
+PKT2
PRTQUE010
BILLIB
F12=Cancel
Character value
Name, *XDPEQUE
Name, *XDPELIB
Character value
Name, *XDPEQUE
Name, *XDPELIB
Character value
Name, *XDPEQUE
Name, *XDPELIB
F13=How to use this display
Monitor Queue will locate and use the INVOICE packet when it processes
the spool file containing INVOICE in the Packet data field, then processes
the spool file once for every packet name listed for Printer control packet
list, according to the values specified for the PACKETDATA and ALWAYS
Monitor Queue parameters.
In this example, Monitor Queue has been started with
ALWAYS(*DIRECT) specified.
Printing Documents with XDPE/400 (9/2001)
24-6
Multi-part printing
The Printer control packet list in this example is used as follows:
•
Part 1 for the sales department is created using the printer controls
from the #PKT1 packet residing in either the XDPEFLR/XES, DJDE,
PCL or JDTLIB (for VIPP mode only) subfolder, based on the value
specified for the Printer mode (MODE) Monitor Queue parameter.
Printer controls used are from this packet only; no printer file
parameters are applied. This part is printed essentially using the
*DIRECT method. The spool file generated is placed on the
PRTQUE025 output queue located in a library in the library list.
•
Part 2 for the shipping department is printed using the current printer
file parameters; no packet is specified. This part is printed
essentially using the *INDIRECT method. XDPE/400 places the
spool file in the internal output queue.
•
Part 3 for the customer is printed using the printer controls from the
+PKT2 packet residing in the appropriate subfolder and the current
printer file parameters. The order the controls are applied depends
on the value for the SEQUENCE Monitor Queue parameter. This part
is printed essentially using the *COMBINED method. The spool file
is placed on the PRTQUE025 output queue located in the current
library.
Printing Documents with XDPE/400 (9/2001)
24-7
Multi-part printing
Changing a multi-part packet
Follow these steps to change a multi-part packet:
Step 1.
Enter CHGXMPT and press ENTER. The Change Multi-part Packet menu
displays.
Change Multi-part Packet (CHGXMPT)
Type choices, press Enter.
Multi-part packet name. . . . . .
F3=Exit F4=Prompt
F24=More keys
Step 2.
F5=Refresh
F12=Cancel
Name, F4 for list
F13=How to use this display
Enter the name of the multi-part packet you want to change and press
ENTER. XDPE/400 displays the printer control packet list for the
multi-part packet, including the output queues and libraries for each
printer control packet.
NOTE: You may see the message, “Messages pending on other
displays,” on the bottom of the screen. You should ignore this
message.
Step 3.
Make any necessary changes in the printer control packet list.
Printing Documents with XDPE/400 (9/2001)
24-8
Multi-part printing
Deleting a multi-part packet
Follow these steps to delete a multi-part packet:
Step 1.
Enter DLTXMPT and press ENTER. The Delete Multi-part Packet menu
displays.
Delete Multi-part Packet (DLTXMPT)
Type choices, press Enter.
Multi-part packet name. . . . . .
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
F12=Cancel
Name, F4 for list
F13=How to use this display
CAUTION: Make sure you correctly specify the name of the multi-part
packet you want to delete. The system deletes the packet without
confirmation.
Step 2.
Enter the name of the multi-part packet you want to delete and press
ENTER.
Printing Documents with XDPE/400 (9/2001)
24-9
Multi-part printing
Starting multi-part processing
To maintain data integrity and control multi-part processing, make these
selections when you start the Monitor Queue:
•
Select *PAGE for File processing mode (PROCMODE). When in
*PAGE mode, Monitor Queue creates a single integrated spool file
that contains printer commands and user spool file data. Using
*PAGE mode ensures the spool file is printed in the order the entries
are listed in the multi-part packet.
•
Specify 0 (zero) for Wait time between files (WAITTIME). This
ensures a spool file is processed for each entry in the multi-part
packet without undue waiting.
•
Specify *YES for Multi-part printing (XMPT).
Refer to the File processing mode (PROCMODE) parameter definition in
chapter 19 for more information about the *PAGE processing mode.
Printing Documents with XDPE/400 (9/2001)
24-10
25.
25
Multi-up printing
Multi-up processing prints multiple pages of output on one physical page.
You can use these types of command generation for generating multi-up
output from XDPE/400:
•
•
•
•
•
•
•
DJDE Direct and Indirect command generation
XES Direct command generation
XES Indirect command generation
PCL Direct command generation
PCL Indirect command generation
VIPP Direct command generation
VIPP Indirect command generation
XDPE/400 offers these levels of functionality:
•
The Indirect command generation methods listed allow up to four
logical pages per physical page.
•
The Direct command generation methods in XES and PCL mode
allow up to 32,767 logical pages per side (depending on your
printer’s capabilities). The Direct command generation method in
VIPP mode has no defined maximum number of logical pages
because the maximum allowed is printer-dependent.
This chapter explains each method of multi-up generation in detail.
Refer to appendix C for information about the use of SCS commands and
multi-up printing.
DJDE multi-up generation
For DJDE Direct and Indirect modes, the FONT, PAGRTT, and MULTIUP
parameters specify which PDE to select from the list of PDEs specified in
the WRKGBLVAL command. These parameters define the number of
logical pages per physical sheet and the orientation of the page.
Table 25-1 shows the orientation and number of logical pages per side for
each PDE supplied with XDPE/400. The table also shows the maximum
print data line length for each PDE. Using a line length greater than the
maximum line lengths specified in the table may result in print data
overlapping between adjoining physical pages. Note that the line lengths
include the first character as a control character.
Printing Documents with XDPE/400 (9/2001)
25-1
Multi-up printing
Table 25-1.
Orientation
PDEs supplied with XDPE/400
Number of
pages per side
PDE name
Maximum
line length
Portrait
1
ONEPOR
97
Portrait
2
TWOPOR
153
Portrait
4
FORPOR
115
Landscape
1
ONELAN
142
Landscape
2
TWOLAN
109
Landscape
4
FORLAN
109
The following panels show the page formatting commands that are sent
to the printer by each PDE.
This is the contents of the ONELAN PDE:
FILENAME : ONELAN
BEGIN : 1
+54,+198
FONTS : 1
Font Name : LPI08L
OVERRIDE LPI : 37
PMODE : LANDSCAPE
This is the contents of the TWOLAN PDE:
FILENAME : TWOLAN
BEGIN : 2
+150,+30 +0, +1620
FONTS : 1
Font Name : LPI12L
OVERRIDE LPI : 25
PMODE : LANDSCAPE
This is the contents of the FORLAN PDE:
FILENAME : FORLAN
BEGIN : 4
+45,+30 +1260,+0 +0,+1620 +1260,+1620
FONTS : 1
Font Name : LPI16L
OVERRIDE LPI : 19
PMODE : LANDSCAPE
Printing Documents with XDPE/400 (9/2001)
25-2
Multi-up printing
This is the contents of the ONEPOR PDE:
FILENAME : ONEPOR
BEGIN : 1
+150,+150
FONTS : 1
Font Name : LPI12P
OVERRIDE LPI : 25
PMODE : PORTRAIT
This is the contents of the TWOPOR PDE:
FILENAME : TWOPOR
BEGIN : 2
+120,+60 +0,+1620
FONTS : 1
Font Name : LPI12P
OVERRIDE LPI : 25
PMODE : PORTRAIT
This is the contents of the FORPOR PDE:
FILENAME : FORPOR
BEGIN : 4
+30,+60 +0,+1620 +1260,+0 +1260,+1620
FONTS : 1
Font Name : LPI16P
OVERRIDE LPI : 19
PMODE : PORTRAIT
The following examples show how the FONT, PAGRTT, and MULTIUP
parameters determine the selection of the PDE for a given job.
Printing Documents with XDPE/400 (9/2001)
25-3
Multi-up printing
Case 1
If FONT is not *CPI or *DEVD, and the printer is not a 4450 with the
interface mode set to Normal, and the interface is not BARR with the
interface mode set to Normal, create a JDE/PDE= DJDE using the FONT
ID as the JDE/PDE name.
Case 2
If PAGRTT is *AUTO, *DEVD, or *COR, do not create a DJDE from this
attribute.
Case 3
If the printer is a 4450 with the interface mode set to Normal or if the
interface is BARR with the interface mode set to Normal, refer to the
following table for the PAGRTT values and the corresponding DJDEs that
are created. The MULTIUP value does not affect the type of PMODE
created.
PAGRTT value
Case 4
DJDE created
0
PMODE=PORTRAIT
90
PMODE=LANDSCAPE
180
PMODE=PORTRAIT
270
PMODE=LANDSCAPE
If the global value JDE/PDE name creation mode is *NAME, refer to table
25-2 for the PAGRTT or MULTIUP values and the corresponding
PDE/JDE DJDE name used.
Table 25-2.
PAGRTT- or MULTIUP-to-PDE/JDE-ID mapping
PAGRTT and MULTIUP
values
PDE/JDE-ID mapping
with *NAME
PDE/JDE-ID mapping
with *AUTO
0 and 1
ONEPOR
P1xxx
0 and 2
TWOPOR
P2xxx
0 and 4
FORPOR
P4xxx
90 and 1
ONELAN
J1xxx
90 and 2
TWOLAN
J2xxx
90 and 4
FORLAN
J4xxx
180 and 1
ONEPOR
I1xxx
180 and 2
TWOPOR
I2xxx
180 and 4
FORPOR
I4xxx
270 and 1
ONELAN
L1xxx
270 and 2
TWOLAN
L2xxx
270 and 4
FORLAN
L4xxx
Printing Documents with XDPE/400 (9/2001)
25-4
Multi-up printing
Case 5
If the global value JDE/PDE name creation mode is *AUTO, refer to table
25-2 for the PAGRTT or MULTIUP values and the corresponding
PDE/JDE DJDE name used. (In the table, xxx represents the contents of
the page width field of the spool file attributes.)
NOTE: When a true case is found, the JDE/PDE or PMODE
processing is done for that job.
XES multi-up generation
There are two methods for XES multi-up printing in XDPE/400:
•
•
Indirect method (1, 2, and 4 pages per side)
Direct method (up to 32,767 pages per side)
For the indirect method, XDPE/400 uses the Degree of page rotation
(PAGRTT) and Pages per side (MULTIUP) printer file parameters to
determine the format for the spool file being processed. MULTIUP
determines the number of logical pages printed on each physical page,
either 1, 2, or 4. PAGRTT specifies the orientation of the print data on the
page. XDPE/400 then retrieves the appropriate multi-up packet to
determine the format of the logical page. This table lists the orientation
produced by the PAGRTT value.
Value
Orientation produced
0
Portrait
90
Inverted landscape
180
Inverted portrait
270
Landscape
NOTE: The multi-up packets supplied with XDPE/400 support
landscape and portrait orientations only. For applications using
inverse orientation, you must create your own multi-up packets.
In the direct method, XDPE/400 uses the Number of pages per side
(PAGESPSIDE) XES packet parameter and the Degree of page rotation
(PAGRTT) printer file parameter to determine the orientation and number
of logical pages per side. The Multi-up packet name (XESMUP) XES
packet parameter determines the multi-up packet used to create the
format of the logical page.
Printing Documents with XDPE/400 (9/2001)
25-5
Multi-up printing
Requirements
To use multi-up printing, these conditions must be met:
•
*PAGE must be specified for the File processing mode
(PROCMODE) Monitor Queue parameter.
•
The Font id/Multiple up attributes global value must be *YES.
•
No list or logical processing can be specified.
•
For Indirect command generation:
—
The page rotation (PAGRTT) attribute must have one of these
values: 0, 90, 180, or 270.
—
FONTID must have a default value of *CPI or *DEVD.
—
Always generate (ALWAYS) must be either:
•
•
•
*INDIRECT
*COMBINED with *PACKET specified for Order of sequence
(SEQUENCE)
—
The maximum number of logical pages per side is 4.
—
Multi-up packet naming conventions must be adhered to when
creating multi-up packets.
For Direct command generation:
—
You must enter values for these parameters in the XES packet
for multi-up printing:
•
•
—
Number of pages per side (PAGESPSIDE)
Multi-up packet name (XESMUP)
Always generate (ALWAYS) must be either:
•
•
*DIRECT
*COMBINED with *ATTRIB specified for Order of sequence
(SEQUENCE)
When these conditions are met, XDPE/400 searches in the
XDPEFLR/XESMUP subdirectory for the appropriate multi-up packet.
Using the multi-up packet, the entire user spool file is processed and
converted to ASCII. The following limited set of IBM SCS commands
which are present for the IBM 5225 printer data stream are processed to
maintain the printer line position:
•
•
•
Absolute/Relative Horizontal Presentation Position
Absolute/Relative Vertical Presentation Position
New lines, Carriage Return, Required New Line, Line Feed
If you are using the Direct method and multi-up is active, these XES
packet parameters will be ignored:
•
•
•
•
•
4325 page format
Margin setting
Page font selection
Generic packet
Resource list
The values for the margin and font parameters are taken from the multi-up
packet. The 4235 page format, generic packet, and Resource list
parameters are disabled for multi-up printing.
Printing Documents with XDPE/400 (9/2001)
25-6
Multi-up printing
Creating multi-up XES packets
Multi-up packets contain relevant font and positioning information. The
XDPEFLR/XESMUP subdirectory contains a collection of multi-up
packets supplied with XDPE/400. If you do not want to use one of these
default packets, you can create your own using an editor on a personal
computer (PC) or using IBM Source Entry Utility (SEU).
The format of the XES multi-up packet is outlined below and must be
adhered to when developing multi-up packets. You can use the default
packets provided by XDPE/400 as templates.
XDPE/400-supplied multi-up packets
The XDPEFLR/XESMUP subfolder contains a set of XDPE/400-supplied
multi-up packets to use with XDPE/400.
Table 25-3 shows the XES multi-up packets distributed with XDPE/400,
and the method of command generation that can be used with them. The
table also shows the maximum print data line length that can be used for
each XES packet. Using a line length greater than the maximum line
lengths specified in the table may result in print data overlapping between
adjoining logical pages. Note that the line lengths include the first
character as a control character.
Table 25-3.
XDPE/400-supplied XES multi-up packets
Portrait
Description
Type of generation
Packet
name
Maximum
line length
Landscape
Packet
name
Maximum
line length
1-up packet
All
P1XEROX
135
L1XEROX
135
2-up packet
All
P2XEROX
137
L2XEROX
137
4-up packet
All
P4XEROX
104
L4XEROX
137
8-up packet
*COMBINED with *ATTRIB
and *DIRECT
P8XEROX
N/A
L8XEROX
N/A
16-up packet
*COMBINED with *ATTRIB
and *DIRECT
P16XEROX
N/A
L16XEROX
N/A
24-up packet
*COMBINED with *ATTRIB
and *DIRECT
P24XEROX
N/A
L24XEROX
N/A
33-up packet
*COMBINED with *ATTRIB
and *DIRECT
P33XEROX
N/A
L33XEROX
N/A
The 1-, 2-, and 4-up packets can be used for both the Indirect (*INDIRECT
and *COMBINED with *PACKET) and the Direct (*DIRECT and
*COMBINED with *ATTRIB) methods, while the 8-, 16-, 24-, and 33-up
packets can only be used with the Direct method.
Printing Documents with XDPE/400 (9/2001)
25-7
Multi-up printing
For multi-up printing in Indirect mode, if a user-created multi-up packet is
not found, XDPE/400 uses the appropriate XDPE/400-supplied 1-, 2-, or
4-up multi-up packet. Because of this, they are referred to as “default”
packets. Note these considerations for the default packets:
•
Do not rename these packets. If a user-created multi-up packet or
the appropriate default packet are not found, XDPE/400 will be
unable to perform multi-up processing.
•
If you want to make changes, use the default packets as templates
for creating your own multi-up packets. Do not modify the default
packets.
The 8-, 16-, 24-, and 33-up packets are used with the Direct method only
and are referred to as “sample” packets. You can use these packets for
your jobs “as-is,” or use them as templates for creating your own multi-up
packets.
These panels show the contents of the default multi-up packets supplied
with XDPE/400:
NOTE: The panels show the contents of the letter-size (8.5 by
11 inch) default multi-up packets only. The contents of the A4 default
multi-up packets can be viewed using the IBM Source Entry Utility
(SEU) and the OS/400 command CPYFRMPCD.
P1XEROX:
P07TYA LOAD
m3300,300,0,300,2550
a300,3000
rr0
P2XEROX:
LPI12P LOAD
m3300,150,0,150,2550
a150,3150
rr0
a150,1575
rr0
Printing Documents with XDPE/400 (9/2001)
25-8
Multi-up printing
P4XEROX:
LPI16P LOAD
m3300,75,0,75,2550
a75,3225
rr0
a75,1612
rr0
a1275,3225
rr1200
a1275,1612
rr1200
L1XEROX:
LPI08L LOAD
m2550,150,0,300,3300
a150,300
rr0
L2XEROX:
LPI12L LOAD
m2550,150,0,150,3300
a150,150
rr0
a150,1650
rr1500
L4XEROX:
LPI16L LOAD
m2550,75,0,75,3300
a75,75
rr0
a1275,75
rr0
a75,1650
rr1575
a1275,1650
rr1575
Printing Documents with XDPE/400 (9/2001)
25-9
Multi-up printing
Naming multi-up packets
For the Direct method, XDPE/400 takes the name of the multi-up packet
from the Multi-up packet name (XESMUP) parameter in the XES packet.
You must specify a value for this parameter if the Number of pages per
side (PAGESPSIDE) parameter is set to any value other than *NONE. The
multi-up packet name can be any one- to eight-character alphanumeric
value.
When using Indirect or Combined to print multi-up packets, if you specify
*PACKET in the Order of sequence (SEQUENCE) Monitor Queue
parameter, the multi-up packet name must follow the conventions outlined
below.
The format of a multi-up packet name is:
rpwww
where
r
p
www
Represents the page rotation
Represents the number of pages per side
Represents the page width in positions-per-line
The possible values for each representation are outlined below:
•
Page rotation — Identifies a one-character packet name prefix that is
used to symbolize the rotation degrees, as shown in this table.
Character
•
Orientation
Degrees
P
Portrait
0
J
Inverted landscape
90
I
Inverted portrait
180
L
Landscape
270
Number of pages per side — Identifies a one-character field that is
used to symbolize the logical pages per side, as shown in this table.
Character
Pages per side
1
1
2
2
4
4
Printing Documents with XDPE/400 (9/2001)
25-10
Multi-up printing
•
Page width — Identifies a three-character field that represents the
page width attribute in positions-per-line.
For Indirect processing, XDPE/400 searches the XDPEFLR/XESMUP
subfolder for a multi-up ASCII XES packet based on these attributes. For
example, XDPE/400 would search for a multi-up packet named P2132
based on these attributes:
Page rotation0 degrees
Pages per side2
Page width132 positions-per-line
If the packet is not present, XDPE/400 uses XDPEFLR/
XESMUP/P2XEROX as the default.
Multi-up packet format
The format of the multi-up packet is outlined below and must be adhered
to when developing additional multi-up packets. The format of an XES
multi-up packet is:
FONT
MARGIN
Page 1 Absolute position
Page 1 Relative position
Page 2 Absolute position
Page 2 Relative position
Page 3 Absolute position
Page 3 Relative position
Etc...
Each command must be on its own line and in the sequence shown.
Absolute and relative position commands must be given for each logical
page that will be printed on the physical page. End each line with an ASCII
carriage return and an ASCII line feed. XDPE/400 inserts the escape
character for each command line.
For more information about the XES commands used to create multi-up
packets, refer to the Xerox 4700 XES Reference Guide.
Printing Documents with XDPE/400 (9/2001)
25-11
Multi-up printing
To create your own packet, you can use one of the XDPE/400-supplied
multi-up packets as a template. Table 25-4 shows an example of the
XDPE/400-supplied P8XEROX XES letter multi-up packet.
Table 25-4.
P8XEROX XES multi-up packet contents
Packet source line
Description
LPI16P LOAD
Font command
m3300,75,0,75,2550
Margin command
a75,3225
Absolute position of logical page 1
rr0
Relative position for each line of logical
page 1
a75,2400
Absolute position of logical page 2
rr0
Relative position for each line of logical
page 2
a75,1575
Absolute position of logical page 3
rr0
Relative position for each line of logical
page 3
a75,750
Absolute position of logical page 4
rr0
Relative position for each line of logical
page 4
a1360,3225
Absolute position of logical page 5
rr1285
Relative position for each line of logical
page 5
a1360,2400
Absolute position of logical page 6
rr1285
Relative position for each line of logical
page 6
a1360,1575
Absolute position of logical page 7
rr1285
Relative position for each line of logical
page 7
a1360,750
Absolute position of logical page 8
rr1285
Relative position for each line of logical
page 8
Printing Documents with XDPE/400 (9/2001)
25-12
Multi-up printing
FONT command
This command calls for an XES font to be dynamically downloaded and
invoked for printing a multi-up page. There are three ways to use this
command. The syntax of each method is shown below:
font1
In this case, font1 is the actual name of a font file loaded on the printer.
Since the file was previously downloaded, the LOAD keyword is not
required. This is an example of the command:
XGT30P
font1 LOAD
In this case, the command downloads a font that is resident in the
XDPEFLR/XESFONTS directory. To use this method, the name of the
member must be the same as the internal font name contained in the
header of the font member. You do not need to specify the .FNT file
extension. The LOAD keyword is required to initiate loading. Once it is
downloaded to the printer, the font retains the name used in the directory.
This is an example of the command:
XGT30P LOAD
font2 LOAD font1
In this case, the command downloads a font that is resident in the
XDPEFLR/XESFONTS directory, but the member name in the directory
and the internal font name contained in the header of the font member are
different. This is an example of the command:
XGT30 LOAD XGT30P
XGT30 is the name of a member in the XDPEFLR/XESFONTS directory,
which contains the printer font identified as XGT30P. The second name
must be the internal font name of the font. When the font is downloaded
to the printer, the printer will refer to it by this name.
MARGIN command
The MARGIN command specifies the page dimension and the logical
page boundaries in units of 1/300 inch. The format of this command is:
mph,tm,bm,lm,rm
where
ph
Distance between the top edge of the page and the bottom edge
tm
Top margin
bm
Bottom margin
lm
Left margin
rm
Right margin, measured from the left edge of the physical page
to the right edge of the text
Example:
m3300,0,0,120,2550
Printing Documents with XDPE/400 (9/2001)
25-13
Multi-up printing
Absolute position command
Use this command to specify the origin point of the logical page using
units of 1/300 inch. The format of this command is:
ax,y
where
x
y
Horizontal distance from the origin point
Vertical distance from the origin point
Example:
a120,3210
Relative position command
The first line of text is placed at the logical page origin. However, the lines
immediately following can be offset to the right or left of the logical page
origin. Use the relative position command to specify this offset. The
format of this command is:
rpx
where
p
Specifies whether the offset will be to the right or left of the logical
page origin. Use r to indicate placement to the right or l to indicate left
of the logical page origin.
x
Number of pixels the text is offset.
Example:
rr0
Using the IBM SEU
Follow these steps to create a multi-up ASCII packet using IBM SEU:
Step 1.
Create a member that represents the EBCDIC text version of the packet
within a physical source file.
Step 2.
Use the CPYTOPCD command to copy the source file member to the
XDPEFLR/XESMUP file. You can use these command options:
•
•
An EBCDIC to ASCII translation table
*TEXT as the PC data format
Using the DOS ASCII editor
Follow these steps to create a multi-up ASCII packet using the DOS ASCII
Editor and OS/400 Client Access:
Step 1.
Create an ASCII text file that has the XES packet format.
Step 2.
Copy the file to the shared I:/XDPEFLR/XESMUP folder.
Printing Documents with XDPE/400 (9/2001)
25-14
Multi-up printing
PCL multi-up generation
There are two methods for PCL multi-up printing in XDPE/400:
•
•
Indirect method (1, 2, and 4 pages per side)
Direct method (up to 32,767 pages per side)
NOTE: Multi-up packets that use euro fonts can only be used with the
Direct method.
Indirect method
For the indirect method, XDPE/400 uses the Degree of page rotation
(PAGRTT) and Pages per side (MULTIUP) printer file parameters to
determine the format for the spool file being processed. MULTIUP
determines the number of logical pages printed on each physical page,
either 1, 2, or 4. PAGRTT specifies the orientation of the print data on the
page. XDPE/400 then retrieves the appropriate multi-up packet to
determine the format of the logical page. This table lists the orientation
produced by the PAGRTT value.
Value
Orientation produced
0
Portrait
90
Inverted landscape
180
Inverted portrait
270
Landscape
*COR
Landscape
NOTE: The multi-up packets supplied with XDPE/400 support
landscape and portrait orientations only. For applications using
inverse orientation, you must create your own multi-up packets.
Direct method
In the direct method, XDPE/400 uses the Number of pages per side
(PAGESPSIDE) and Page orientation (ORIENT) PCL packet parameters
to determine the orientation and number of logical pages per side. The
Multi-up packet name (PCLMUP) PCL packet parameter determines the
multi-up packet used to create the format of the logical page.
Printing Documents with XDPE/400 (9/2001)
25-15
Multi-up printing
Requirements
To use multi-up printing, these conditions must be met:
•
*PAGE must be specified for the File processing mode
(PROCMODE) Monitor Queue parameter.
•
The Font id/Multiple up attributes global value must be *YES.
•
No list or logical processing can be specified.
•
For Indirect command generation:
—
The page rotation (PAGRTT) attribute must have one of these
values: 0, 90, 180, or 270.
—
FONTID must have a default value of *CPI or *DEVD.
—
Always generate (ALWAYS) must be either:
—
—
•
*INDIRECT
*COMBINED with *PACKET specified for Order of sequence
(SEQUENCE)
—
The maximum number of logical pages per side is 4.
—
Multi-up packet naming conventions must be adhered to when
creating multi-up packets.
For Direct command generation:
—
You must enter values for these parameters in the PCL packet
you want to use for multi-up printing:
—
—
—
ALWAYS must be either:
—
—
—
Number of pages per side (PAGESPSIDE)
Multi-up packet name (PCLMUP)
*DIRECT
*COMBINED with *ATTRIB specified for Order of sequence
(SEQUENCE)
If you are using euro fonts, the PC/Support translation table
(PCSLIB) global value must:
—
Specify an EBCDIC to ASCII translation table that supports
the euro character
—
Be compatible with the EBCDIC code page specified in the
printer file
—
Be compatible with the selected euro keyboard type
NOTE: See the PCSLIB global value in Chapter 6 of Section
Two: Installing and Customizing XDPE/400 for more information
on translation tables and code pages that support the euro.
Printing Documents with XDPE/400 (9/2001)
25-16
Multi-up printing
When these conditions are met, XDPE/400 searches in the
XDPEFLR/PCLMUP subdirectory for the appropriate multi-up packet.
Using the multi-up packet, the entire user spool file is processed and
converted to ASCII. The following limited set of IBM SCS commands
which are present for the IBM 5225 printer data stream are processed to
maintain the printer line position:
•
•
•
Absolute/Relative Horizontal Presentation Position
Absolute/Relative Vertical Presentation Position
New lines, Carriage Return, Required New Line, Line Feed
If you are using the Direct method and multi-up is active, these PCL
packet parameters will be ignored:
•
•
•
•
•
Margin setting
Page font selection
Lines per inch (LPI)
Generic packet
Resource list
The values for the Lines per inch (LPI), margin, and font parameters are
taken from the multi-up packet.
Creating multi-up PCL packets
Multi-up packets contain relevant font and positioning information. The
XDPEFLR/PCLMUP subdirectory contains a collection of multi-up
packets supplied with XDPE/400. If you do not want to use one of these
default packets, you can create your own using an editor on a personal
computer (PC) or using IBM Source Entry Utility (SEU).
The format of the PCL multi-up packet is outlined below and must be
adhered to when developing multi-up packets. You can use the default
packets provided with XDPE/400 as templates.
XDPE/400-supplied multi-up packets
The XDPEFLR/PCLMUP subfolder contains a set of XDPE/400-supplied
multi-up packets to use with XDPE/400.
Table 25-5 shows the PCL multi-up packets distributed with XDPE/400,
and the method of command generation that can be used with them. The
table also shows the maximum print data line length that can be used for
each PCL packet. Using a line length greater than the maximum line
lengths specified in the table may result in print data overlapping between
adjoining logical pages. Note that the line lengths include the first
character as a control character.
Printing Documents with XDPE/400 (9/2001)
25-17
Multi-up printing
Table 25-5.
XDPE/400-supplied PCL multi-up packets
Portrait
Description
Type of generation
Packet
name
Maximum
line length
Landscape
Packet
name
Maximum
line length
1-up packet
All
P1XEROX
135
L1XEROX
135
2-up packet
All
P2XEROX
or
P2EURO
137
L2XEROX
or
L2EURO
137
4-up packet
All
P4XEROX
104
L4XEROX
137
8-up packet
*COMBINED with *ATTRIB
and *DIRECT
P8XEROX
N/A
L8XEROX
N/A
16-up packet
*COMBINED with *ATTRIB
and *DIRECT
P16XEROX
N/A
L16XEROX
N/A
24-up packet
*COMBINED with *ATTRIB
and *DIRECT
P24XEROX
N/A
L24XEROX
N/A
33-up packet
*COMBINED with *ATTRIB
and *DIRECT
P33XEROX
N/A
L33XEROX
N/A
The 1-, 2-, and 4-up packets can be used for both the Indirect (*INDIRECT
and *COMBINED with *PACKET) and the Direct (*DIRECT and
*COMBINED with *ATTRIB) methods, while the 8-, 16-, 24-, and 33-up
packets can only be used with the Direct method.
For multi-up printing in Indirect mode, if a user-created multi-up packet is
not found, XDPE/400 uses the appropriate XDPE/400-supplied 1-, 2-, or
4-up multi-up packet. Because of this, they are referred to as “default”
packets. Note these considerations for the default packets:
•
Do not rename these packets. If a user-created multi-up packet or
the appropriate default packet are not found, XDPE/400 will be
unable to perform multi-up processing.
•
If you want to make changes, use the default packets as templates
for creating your own multi-up packets. Do not modify the default
packets.
The 8-, 16-, 24-, and 33-up packets are used with the Direct method only
and referred to as “sample” packets. You can use these packets for your
jobs “as-is,” or use them as templates for creating your own multi-up
packets.
The following panels show the contents of the default multi-up packets
supplied with XDPE/400.
NOTE: The panels show the contents of the letter-size (8.5 by
11 inch) default multi-up packets only. The contents of the A4 default
multi-up packets can be viewed using the IBM Source Entry Utility
(SEU) and the OS/400 command CPYFRMPCD.
Printing Documents with XDPE/400 (9/2001)
25-18
Multi-up printing
P1XEROX:
LPI12P LOAD
&l0O
&l12D
&l0E
&l132F
&a141M
&a0C
&a8L
*p150Y
P2XEROX:
LPI12P LOAD
&l0O
&l12D
&l0E
&l132F
&a143M
&a0C
&a8L
*p75Y
; Page 2 **********
*p1725Y
P2EURO:
XGT30.HPP LOAD
&l0O
&l12D
&l0E
&l132F
&a143M
&a0C
&a8L
*p75Y
; Page 2 *********************
*p1725Y
Printing Documents with XDPE/400 (9/2001)
25-19
Multi-up printing
P4XEROX:
LPI16P LOAD
&l0O
&l16D
&l2E
&l200F
&a240M
&a0C
&a1L
*p70Y
; Page 2 **********
&a0C
&a1L
*p1630
; Page 3 **********
&a116L
*p70Y
; Page 4 **********
&a116L
*p1630Y
L1XEROX:
LPI08L LOAD
&l1O
&l8D
&l0E
&l166F
&a141M
&a0C
&a8L
*p150Y
L2XEROX:
LPI12L LOAD
&l1O
&l12D
&l0E
&l100F
&a300M
&a0C
&a1L
*p150Y
; Page 2 **********
&a150L
*p150Y
Printing Documents with XDPE/400 (9/2001)
25-20
Multi-up printing
L2EURO:
XGB10.HPL LOAD
&l1O
&l12D
&l0E
&l100F
&a300M
&a0C
&a1L
*p150Y
; Page 2 *********************
&a150L
*p150Y
L4XEROX:
LPI16L LOAD
&l1O
&l16D
&l0E
&l160F
&a300M
&a0C
&a1L
*p75Y
; Page 2 **********
&a0C
&a1L
*p1290
; Page 3 **********
&a150L
*p75Y
; Page 4 **********
&a150L
*p1290Y
Printing Documents with XDPE/400 (9/2001)
25-21
Multi-up printing
Naming multi-up packets
For the Direct method, XDPE/400 takes the name of the multi-up packet
from the Multi-up packet name (PCLMUP) parameter in the PCL packet.
You must specify a value for this parameter if the Number of pages per
side (PAGESPSIDE) parameter is set to any value other than *NONE. The
multi-up packet name can be any one- to eight-character alphanumeric
value, that starts with an alphabetic character.
When using Indirect or Combined to print multi-up packets, if you specify
*PACKET in the Order of sequence (SEQUENCE) Monitor Queue
parameter, the multi-up packet name must follow the conventions outlined
below.
The format of a multi-up packet name is:
rpwww
where
r
p
www
Represents the page rotation
Represents the number of pages per side
Represents the page width in positions-per-line
The possible values for each representation are outlined below:
•
Page rotation — Identifies a one-character packet name prefix that is
used to symbolize the rotation degrees, as shown in this table.
Character
•
Orientation
P
Portrait
0
J
Inverted landscape
90
I
Inverted portrait
180
L
Landscape
270
Number of pages per side — Identifies a one-character field that is
used to symbolize the logical pages per side, as shown in this table.
Character
•
Degrees
Pages per side
1
1
2
2
4
4
Page width — Identifies a three-character field that represents that
page width attribute.
Printing Documents with XDPE/400 (9/2001)
25-22
Multi-up printing
For Indirect processing, XDPE/400 searches the XDPEFLR/PCLMUP
subfolder for a multi-up ASCII PCL packet based on these attributes. For
example, XDPE/400 would search for a multi-up packet named P2132
based on these attributes:
Page rotation0 degrees
Pages per side2
Page width132
If the packet is not present, XDPE/400 uses XDPEFLR/
PCLMUP/P2XEROX as the default.
Multi-up packet format
The format of a PCL multi-up packet is:
Font
Page orientation
Line spacing
Top margin
Right margin
Horizontal cursor position
Left margin
Vertical cursor position
logical page separator
page 2 Left margin
page 2 vertical cursor position
Etc...
You can use any PCL command to implement the multi-up feature. Each
PCL command must be on a separate line, and an escape character is not
required. End each line with an ASCII carriage return and an ASCII line
feed. There are no command numbers or type restrictions; however, you
should use the minimum number of commands required to perform the
function.
To separate each logical page setting, type a semicolon character (;) as
the first character on a line. The remaining text is ignored.
For more information about the PCL commands used to create multi-up
packets, refer to the PCL 5 Printer Language Technical Reference
Manual.
To create your own packet, you can use one of the XDPE/400-supplied
multi-up packets as a template. Table 25-6 shows an example of the
XDPE/400-supplied P8XEROX PCL letter multi-up packet.
Table 25-6.
P8XEROX PCL multi-up packet contents
Packet source line
Description
XGB10P LOAD
Font command
&l0O
Page orientation
&l16D
LPI line spacing
&l4E
Top page margin
&a200M
Right margin in columns
&a0C
Horizontal cursor position in columns
Printing Documents with XDPE/400 (9/2001)
25-23
Multi-up printing
Table 25-6.
P8XEROX PCL multi-up packet contents
Packet source line
Description
&a1L
Left margin in columns
*p0Y
Vertical cursor position in dots
; Page 2 ********************
Logical page separator
&a116L
Left margin in columns
*p0Y
Vertical cursor position in dots
; Page 3 ********************
Logical page separator
&a0C
Horizontal cursor position in columns
&a1L
Left margin in columns
*p825Y
Vertical cursor position in dots
; Page 4 ********************
Logical page separator
&a116L
Left margin in columns
*p825Y
Vertical cursor position in dots
; Page 5 ********************
Logical page separator
&a0C
Horizontal cursor position in columns
&a1L
Left margin in columns
*p1650Y
Vertical cursor position in dots
; Page 6 ********************
Logical page separator
&a116L
Left margin in columns
*p1650Y
Vertical cursor position in dots
; Page 7 ********************
Logical page separator
&a0C
Horizontal cursor position in columns
&a1L
Left margin in columns
*p2475Y
Vertical cursor position in dots
Page 8 ********************
Logical page separator
&a116L
Left margin in columns
*p2475Y
Vertical cursor position in dots
Printing Documents with XDPE/400 (9/2001)
25-24
Multi-up printing
FONT command
The format begins with a single line of text. This line calls for a PCL font
to be dynamically downloaded and invoked for printing a multi-up page.
The syntax of the initial line is:
font-name LOAD
where
font-name
Name of the laser jet font file (with an .FLJ extension) in the
XDPEFLR/PCLFONTS directory.
The font name that is in the text line of the packet does not have the .FLJ
file extension. The LOAD keyword is required because it allows you to
load and assign a font. XDPE/400 inserts the PCL command sequence to
invoke the font and assigns an ID 8000 to the loaded font. If you select
the font by using PCL commands (selecting a resident font or selecting a
font by attributes) within the packet, you can use any text on this line,
except the word LOAD.
Page orientation
This command specifies page orientation. The format of this command is:
&lxO
where
x
1 for landscape orientation or 0 for portrait orientation.
Line spacing
Specifies the line spacing value in lines per inch. The format of this
command is:
&lxD
where
x
Number of lines per inch.
Top Margin
Specifies the distance from the top of the page to the top edge of the text
in lines. The format of this command is:
&lxE
where
x
Number of lines.
Printing Documents with XDPE/400 (9/2001)
25-25
Multi-up printing
Right margin
Specifies the distance from the left edge of the page to the right edge of
the text in columns. The format of this command is:
&axM
where
x
Number of columns.
Left margin
Specifies the distance from the left edge of the page to the left edge of the
text in columns. The format of this command is:
&axL
where
x
Number of columns.
Vertical cursor position
This command moves the cursor position vertically in relation to the top
margin. A positive number places the cursor below the top margin, while
a negative number moves the cursor above the top margin. The value is
entered in 1/300 of an inch, and the valid values are from -32,767 to
32,767. The format of this command is:
*pxY
where
x
Units of 1/300 inch.
Horizontal cursor position
The Horizontal Cursor Position (HCP) command is used to ensure the
correct horizontal positioning for each row of logical pages. This
command is used at the end of each row to reset the position of the cursor
back to ’0’. The left margin will use this position as it’s origin. The format
of this command is:
&axC
where
x
Number of columns.
Printing Documents with XDPE/400 (9/2001)
25-26
Multi-up printing
Using the IBM SEU
Follow these steps to create a multi-up ASCII packet using IBM SEU:
Step 1.
Create a member that represents the EBCDIC text version of the packet
within a physical source file.
Step 2.
Use the CPYTOPCD command to copy the source file member to the
XDPEFLR/PCLMUP file. You can use these command options:
•
•
An EBCDIC to ASCII translation table
*TEXT as the PC data format
Using the DOS ASCII editor
Follow these steps to create a multi-up ASCII packet using the DOS ASCII
Editor and OS/400 Client Access:
Step 1.
Create an ASCII text file that has the PCL packet format.
Step 2.
Copy the file to the shared I:/XDPEFLR/PCLMUP folder.
VIPP multi-up generation
There are two methods that can be used for VIPP multi-up printing in
XDPE/400:
•
Indirect method (1, 2, 3 or 4 logical pages per side)
•
Direct method (any number of logical pages per side as supported
by VIPP for your printer)
The Combined method currently is not supported for VIPP multi-up
printing when using the spool file attributes if a JDT is specified. If you use
the Combined method as your command generation method, you can
produce VIPP multi-up printing in one of these ways:
•
If you specify a JDT name for a print job, then you must define a
VIPP TWOUP or SETMULTIUP command as the first command in
the JDT to generate multi-up printing.
•
If you do not specify any JDT name for a print job, XDPE/400
automatically uses the value defined for the MULTIUP spool file
attribute.
Printing Documents with XDPE/400 (9/2001)
25-27
Multi-up printing
Indirect method
For the Indirect method, XDPE/400 uses the Pages per side (MULTIUP)
parameter value and the XDPE internal folder ID (Letter or A4) to
determine the format for the spool file being processed.
•
The MULTIUP parameter determines the number of logical pages
printed on each physical page: 1, 2, 3 or 4.
•
The XDPE folder ID determines the relative dimensions of the logical
page. This page height-to-width ratio can be either in inches (US
Letter) or centimeters (A4) units of measure.
NOTE: XDPE/400 ignores any PAGRTT printer file parameter value
in the spool file.
XDPE/400 then generates the appropriate VIPP multi-up command to
determine the format of the logical page. XDPE/400 will generate VIPP
commands based on the MULTIUP value:
•
If the MULTIUP value is 1, XDPE/400 does not generate any VIPP
command. The VIPP default is ONEUP.
•
If the MULTIUP value is 2, XDPE/400 generates a VIPP TWOUP
command. The VIPP TWOUP command references the default
values, including the orientation value, defined in the VIPP default
configuration file, xgf.mup. This file is located in the /usr/xgf/src/
directory on the printer controller.
•
If the MULTIUP value is 3 or 4, XDPE/400 generates a VIPP
SETMULTIUP command. The VIPP horizontal and vertical origins
and scaling parameters are based on the MULTIUP value and the
XDPE folder ID. The width and height parameters than can be
specified for the VIPP SETMULTIUP command in VIPP software
version 2.1 and higher are not used.
The physical page orientation will be portrait. The orientation of each
logical page will be determined by the length and width of the logical
page.
Refer to the Xerox Variable Data Intelligent PostScript PrintWare (VIPP)
Reference Manual for information about the default values used by your
printer controller for the VIPP TWOUP and SETMULTIUP commands.
Printing Documents with XDPE/400 (9/2001)
25-28
Multi-up printing
Direct method
For the Direct method, you must define the appropriate VIPP TWOUP or
SETMULTIUP command as the first command in your JDT and then
download the JDT to the printer controller. Refer to chapter 21 for
instructions on downloading a JDT.
NOTE: The default VIPP multi-up settings are defined in the VIPP
xgf.mup core file, which is located in the /usr/xgf/src/ directory on the
printer controller.
Refer to the Xerox Variable Data Intelligent PostScript PrintWare (VIPP)
Reference Manual for the TWOUP and SETMULTIUP command syntax
and coding requirements, and for detailed information about xgf.mup.
Requirements
To use VIPP multi-up printing, these conditions must be met:
•
•
For Indirect command generation:
—
The Font id/Multiple up attributes parameter for global values
must be *YES.
—
The MULTIUP value must be 1, 2, 3, or 4.
—
The Always generate (ALWAYS) Monitor Queue parameter must
be *INDIRECT.
For Direct command generation:
—
The Always generate (ALWAYS) Monitor Queue parameter must
be *DIRECT.
—
The JDT specified for the print job must contain a VIPP TWOUP
or SETMULTIUP command as the first command in the JDT.
Printing Documents with XDPE/400 (9/2001)
25-29
Multi-up printing
Printing Documents with XDPE/400 (9/2001)
25-30
26.
26
Troubleshooting
This chapter describes procedures that you can use to diagnose and
correct problems you might encounter when using XDPE/400. Known
considerations and limitations are also presented. The chapter is
organized as follows:
•
Monitor Queue solutions
•
XDPM (XES) solutions and considerations
•
PCL solutions, considerations, and limitations
•
VIPP solutions
Monitor Queue solutions
This section provides solutions to problems related to Monitor Queue
processing. Information is also provided on the XDPE/400 Diagnostic
Utility, which can be used to find solutions to internal problems with
Monitor Queue processing. These topics are covered:
•
•
•
•
Job does not print
Multiple Monitor Queue session database errors
Monitor Queue Diagnostic Utility
Switching from A4 size paper to US letter size paper is unsuccessful
Job does not print
If your job does not print, check the XDPEMSGQ message file to
determine the cause of the error.
To view the message file, type this command and press ENTER:
DSPMSG XDPEMSGQ
Also, check the following:
•
Monitor Queue may not be active. Verify that Monitor Queue is active
with the OS/400 WRKACTJOB command.
•
Look at the QSPL subsystem for a Monitor Queue job. The job must
have the same name as the output queue being monitored. If the job
is active, it will have a status of RUN or DEQW.
Refer to chapter 27 for instructions about how to display messages
produced by XDPE/400.
Printing Documents with XDPE/400 (9/2001)
26-1
Troubleshooting
Multiple Monitor Queue session database errors
If you are running multiple sessions and receive error messages that refer
to multiple sessions or the multiple session database, your multiple
session database and data areas are out of sync. Follow the instructions
in the next section, “Cleaning up the multiple session database,” to
correct this problem.
Cleaning up the multiple session database
Follow these instructions carefully; you will be creating two lists and
deleting specific data areas and files based on those lists:
Step 1.
Enter this command to display all data areas:
DSPOBJD
OBJ(library/*ALL)
OBJTYPE(*DTAARA)
where
library
The name of the XDPE/400 application library is XDPEvrm,
where
•
•
•
v is the version number
r is the release number
m is the modification number
Make a list containing each data area name displayed EXCEPT these:
BUFFER
DRAWERS
DUPLEXSTD
FILESIZE
INHIBLST
IOFFSET
IPREFIX
ISKIP
Step 2.
JDEPDE
MULPRTLST
PDEIDL
PDEIDP
RECSIZE
RESLIB
ROFFSET
RSTRING
RUNPTY
SHIFT
SPECPACK
TIMESLICE
XDPEAPPLIB
XDPEDIAG
Enter the Work With Active Job (WRKACTJOB) command and press
ENTER. Page forward to the QSPL subsystem area.
On the list you created in step 1, cross off any matching names of active
sessions with PGM-MONITOR QUEUE displayed.
Step 3.
Enter this command for each data area on the list you created in steps 1
and 2:
DLTDTAARA
DTAARA(library/data-area-name)
where
library
The name of the XDPE/400 application library is XDPEvrm.
Printing Documents with XDPE/400 (9/2001)
26-2
Troubleshooting
Step 4.
Enter this command to display all multiple session files:
DSPFD
FILE(library/XDPEMQSESS)
TYPE(*MBRLIST)
where
library
The name of the XDPE/400 application library is XDPEvrm.
Make a new list and write down the name of each file displayed.
Step 5.
Enter the Work With Active Job (WRKACTJOB) command and press
ENTER. Page forward to the QSPL subsystem area.
On the list you created in step 4, cross off any matching names of active
sessions with PGM-MONITOR QUEUE displayed.
Step 6.
Enter this command for each file on the list you created in steps 4 and 5:
RMVM
FILE(library/XDPEMQSESS)
MBR(file-name)
where
library
The name of the XDPE/400 application library is XDPEvrm.
Printing Documents with XDPE/400 (9/2001)
26-3
Troubleshooting
Monitor Queue Diagnostic Utility
The XDPE/400 Monitor Queue Diagnostic Utility is designed to help Xerox
Support find solutions to internal problems with Monitor Queue processing.
With the Diagnostic Utility turned on, user space dumps are created in the
form of spool files that can be used to resolve problems. The diagnostic
spool files will be created in the QEZDEBUG OUTQ in the QUSRSYS
library.
To use this utility, both XDPEUSR and the user who starts the Monitor
Queue must have *USE authority to QSYS/DMPOBJ *CMD.
Enter XDPDIAUTIL to bring up the user interface that allows you to set
diagnostics in XDPE/400. The XDPE/400 Diagnostic Utility menu displays.
XDPE/400 Diagnostic Utility
2
Select a diagnostic setting. The current value
is displayed.
1) No diagnostics are performed.
2) Error diagnostics are performed only if
there is an API error.
3) Error diagnostics are performed with or
without an API error.
Enter your selection and press Enter/Return.
F3=Exit
F12=Cancel
You can choose from three settings:
•
Setting 1 turns the internal diagnostics off within XDPE/400 Monitor
Queue processing.
•
Setting 2, the recommended setting, generates two user space
dumps when an internal API fails or reports an error. In the majority
of cases, when an API fails these dumps are critical in resolving the
error.
•
Setting 3 generates several user space dumps for each spool file
that is processed by the XDPE/400 Monitor Queue. These dumps
are generated with or without an internal API failure. Only select this
setting when it is recommended by Xerox Technical Support.
NOTE: Using setting 3 will create multiple diagnostic spool files
for each spool file processed by XDPE/400, which can consume
large amounts of storage space on your system and significantly
increase processing time.
Printing Documents with XDPE/400 (9/2001)
26-4
Troubleshooting
Switching from A4 size paper to US letter size paper is
unsuccessful
To switch from A4 size paper to US letter size paper or the reverse, follow
this procedure:
Step 1.
Identify all user folder objects by name and subdirectory.
Step 2.
Print all DJDE, XES, PCL, VIPP, LPP, multi-up packets, and
downloadable resources that may contain the following page size specific
values:
•
•
•
•
•
•
•
Forms
Images
Generic packets
DJDE JDEs
JSL/FSL
PostScript DSC
Xerox job tickets
Review the changes that need to be made for the new page sizes.
Step 3.
Backup the XDPE/400 library and folder.
Step 4.
Delete the XDPE/400 library and folder.
Step 5.
Install the base XDPE/400 specifying the new folder format.
Step 6.
Restore all user, XDPE/400, and printer resources that do not require
page size changes individually by name from the folder backup. For
example, this would include multi-part packets, fonts, logos, encoding
lists, resource lists, and color packets.
Step 7.
Recreate all other user packets using the print out from step 2 and
adjusting all page size specific values.
Printing Documents with XDPE/400 (9/2001)
26-5
Troubleshooting
XDPM (XES) solutions and considerations
This section provides solutions to problems related to the XDPM data
stream. Known XES processing considerations are also documented.
These topics are covered:
•
•
XES duplex job using Flex i-data box prints simplex
Considerations when using generic packets
Duplex job using Flex i-data box prints simplex
When using the Flex i-data interface box, if XDPE/400 is controlling the
tray selection via XES packets or spool file attributes and you want to
produce duplex output, both the XES packet and the spool file (printer file)
tray settings must match. Because of this, it is recommended that the tray
selection be made by the interface box rather than using XDPE/400.
To control tray selection during duplex printing using XDPE/400, you must
synchronize both the printer file and XES packet tray parameters. The
printer file parameter is DRAWER (n), where n is either the drawer
number or *E1 for the envelope feeder. The XES packet parameter is
TRAY (*TRAYn), where n is the tray number.
If you choose to set tray selection using the interface box, use this
procedure:
Step 1.
Create a Flex i-data function 11 command to specify tray selection. The
command must be included in the spool file before any printable data.
This example selects tray 3:
&&??%
%Y11,6%
&&??
1First line of print data . . . ,
where
&&??%
Sets a temporary i-data escape character. The % can be a
special character of your choice.
%Y11,n%
The function 11 command where n is 2 for tray one, 3 for tray
two, or 6 for tray three. % is the temporary escape character
defined in the first command.
&&??
Resets the temporary i-data escape character. Note the
command is five characters long and the underscore
following the second question mark specifies a blank
(required).
Printing Documents with XDPE/400 (9/2001)
26-6
Troubleshooting
Step 2.
Specify the default tray selection parameters for XDPE/400, both in the
printer file and in the XES packet as follows:
•
In the printer file, specify:
DRAWER=*SAME
•
In the XES packet, do not include a tray parameter
Refer to the i-data XES/PCL Twinax Interface Controller for Xerox
Printers User's Guide and the i-data Twinax XES/PCL Interface Controller
for Xerox Printers Programmer's Guide for more information.
For an XES job, if:
•
You have specified *YES or *TUMBLE for the Print on both sides of
sheet (DUPLEX) parameter
•
You have specified a format number for the 4235 Page format
(FORMAT) parameter
•
Your printer is connected via an i-data interface
You also must specify these items:
•
Specify a “dummy” Generic XES (GENXES) packet name; this
packet can be empty
•
Specify *PAGE for the GENXES Generic XES Invocation type
parameter
•
Specify *YES for the GENXES Generic XES Interface formatting off
parameter
Considerations when using generic packets
If you use generic packets, you must reset all appropriate parameters,
either within the generic packet or in a generic packet in the beginning of
the next page.
Printing Documents with XDPE/400 (9/2001)
26-7
Troubleshooting
PCL solutions, considerations, and limitations
This section provides solutions to problems related to the PCL data
stream. Known considerations and limitations are also documented.
These topics are covered:
•
Multiple copies do not print with DEVCLS set to *NET
•
NPS printer will not print duplex
•
Jobs sent to network printers do not print some special characters
•
Problems using three-hole punched paper with the 4220/4230 printer
•
Considerations when using generic packets
•
Known PCL limitations
—
Job prints wrong font on 4220 printer using FONT PCL
parameter
—
Duplex problem on DP65 printer
—
Job ignores margin defined in PCL packet when printing in
*COMBINED with *ATTRIB mode
—
Job ignores top margin defined in PCL packet in *DIRECT mode
when printing spool files created using Data Description
Specification (DDS)
Multiple copies do not print with DEVCLS set to *NET
If only one copy prints of a multiple copy job when the Device class
(DEVCLS) Monitor Queue parameter is set to *NET in PCL mode, follow
this procedure:
Step 1.
End the remote writer by issuing the ENDWTR command.
Step 2.
Add the Destination Option ‘XAIX’ to the remote queue by issuing this
command (enter the Destination Option in uppercase):
CHGOUTQ
OUTQ(library-name/outq-name)
DESTOPT('XAIX')
If the remote output queue has other values already defined for the
Destination Option, you must specify the new value and any other
value(s) in DESTOPT. Each value must be separated by at least one
space. For example, if the Destination Option “C(duplex)” is already
specified for the remote output queue, and now you want to specify the
copies parameter, you would issue this command:
CHGOUTQ
OUTQ(library-name/outq-name)
DESTOPT('C(duplex) XAIX')
NOTE: This printing problem is dependent upon the way your printer
is attached to the network. Therefore, do not perform this procedure
unless you encounter this problem.
Printing Documents with XDPE/400 (9/2001)
26-8
Troubleshooting
NPS printer will not print duplex
If your NPS printer is running NPS version 1.6 or higher in PCL mode and
will not print duplex copies, you need to provide job level instructions to
NPS to indicate that the printer can print in duplex. NPS will print duplex
only if the duplex parameter is specified either on the LPR command or
on the Virtual Printer on the NPS controller.
The LPR command is generated internally by OS/400 using the remote
output queue attributes.
NOTE: Once you specify the duplex parameter, all jobs, including
simplex jobs, will print at the duplex speed.
Specifying the duplex parameter in the remote output queue
To specify the duplex parameter in the remote output queue, perform
these steps:
Step 1.
End the remote writer by issuing the ENDWTR command.
Step 2.
Add the Destination Option 'C(duplex)' to the remote queue by issuing this
command. (Enter the Destination Option in mixed-case, exactly as
shown.)
CHGOUTQ
OUTQ(library-name/outq-name)
DESTOPT('C(duplex)')
where
library-name
The name of the XDPE/400 application library.
outq-name
The name of the remote output queue.
If the remote output queue has other values already defined for the
Destination Option, you must specify the new value and any other
value(s) in DESTOPT. Each value must be separated by at least one
space. For example, if the destination option “XAIX” is already specified
for the remote output queue, and now you want to specify the duplex
parameter, you would issue this command:
CHGOUTQ
OUTQ(library-name/outq-name)
DESTOPT('C(duplex) XAIX')
Printing Documents with XDPE/400 (9/2001)
26-9
Troubleshooting
Specifying a Virtual Printer
To create a Virtual Printer for duplex on the NPS printer controller,
perform one of these actions:
•
If your OS/400 output queue is defined with Destination Option
'C(duplex)', issue this command:
Create Virtual Printer printer-name
where printer-name is the name of your Virtual Printer.
•
If your OS/400 output queue is not defined with Destination Option
'C(duplex)', issue these commands:
Create Virtual Printer printer-name
Change Virtual Printer printer-name Plex duplex
where printer-name is the name of your Virtual Printer.
Jobs sent to network printers do not print some special
characters
In order to get the special characters to print, modify your workstation
customizing object as follows:
Step 1.
Create a new workstation customizing object by making a copy of one of
the default workstation customizing objects supplied with XDPE/400,
which are located in the SAMPLE source file in the XDPE/400 application
library. Use a different name than the original for the new object. Only
make modifications to the new object, not the original. The default
WSCST options for PCL are:
WSCST
Step 2.
Printers
XWSCSTN32
N32, N24, and DP65 printers in PCL mode
XWSCST4220
•
NPS and DocuSP printers when the
XTICKET Suppress PCL option is set
to *NO
•
All other network PCL printers
Delete this DFTASCCP parameter from the transformation table:
:DFTASCCP
ASCIICP= xxxx.
where
xxxx
The ASCII code page number.
Printing Documents with XDPE/400 (9/2001)
26-10
Troubleshooting
Step 3.
Enter this command to create the new WSCST in the XDPE/400
application library under the new member name:
CRTWSCST
WSCST(library/object-name)
SRCMBR(*WSCST)
SRCFILE(library/source-filename)
AUT(*USE)
REPLACE(*YES)
where
library
The name of the XDPE/400 application library is
XDPEvrm, where
•
•
•
object-name
v is the version number
r is the release number
m is the modification number
Name of new workstation customizing object.
source-filename Name of the source file where the new workstation
customizing source is located.
Step 4.
Specify the new object name in the Workstation customizing object
(WSCST) Monitor Queue parameter.
Step 5.
Rerun your print job. Refer to OS/400 Workstation Customization
Programming for more information about how to create and use
workstation customizing objects.
Problems using three-hole paper with 4220/4230 printers
If you are printing on three-hole punched paper to a 4220 or 4230 printer
and your jobs print on the opposite side as the holes, try one of these
solutions to correct the problem:
•
Change the direction the paper is loaded in the printer. If the paper is
loaded so that the holes are on the left side of the drawer, turn the
paper around so that the holes are on the right side.
•
Change the Invert Duplex Printer Direction option on your printer.
Refer to the Xerox MRP Family 4220/MRP, 4230/MRP System
Administrator Guide for instructions.
•
If you are running in Direct or Combined mode with no packet or with
a packet where the Page orientation (ORIENT) printer file parameter
is set to *NONE, specify a packet with explicit orientation:
ORIENT(*COR), ORIENT(*PORT), ORIENT(*IPORT),
ORIENT(*LAND), and ORIENT(*ILAND).
Printing Documents with XDPE/400 (9/2001)
26-11
Troubleshooting
•
If you are running in Combined or Indirect mode with the Degree of
page rotation (PAGRTT) printer file parameter set to *AUTO, try one
of the following:
—
—
Modify a copy of the workstation customizing object
XWSCST4220. Do not modify the original workstation
customizing object included with XDPE/400. Source copies of
the transform tables included with XDPE/400 are located in the
SAMPLE database file in the XDPE/400 application library.
Refer to OS/400 Workstation Customization Programming for
more information about how to create and use these objects.
Make these changes to your copy of XWSCST4220:
•
In the :PRTORIENT ORIENT=LANDSCAPE section, change
DATA ='1B266C334F'X to DATA ='1B266C314F'X
•
In the :PRTORIENT ORIENT=RTT270 section, change
DATA ='1B266C314F'X to DATA ='1B266C334F'X
Specify a specific page orientation. This will put your job in
multi-up processing mode so the orientation is controlled by the
multi-up packets, which you can customize.
•
For portrait, specify PAGRTT(0) or PAGRTT(180)
•
For landscape, specify PAGRTT(90) or PAGRTT(270)
Considerations when using generic packets
If you use generic packets, you must reset all appropriate parameters,
either within the generic packet or in a generic packet in the beginning of
the next page.
Example
The job level PCL packet does not specify any font attributes but specifies
that the generic PCL packet be invoked via PAGE boundary. However,
because no font attributes are specified in the job level PCL packet, the
default font (ROMAN8 FIXED) is selected.
In the generic PCL packet, the following font attributes are specified:
•
•
Hex x'1B2838' or ASCII Esc(8
(Symbol Set of Roman8)
Hex x'1B2873313648' or ASCII Esc(s16H
(Pitch of 16)
The expected output is as follows: the top of page 1 will use the default
font, and the bottom of page 1 will use the 16 pitch font. Page 2 and
subsequent pages will print identically to page 1.
Printing Documents with XDPE/400 (9/2001)
26-12
Troubleshooting
Results
The job prints as follows:
•
The job level PCL packet is used to print the top of page 1 using the
default font.
•
The generic PCL packet is used to print the bottom of page 1 using
the 16 pitch font.
•
The job level PCL packet is used to print the top of page 2 using the
16 pitch font.
•
The generic PCL packet is used to print the bottom of page 2 using
the 16 pitch font.
•
Subsequent pages print using the 16 pitch font.
This output prints in error because the PCL language prints with the active
font until a request is made to switch to a specific font. Therefore, once a
generic packet is invoked in the data stream, all subsequent pages print
with the font attribute specified in the generic packet instead of with the
default font.
NOTE: Because many PCL commands stay active for the duration of
a job unless specifically changed, you should reset all appropriate
parameters to prevent printing errors.
Refer to PCL 5 Printer Language Technical Reference Manual for more
information on using PCL commands.
Solutions
Use one of these three options to prevent this error from occurring:
•
Option 1 — Specify the default font attributes in the job level PCL
packet. This will force the correct font to be selected since the job
level packet resets the default font for printing.
•
Option 2 — Specify the default font attributes at the bottom of the
generic PCL packet. This will force the active font to be the default
font for printing on the next page. This occurs because the default
font for printing is reset before the job level PCL packet is invoked,
therefore making the active font the default font for printing.
•
Option 3 — Specify the default font attributes in the beginning of the
next page via a generic packet using logical page processing. This
will force the active font to be the default font for printing. This
occurs because the default font is reset before the job level PCL
packet is invoked, therefore making the active font the default font
for printing.
Printing Documents with XDPE/400 (9/2001)
26-13
Troubleshooting
Known PCL limitations
If you experience appearance problems with your PCL jobs, you may be
able to produce the desired output by using a generic PCL packet to insert
the appropriate PCL commands into your job. The following sections list
some common appearance problems and their suggested solutions.
The solutions offered here may not be the correct solution for your job.
Before implementing any of these solutions, verify that all the parameters
and settings used to print your job are correct for the output you desire.
These can include:
•
•
•
•
•
•
•
Monitor Queue settings
Global values
Printer file parameters
Packet parameters
Printer defaults
Interface defaults
OS/400 printer emulation mode
Job prints wrong font on 4220 printer using FONT PCL
parameter
When printing a PCL job to a 4220 printer where the Font selection by
attributes (FONT) packet parameter has all of its attributes set, and the
height, style, weight, and typeface attributes are not set to *NONE, the
wrong font is used for the job.
The Font selection by attributes (FONT) PCL packet parameter has seven
attributes:
•
•
•
•
•
•
•
symbol set
spacing
pitch
height
style
weight
typeface
When values other than *NONE are selected for height, style, weight, and
typeface, they override the values set for symbol set, spacing, and pitch.
This causes the wrong font to print. To correct this problem, use one of
these two solutions:
Select *NONE for the height, style, weight, and typeface attributes of the
Font selection by attributes (FONT) PCL packet parameter.
Download a font and assign it a specific font ID using the Page font
selection by ID (FONTID) PCL packet parameter. FONTID is used in place
of the FONT parameter.
Printing Documents with XDPE/400 (9/2001)
26-14
Troubleshooting
Duplex problems on DP65 printer
If you experience duplex problems when printing to a DP65 printer and
you are using banner and/or trailer pages, make sure you have not
specified duplex or tumble duplex for the %XRXrequirements: command
in your extended job ticket packet. You can edit or display the contents of
your extended job ticket packet by using the CHGXTCK command.
The Monitor Queue automatically generates an internal job ticket that
contains the %XRXrequirements: command. Therefore, you do not need
to include this command in your extended job ticket packet. Refer to
“Internal job ticket commands” in chapter 16 for a list of internally created
job ticket commands.
Job ignores margin defined in PCL packet when printing in
*COMBINED with *ATTRIB mode
If your job prints with the MARGIN spool file attribute instead of the
MARGIN PCL packet parameter when Monitor Queue has been started
with the ALWAYS Monitor Queue parameter set to *COMBINED and the
SEQUENCE Monitor Queue parameter set to *ATTRIB, you will need to
specify both a top margin value and a left margin value for the MARGIN
parameter in the PCL packet.
Job ignores top margin defined in PCL packet in *DIRECT
mode when printing spool files created using DDS
While in *DIRECT mode, if your job prints a larger margin than defined in
the PCL packet, you will need to create a generic PCL packet to adjust
the top margin for the extra carriage return/line feed commands generated
by the Host Print Transform (HPT) from the Data Description Specification
(DDS).
The PCL generic packet must contain a PCL Vertical Cursor Position
command with a negative value, which is the number of lines where the
margin prints, less the number of lines specified in the PCL packet Top
margin parameter.
For example, if the job prints with a margin of 8 lines and the PCL packet
Top margin parameter is 6 lines, you would use the value -2. The syntax
of the Vertical Cursor Position command is:
Hex ‘1B 26 61 2D 32 52’ or ASCII (Esc)&a-2R
Refer to the PCL 5 Printer Language Technical Reference Manual for
information on the implementation of PCL commands.
Printing Documents with XDPE/400 (9/2001)
26-15
Troubleshooting
VIPP solutions
This section provides solutions to problems related to the VIPP data
stream:
•
Jobs print with incorrect line spacing
•
Jobs sent to NPS printer shows “ineligible” status
•
DP65 jobs print additional, incomplete copies when using trailer
pages
•
NPS printer will not print duplex
•
LPP duplex jobs print simplex
•
Multiple copy jobs print incorrectly when using trailer pages
Jobs print with incorrect line spacing
VIPP mode jobs may produce pages with incorrect line spacing and
misaligned data. An additional indicator of this problem is the message,
“Overprinting not displayed” occurs when viewing the spool file.
To resolve this situation, add the VIPP command OVERPRINT_on at the
beginning of the JDT for the jobs.
Job sent to NPS printer shows “ineligible” status
A VIPP mode job that uses a DSC packet may show an “ineligible” status
after being transmitted to an NPS printer controller. This situation occurs
when all of the parameters in the %%DocumentMedia statement in your
DSC packet do not have corresponding trays defined on your NPS printer.
For example, if the parameters in your %%DocumentMedia statement
refer to USLetter and USLegal media types, you must have both USLetter
and USLegal trays defined on your NPS printer. Otherwise, the spool file
will reflect an “ineligible” status.
For more information about specifying media in relation to the NPS Set
Tray command, refer to the Xerox DocuPrint Network Printer Series Guide
to Managing Print Jobs.
DP65 jobs print additional, incomplete copies when using
trailer pages
VIPP mode jobs that use trailer pages may produce additional, incomplete
copies when sent to a DP65 printer. In this situation, the job will print from
the beginning to the point of insertion of the trailer page and then start over
again from the beginning. This results in the repeated printing of the first
part of the job; however, the last part of the job never prints.
The first status line of the DocuSP Print Services’ System Administration
window also will display the message “Printing Job jobno: Sets nn of 1
completed....” where jobno is the job number and nn is the number of
copies.
To resolve this situation, remove the VIPP SETPAGESIZE command from
the separator page JDT (XDPSPR.JDT) and download the updated JDT to
the printer controller.
Printing Documents with XDPE/400 (9/2001)
26-16
Troubleshooting
NPS printer will not print duplex
If your NPS printer is running VIPP mode and will not print duplex copies,
you need to provide job level instructions to NPS to indicate that the
printer can print in duplex. NPS will print duplex only if the duplex
parameter is specified either on the LPR command or on the Virtual
Printer on the NPS controller.
The LPR command is generated internally by OS/400 using the remote
output queue attributes.
NOTE: Once you specify the duplex parameter, all jobs, including
simplex jobs, will print at the duplex speed.
Specifying the duplex parameter in the remote output queue
To specify the duplex parameter in the remote output queue, perform
these steps:
Step 1.
End the remote writer by issuing the ENDWTR command.
Step 2.
Add the Destination Option 'C(duplex)' to the remote queue by issuing this
command. (Enter the Destination Option in mixed-case, exactly as
shown.)
CHGOUTQ
OUTQ(library-name/outq-name)
DESTOPT('C(duplex)')
where
library-name
The name of the XDPE/400 application library.
outq-name
The name of the remote output queue.
If the remote output queue has other values already defined for the
Destination Option, you must specify the new value and any other
value(s) in DESTOPT. Each value must be separated by at least one
space. For example, if the destination option “XAIX” is already specified
for the remote output queue, and now you want to specify the duplex
parameter, you would issue this command:
CHGOUTQ
OUTQ(library-name/outq-name)
DESTOPT('C(duplex) XAIX')
Printing Documents with XDPE/400 (9/2001)
26-17
Troubleshooting
Specifying a Virtual Printer
To create a Virtual Printer for duplex on the NPS printer controller,
perform one of these actions:
•
If your OS/400 output queue is defined with Destination Option
'C(duplex)', issue this command:
Create Virtual Printer printer-name
where printer-name is the name of your Virtual Printer.
•
If your OS/400 output queue is not defined with Destination Option
'C(duplex)', issue these commands:
Create Virtual Printer printer-name
Change Virtual Printer printer-name Plex duplex
where printer-name is the name of your Virtual Printer.
LPP duplex jobs print simplex
Some printer control commands may cause a duplex print job to print in
simplex when inserted as part of a true logical processing test where
*ONCE is specified for the Application duration (DURATION) logical
processing packet parameter.
This may occur if there is a conflict between either the DUPLEX_on or
TUMBLEDUPLEX_on VIPP parameter and other VIPP parameters in your
JDTs. To find the parameters in conflict, review the VIPP commands in
these printer controller defaults and JDTs:
1.
General defaults, which can be found in /usr/xgf/src/xgf.def on the
printer controller
2.
Job-level JDTs that were downloaded to the printer controller from
the XDPEFLR/JDTLIB folder
3.
Page-level JDTs that were downloaded to the printer controller from
the XDPEFLR/JDTLIB folder
To resolve the problem, refer to the Xerox Variable Data Intelligent
PostScript PrintWare (VIPP) Reference Manual for any notes or related
commands pertaining to the parameters. If the conflicts between job-level
and page-level JDTs cannot be resolved, move the DUPLEX_on or
TUMBLEDUPLEX_on VIPP parameter from the JDT to the general
defaults on the printer controller.
Printing Documents with XDPE/400 (9/2001)
26-18
Troubleshooting
Multiple copy jobs print incorrectly when using trailer pages
If one of these conditions exist:
•
You are using trailer pages with the Direct or Combined method, and
specify the VIPP SETCYCLECOPY command either in the separator
page JDT (XDPSPR.JDT) or a user-defined JDT.
•
You are using trailer pages with the Indirect or Combined method
and specify the COPIES spool file attribute.
VIPP may ignore VIPP commands once the first copy is generated with a
trailer page. For example, if you specified both the VIPP
SETCYCLECOPY and PORT commands in XDPSPR.JDT but indicated a
landscape orientation for the data stream, the first copy will print in the
correct orientation for the banner, job, and trailer pages. All subsequent
copies may print in portrait orientation for the banner, data, and trailer
pages.
This situation occurs only when using trailer pages on multiple copy jobs.
To resolve this situation, use one of these methods when generating
multiple copy print jobs:
•
Specify the Process separator page (BANNER) Monitor Queue
parameter to not generate trailer pages for multiple copy print jobs.
Specify either the *YES or *NO option; do not use either the *BOTH
or *TRLR option.
•
Remove the SETCYCLECOPY command from the separator page
JDT (XDPSPR.JDT).
NOTE: If you change either XDPSPR.JDT or the user JDT, you must
download the new version to the /usr/xgfc/jdtlib/ directory on the
printer controller before your changes will be in effect. Refer to
chapter 21 for instructions on downloading JDTs.
Printing Documents with XDPE/400 (9/2001)
26-19
Troubleshooting
Printing Documents with XDPE/400 (9/2001)
26-20
27.
27
Messages
This chapter describes how to retrieve messages generated by XDPE/400
and display detailed information about them.
XDPE/400 message details
Detailed information for each XDPE/400 message typically can be found
on the Additional Message Information screen, which is a standard
OS/400 screen. Refer to the IBM publication, OS/400 Advanced Series
System Operation, for detailed information about using this screen.
For XDPE/400-generated messages, the first three characters of the
Message ID value on this screen will contain letters that identify which
XDPE/400 function is generating the message. Table 27-1 lists these
prefixes and the corresponding functionality that generates them.
.
Table 27-1.
Message prefixes/functionality
Prefix
Functionality
CPY
Messages that occur while working with the EDTDJDE copy
function
CRT
Messages that occur while working with the EDTDJDE
create function
DFT
Messages related to default packet handling
DIA
Diagnostic messages
DLT
Messages that occur while working with the EDTDJDE
delete function
DMQ
Messages related to Monitor Queue JOB processing
DPF
Messages related to general Monitor Queue functions
DSP
Messages that occur while working with the EDTDJDE
display function
DXV
Messages related to displaying the version and PTF level of
XDPE/400
EDT
Messages related to general EDTDJDE functions
ELT
Messages that occur while working with the EDTDJDE text
generation function
END
Messages related to the End Monitor Queue function
Printing Documents with XDPE/400 (9/2001)
27-1
Messages
Table 27-1.
Message prefixes/functionality (Continued)
Prefix
Functionality
FRM
Messages related to the Monitor Queue form type
processing function
GBL
Messages related to global values
HPT
Messages related to the use of Host Print Transform
JOB
Messages related to active Monitor Queue jobs
JTK
Messages related to Xerox job ticket packets and VIPP
resources
LOD
Messages related to XDPE/400 installation and
maintenance functions
LPP
Messages related to logical page processing
LST
Messages related to spool file creation, packets, and printer
files
MEM
Messages related to Monitor Queue memory problems
MJB
Messages related to using the WRKMONQ command
MPT
Multi-part processing
MQS
Messages related to multiple Monitor Queue sessions
PRT
Messages that occur while working with EDTDJDE packet
printing
QUE
Messages related to the output queue processing
RNM
Messages that occur while working with the EDTDJDE
packet rename process
RSC
Messages related to printer resource processing
RST
Messages related to the Monitor Queue reset function
VIP
Messages related to VIPP processing functions
WSP
Messages related to the Monitor Queue spool file
processing function
WTR
Messages related to printer writers
XCL
Messages related to DJDE packet handling functions, such
as creating, changing, and deleting packets
XCP
Informational messages related to DJDE packet handling
functions
XCU
Messages related to printer command packet processing
Printing Documents with XDPE/400 (9/2001)
27-2
Messages
Table 27-1.
Message prefixes/functionality (Continued)
Prefix
Functionality
XMT
Messages related to XDPE/400 installation and
maintenance functions
XPL
Messages related to interactive PCL packet commands
XPR
Messages related to general spool file processing tasks
Locating error messages
This section describes how to locate the messages that can be generated
by XDPE/400 and for OS/400 components used by XDPE/400. The types
of messages that can be generated are identified in table 27-2.
Table 27-2 also identifies the commands/locations in which you can find
each message type. The commands/locations are identified for active and
abnormally-ended processes.
An abnormally-ended process is any process whose error severity level
meets or exceeds the default severity level set for the ENDSEV parameter
on the Job Description for your job. XDPE/400 is distributed with the
default job end severity level set to 30. Therefore, a message will appear
in a job log if the severity level is 30 or higher, unless the XDPE/400
default for ENDSEV has been changed on your system. To display the
Job Description for your system, issue the DSPJOBD command.
Table 27-2.
Message type and location
Message location for:
Message type
Active processes
Monitor Queue messages
(XDPE message queue)
Abnormally ended processes
WRKMONQJOB
Monitor Queue messages (job log)
WRKMONQJOB
QUSRSYS/QEZJOBLOG output queue
Writer messages
WRKMONQJOB
QUSRSYS/QEZJOBLOG output queue
On-screen display
and/or
DSPJOBLOG
QUSRSYS/QEZJOBLOG output queue
Interactive session messages
(for example, STRMONQ,
DNLDPCLFNT, CRTVIPRSC)
The procedures for accessing each message location are described
below.
Printing Documents with XDPE/400 (9/2001)
27-3
Messages
Using the WRKMONQJOB command
You can use the WRKMONQJOB command to access XDPE message
queue, Monitor Queue job log, or writer job log. To access these, enter
WRKMONQJOB on the command line.
The Work With XDPE Monitor Queue screen appears:
Work With XDPE Monitor Queue
Position to
. . . . .
_________
Starting characters
Type options, then press Enter.
1=XDPE jobs
7=XDPE messages
Opt
___
2=Change
3=Hold
4=End
8=Application output queue
Library/Queue
TCA49017/OUTQVIPP
Writer
*NONE
Status
DEQW
5=Display
6=Release
9=XDPE output queue
Current/Last Job
Bottom
Parameters or command
===> ______________________________________________________________________
F3=Exit
F4=Prompt
F5=Refresh
F9=Retrieve
F12=Cancel
F22=Printer
From this screen, you can access the queue or job logs by following the
appropriate procedure below.
Accessing the XDPE message queue
Perform these steps to access the XDPE message queue from
WRKMONQJOB:
Step 1.
Select option 7 (XDPE messages) and press ENTER. The Display
Messages screen appears.
Step 2.
On the Display Messages screen, position your cursor under the message
you want to view. Then press F1 to display the Additional Message
Information screen.
Printing Documents with XDPE/400 (9/2001)
27-4
Messages
Accessing the Monitor Queue job log
Perform these steps to access the Monitor Queue job log from
WRKMONQJOB:
Step 1.
Enter option 1 (XDPE jobs) next to any entry and press ENTER.
The Work with Active Jobs screen appears, displaying a list of all active
Monitor Queues and writers.
Work with Active Jobs
CPU %:
.0
Elapsed time:
Type options, press Enter.
2=Change
3=Hold
4=End
8=Work with spooled files
Opt
___
___
___
___
Subsystem/Job
OUTQVIPP
QSPL
DPSRMTQ
PRT010405
00:00:00
S1007C2G
06/30/99 09:08:20
Active jobs:
148
5=Work with
6=Release
13=Disconnect ...
User
XE99999
QSYS
QSPLJOB
QSPLJOB
Type
BCH
SBS
WTR
WTR
CPU %
.0
.0
.0
.0
7=Display message
Function
PGM-MONITORQUE
Status
DEQW
DEQW
EVTW
EVTW
Bottom
Parameters or command
===> ________________________________________________________________________
F3=Exit
F5=Refresh
F7=Find
F10=Restart statistics
F11=Display elapsed data
F12=Cancel
F23=More options
F24=More keys
Step 2.
On the Work with Active Jobs screen, enter option 5 (Work with) in the Opt
column next to the name of the Monitor Queue for which you want to view
messages. Press ENTER to display the Work with Job screen.
Step 3.
On the Work with Job screen, select option 10 (Display job log, if active
or on job queue). Press ENTER to display the Display Job Log screen.
Step 4.
On the Display Job Log screen, press F10 (Display detailed messages) to
display any associated messages. Any detailed messages typically will
appear at the bottom of the output.
Step 5.
To obtain additional message information, position your cursor under the
message in which you are interested. Then press F1 to display the
Additional Message Information screen.
Printing Documents with XDPE/400 (9/2001)
27-5
Messages
Accessing the writer job log
Perform these steps to access the writer job log from WRKMONQJOB:
Step 1.
Enter option 1 (XDPE jobs) next to any entry and press ENTER.
The Work with Active Jobs screen appears, displaying a list of all active
Monitor Queues and writers.
Step 2.
On the Work with Active Jobs screen, enter option 5 (Work with) in the Opt
column next to the name of the writer for which you want to view
messages. Press ENTER.
Either the Work with Remote Writer or Work with Printer Writer screen
appears.
Step 3.
On the screen that appears, press F17 (Writer job) to display the Work
with Job screen.
Step 4.
On the Work with Job screen, select option 10 (Display job log, if active
or on job queue). Then press ENTER to display the Display Job Log
screen.
Step 5.
On the Display Job Log screen, press F10 (Display detailed messages) to
display any associated detailed messages. Any detailed messages
typically will appear at the bottom of the output.
Step 6.
To obtain additional message information, position your cursor under the
message in which you are interested and then press F1 to display the
Additional Message Information screen.
Accessing the on-screen display
XDPE/400 follows OS/400 conventions for any messages that result from
using an interactive command. For example:
•
If you encounter an error while using an interactive command,
XDPE/400 displays a message at the bottom of the screen.
•
If you position your cursor under the message and press F1, the
Additional Message Information screen appears.
Printing Documents with XDPE/400 (9/2001)
27-6
Messages
Accessing DSPJOBLOG
Perform these steps to access DSPJOBLOG (your job log):
Step 1.
On the command line, enter this command and press ENTER:
DSPJOBLOG
The Display Job Log screen appears.
Step 2.
On the Display Job Log screen, press F10 (Display detailed messages).
The Display All Messages screen appears.
Step 3.
On the Display All Messages screen, position the cursor under the
message you want to view. Then press F1 to display the Additional
Message Information screen.
Accessing the QUSRSYS/QEZJOBLOG output queue
Perform these steps to access spool files for jobs (such as Monitor Queue
sessions, writers, or interactive sessions) that have terminated
abnormally:
Step 1.
On the command line, enter this command and press ENTER:
WRKOUTQ QUSRSYS/QEZJOBLOG
The Work with Output Queue screen appears. This screen lists job logs in
order by user id. Job logs for Monitor Queue sessions will have the name
of the monitored output queue in the User Data column, while job logs for
writers will have the name of the writer.
Step 2.
On the Work with Output Queue screen, enter 5 (Display) in the Opt
column next to the job log that you want to view. Press ENTER to display
the Display Spooled File screen.
The Display Spooled File screen is formatted for a 132 column text line.
Therefore, you will have to use the F20 (Right) function key to view the
remainder of a text line if your terminal only supports 80 columns.
Printing Documents with XDPE/400 (9/2001)
27-7
Messages
Printing Documents with XDPE/400 (9/2001)
27-8
Section Four:
Appendices
XDPE/400 User Documentation (9/2001)
A.
A
XDPE/400-supported interface boxes
This appendix provides information about these twinax-to-Xerox printer
interface boxes:
•
•
•
•
•
•
•
•
•
•
3X Twinax Printstation
42XX INTERNAL
4450 INTERNAL
Agile 5250 OPTIMA
BARR
Flex i-data 5250 C/RS-Xerox
IBM AS/400 PC Support or Client Access
Smart
Solimar
Spur/USAll
3X Twinax Printstation interface
You can use the 3X Twinax Printstation (3X) interface box to connect
these printers:
•
Xerox 4030 printer for printing in XDPM mode
•
Xerox 4235 printer to the AS/400 for printing in either XPPM or
XDPM mode
XDPE/400 supports these versions of the 3X Twinax Printstation:
•
Version 1.38FOR/US and later, for resource downloading and
printing in XPPM and XDPM modes
•
Version 1.37FOR/US and earlier, for printing in XPPM and XDPM
modes and for centralized printer resource downloading
For printing in XPPM mode, 3X must be in either GENERIC EBCDIC 5225
mode or GENERIC EBCDIC 5219 mode. Table A-1 shows the 3X switch
settings for XPPM mode.
Table A-1.
3X switch settings for XPPM mode
Mode
1
2
Function (SW0)
3
4
5
6
7
8
Device (SW1)
7
GENERIC EBCDIC 5225
UP DN DN DN UP DN DN DN
UP
GENERIC EBCDIC 5219
DN DN UP DN DN DN UP DN
UP
XDPE/400 User Documentation (9/2001)
A-1
XDPE/400-supported interface boxes
For printing in XDPM mode, 3X must be in either XES ASCII 5225 mode
or XES ASCII 5219 mode. Table A-2 shows the 3X switch settings for
XDPM mode.
Table A-2.
3X switch settings for XDPM mode
1
Mode
2
Function (SW0)
3
4
5
6
7
8
Device (SW1)
7
XES ASCII 5225
DN UP DN DN DN UP DN DN
UP
XES ASCII 5219
DN DN DN DN DN DN DN DN
DN
You also must set the Twinax Printstation address. Table A-3 shows the
correct switch settings for all possible addresses.
Table A-3.
Twinax Printstation address switch settings
Address
Device (SW1)
1
2
3
0
UP
UP
UP
1
UP
UP
DN
2
UP
DN
UP
3
UP
DN
DN
4
DN
UP
UP
5
DN
UP
DN
6
DN
DN
UP
No printer attached
DN
DN
DN
NOTE: If you are using XDPE/400 to print on a Xerox 4235 printer
and the print data contains characters that are not available in the
font, the system overprints all remaining print data. If this occurs, you
must reset the interface box to continue printing.
XDPE/400 User Documentation (9/2001)
A-2
XDPE/400-supported interface boxes
42XX INTERNAL interface
The MRP twinax level 116.040.05 currently is supplied with XDPE/400.
New levels will be made available as they are verified.
Before you load the supplied twinax code into the MRP interface, be
aware of these considerations:
•
You need a PC and a mini-Centronics adapter cable to perform the
upgrade to your interface card.
•
You need to reconfigure the interface card after the upgrade. It is
recommended that you print and save a copy of the Interface
Configuration Report as a reference.
Follow these steps to load the supplied twinax code into the MRP
interface:
Step 1.
Power off the printer.
Step 2.
Install the mini-Centronics cable to the mini-Centronics port on the
interface card.
Step 3.
Connect a standard Centronics cable from the adapter to the PC.
Step 4.
Power on the printer.
Step 5.
At the PC, enter this command:
COPY disk-drive-letter: 11604005.XTX LPT1: /B
After the file has been copied to the printer, the LED on the interface
board starts blinking.
Step 6.
Power the printer off and then on again.
Your Interface Configuration Report will show 116.040*05 as the firmware
version. Ignore any error sheets that are printed on the first power-on after
loading new firmware. The system generates these sheets when it
recognizes the new software.
Note these considerations when using the 42XX INTERNAL interface at
this firmware level:
•
The twinax 116.040.05 adds an extra line at the top of a page when
receiving XDPE/400-generated commands.
•
The default setting of the output destination tray for the twinax level
116.040.05 is output destination 2, which is the face-up tray on a
4220. To change the output destination tray, refer to the “FSL Y11 —
Set default paper path support in twinax” section in Xerox 4220/MRP
Family Documentation Addendum (publication 720P13501).
XDPE/400 User Documentation (9/2001)
A-3
XDPE/400-supported interface boxes
4450 INTERNAL interface
The Xerox 4450 twinax-attached printer processes IBM AS/400 print data
streams with optional externally embedded DJDE commands. You can
configure the 4450 with normal mode processing (to create printer DJDE
commands from IBM SCS commands) or pass-through mode processing
(to pass the data without additional DJDE printer commands).
The 4450 and XDPE/400 are designed to work together. When you start
the XDPE/400 Monitor Queue, you must specify the printer’s processing
mode. Differences in printer modes affect how the page rotation,
multiple-up, and font ID spool file attributes are processed. In normal
mode, the font ID and multiple-up fields are not processed. The page
rotation attribute is mapped to a PMODE DJDE command.
Refer to Xerox 4450/MRP Product Reference for further information.
Agile 5250 OPTIMA interface
The Agile 5250 interface (minimum level, version 5.08B) connects Xerox
decentralized printers to twinax environments for printing and resource
downloading in both XPPM and XDPM modes.
XPPM mode
To use the Agile 5250 OPTIMA interface in XPPM mode, set up the Agile
5250 with these parameters:
•
Twinax port settings
—
—
•
Emulation option: IBM5225
Mode option: 275 Emulation
Special options for the Xerox printers
—
Turn off automatic UDK translation:
UDK XLT=NOUDK XLT
—
Suppress automatic PFS command generation:
PFSSPRS=SUPPRESS
•
Parallel port settings
—
Load the 4235PPM printer configuration from the interface
floppy disk:
LOAD>__4235PPM
Set up your printer file with the Width--positions per line subparameter of
the Page size (PAGESIZE) printer file parameter set to 70 or the
maximum length of your largest DJDE record, whichever is greater.
If you are using a 4235 printer, enable these options on the printer:
•
•
•
•
•
Elixir Form Download — AC
EBCDIC Parallel Meta/GHO Enabler — IB
GHO Application Processing — MP
Blank Lines with Fontindexing — FI
Prohibit Blank Page Before Banner — BC
XDPE/400 User Documentation (9/2001)
A-4
XDPE/400-supported interface boxes
XDPM mode
To use the Agile 5250 OPTIMA interface in XDPM mode, set up the Agile
5250 with these parameters:
•
Twinax port settings
—
—
•
Emulation option: IBM3812 or IBM5225
Mode option: IBM Emulation
Special options for the Xerox printers
—
Turn on automatic UDK translation:
UDK XLT=XLT UDKS
—
Suppress automatic PFS command generation:
PFSSPRS=AUTOSPRS/BU
•
Parallel port settings
—
Load the 4235ASC printer configuration from the interface
floppy disk:
LOAD>__4235ASC
—
Delete the PFS strings for job start, job end, and time out:
PFSINFO>JOBSTRT>END
PFSINFO>JOBEND>END
PFSINFO>TIMEOUT>END
NOTE: If you are using an Agile 5250 OPTIMA with XDPE/400 to print
on a Xerox 4235 printer and the print data contains characters that
are not available in the font, the system inserts spaces where the
characters should appear.
XDPE/400 User Documentation (9/2001)
A-5
XDPE/400-supported interface boxes
BARR interface
The BARR interface is a twinax connection that connects centralized
printers to network, mainframe, and twinax environments for printing and
resource downloading in XPPM mode. The BARR interface also allows
remote print job spooling and job queue management.
To use the BARR interface with XDPE/400, order BARR/SPOOL or
BARR/RJE with the PRINT/TWINAX and the PRINT370 option release
90D29.
Perform these steps to use the BARR/Twinax interface:
Step 1.
Configure the BARR/Twinax interface as follows:
•
•
•
5250 description settings
—
Set the Receiving BARREOF end of file string to YES.
—
Set the Xerox XDPE/400 package installation AS/400 to YES.
—
Leave other options within the 5250 description setup at default
interface settings unless changes were made to the PC adapter
card during installation.
Adapter description
—
Set the Printer Emulation to 5225 for all printer sessions
defined.
—
Set the PC Printer Type to Line Printer for all printer sessions
defined.
—
Leave other options within the Adapter description setup at
default interface settings unless changes were made to the PC
adapter card during installation.
S/370 channel-attached printer
—
Set the address of the centralized printer from the menu options.
—
Select Set Printer Options.
—
Set the Modify Advanced printer options to YES.
—
On the Advanced Printer Options menu, set the Pad Zero
Length Records to NO, and the Pad Zero Length Skip to
Channel 1 to ALWAYS.
NOTE: This is the recommended setting. However,
unpredictable results may occur, and effects may vary with each
application.
XDPE/400 User Documentation (9/2001)
A-6
XDPE/400-supported interface boxes
•
Assign devices (for the Twinax Printer to Spool settings)
—
Do not specify a fixed spool file name.
—
Select Options from the menu line at the bottom of the Assign
Devices menu. The available options will be displayed. Set the
Output Statement Used in the File option to YES.
NOTE: XDPE/400 generates a BARR OUTPUT statement that
provides the BARR with information for spool file management.
When the Output Statement Used in the File option is set to
YES, BARR will extract this statement from the file and place it
in the file header. If the option is set to NO, BARR will ignore the
statement and it will be printed. For use with XDPE/400, the
setting of YES is recommended for the Twinax Printer to Spool
settings.
Step 2.
Start Monitor Queue with these options:
•
Set the Interface box (INTERFACE) parameter to *BARR.
•
Set the Xerox interface mode (XINTMODE) parameter to
*PASSTHRU.
Refer to the BARR/Twinax documentation for any release-specific
updates or further recommendations.
XDPE/400 User Documentation (9/2001)
A-7
XDPE/400-supported interface boxes
Flex i-data 5250 C/RS-Xerox interface
XDPE/400 has been tested against XEROX-Flex 3X-400 firmware version
121.032, and supports printing and resource downloading in both XPPM
and XDPM mode.
The device address switches available are 00 and 05, with 00 as the
default; each specifies emulation of these IBM printers:
•
•
•
5219
3816
3812
Table A-4 shows the recommended defaults to use with XDPE/400.
Table A-4.
No.
i-data default settings
Function name
Default setting
2
LPI
6
3
CPI
10
10
Orientation
COR
36
Suppress SES control
0
37
IBM Printer Emulation Select
3812/5219/3816
88
Physical Margins
+0,-480,+0,-480,+0,-480
98
Orientation select
Automatic
XDPE/400 provides two initialization options for the Flex box:
•
•
Initialize to the appropriate mode when printing
Do not initialize to the appropriate mode
The initialization sequence used depends on the Set interface mode
(INTFINIT) Monitor Queue parameter and on the printing mode.
Table A-5 shows the relationship between the STRMONQ parameters
and the Flex box initialization sequence that is used. Whenever
XDPE/400 downloads an XPPM mode resource through a Flex box, the
Flex box is initialized with a Y70,2.
Table A-5.
Flex box initialization sequence
Set interface mode
(INTFINIT)
XPPM
XDPM
*NO
No initialization sequence
No initialization sequence
*YES
Y70,2
Y70,1
XDPE/400 User Documentation (9/2001)
A-8
XDPE/400-supported interface boxes
XDPE/400 sends a reset FSL command (%X4) to the Flex i-data interface
after processing each spool file. Note these considerations:
•
If you have made changes to the default interface settings in a spool
file and want those changes to remain in effect for subsequent spool
files, each subsequent spool file must also contain those changes.
•
To make any permanent (session level) setting changes to the Flex
i-data interface, you must do so before starting a Monitor Queue
session.
XPPM considerations
If you use the 4235 printer in XPPM mode with the Flex i-data 5250
C/RS-Xerox interface, you must enable these options on the printer:
•
•
•
•
•
Elixir Form Download — AC
EBCDIC Parallel Meta/GHO Enabler — IB
GHO Application Processing — MP
Blank Lines with Fontindexing — FI
Prohibit Blank Page Before Banner — BC
XDPM considerations
With this interface, if XDPE/400 is controlling the tray selection via XES
packets or spool file attributes and you want to produce duplex output,
both the XES packet and the spool file (printer file) tray settings must
match. Because of this, it is recommended that the tray selection be made
by the interface box rather than using XDPE/400.
To control tray selection during duplex printing using XDPE/400, you must
synchronize both the printer file and XES packet tray parameters. The
printer file parameter is DRAWER (n), where n is either the drawer
number or *E1 for the envelope feeder. The XES packet parameter is
TRAY (*TRAYn), where n is the tray number.
If you choose to set tray selection using the interface box, use this
procedure:
Step 1.
Create a Flex i-data function 11 command to specify tray selection. The
command must be included in the spool file before any printable data.
This example selects tray 3:
&&??%
%Y11,6%
&&??
1First line of print data . . . ,
where
&&??%
Sets a temporary i-data escape character. The % can be a
special character of your choice.
%Y11,n%
The function 11 command where n is 2 for tray one, 3 for tray
two, or 6 for tray three. % is the temporary escape character
defined in the first command.
&&??
Resets the temporary i-data escape character. Note the
command is five characters long and the underscore
following the second question mark specifies a blank
(required).
XDPE/400 User Documentation (9/2001)
A-9
XDPE/400-supported interface boxes
Step 2.
Specify the default tray selection parameters for XDPE/400, both in the
printer file and in the XES packet as follows:
•
In the printer file, specify:
DRAWER=*SAME
•
In the XES packet, do not include a tray parameter
Refer to the i-data XES/PCL Twinax Interface Controller for Xerox
Printers User's Guide and the i-data Twinax XES/PCL Interface Controller
for Xerox Printers Programmer's Guide for more information.
For an XES job, if:
•
You have specified *YES or *TUMBLE for the Print on both sides of
sheet (DUPLEX) parameter
•
You have specified a format number for the 4235 Page format
(FORMAT) parameter
•
Your printer is connected via an i-data interface
You also must specify these items:
•
Specify a “dummy” Generic XES (GENXES) packet name; this
packet can be empty
•
Specify *PAGE for the GENXES Generic XES Invocation type
parameter
•
Specify *YES for the GENXES Generic XES Interface formatting off
parameter
IBM AS/400 Client Access interface
The IBM Client Access interface supports Xerox printers that are attached
to a PC parallel port or are connected on a network from a PC. When you
use this interface, job level commands, printer resources, and arbitrary
printer control commands are conditioned for Xerox printers that are
attached via the parallel port.
The settings below are examples of how you can configure a Xerox 4213
printer session for XDPE/400 using Client Access. Other configurations
are possible and are supported. Refer to your local AS/400 System
Administrator for assistance.
Select Printer Model panel Printer manufacturer
Printer Model
Personal Printer Options panel
Printer function table file name
Printer alarm
Begin printer session suspended
Form feed on suspend
Initial font
Prompt to change font
Network printing
Initial paper handling equipment
Continuous forms width
Number of cut sheet drawers
Form size control
Envelope hopper
Automatic print adjustment
XDPE/400 User Documentation (9/2001)
9. Other
User-defined, non-laser printer
C:\PCS\DEFAULT.PFT
No
No
No
[0B] Courier 10
No
No
Cut sheet
13.2 inches
2
None
No
No
A-10
XDPE/400-supported interface boxes
Smart interface
XDPE/400 supports printing and resource downloading on the Smart
interface at the 950614-1000 firmware level. Refer to the Smart reference
manual to set up the Smart interface.
Solimar interface
XDPE/400 supports printing and resource downloading on the Solimar
SRx5219 version 1.53 and on the Solimar SRx5225 version 2.42.
XDPE/400 supports printing on the Solimar SRx5219 version 1.52 and
earlier and on the Solimar SRx5225 version 2.41 and earlier.
Table A-6 shows the required parameters for the Xerox printer when using
XDPE/400 with the Solimar SRX5219.
Table A-6.
Xerox printer parameters for the Solimar interface
Parameter
XDPE/400
Xerox printer
Solimar
RSTACK string
A text string that matches a valid
DJDE END/ sequence for the
IDEN setup for this XDPE/400.
Replace the blanks between the
IDEN prefix and the END; with “X”.
Same as Solimar
Same as the printer
RSTACK offset
Same as IDEN offset
Same as Solimar
Same as the printer
IDEN prefix
Same as printer and Solimar
Same as XDPE/400 and
Solimar
Same as printer and
XDPE/400
IDEN offset
Same as printer and Solimar
Same as XDPE/400 and
Solimar
Same as printer and
XDPE/400
IDEN skip
Same as printer and Solimar
Same as XDPE/400 and
Solimar
Same as printer and
XDPE/400
Xerox XDPE/400 supports the Solimar control mode (SOLIMODE) global
value. This global value controls the insertion of Solimar-specific control
strings into the print data stream. For more information about Solimar
XDPE/400 support or details on using this feature, contact:
Solimar Systems, Inc.
1215 Second Avenue
San Diego, California 92101
619.849.2800
Facsimile: 619.849.2801
http:\\www.SolimarSystems.com
If you use this feature with a Solimar interface that does not support it,
extraneous print lines will appear in the output.
XDPE/400 User Documentation (9/2001)
A-11
XDPE/400-supported interface boxes
Spur/USAII interface
XDPE/400 supports printing and resource downloading on the Spur/USAII
interface. Refer to the USAII reference manual to set up the Spur/USAII
interface.
When using the Spur/USAII interface box to print XPPM (DJDE) jobs, the
Width (positions per line subparameter of the Page size (PAGESIZE)
printer file parameter) must be set to 70 or the maximum length of your
largest DJDE record, whichever is greater.
XDPE/400 User Documentation (9/2001)
A-12
B.
B
XDPE/400 distributed samples and
resources
This appendix lists the samples and resources distributed with XDPE/400.
Samples are located in the XDPE/400 application library and resources
are located in the XDPEFLR resource folder.
CAUTION: If you want to modify any of these distributed samples or
resources, make a copy and modify the copy, not the original. Any
changes made to these objects may be lost during the application of
maintenance or when upgrading to a new version of XDPE/400.
SAMPLE file contents
The SAMPLE file contains these members:
•
$READ_ME — Xerox disclaimer notice
•
BANNER — OS/400 writer-style separator page
•
BANXDPEN — XDPE/400 standard separator page
•
BANXDPES — XDPE/400 italic-style separator page
•
DSCMEDIA — Sample PostScript DSC statements for media type
•
DSCSIZE — Sample PostScript DSC statements for page size
•
TRLXDPEN — XDPE/400 trailer page
•
XWSCSTN32 — PCL workstation customizing source
•
XWSCSTSUP — PCL workstation customizing source
•
XWSCSTVIPP — PostScript workstation customizing source
•
XWSCST4220 — PCL workstation customizing source
•
EWSCSTN32 — Euro-capable PCL workstation customizing source
•
EWSCSTSUP — Euro-capable PCL workstation customizing source
•
EWSCST4220 — Euro-capable PCL workstation customizing source
XDPE/400 User Documentation (9/2001)
B-1
XDPE/400 distributed samples and resources
XDPEFLR resource folder
The XDPEFLR resource folder, both the letter and A4 versions, contains
these subfolders:
•
COLOR — Color palette packets (empty)
•
DJDE — DJDE packets
•
ENCODING — VIPP encoding tables (empty)
•
FONTS — DJDE fonts
•
FORMLIB — VIPP forms and segments
•
FORMS — DJDE forms
•
FSL — DJDE source FSLs
•
GENPCL — Generic PCL packets (empty)
•
GENXES — Generic XES packets (empty)
•
IMAGES — DJDE images (empty)
•
IMGLIB — VIPP images (empty)
•
JDL — DJDE JDLs
•
JDTLIB — VIPP JDTs
•
JSL — DJDE source JSLs
•
LOGOS — DJDE logos (empty)
•
LPP — Logical processing packets (empty)
•
MISLIB — VIPP core and setup files, PostScript fonts, and
PostScript DSC packets
•
PCL — PCL packets
•
PCLFONTS — PCL fonts
•
PCLMAC — PCL macros
•
PCLMUP — PCL multi-up packets
•
PDL — PDL objects (CMEs, PDEs, TSTs)
•
RSCLIST — Resource lists (empty)
•
XES — XES packets
•
XESFONTS — XES fonts
•
XESFORMS — XES forms
•
XESMUP — XES multi-up packets
•
XMPT — Multi-part packets (empty)
•
XTICKET — Extended job ticket packets (empty)
XDPE/400 User Documentation (9/2001)
B-2
XDPE/400 distributed samples and resources
XDPEFLR contents (letter version)
Table B-1 lists the contents of the letter version of the XDPEFLR resource
folder.
Table B-1.
XDPEFLR letter contents
Subfolder
Resource
DJDE
XIVP
FONTS
LPI08L.FNT
LPI12L.FNT
LPI12P.FNT
LPI16L.FNT
LPI16P.FNT
L0112B.FNT
P07TYA.FNT
XGB10L.FNT
XGB10P.FNT
XGB20L.FNT
XGB20P.FNT
XGT30L.FNT
XGT30P.FNT
FORMLIB
XDPBCK.FRM
XDPIVP.FRM
XDPLPJOB.FRM
XDPLPPGE.FRM
XDPSMP.FRM
FORMS
FORLAN.FRM
FORPOR.FRM
ONELAN.FRM
ONEPOR.FRM
TWOLAN.FRM
TWOPOR.FRM
FSL
FORLAN.FSL
FORPOR.FSL
ONELAN.FSL
ONEPOR.FSL
TWOLAN.FSL
TWOPOR.FSL
JDL
XDPE.JDL
JDTLIB
XDPLPJOB.JDT
XDPLPPGE.JDT
XDPSMP.JDT
XDPSPR.JDT
XIVP.JDT
JSL
PDESRC.JSL
PDESR2.JSL
XDPE.JSL
MISLIB
XGF.DEF
PCL
XIVP
XDPE/400 User Documentation (9/2001)
B-3
XDPE/400 distributed samples and resources
Table B-1.
XDPEFLR letter contents (Continued)
Subfolder
Resource
PCLFONTS
LPI08L.FLJ
LPI12L.FLJ
LPI12P.FLJ
LPI16L.FLJ
LPI16P.FLJ
L0112B.FLJ
P07TYA.FLJ
XGB10.HPL
XGB10.HPP
XGB10L.FLJ
XGB10P.FLJ
XGB20L.FLJ
XGB20P.FLJ
XGT15L.FLJ
XGT18P.FLJ
XGT24L.FLJ
XGT24P.FLJ
XGT30.HPL
XGT30.HPP
XGT30L.FLJ
XGT30P.FLJ
PCLMAC
XFORM1
XFORM2
PCLMUP
L1XEROX
L16XEROX
L2EURO
L2XEROX
L24XEROX
L33XEROX
L4XEROX
L8XEROX
P1XEROX
P16XEROX
P2EURO
P2XEROX
P24XEROX
P33XEROX
P4XEROX
P8XEROX
PDL
FORLAN.PDE
FORPOR.PDE
ONELAN.PDE
ONEPOR.PDE
TWOLAN.PDE
TWOPOR.PDE
XES
XIVP
XDPE/400 User Documentation (9/2001)
B-4
XDPE/400 distributed samples and resources
Table B-1.
XDPEFLR letter contents (Continued)
Subfolder
Resource
XESFONTS
KOSMOS8.FNT
KOSMOS8L.FNT
LPI08L.FNT
LPI12L.FNT
LPI12P.FNT
LPI16L.FNT
LPI16P.FNT
L0112B.FNT
P07TYA.FNT
XGB10L.FNT
XGB10P.FNT
XGB20L.FNT
XGB20P.FNT
XGT30L.FNT
XGT30P.FNT
XESFORMS
XFORM1.FRM
XFORM2.FRM
XESMUP
L1XEROX
L16XEROX
L2XEROX
L24XEROX
L33XEROX
L4XEROX
L8XEROX
P1XEROX
P16XEROX
P2XEROX
P24XEROX
P33XEROX
P4XEROX
P8XEROX
XDPE/400 User Documentation (9/2001)
B-5
XDPE/400 distributed samples and resources
XDPEFLR contents (A4 version)
Table B-2 lists the contents of the A4 version of the XDPEFLR resource
folder.
Table B-2.
XDPEFLR A4 contents
Subfolder
Resource
DJDE
XIVP
FONTS
LPI08L.FNT
LPI12L.FNT
LPI12P.FNT
LPI16L.FNT
LPI16P.FNT
L0112B.FNT
P07TYA.FNT
XGB10L.FNT
XGB10P.FNT
XGB20L.FNT
XGB20P.FNT
XGT30L.FNT
XGT30P.FNT
FORMLIB
XDPBCK.FRM
XDPIVP.FRM
XDPLPJOB.FRM
XDPLPPGE.FRM
XDPSMP.FRM
FORMS
FORLAN.FRM
FORPOR.FRM
ONELAN.FRM
ONEPOR.FRM
TWOLAN.FRM
TWOPOR.FRM
FSL
A4FORL.FSL
A4FORP.FSL
A4ONEL.FSL
A4ONEP.FSL
A4TWOL.FSL
A4TWOP.FSL
FORLAN.FSL
FORPOR.FSL
ONELAN.FSL
ONEPOR.FSL
TWOLAN.FSL
TWOPOR.FSL
GENXES
CR
JDL
XDPE.JDL
JDTLIB
XDPLPJOB.JDT
XDPLPPGE.JDT
XDPSMP.JDT
XDPSPR.JDT
XIVP.JDT
XDPE/400 User Documentation (9/2001)
B-6
XDPE/400 distributed samples and resources
Table B-2.
XDPEFLR A4 contents (Continued)
Subfolder
Resource
JSL
A4PDESRC.JSL
PDESRC.JSL
PDESR2.JSL
XDPE.JDL
MISLIB
XGF.DEF
PCL
XIVP
PCLFONTS
LPI08L.FLJ
LPI12L.FLJ
LPI12P.FLJ
LPI16L.FLJ
LPI16P.FLJ
L0112B.FLJ
P07TYA.FLJ
XGB10.HPL
XGB10.HPP
XGB10L.FLJ
XGB10P.FLJ
XGB20L.FLJ
XGB20P.FLJ
XGT15L.FLJ
XGT18P.FLJ
XGT24L.FLJ
XGT24P.FLJ
XGT30.HPL
XGT30.HPP
XGT30L.FLJ
XGT30P.FLJ
PCLMAC
XFORM1
XFORM2
PCLMUP
L1XEROX
L16XEROX
L2EURO
L2XEROX
L24XEROX
L33XEROX
L4XEROX
L8XEROX
P1XEROX
P16XEROX
P2EURO
P2XEROX
P24XEROX
P33XEROX
P4XEROX
P8XEROX
PDL
FORLAN.PDE
FORPOR.PDE
ONELAN.PDE
ONEPOR.PDE
TWOLAN.PDE
TWOPOR.PDE
XDPE/400 User Documentation (9/2001)
B-7
XDPE/400 distributed samples and resources
Table B-2.
XDPEFLR A4 contents (Continued)
Subfolder
Resource
XES
XIVP
XESFONTS
KOSMOS8.FNT
KOSMOS8L.FNT
LPI08L.FNT
LPI12L.FNT
LPI12P.FNT
LPI16L.FNT
LPI16P.FNT
L0112B.FNT
P07TYA.FNT
XGB10L.FNT
XGB10P.FNT
XGB20L.FNT
XGB20P.FNT
XGT30L.FNT
XGT30P.FNT
XESFORMS
XFORM1.FRM
XFORM2.FRM
XESMUP
L1XEROX
L16XEROX
L2XEROX
L24XEROX
L33XEROX
L4XEROX
L8XEROX
P1XEROX
P16XEROX
P2XEROX
P24XEROX
P33XEROX
P4XEROX
P8XEROX
XDPE/400 User Documentation (9/2001)
B-8
C.
C
Processing notes
This appendix provides information about the implementation of multiple
up (multi-up) processing, logical processing, and color processing relative
to spooled file decomposition.
Spool file scanning
When performing logical processing, color processing, or multi-up
processing, Monitor Queue processes most or all of the characters in the
spool file. This appendix describes the mechanism used for this
processing.
The scanning of the spool file is covered in terms of a virtual process.
Table C-1 shows the variables used by this process.
Table C-1.
Spool file decomposition process variables
Process variables
Description
currentpage
The number of the page currently being processed. Corresponds to the page
number in the spool file. Page numbers count from one.
currentphysicalpage
The enumerated value (page number) of a collection of logical pages that are
printed on a single side of a page.
currentphysicalpage = ((currentpage - starting page) / (number of logical pages
per physical page)) + 1.
currentlogicalpage
Only used in multi-up processing. This is the page number of the currentpage
when mapped onto the currentphysicalpage.
currentlogical page = ((currentpage - starting page)% (number of logical pages
per physical page)) +1.
currentline
The line on which the current data is printed. currentline counts from one.
currentposition
The character position in the line currently being processed.
XDPE/400 User Documentation (9/2001)
C-1
Processing notes
SCS commands
Table C-2 lists the SCS commands that are processed. All other SCS
commands and non-printable data are ignored.
Table C-2.
SCS commands
SCS command
1
Command
name
Processed
by 1
Processing description
03 nn
ATRN
ASCII transparency
logical, color,
multi-up
The 03 and the following nn characters are
ignored.
05
HT
Horizontal tab
logical
If tabs are defined, blank fills to the next tab
position; if there is no next tab, blank fills to the
next character position congruent to zero
module 5.
06
RNL
required new line
logical, multiup
Treated as a new line (NL).
0C
FF
form feed
logical, multiup
Process current line currentline=1
currentposition=1
0D
CR
carriage return
logical, multiup
Process current line currentposition=1
15
NL
new line
logical, multiup
Process current line currentline=currentline +
1 currentposition=1
16
BS
Back space
logical
If currentposition>1,
currentposition=currentposition-1
1A
UBS
unit back space
logical
Treated as a backspace (BS).
1E
IRS
Interchange record
separator
logical, multiup
Treated as a new line (NL).
25
LF
line feed
logical, multiup
Process current line currentline=currentline +1
2B D2 nn 01 ff
al tabs
STAB
set horizontal tabs
logical
Only floating tabs (character position as
opposed to fixed position tabs) are supported.
2D D2 nn 2D cc
SPC
set presentation color
color
Removes the SPC SCS command from the
print data stream, creates an “ink change” XES
command, and inserts it into the print data
stream.
33
IRT index return
logical, multiup
Treated as a new line (NL).
34 C0 ah
AHPP absolute
horizontal
presentation position
logical, color,
multi-up
Process line. If ah=0 or ah is after the last line
on page, do nothing. If ah < currentline,
currentpage=currentpage + 1.
logical=logical processing; color=color processing; multi-up=multiple up processing
XDPE/400 User Documentation (9/2001)
C-2
Processing notes
Multi-up processing
Multi-up processing is designed to support print data streams intended for
IBM 5225 or 5219 printers. The only SCS commands supported are CR,
LF, AVPP, AHPP, RVPP, and RHPP. All other SCS commands are
ignored by Monitor Queue in XES/PCL multi-up mode.
Multi-up processing is implemented by extracting the printable data from
the spooled file, recreating the line positioning commands, and then
writing a new spooled file.
Logical processing and color processing
Logical processing by itself and logical processing with color processing
involves the extraction of the print data lines from the SCS print data
stream for testing. The data is extracted and the print lines are
reconstructed because there may be embedded SCS commands that
interfere with the test. The line numbers must also be tracked because the
logical processing tests are sensitive to both character position and line
number.
Color processing
Color processing is performed without consideration of line and character
positioning. For color processing, each character in the SCS print data
stream is examined for an SCS set presentation color (SPC) command.
When a command is found, it is replaced with the appropriate XES color
command. Only the SCS commands are recognized and are skipped.
Otherwise, a portion of an SCS command might look like the start of an
SPC command.
XDPE/400 User Documentation (9/2001)
C-3
Processing notes
XDPE/400 User Documentation (9/2001)
C-4
D.
D
SCS commands for the 5225 and
5219 printers
Monitor Queue creates SCS commands for DJDE, XES, and PCL that are
based on the attributes of the application spool file. It can insert the SCS
commands before your application data for the IBM 5225 and the IBM
5219 IBM printer emulation. This allows you to print spool files just as you
would without XDPE/400. You can control the type of emulation required
for the Xerox printers. Optionally, you can disable the insertion of SCS
commands by the Monitor Queue by selecting the *NOSCS value for the
Printer emulation (PRTTYPE) Monitor Queue parameter.
SCS commands
Table D-1 lists the SCS commands created by XDPE/400. The table also
includes the printer emulation mode for each command and the printer file
parameter on which each command is based.
.
Table D-1.
SCS commands
SCS command name
5225
5219
Absolute vertical
X
Set initial condition
X
Set justify mode
X
Set line spacing
X
Set horizontal margin
X
Set horizontal tab
X
Set text orientation
X
XDPE/400 User Documentation (9/2001)
Parameter(s)
Justify
Value(s)
0
50
100
Record length CPI
PAGRTT
*AUTO
*DEVD
*COR
0
90
180
270
D-1
SCS commands for the 5225 and 5219 printers
Table D-1.
SCS commands (Continued)
SCS command name
5225
Set page presentation media
5219
X
Parameter(s)
Drawer
PRTQLTY
Duplex
1
Set FID Through GFID 1
X
Set vertical margin
X
Set presentation page
Value(s)
*E1
1
2
*STD
*DEVD
*DRAFT
*NLQ
*FASTDRAFT
*NO
*YES
FONT
CPI
font-id
cpi
spacing
X
PAGESIZE
page-width-cpi
page-length-lpi
Set single line density
X
LPI
6
Set coded graphic set through local ID
X
Set graphic error action
X
RPLUNPRT
Y
N
Set error action
X
Set line density
X
LPI
Set character density
X
CPI
Set vertical format
X
Page length
Set horizontal format
X
Page width
See the next section for more information on this command in 5219 printer emulation mode.
XDPE/400 User Documentation (9/2001)
D-2
SCS commands for the 5225 and 5219 printers
Set FID through GFID SCS command in 5219 printer
emulation mode
The Set FID Through GFID SCS command is only generated when the
Printer emulation (PRTTYPE) Monitor Queue parameter is set to 5219.
This command consists of three parameters: font identifier (FONT),
characters per inch (CPI), and a one-byte number that specifies whether
the font is monospaced or proportionally spaced.
XDPE/400 takes the value that is specified for the Font identifier (FONT)
printer file parameter, assigns it a specific value, and creates the SCS
command using this mapped value. Table D-2 shows the font identifier
that is specified for the FONT printer file parameter (Specified font ID) and
the corresponding font identifier (Mapped font ID) mapped through
XDPE/400.
NOTE: If you want to use the font identifier to specify a font, your
interface must be configured for the mapped font identifier, not the
font identifier specified by the printer file. Refer to your interface
manual for instructions on changing the font at the interface.
For example, if you specified 87 for the Font identifier (FONT) printer file
parameter, you would first look up the appropriate range where 87 falls
under the “Specified font ID” column in table D-2. Then look under the
“Mapped font ID” column to find the mapped value, which is 85. You will
need to change the Font identifier value from 87 to 85 at the interface to
correctly pick up your font.
Table D-2.
Mapped font identifiers
Specified font ID
Mapped font ID
Spacing
CPI
0 to 65
11
M
10
66 to 153
85
M
12
154 to 200
160
P
12
201 to 210
204
M
13
211 to 239
223
M
15
240 to 246
245
M
5
247 to 257
252
M
17
258 to 259
259
M
18
260 to 273
434
M
8
274 to 279
279
M
17
XDPE/400 User Documentation (9/2001)
D-3
SCS commands for the 5225 and 5219 printers
Table D-2.
Mapped font identifiers (Continued)
Specified font ID
Mapped font ID
Spacing
CPI
280 to 284
281
M
20
285 to 289
285
M
25
290 to 299
290
M
27
300 to 2303
252
M
17
XDPE/400 User Documentation (9/2001)
D-4
Section Five:
Glossary
XDPE/400 User Documentation (9/2001)
Glossary
A
C
American Standard Code for Information
Interchange (ASCII) — Method of encoding
alphabetic and symbolic characters in a format
that is convenient for electronic storage and data
communication. Used by XES, PCL, PostScript,
and some DJDE printers.
CCSID — See Coded Character Set ID.
AS/400 administrator — Person responsible for
the AS/400 environment. An AS/400 administrator
may coordinate upgrades and installations of new
equipment or software, place service calls,
monitor usage, and monitor security.
B
BACKOVL — Keyword in an AS/400 printer file
and spool file attribute list for the form printed on
the reverse side of duplex pages on IBM printers.
The form can be printed with variable data,
depending on the printer language.
banner page — A separator page that prints at
the beginning of a job.
BFORM — Form printed on the reverse side of a
duplex page without variable data on Xerox
printers. BFORMs are often used to convert
simplex reports to duplex reports where all the
information on the reverse side of the report is
fixed.
BIN — Part of an electronic printer that receives
and holds pages after they have been imaged.
character set — A defined set of characters with
no coded representation assumed. A character set
may be defined by alphabet, by language, or by a
combination of these definitions. Note that a
character set is not the same as a display font or
printer font.
characters per inch (CPI) — Standard method
for specifying font spacing.
code page — A mapping of a subset of all
characters into explicit EBCDIC or ASCII positions
representing keyboard characters. There are
many more characters than can be represented by
the EBCDIC or ASCII standards for data encoding,
so a code page is used to identify which
characters can be used for a given application. For
example, EBCDIC code page 00285 contains the
British Pound Sterling symbol at x'5B' and
EBCDIC code page 00037 contains the US Dollar
symbol at x'5B'. To use both in the same
application would require using EBCDIC code
page 500, which has the US Dollar at x'5B' and the
British Pound Sterling at x'B1'. OS/400 supports
many EBCDIC and ASCII code pages and
translation tables related to them as part of
OS/400 National Language Support.
Coded Character Set ID (CCSID) — An OS/400
parameter used with many OS/400 and XDPE/400
commands to specify the combined use of a
specific code page and character set.
collate — Print mode where all pages of each
copy of a report are printed before the pages of the
next copy of the report.
copy modification entry (CME) — Xerox
printer control command which allows you to
change fonts and to replace print data with
pre-specified static data.
XDPE/400 User Documentation (9/2001)
G-1
Glossary
D
F
Document Services Platform (DocuSP) — A
Xerox hardware/software interface between client
systems and the printer that accepts a document
as a page description language file, converts the
file to a bitmap image, and sends the data through
a dedicated electrical connection to a
DocuTech/DocuPrint printer.
File Transfer Protocol (FTP) — A client
function that allows a user to send and receive
copies of files to and from remote systems across
a TCP/IP network.
Document Structuring Conventions (DSC)
packet — A packet that contains PostScript DSC
instructions to be applied by the PostScript
document manager to the entire job. For more
information about DSC instructions, refer to the
PostScript Language Reference Manual.
font — Collection of character descriptions
residing within a single file.
duplex — Refers to printing on both sides of a
page.
duplex standard — The XDPE/400 printing
standard for duplex and tumble plexing.
XDPE/400 uses either the standard defined by
Hewlett Packard’s PCL or by IBM’s OS/400.
dynamic job descriptor entry (DJDE) —
Command within a printer input data stream used
to modify the printing environment on a Xerox
Printing System.
E
electronic printing system (EPS) — See laser
printing system.
euro — The common unit of currency for the
European Economic and Monetary Union (EMU).
The euro currency symbol is €.
Extended Binary-Coded Decimal Interchange
Code (EBCDIC) — Method of encoding
alphabetic and symbolic characters in a format
that is convenient for electronic storage and data
communication. Used by AS/400 and some DJDE
printers.
XDPE/400 User Documentation (9/2001)
folder — AS/400 hierarchal file directory which is
similar to a PC directory.
font index — Character within the DJDE print
data stream line to specify the font to use. The font
index is treated as a number and is used to index
to the current font list of the print job. This font is
used to print the current line.
form — Electronic representation of fixed
overlay. Forms may be imaged on both sides of a
sheet and may be changed from page to page.
forms source language (FSL) — Editable
version of an electronic form. FSLs are compiled
by a Xerox forms compiler to produce FRMs. FSL
is also the name of the Xerox printer filing system
directory in which FSLs are stored.
FRM — Object version of an electronic form.
FRM is also the name of the Xerox printer filing
system directory in which FRMs are stored.
G
generic device support — Enables standard
LCDS, PCL, Xerox Job Ticketing and VIPP
support for new devices that XDPE does not yet
explicitly support, and provides minimal standard
functionality of each printer language type.
Generic device support provides a means to use
new devices during the time period between their
release and the implementation and verification of
support for that device in XDPE/400.
graphic character set — See character set.
G-2
Glossary
H
Host Print Transform (HPT) — Allows printing
to ASCII printers without an interface box.
job ticket — A set of commands that specifies
the printing, finishing, and job management
requirements of a print job. Used by NPS and
DocuSP printers.
L
I
IDEN — Xerox JSL command that defines DJDE
characteristics.
image — A picture represented by a pattern of
dots that is compressed and encoded.
installation verification procedure
(IVP) — A job run after product software
installation that validates product functionality.
interface box — Device that manages the
electronic conversation between two other
devices. Switches on this device configure it to
emulate a printer that is native to the AS/400. Its
main purpose is to convert IBM SCS commands to
Xerox XES or PCL commands.
J
job descriptor entry (JDE) — Compiled job
description. JDEs are contained in JDLs.
job descriptor library (JDL) — Collection of
compiled job descriptions resident on the Xerox
Printing System. JDL is also the name of the Xerox
printer filing system directory in which JDLs are
stored. Uncompiled job descriptions are known as
job source language (JSL).
Job Descriptor Ticket (JDT) — A file that
contains VIPP commands which control the page
composition of a job. With the exception of Native
Mode Prefix (NMP) records, the printer file to
which a JDT is applied typically is a file that
consists of raw data which does not have any
embedded composition commands. For more
information, refer to the Xerox Variable Data
Intelligent PostScript PrintWare (VIPP) Reference
Manual.
landscape — One of two possible orientations
for a printed page. A landscape page is imaged so
it is “read” with the long edge parallel to the
horizon.
laser printing system (LPS) — A printer that
uses laser technology to transfer characters and
images onto a page. Also known as an electronic
printing system (EPS).
logo — Logotype used to print large (up to
two-inch square) regions with a fixed pattern.
Logos are often used to print signatures and
company logos. Used by DJDE printers.
M
Metacode — Control codes used by Xerox
centralized printers to control the internal
functions of their imaging systems. Functions,
such as font selection, print orientation selection,
and character positioning, are controlled by
Metacodes. Metacodes can be created and
inserted into the print data stream, either by the
printer ESS when formatting data for printing, or
by application programs when formatting the print
data stream.
Monitor Queue — Main control processing
program of XDPE/400. Monitor Queue scans the
output queue for files to print, creates banner
pages, creates printer control packets (by
translating spool file attributes or retrieving
user-defined packets), and releases the spool files
to the printer writer.
multi-part packet — Packet containing a list of
packets used to create spool files from a user
spool file. A specific output queue may also be
specified for each packet.
job source language (JSL) — Editable format
of the control language for printing jobs on a Xerox
printer. JSL is also the name of the Xerox printer
filing system directory in which JSLs are stored.
multi-part printing — Enables the creation of
multiple spool files from a single user spool file.
The spool files may be created using different
command generation modes and printer command
packets, and sent to different output queue
destinations.
XDPE/400 User Documentation (9/2001)
G-3
Glossary
multi-up packet — ASCII packet used for
multi-up printing that contains font and positioning
information.
portrait — One of two possible orientations for a
printed page. A portrait page is imaged so it is
“read” with the short edge parallel to the horizon.
multi-up printing — Enables the printing of
multiple logical pages on a single physical page.
print description language (PDL) — Language
on Xerox Printing Systems to describe print jobs to
a laser printing system. PDL describes the input
(type, format, characteristics), performs the
processing functions (logical processing), and
describes the output (type, format, font selection,
accounting options).
N
Native Mode Prefix (NMP) record — A VIPP
command that is embedded in the data stream in
order to dynamically change the page layout. An
NMP record is a VIPP command that is prefixed
with %%XGF (for example, %%XGF PORT) to
indicate that it should be processed as a command
rather than as printable data. For more
information, refer to the Xerox Variable Data
Intelligent PostScript PrintWare (VIPP) Reference
Manual.
network printing system (NPS) — A
network-connected printer that uses laser
technology to transfer characters and images onto
a page.
O
output queue — AS/400 object which contains
spooled files.
overlay — AS/400 equivalent to a Xerox form.
P
packet data field — Spool file attribute that may
specify the method of Xerox printer control
generation, the name of the user-defined packet of
commands to use for the direct or combine
method, and the name of a list of resources to
send to the printer with the job. The Monitor Queue
startup parameter called ‘Packet data field’ is used
to select which spool file attribute is the packet
data field for a particular session.
page description entry (PDE) — Entry on
Xerox Printing Systems to describe print jobs to a
laser printing system.
XDPE/400 User Documentation (9/2001)
Printer Command Language (PCL) —
Language developed by the Hewlett-Packard
Company to provide control commands that are
used to control Xerox PCL printers. For more
information, refer to the PCL 5 Printer Language
Technical Reference Manual.
printer control packet — XDPE/400 name for
the set of printer control codes that are inserted
into the print data stream by XDPE/400. Also
refers to a set of Xerox printer control commands
predefined by the user and stored in the
appropriate subfolder of the XDPEFLR folder.
printer writer — AS/400 printer task that is used
to print spool files.
R
RSTACK — Xerox PDL statement used to
identify report (job) boundaries and to specify
report separation processing. Report boundaries
are identified by searching every line in the print
stream for a user-specified test string.
S
separator page — A page that is printed at the
beginning and/or end of a job to separate and
identify jobs.
simplex — Refers to printing on one side of a
page.
Source Entry Utility (SEU) — An OS/400 utility
used to create, edit, display, and print source
members in source physical files.
G-4
Glossary
spool file — File containing output data and a
set of attributes that specify how the data is to be
printed.
W
subfolder — See folder.
workstation customizing object — An OS/400
object that specifies how Host Print Transform
(HPT) will convert SCS EBCDIC spool files to a
format that can be used by your Xerox printer.
symbol set — A unique ordering of the
characters in a PCL font. Symbol set is an attribute
of the Font selection by attributes (FONT) PCL
packet parameter. For information on symbol sets,
refer to the PCL 5 Printer Language Technical
Reference Manual. For information on symbol set
values, refer to the PCL 5 Comparison Guide.
X
T
Xerox Distributed Print Mode
(XDPM) — A Xerox term that describes printing
in a decentralized environment.
trailer page — A separator page that prints at
the end of a job.
Xerox Escape Sequence (XES) — A
user-defined character used in control code
sequences sent to decentralized printers.
V
Variable Data Intelligent PostScript PrintWare
(VIPP) — A set of page layout functions bundled
as PostScript programs. This provides an easy
way to use Xerox PostScript devices in a
traditional non-PostScript environment. Output,
such as line mode data produced by traditional
applications, can be imaged on a Xerox PostScript
printer while requiring few, if any, modifications to
the applications that generate the data. For more
information, refer to the Xerox Variable Data
Intelligent PostScript PrintWare (VIPP) Reference
Manual.
XDPE/400 User Documentation (9/2001)
Xerox Generic Format (XGF) — Former name
of Variable Data Intelligent PostScript PrintWare
(VIPP). Some elements of VIPP, such as Native
Mode Prefix (NMP) records, contain nomenclature
related to XGF, such as the %%XGF prefix and
printer controller folder names. For more
information, refer to the Xerox Variable Data
Intelligent PostScript PrintWare (VIPP) Reference
Manual.
Xerox Production Print Mode (XPPM) — A
Xerox term that describes printing in a centralized
environment.
XJDC — Xerox software product. XJDC is a PC
resident PDL compiler used to create JDLs for
Xerox XPPM printers.
G-5
Glossary
XDPE/400 User Documentation (9/2001)
G-6
Section Six:
Index
XDPE/400 User Documentation (9/2001)
Index
Symbols
A
*AUTO file processing mode, definition of, 18-10,
19-2
*JOB file processing mode
definition of, 18-10, 19-1
examples, 19-4 to 19-5
using, 19-2 to 19-5
*PAGE file processing mode
definition of, 18-10, 19-1
examples, 19-8
using, 19-6 to 19-8
*PCL printer mode, 20-4
*VIPP printer mode, 18-9, 20-4
ADDDIRE command, 4-3, 5-2
ADDLIBLE command, 5-7
Agile 5250 OPTIMA interface
in XDPM mode, A-5
in XPPM mode, A-4
requirements, A-4
Agile 5250 OPTIMA interface, specifying, 18-7
ALIGN printer file parameter, 12-5
ALIGN spool file attribute, 11-1
ALWAYS Monitor Queue parameter, 10-3, 18-13
AS/400
printing elements, 1-5
printing to, 1-4
system requirements, 4-1
CD ROM drive, 4-1
disk storage, 4-1
tape drive, 4-1
ASCII editor, using to create multi-up packet, 25-14,
25-27
*AUTO file processing mode, definition of, 18-10,
19-2
Numerals
3X Twinax Printstation interface
connectivity, A-1
supported versions, A-1
3X Twinax Printstation interface, specifying, 18-7
4030 printer, constant merge page load, activating,
13-4
4213 printer
shift command, creating, 13-4
XES form, activating, 13-4
4235 printer
page format, specifying, 13-15
shift command, creating, 13-4
version, specifying, 18-8
XES form, activating, 13-4
4235 printer, switching modes, 4-8
42XX INTERNAL interface
loading the interface, A-3
MRP internal interface, 15-20, 18-20
requirements, A-3
specifying, 18-7
4450 INTERNAL interface
definition of, A-4
requirements, A-4
4450 INTERNAL interface, specifying, 18-7
4700 printer
page format, specifying, 13-15
XES form, activating, 13-4
54394-1-generic devices, 15-14
54746-1, 21-8
XDPE/400 User Documentation (9/2001)
B
BACKMGN printer file parameter
DJDE mode processing of, 12-6
PCL mode processing of, 15-6
XES mode processing of, 13-6
BACKOVL printer file parameter
DJDE mode processing of, 12-4
PCL mode processing of, 15-7
VIPP mode processing of, 17-4, 17-5
XES mode processing of, 13-4
BACKOVL spool file attribute, 11-2
BANNER Monitor Queue parameter, 26-19
banner pages, 6-20
BANNERSRC Monitor Queue parameter, 18-15
BARR interface
configuration, A-6
definition of, A-6
requirements, A-6
BARR interface, specifying, 18-7
batch job log, 27-7
BFORM printer file parameter, 10-10
BFORM, specifying, 10-10, 12-12
BUFFER global parameter, 6-15
I-1
Index
C
CALL command, 6-30
Change Color Command Packet command, 14-11
Change Monitor Queue command, 18-26
Change Xerox PCL Packet command, 15-27
Change Xerox Printer File command, 8-4, 10-6,
10-13
Change XES Packet command, 13-19
CHGDJDE command, 12-17
CHGJOBD command, 6-28
CHGMONQ command, 18-26, 20-15
CHGPRTF command, 6-31, 7-2, 13-4, 17-5
CHGVIPRSC command, 9-1, 17-24 to 17-26
CHGXES command, 13-19
CHGXLPP command, 23-13
CHGXMPT command, 24-8
CHGXPCL command, 15-27
CHGXPRTF command, 8-4, 10-6, 10-13, 12-15,
13-19, 15-25
CHGXTCK command, 9-1
CHRID spool file attribute, 11-3
CME, specifying, 12-12
CNTCHAR global parameter, 6-14
color
IBM command names, 14-9 to 14-10
names, available for CRTXCOL command, 14-2
color packets
changing, 14-11
creating, 14-2 to 14-8
mapping, 14-7 to 14-8
names, syntax, 14-2
parameters, 14-6
processing, 14-12
color processing
definition of, 14-1
SCS commands, C-3
combined method
DJDE packets, 12-8
PCL packets, 15-9
VIPP packets, 17-3, 17-11 to 17-12
XES packets, 13-8
command group menus
accessing, 9-3
available, 9-3
definition of, 9-3
example, 9-4
constant back pages
job elements, 15-40
print jobs, restarting, 23-3
requirements, 15-40
XDPE/400 User Documentation (9/2001)
COPIES printer file parameter
DJDE mode processing of, 12-5
PCL mode processing of, 15-4
VIPP mode processing of, 17-4, 17-5
XES mode processing of, 13-5
copies, specifying number of, 12-5, 12-11, 13-5,
13-13, 15-4, 17-5
COPIES spool file attribute, 11-3
COR, definition of, 15-14
CPYTOPCD command, 21-3
Create a Xerox LPP command, 23-7
Create Xerox Color Palette command, 14-1
Create Xerox PCL Packet command, 15-10
Create Xerox resource list command, 13-23
Create XES Packet command, 13-9, 13-23
CRTCLPGM command, 6-30
CRTDJDE command, 12-9
CRTLIB command, 6-29
CRTOUTQ command, 20-8
CRTPRTF command, 13-4, 15-44, 17-5
CRTSRCPF command, 6-29
CRTUSRPRT command, 5-2
CRTVIPRSC command, 9-1, 17-15 to 17-23
example, 17-20 to 17-23
resource creation parameters, 17-17 to 17-19
using, 17-16 to 17-17, 17-24 to 17-25
CRTXCOL command, 14-1, 14-2
CRTXES command, 13-10, 13-23
CRTXIVP command, 7-5
CRTXLPP command, 23-7
CRTXMPT command, 24-3
CRTXPCL command, 15-41
CRTXRSCLST command, 13-23, 14-12, 15-41,
22-1, 22-4, 22-7, 23-15
CRTXTCK command, 9-1
D
Data Description Specification (DDS)-formatted files
in VIPP mode, 17-2
DATASRC Monitor Queue parameter, 18-15
default packet
DJDE packet, 12-7
processing, 10-2
specifying in Monitor Queue, 18-16
Xerox PCL packet, 15-8
XES packet, 13-7
default packet processing, 10-3
Delete Xerox PCL Packet command, 15-30
Delete XES Packet command, 13-21
DEVCLS Monitor Queue parameter
remote/network printer setup requirements for,
20-4
I-2
Index
device classes
local, definition of, 20-1
network, definition of, 20-1
recognized by XDPE/400, 20-1
remote, definition of, 20-1
specifying, 18-18
device description, creating, 4-11
device description file, specifying, 18-7
DFTPKT Monitor Queue parameter, 18-16
direct method
DJDE packets, 12-7
PCL packets, 15-8
VIPP packets, 17-3, 17-10 to 17-11
XES packets, 13-7
Display XDPE Monitor Queue command, 18-24
Display XDPE PCL packet command, 15-31
distribution text, specifying, 12-12
DJDE
control commands, using, 12-2
full-screen editor, using, 12-19 to 12-26
parameters, how applied, 12-8
DJDE commands, created or inserted, 6-9
DJDE packets
combined method, 12-8
creating, 12-9 to 12-17
default, 12-7
direct method, 12-7
indirect method, 12-3 to 12-6
multi-up
examples, 25-4 to 25-5
processing, 25-1 to 25-5
name
specifying, 12-11
syntax, 12-9
parameters, changing, 12-17 to 12-18
termination mode, setting, 12-5
DJDE printer file parameter, 10-12
DJDEBFR global parameter, 6-13
DLTLIB command, 5-7
DLTVIPRSC command, 9-1, 17-27
using, 17-27
DLTXES command, 13-21
DLTXMPT command, 24-9
DLTXPCL command, 15-30
DLTXTCK command, 9-1
DNLDFRMRSC command, 22-9
DNLDPCLFNT command, 21-10
DNLDPCLMAC command, 21-9
DNLDVIPENC command, 9-2, 21-1, 21-18
DNLDVIPFNT command, 9-2, 21-1, 21-18
DNLDVIPFRM command, 9-2, 21-1, 21-18
DNLDVIPIMG command, 9-2, 21-1, 21-18
DNLDVIPJDT command, 9-2, 21-1, 21-18
XDPE/400 User Documentation (9/2001)
DNLDVIPRSC command, 9-2, 21-2, 21-12
resource download parameters for, 21-15 to
21-16
using, 21-13 to 21-14
DocuSP printers
definition of
PCL mode, 1-10
VIPP mode, 1-11
interface devices for, 4-10, 18-9
PCL mode printer software requirements, 4-6
remote output queue, specifying
PCL mode requirements, 20-11
VIPP mode requirements, 20-11
VIPP mode
printer software requirements for, 4-7
support for, 1-11
VIPP mode requirements, 26-16
Download PCL Fonts Resource command, 21-10
DRAWER global parameter, 6-10
DRAWER printer file parameter, 13-6
DJDE mode processing of, 12-5
PCL mode processing of, 15-4
DRILLED printer file parameter, 10-11
DSC packets
changing, 17-24 to 17-26
considerations when using, 17-11, 17-12
creating, 17-13, 17-15 to 17-19
definition of, 17-1, 17-13
deleting, 17-27
displaying, 17-24 to 17-25
inserting contents of, 17-6, 17-10, 17-13
naming conventions for, 17-17 to 17-18
printing, 17-24 to 17-25
subfolder requirements, 17-15
using %%DocumentMedia statement in, 26-16
DSC packets, specifying Attribute include/exclude
flag (INHIBLST) for, 6-9
DSC statements, inserted, 17-6, 17-10, 17-11
DSCMEDIA member of SAMPLE file, 17-11, 17-12,
17-14
DSCSIZE member of SAMPLE file, 17-11, 17-12,
17-14
DSPMONQ command, 18-24
DSPMSG command, 26-1
DSPOBJD command, 26-2
DSPXPCL command, 15-31
DUPLEX printer file parameter
DJDE mode processing of, 12-4
PCL mode processing of, 15-4
specifying, 10-10
VIPP mode processing of, 17-4, 17-6
XES mode processing of, 13-5
I-3
Index
duplex printing
considerations for logical processing, 23-5
NPS printer setup requirements for, 20-4 to 20-5,
26-9 to 26-10, 26-17 to 26-18
specifying, 10-10, 11-5, 12-4, 12-12, 13-5,
13-13, 15-4, 15-13, 17-17
DUPLEX spool file attribute, 11-5
DUPLEXSTD global parameter, 6-16
E
EDTDJDE command, 12-19
ENCODING subfolder of XDPEFLR, 17-15, 17-19,
21-2, 21-15, 21-18, B-2
ENDMONQ command, 18-28
ENDWTR command, 20-14
Enter, 27-6
euro currency symbol, 21-20
euro fonts, 21-20
euro support, 21-20
AS/400 system changes, 21-20
multi-up printing considerations, 21-26
PCL tasks, 21-24
F
FILESEP spool file attribute, 11-3
FILESIZE global parameter, 6-15
Flex i-data interface
initialization options, A-8
mode, specifying, 18-10
relationship with STRMONQ, A-8
requirements, A-8
specifying, 18-7
using to control tray selection, 26-6, A-9
FLRSPC screen parameter, 17-19
FONT ID printer file parameter
VIPP mode processing of, 17-4, 17-6, 17-10,
17-11, 17-12, 17-13
FONT printer file parameter, 12-6, 13-6, 15-5, 15-39
fonts
for PCL packets, specifying, 15-16
for XES packets, specifying, 13-16
loaded on PCL printer, using, 15-17
PCL, downloading, 21-10 to 21-11
PostScript, downloading, 21-13
form feeds, specifying, 15-20
FORMFEED printer file parameter
DJDE mode processing of, 12-5
PCL mode processing of, 15-5
VIPP mode processing of, 17-4, 17-6 to 17-7
XES mode processing of, 13-4
XDPE/400 User Documentation (9/2001)
FORMFEED spool file attribute, 11-3
FORMLIB subfolder of XDPEFLR, 17-14, 17-15,
17-19, 21-2, 21-15, 21-18, B-2
forms
electronic, specifying name of, 13-13
specifying
for DJDE packets, 12-4, 12-12
for duplex printing, 12-4
type options, 18-17
VIPP
see also VIPP resources
creating, 17-15
downloading, 21-13
FORMTYPE spool file attribute, 17-10
FRONTMGN printer file parameter
DJDE mode processing of, 12-6
PCL mode processing of, 15-5
VIPP mode processing of, 17-4, 17-7
XES mode processing of, 13-6
FRONTOVL printer file parameter
DJDE mode processing of, 12-4
PCL mode processing of, 15-6
VIPP mode processing of, 17-4, 17-8
XES mode processing of, 13-4
FRONTOVL spool file attribute, 11-4
FTP process for downloading VIPP resources, 21-12
G
generic packets
building
BFORM merge PCL, 15-43
job level PCL, 15-41
PCL, 15-43
resource list, 15-41
considerations when using, 26-7, 26-12
creating ASCII file, 15-37 to 15-38
definition of, 15-37
inserting, 15-38 to 15-39
sample application for constant back forms,
15-40
specifying
for PCL processing, 15-19
for XES processing, 13-17
using with PCL, 15-37 to 15-44
XES, using, 13-22 to 13-24
Generic printer devices, 1-11
GENPCL PCL packet parameter, 15-39
global value command, definition of, 6-1
global values, changing, 6-1
GRTOBJAUT command, 5-2
I-4
Index
H
IVP
data streams created
combined mode printing, 7-1
direct mode printing, 7-1
indirect mode printing, 7-1
resource loading, 7-1
executing, 7-5 to 7-6
functions performed, 7-1
output, verifying, 7-6
parameters, creating, 7-6
printer JSL requirements, 7-2
sample output, 7-7
VIPP resource downloading requirements, 7-3
HPT
customizing, 20-7
definition of, 20-7
using with TCP/IP, 20-7
HPT, supported printers for, 4-10
I
IBM PC Support interface
configuration for 4213 printer, A-10
definition of, A-10
IDEN parameters, specifying, 6-2 to 6-3
images, downloading VIPP, 21-13
IMGLIB subfolder of XDPEFLR, 21-2, 21-15, 21-18,
B-2
indirect method
DJDE packets, 12-3 to 12-6
PCL packets, 15-3
VIPP packets, 17-3, 17-4 to 17-9
XES packets, 13-3
INHIBLST global parameter, 6-8
installation
AS/400 requirements, 4-1
authority required, 4-3
current system
backing up, 5-3
device description, creating, 4-11
printer requirements, 4-3 to 4-8
printer/interface box configurations, 4-9 to 4-11
procedure, 5-2 to 5-7
security requirements, 4-2
Interactive command messages, 27-3
interface boxes
for network printing, 20-6
specifying connection, 18-7
supported (by printer model), 4-9, 20-3
interface mode, specifying, 18-9
interface settings, specifying, 4-11
internal interface, specifying, 18-7
IOFFSET global parameter, 6-3
IP address, setting up, 20-12
IPREFIX global parameter, 6-3
ISKIP global parameter, 6-3
XDPE/400 User Documentation (9/2001)
J
JDE
definition of, 12-1
dynamically changing, 12-1
specifying for a DJDE job, 12-11
JDE/PDE ID parameters, specifying, 6-5
JDEPDE global parameter, 6-5
JDEPDEMODE global parameter, 6-5
JDL
definition of, 12-1
dynamically changing, 12-1
specifying for a DJDE job, 12-11
JDTLIB subfolder of XDPEFLR, 17-15, 17-19, 21-2,
21-15, 21-18, B-2
JDTs
see also VIPP resources
creating, 17-15
definition of, 17-1
downloading, 21-13
name, specifying, 10-12, 17-2, 17-10
*JOB file processing mode
definition of, 18-10, 19-1
examples, 19-4 to 19-5
using, 19-2 to 19-5
job accounting function, support for, 19-12
Job Descriptor Tickets, see JDTs
job name
constructing for XES command string, 13-4
specifying, 13-12
JOB printer file parameter, 13-4
job priority, specifying, 13-5, 13-13
JOB spool file attribute, 11-4
job ticket packets
creating, 16-6
creating, displaying, and printing, 16-8
deleting, 16-10
job ticket processing, 16-1
I-5
Index
L
M
lines per inch, specifying, 15-6, 15-20
list name, specifying, 22-5
list processing
creating a Xerox resource list, 22-4 to 22-5
examples, 22-2
formats, 22-2
job, configuring, 22-6
list contents, 22-2
objects used, 22-3
overview, 22-2 to 22-3
packet name, specifying, 22-2
record length requirements, 22-2
use with logical processing, 23-1
using to insert generic packets, 15-38
list processing, definition of, 1-8
local printing
configurations, 20-3
definition of, 20-1
local printing, connections for, 4-9
logical page boundaries, specifying, 13-15
logical pages, specifying number of, 13-17, 15-21
logical processing
application
how many times to apply, 23-11
when to apply, 23-11
considerations and restrictions, 23-3 to 23-6
overview, 23-1 to 23-2
packet name
specifying, 23-9
syntax, 23-7
packets
changing, 23-13 to 23-14
creating, 23-7 to 23-12
parameters, 23-9 to 23-12
specifying, 23-1
SCS commands, C-3
starting, 23-15
test
attributes, specifying, 23-10 to 23-11
comparison results, 23-1
creating for generic packets, 15-42
type, specifying, 23-9
Test type parameter
*CHANGE, 23-2
*MATCH, 23-2
using to insert a generic packet, 15-39
LPI printer file parameter
PCL mode processing of, 15-6
LPI spool file attribute, 11-4
maintenance, installing, 5-6
margins, specifying front and back, 12-6
message file, viewing, 26-1
message queue, specifying, 18-16
messages
functionality, 27-1
prefixes, 27-1
variable definitions, 27-3
METHOD printer file parameter, 10-12
migration issues, 4-12 to 4-13
MISLIB subfolder of XDPEFLR, 17-13, 17-15, 17-19,
21-2, 21-15, 21-18, B-2
MODE Monitor Queue parameter, 18-9, 20-4
Monitor Queue
job log, 27-5
changing, 18-26 to 18-27
changing for TCP/IP, 20-15
file processing mode restrictions, 13-2, 15-2
for IVPs, starting, 7-4
job log, 6-28
jobs, working with, 19-10 to 19-11
messages, 18-32
methods
determining, 8-3
packet data field, 10-2
packet data parameter, 8-3
multiple sessions
database errors, 26-2
example, 18-2
operation, 18-2
parameters, 18-6 to 18-21
processing modes, 19-1 to 19-8
properties, displaying, 18-24 to 18-25
SCS commands, using, D-1
separator pages, generating, 6-20
session
ending, 18-28
examples, 18-22 to 18-23
resetting, 18-31
starting, 18-4 to 18-21
starting for TCP/IP, 20-14 to 20-15
MPI interface, specifying, 18-7
MPRLST global parameter, 6-12
MRP internal interface, specifying, 15-20, 18-20
MULCPYSEP global parameter, 6-15
multi-part packets
changing, 24-8
considerations, 24-5
creating, 24-3 to 24-7
deleting, 24-9
example, 24-6
multi-part printing, definition of, 1-8
XDPE/400 User Documentation (9/2001)
I-6
Index
multi-part processing
definition of, 24-1
overview, 24-1 to 24-2
sample job, 24-2
specifying in Monitor Queue, 18-18
starting, 24-10
multi-up packet, specifying, 13-17, 15-22
multi-up printing
PCL generation, 25-15 to 25-27
SCS commands, C-3
specifying, 11-5
VIPP command generation, 25-27 to 25-29
XES generation, 25-5 to 25-14
multi-up printing, definition of, 1-8
multiple session database, cleaning, 26-2
MULTIUP printer file parameter
DJDE mode processing of, 12-6
PCL mode processing of, 15-7
VIPP mode processing of, 17-4, 17-8
XES mode processing of, 13-6
MULTIUP spool file attribute, 11-5, 25-27
NPS printers
AS/400 system requirements for
PCL mode, 4-1
VIPP mode, 4-1
command modifications for using A4 paper in
PCL mode, 6-31
definition of
PCL mode, 1-10
VIPP mode, 1-11
duplex printing setup requirements, 20-4, 26-10,
26-18
interface devices for, 4-10, 18-9
PCL mode printer requirements, 4-6
remote output queue, specifying
PCL mode requirements, 20-11
VIPP mode requirements, 20-11
Set Tray command requirements in VIPP mode,
26-16
VIPP mode
printer software requirements for, 4-7
support for, 1-11
N
O
N-series
definition of
VIPP mode, 1-11
VIPP mode
support for, 1-11
N-series printers
interface devices for, 4-10, 18-9
network printing
configurations, 20-3
definition of, 20-1
requirements
interfaces, 20-6
IP address, setting up, 20-12
Monitor Queue parameter, 20-4
XDPE processing, 20-12
network printing, connections for, 4-10
NMP records
created and inserted, 17-4 to 17-9, 17-11
definition of, 17-1
Office Vision-formatted files in VIPP mode, 17-2
offset, specifying, 13-6, 15-5, 15-6
operator message, specifying, 13-12
ORIENT printer file parameter, 10-9
OUTPTY spool file attribute, 11-4
OUTPUT PRIORITY printer file parameter, 13-5
output queue
specifying
name, 18-6, 18-18
remote, 18-19
output queue, monitoring, 1-9
output, specifying multiple pages per physical page,
13-6, 15-7
OUTQ XDPE IVP parameter, 7-6
OVRPRTF command, 13-4, 17-5
OVRXPRTF command, 8-4, 10-14, 10-15
P
packet data field
PACKETDATA Monitor Queue parameter, 18-12
setting parameters for, 10-2 to 10-3
packet flag, specifying for list processing, 22-2
packet mode keyword, specifying for list processing,
22-2
packet name, specifying for list processing, 22-2
PACKETDATA Monitor Queue parameter, 10-2,
17-10, 18-12
PACKETDATA printer file parameter, 10-12
XDPE/400 User Documentation (9/2001)
I-7
Index
*PAGE file processing mode
definition of, 18-10, 19-1
examples, 19-8
using, 19-6 to 19-8
page dimensions, specifying, 13-15
page format, specifying, 13-15
page formatting parameters, specifying, 12-12
page margins, setting, 15-15
page orientation
*COR option, 15-14
specifying, 15-14
page shift, specifying for predrilled paper, 12-5,
13-15, 15-5, 15-14, 17-6
PAGESIZE printer file parameter, 15-7
PAGRTT printer file parameter
DJDE mode processing of, 12-6
PCL mode processing of, 15-7
VIPP mode processing of, 17-4, 17-9
XES mode processing of, 13-6, 13-17
paper trays, selecting, 12-13, 15-14
PC interface, specifying, 18-7
PCL commands, created or inserted, 6-9
PCL commands, methods for generating
combined method, 15-1
direct method, 15-1
indirect method, 15-1
PCL euro fonts, 21-20
PCL font attributes
height, 15-16
pitch, 15-16
spacing, 15-16
style, 15-16
symbol set, 15-16
typeface, 15-17
weight, 15-17
PCL fonts
downloading, 21-10 to 21-11
parameters, 21-10 to 21-11
PCL macros
activating, 15-6, 15-7
downloading, 21-8 to 21-9
downloading automatically, 15-18
parameters, 21-8
XDPE/400 User Documentation (9/2001)
PCL packets
changing, 15-27
combined method, 15-9
commands, deleting, 15-6, 15-18, 21-9
creating, 15-10 to 15-25
default, 15-8
deleting, 15-30
direct method, 15-8
displaying, 15-31 to 15-32
generic, specifying, 15-37 to 15-44
indirect method, 15-2, 15-3
multi-up
creating, 25-17 to 25-27
default packets, 25-17
format, 25-23 to 25-26
naming, 25-22 to 25-23
overview, 25-15
requirements, 25-16
working with macro invocation types, 15-34 to
15-36
PCL printer tray selection, 15-45
PCL printers
requirements, 4-6
supported, 1-10
PCL processing, limitations, 26-14
PCL resources, processing, 21-9
PCSLIB global parameter, 6-7
PDE
definition of, 12-1
dynamically changing, 12-1
multi-up, supplied with XDPE/400, 25-2
selecting, 12-6
specifying, 12-12
PDLIDL global parameter, 6-5
PDLIDP global parameter, 6-5
PostScript printers
interface settings for, 4-11
mode, specifying, 18-9
supported, 1-9, 1-11
VIPP data streams
printer software requirements for, 4-7
VIPP software requirements for, 4-7
Pre-drilled paper printer file parameter, see DRILLED
printer file parameter
printer control commands, changing generation
methods, 11-1
printer control commands, generating, 1-7
Printer control packet name, specifying, 10-12
I-8
Index
printer file parameters
ALIGN, 12-5
allowed with PROCMODE, 15-2
BACKMGN, 12-6, 13-6, 15-6
BACKOVL, 12-4, 13-4, 15-7, 17-5
COPIES, 12-5, 13-5, 15-4, 17-5
DRAWER, 12-5, 13-6, 15-4
DUPLEX, 12-4, 13-5, 15-4, 17-6
FONT, 12-6
FONT ID, 17-6
FONT (identifier), 13-6, 15-5
FORMFEED, 12-5, 13-4, 15-5, 17-6
FRONTMGN, 12-6, 13-6, 15-5, 17-7
FRONTOVL, 12-4, 13-4, 15-6, 17-8
JOB, 13-4
LPI, 15-6
mapped
to PCL features, 15-3
to XES features, 13-3
modifying
for DJDE packets, 12-4 to 12-6
for PCL packets, 15-4 to 15-7
for VIPP command generation, 17-5
for XES packets, 13-4 to 13-6
MULTIUP, 12-6, 13-6, 15-7, 17-8
OUTPUT PRIORITY, 13-5
PAGRTT, 12-6, 13-6, 15-7, 17-9
printer files
changing, 10-6 to 10-13
commands, 10-6
creating, 10-1 to 10-5
examples, 10-4 to 10-5
overriding, 10-14 to 10-15
parameters, 10-9 to 10-13
parameters, modifying, 8-4
spooling parameters, setting, 10-1 to 10-2
printer model, specifying, 18-8
printer writer, specifying, 18-7
printers
emulation mode, specifying, 18-8
for network printing, 20-3
printers supported by XDPE/400, 1-9 to 1-11
printing
local, 4-9
network, 4-10
remote, 4-9
printing features, specifying, 10-4
PROCMODE Monitor Queue parameter, 15-2, 17-2,
18-10
PRTCTLID screen parameter, 21-16
PRTCTLPW screen parameter, 21-16
XDPE/400 User Documentation (9/2001)
Q
QPSUPRTF spool file, 17-25
R
RECSIZE global parameter, 6-7
remote printing
configurations, 20-3
definition of, 20-1
remote printing, connections for, 4-9
Reset Monitor Queue command, 18-31
RESLIB global parameter, 6-6
resource folder, restoring, 5-5
resource lists
creating, 22-7 to 22-8
downloading, 22-9 to 22-10
example download using list processing, 22-7 to
22-10
source list, creating, 22-7
support for multiple, 22-10
resources
copying
from database file, 21-3
from PC, 21-4
downloadable, 21-1
downloading, 13-17, 15-19
automatically, 21-19
manually, 21-5 to 21-11
parameters, 21-6 to 21-7, 21-18
managing, 21-1 to 21-19
processing for PCL, 21-9
resources, managing, 1-8
RMTSYS screen parameter, 21-16
ROFFSET global parameter, 6-4
rotation, specifying degree of, 13-6, 15-7
RSTACK parameters, specifying, 6-3 to 6-4
RSTDLO command, 5-5
RSTLIB command, 5-5
RSTMONQ command, 18-31
RSTRING global parameter, 6-4
RUNPTY global parameter, 6-5
S
SAMPLE file, 17-12, 17-14
SAVDLO command, 5-3
SAVLIB command, 5-3
SCS commands
in VIPP print data stream, 17-2
in XES print data stream, 14-1
processed by XDPE/400, C-2
used for 5219 and 5225 emulation, D-1
I-9
Index
search mode, specifying, 18-11
security requirements, 4-2 to 4-3
separator pages
customizing
format contents of, 6-20 to 6-25
layout in VIPP mode, 6-27
generated by Monitor Queue, 6-20
template
date and time separators, 6-24
definition of, 6-21
file name, 6-21
modifying, 6-21 to 6-25
rules for creating, 6-21
sample page, 6-25
variable data tokens, 6-22
separator pages, specifying source tray, 18-15
SEQUENCE Monitor Queue parameter, 12-8, 17-12,
18-14
SEU
DSC packets
changing or displaying, 17-25 to 17-26
creating, 17-15
multi-up packets, creating, 25-14, 25-27
using, 12-26, 22-4, 22-7
VIPP resources
changing or displaying, 17-25 to 17-26
creating, 17-15
shift command, creating, 13-4
SHIFT global parameter, 6-11, 17-6
Smart interface, definition of, A-11
Smart interface, specifying, 18-7
Solimar interface
printer parameters, A-11
requirements for, A-11
Solimar interface, specifying, 18-7
SOLIMODE global parameter, 6-13
source drawer
specifying, 12-5, 13-6, 15-4
for data pages, 18-15
for separator pages, 18-15
SPECPACK global parameter, 6-16
spool file attributes
changing, 11-1 to 11-6
conversion of, 12-7
examples of modifying, 11-5 to 11-6
modifying, 11-1 to 11-6
overriding, 11-6
spool file attributes, exclusion parameters, 6-8 to
6-10
XDPE/400 User Documentation (9/2001)
spool files
decomposition, C-1 to C-3
errors when writing to, 26-9, 26-17
processing mode, specifying, 18-10, 18-12
status, checking, 19-8
wait time, specifying, 18-17
spooling parameters
file separators (FILESEP), 10-2
printer device type (DEVTYPE), 10-1
save spooled file (SAVE), 10-2
spool the data (SPOOL), 10-1
spooled output queue (OUTQ), 10-1
spooled output schedule (SCHEDULE), 10-1
Spur/USAII interface
definition of, A-12
requirements, A-12
Spur/USAII interface, specifying, 18-7
STRMONQ command, customizing, 6-31
STRRMTWTR command, 20-12
STRSEU command, 6-29
T
task-specific menus
accessing, 9-4
available, 9-4
definition of, 9-4
example, 9-5
TCP/IP
Host Print Transform, using with, 20-7
output queue
creating, 20-8 to 20-12
parameters, 20-11 to 20-12
remote writer
ending, 20-14
starting, 20-12 to 20-13
setting up, 20-8 to 20-15
text packets
copying, 12-24
creating, 12-21
deleting, 12-25
displaying, 12-25
editing, 12-22 to 12-23
printing, 12-25
renaming, 12-25 to 12-26
text string
leading, specifying, 18-16
specifying for DJDE packet, 12-13
trailing, specifying, 18-16
TIMESLICE global parameter, 6-6
Trailer pages, 26-19
trailer pages, 6-20
translation table parameters, specifying, 6-6 to 6-7
I-10
Index
TYPE IVP parameter, 7-6
U
user job log, 27-7
user profile, creating, 4-11, 5-2
USRDATA spool file attribute, 17-10
V
VIPP /usr/xgf/ directory, 17-5, 17-10, 17-14, 25-28,
25-29
VIPP /usr/xgfc/ directory, 6-26, 6-27, 7-3, 21-14,
21-15, 26-19
VIPP COLLATE_off command, 17-5
VIPP COLLATE_on command, 17-5
VIPP commands, created or inserted, 6-12
VIPP DUPLEX_off command, 6-9, 17-4, 17-6
VIPP DUPLEX_on command, 6-9, 17-4, 17-6
VIPP ILAND command, 17-4, 17-9
VIPP IPORT command, 17-4, 17-9
VIPP LAND command, 17-4, 17-9
VIPP PORT command, 17-4, 17-9
VIPP processing mode
AS/400 system requirements for, 4-1
combined command generation method for,
17-3, 17-11 to 17-12
command application order using Combined
method, 17-12
default workstation customizing object for, 18-19
direct command generation method for, 17-3,
17-10 to 17-11
indirect command generation method for, 17-3,
17-4 to 17-9
installation verification procedure requirements,
7-3
multi-up generation for, 11-5, 17-8, 25-27 to
25-29
NPS printer setup requirements for, 20-4 to 20-5,
26-9 to 26-10, 26-17 to 26-18
page orientation, 10-9
PROCMODE Monitor Queue parameter
requirements for, 17-2, 18-10
remote printer queue requirements, 20-11
resource samples, 17-14
VIPP functionality supported, 17-2
XDPE/400 User Documentation (9/2001)
VIPP resources
changing, 17-24 to 17-26
creating, 17-15 to 17-23
deleting, 17-27
displaying, 17-24 to 17-25
downloading, 21-12 to 21-18
naming conventions for, 17-17 to 17-18
printing, 17-24 to 17-25
VIPP SETBFORM command, 6-9, 10-11, 17-4, 17-5
VIPP SETCYCLECOPY command, 6-9, 6-27, 17-4,
17-5, 17-12, 26-19
VIPP SETFORM command, 6-9, 17-4, 17-8
VIPP SETMARGIN command, 6-9, 17-4, 17-7
VIPP SETMEDIA command, 17-11, 17-12
VIPP SETMULTIUP command, 6-9, 17-4, 25-27,
25-29
VIPP SETPAGESIZE command, 17-11, 17-12,
26-16
VIPP SETUNIT command, 6-12, 17-7
VIPP SHIFT command, 6-9, 6-12, 17-4, 17-6 to 17-7
VIPP STARTLM command, 17-3, 17-4, 17-10,
17-11, 17-12
VIPP TUMBLEDUPLEX_on command, 6-9, 17-4,
17-6
VIPP TWOUP command, 6-9, 17-4, 25-27, 25-29
VIPP xgf.def file, 17-5, 17-10, 17-14
VIPP xgf.mup core file, 25-28, 25-29
VIPRSC screen parameter, 17-17, 21-15
W
wait time, non-zero, specifying, 18-29 to 18-30
WAITTIME Monitor Queue parameter, 18-17, 20-4
Work with Global Values menu, using, 6-1 to 6-15
Work with Monitor Queue Job command, 19-10
Work with XDPE PCL macros command, 15-34
workstation customizing object, specifying, 18-19
writer job log, 27-6
WRKBGLVAL command, definition of, 6-1
WRKMONQJOB command, 19-10
WRKXPCLMAC command, 15-34
WRKXRSC command, 21-5, 22-9
I-11
Index
X
XDPBCK.FRM, 17-14
XDPE/400
commands, 9-1 to 9-2
definition of, -1, 1-4
features, 1-7
installing, 5-1 to 5-7
overview, 1-1
printing with, 1-6
troubleshooting, 26-1 to 26-15
XDPE/400 application library
definition of, 5-1
library list, adding to, 5-7
XDPE/400 commands, customizing, 6-29 to 6-31
XDPE/400 distributed samples and resources, B-1
XDPE/400 SAMPLE file contents, B-1
XDPEFLR folder
ENCODING subfolder, B-2
FONTS subfolder, 22-10
FORMLIB subfolder, B-2
IMGLIB subfolder, B-2
JDTLIB subfolder, B-2
LPP subfolder, 23-2
MISLIB subfolder, B-2
objects
recreating changed, 5-6
PCLMAC folder, 15-6, 21-8
PCLMUP subfolder, 15-22
resource list subfolders, specifying, 22-5
restoring, 5-5
XESFONTS subfolder, 22-10
XESMUP subdirectory, 25-7
XDPEFLR resource folder contents, B-2
XDPEFTPLOG spool file, 21-12, 21-14
XDPEMSGQ file, 18-32
XDPIVP.FRM, 7-3, 17-14
XDPLPJOB.FRM, 17-14
XDPLPJOB.JDT, 17-14
XDPLPPGE.FRM, 17-14
XDPLPPGE.JDT, 17-14
XDPM printers
considerations when using Flex i-data interface,
A-9
requirements, 4-5
supported, 1-10
XDPSMP.FRM, 17-1, 17-14
XDPSMP.JDT, 17-14
XDPE/400 User Documentation (9/2001)
XDPSPR.JDT, 6-27, 7-3, 17-1, 18-15, 26-19
XES commands
application order, 13-8
methods for generating
combined method, 13-1
direct method, 13-1
indirect method, 13-1
XES commands, created or inserted, 6-9
XES forms
activating, 13-4
placement for logical processing, 23-6
XES mode processing of, 13-6
XES packets
changing, 13-19 to 13-20
control packet, specifying name of, 13-12
creating, 13-9 to 13-19
default, 13-7
deleting, 13-21
generic
contents of, 13-22
creating, 13-24
FONT printer file parameter, using, 13-24
GENXES parameter, using, 13-23
how specified, 13-22
list processing, 13-23
parameters, resetting, 13-22
selecting, 13-6
indirect method, 13-3
multi-up
creating, 25-7 to 25-14
default packets, 25-7
format, 25-11 to 25-14
naming, 25-10 to 25-11
overview, 25-5
requirements, 25-6
syntax, 13-10
XGF.DEF, 17-14
XIVP.JDT, 7-3
XPPM printers
considerations when using Flex i-data interface,
A-9
IVP requirements, 7-2
mode, specifying, 18-9
requirements, 4-4
supported, 1-9
XWSCSTVIPP table, 18-19
I-12