HP DECprint Supervisor (DCPS) for OpenVMS

System Manager's Guide

May 2009

This manual describes how to create DCPS print queues, customize the DCPS environment and troubleshoot common printing problems.

Revision/Update Information: This manual supersedes the System Manager's Guide V2.5.

Software Version: HP DECprint Supervisor (DCPS) for OpenVMS, Version 2.7

Operating System: OpenVMS I64 Version 8.2-1, 8.3 or 8.3-1H1
OpenVMS Alpha Version 6.2, 7.3-2, 8.2 or 8.3
OpenVMS VAX Version 5.5-2, 6.2 or 7.3

Hewlett-Packard Company Palo Alto, California

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Adobe, Adobe PostScript 3 and PostScript are trademarks of Adobe Systems Incorporated.

Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation.

UNIX is a registered trademark of The Open Group.

Contents Index

Preface

Intended Audience

This manual is for OpenVMS system managers and data center operators. Using this guide, you can create and modify print queues, maintain the print jobs and print queues, and set up printing environments to meet the needs of the printing system users.

This guide is also intended for advanced users and applications programmers who customize the printing system using form definitions, setup modules and layup definition files. The User's GuideUser's Guide describes how users access the features of the printing system.

Be sure to read the Software Installation GuideSoftware Installation Guide if you have not installed the DECprint Supervisor software.

Document Structure

This manual contains the following chapters and appendices:

Chapter 1 provides an overview of DCPS features.
Chapter 2 provides information about setting up a new printer or changing the setup of an existing printer.
Chapter 3 explains how to start up the DCPS printing environment and test a printer and print queue.
Chapter 4 explains data types and how to customize your DCPS printing environment to handle the types of jobs your users print.
Chapter 5 describes commands used to maintain and control print jobs, queues and the queue manager.
Chapter 6 explains job separator, log and error pages.
Chapter 7 explains setup modules and device control libraries.
Chapter 8 describes how to create and maintain form definitions.
Chapter 9 describes page accounting information reported by DCPS.
Chapter 10 contains information about using DCPS with specific printers.
Chapter 11 contains information about troubleshooting printing problems.
Appendix A reviews OpenVMS DCL commands used to manage queues, jobs and related system resources.
Appendix B provides information about logical names used by DCPS.
Appendix C explains the use of the DCPS font download utility.
Appendix D explains the difference between DECprint Supervisor (DCPS) and DECprint Printing Services (CPS) software, and their ability to coexist.

**Table 1 DECprint Supervisor Documentation**
Software Installation Guide	Describes how to install DCPS.
System Manager's Guide	Describes how system managers, data center operators and application programmers can create and manage DCPS print queues and solve printing problems.
User's Guide	Describes how to use DCPS to print to PostScript® printers.
Software Product Description (SPD 44.15.xx)	Contains the full list of printers supported by DCPS and additional information about the features and requirements of DCPS V2.7.

Reader's Comments

HP welcomes your comments on this manual. Please send comments to:

openvmsdoc@hp.com

How to Order Additional Documentation

For information about how to order additional documentation, see the HP OpenVMS Systems Documentation Ordering page:

http://www.hp.com/go/openvms/doc/order

Conventions

The following conventions may be used in this manual:

Ctrl/ x A sequence such as Ctrl/ x indicates that you must hold down the key labeled Ctrl while you press another key or a pointing device button.

PF1 x A sequence such as PF1 x indicates that you must first press and release the key labeled PF1 and then press and release another key or a pointing device button.

[Return] In examples, a key name enclosed in a box indicates that you press a key on the keyboard. (In text, a key name is not enclosed in a box.)
In the HTML version of this document, this convention appears as brackets, rather than a box.

... A horizontal ellipsis in examples indicates one of the following possibilities:

Additional optional arguments in a statement have been omitted.
The preceding item or items can be repeated one or more times.
Additional parameters, values, or other information can be entered.

.
.
. A vertical ellipsis indicates the omission of items from a code example or command format; the items are omitted because they are not important to the topic being discussed.

( ) In command format descriptions, parentheses indicate that you must enclose choices in parentheses if you specify more than one.

[ ] In command format descriptions, brackets indicate optional choices. You can choose one or more items or no items. Do not type the brackets on the command line. However, you must include the brackets in the syntax for OpenVMS directory specifications and for a substring specification in an assignment statement.

| In command format descriptions, vertical bars separate choices within brackets or braces. Within brackets, the choices are optional; within braces, at least one choice is required. Do not type the vertical bars on the command line.

{ } In command format descriptions, braces indicate required choices; you must choose at least one of the items listed. Do not type the braces on the command line.

bold type Bold type represents the introduction of a new term. It also represents the name of an argument, an attribute, or a reason.

italic type Italic type indicates important information, complete titles of manuals, or variables. Variables include information that varies in system output (Internal error number), in command lines (/PRODUCER= name), and in command parameters in text (where dd represents the predefined code for the device type).

Example This typeface indicates code examples, command examples, and interactive screen displays. In text, this type also identifies URLs, UNIX commands and pathnames, PC-based commands and folders and certain elements of the C programming language.

UPPERCASE TYPE Uppercase type indicates a command, the name of a routine, the name of a file, or the abbreviation for a system privilege.

- A hyphen at the end of a command format description, command line, or code line indicates that the command or statement continues on the following line.

numbers All numbers in text are assumed to be decimal unless otherwise noted. Nondecimal radixes---binary, octal, or hexadecimal---are explicitly indicated.

Chapter 1
DCPS Overview

1.1 Purpose of the DCPS Software

The DECprint Supervisor software allows people to use and manage networked PostScript printers. For example, it allows users to:

Print customized documents, print two-sided and select input trays.
Modify printed documents without changing the files that are printed, which saves paper and allows the production of custom printed documents.
Print different types of files on the PostScript printers.
Access printers from the OpenVMS operating system and from personal computers (PCs) and Macintosh systems.

The system manager makes the printing system easier to use by providing:

Default queue attributes, so users do not have to specify certain parameters, such as duplex printing
Setup modules, which are stored in device control libraries and are used to modify the printing environment for print jobs
Form definitions, specifying sets of print attributes and including setup modules to make them all easier for users to access
Layup definition files, which you can create to customize the way print jobs are printed on the media

DCPS also provides the following features:

Document Formatting
DCPS allows users to:
- Change the size of pages as they are printed to fit the physical size of media, using the following command:
  $ PRINT /PARAMETERS=(PAGE_SIZE=n,SHEET_SIZE=m) file-spec
- Specify page layup handling as the file is printed, using the following command:
  $ PRINT /PARAMETERS=(LAYUP=option=value)
- Save paper, using one of the following commands:
  $ PRINT /PARAMETERS=(PAGE_LIMIT="n,m") $ PRINT /PARAMETERS=(NUMBER_UP=n)
- Print multiple uncollated copies of each sheet via the SHEET_COUNT parameter.
- Use device control modules for all data types via the /SETUP qualifier. ANSI modules may include control sequences. PCL modules may include binary font data.
Data Type Translation
DCPS lets users print additional file data types, including:
- PCL 4 (Printer Control Language) files generated for printing on Hewlett-Packard LaserJet IID devices
- Proprinter files generated for printing on IBM Proprinter XL24 devices
- ReGIS graphics files (monochrome output only)
- TEKTRONIX files, generated for printing on TEKTRONIX 4010/4014 devices
- ASCII text files, to be printed with line numbers, page headers, and alternating groups of gray and white bars
- DIGITAL Document Interchange Format (DDIF) bitonal image files
Automatic Data Type Detection
Users do not need to specify the data type of the print file, in most cases. DCPS recognizes files of the supported data types and automatically translates them to PostScript before printing.
DCPS can print files that contain both text (ANSI, PCL, or Proprinter data) and PostScript data. For example, users can print electronic mail messages that contain PostScript files. The user submits the print job without specifying any data type. The DCPS software begins printing the file as text and automatically recognizes the change to PostScript, printing the file properly.
See Chapter 4 for information about customizing the printing system to recognize and print the files generated by users at your site.

1.2 DCPS Software Components

The DECprint Supervisor software includes the following components:

A print symbiont, which processes print requests from OpenVMS print queues assigned to the printer
Queue management services, as described in Chapter 5
Data type translators to translate non-PostScript files for printing on PostScript devices
A device control library for setup modules that affect the printing of files, as described in Chapter 7

The version of DCPS software currently running on your system is printed on job and file separator pages and displayed when running DCPS$STARTUP.COM. The logical name DCPS$VERSION also contains the version number. If DCPS$VERSION is undefined, DCPS has not been started on the system.

The DECprint Supervisor symbiont is used in place of the OpenVMS print symbiont, PRTSMB. The software is distributed as executable image files, text, and help files.

Figure 1-1 illustrates the process by which print jobs are produced on an OpenVMS system and delivered to the printer.

Figure 1-1 DCPS Software Components

The software components of a DECprint Supervisor printing system are described in the following sections.

1.2.1 The Print Symbiont

Users send jobs to the printer using the DCL PRINT command or using an application program that generates the OpenVMS system service call SYS$SNDJBC. The print symbiont manages the print jobs. The DECprint Supervisor software performs the following operations:

Maintains resources
Sends control data to the printer
Sends the data file to the printer
Monitors printer progress
Reports printer status
Handles exceptions

For example, suppose a user issues the following PRINT command:

$ PRINT /QUEUE=POST3 /NOTIFY THORNTON.TXT

The PRINT command line is translated to system service calls, which are sent to the job controller. The calls are converted to job controller data structures, which are then passed to the symbiont for processing. The symbiont sends the processed arguments and file data to the printer and notifies the user by displaying messages about the status of the print job.

See the User's GuideUser's Guide for information about the PRINT command and its qualifiers.

1.2.2 Device Control Libraries

A device control library is an OpenVMS text library that contains setup modules. The symbiont uses modules from the device control library to implement the various PRINT parameters. The DECprint Supervisor software extracts the appropriate module, depending on the qualifier that either appears on the PRINT command line or is associated with a print queue, and inserts the module into the data stream.

The device control library also contains modules that the symbiont does not automatically use. Some of these modules contain PostScript procedures, for example, to include an error handler in a print job or to extend the findfont procedure to recognize alternate character encodings. These are described in the User's GuideUser's Guide.

You can create setup modules to be used on your own systems. When you create setup modules, you must store them in a device control library other than the DCPS$DEVCTL library. Create a device control library as described in Chapter 7 and add your library to the device control library search list defined in DCPS$STARTUP.COM.

When you create a site-specific device control library for your custom setup modules, the contents of your library are retained from one version of the DECprint Supervisor software to the next. The standard device control library, DCPS$DEVCTL, is overwritten when you upgrade from one version of the software to the next.

1.2.3 Translators

When a print job submits a print file that is not PostScript (or PCL, if your printer has a native PCL interpreter), the symbiont invokes a translator to translate the user's input file into PostScript. (Refer to Chapter 4 for more information about customizing the printing system for certain types of files.)

DECprint Supervisor software can detect the file data type automatically. You need not specify the data type on the PRINT command line. Translation to PostScript for successful printing is automatic. It is not necessary to maintain generic print queues for default data types.

The system manager can associate a default data type with a generic print queue, allowing users to print files by specifying the generic queue name. See Chapter 3 for more information.

If DCPS incorrectly identifies the data type of a file, you can identify the data type on the command line:

$ PRINT MYFILE.MEM /PARAMETERS=DATA_TYPE=ANSI $ PRINT MYFILE.POST /PARAMETERS=DATA_TYPE=POSTSCRIPT

Contents

Index

Ctrl/ x	A sequence such as Ctrl/ x indicates that you must hold down the key labeled Ctrl while you press another key or a pointing device button.
PF1 x	A sequence such as PF1 x indicates that you must first press and release the key labeled PF1 and then press and release another key or a pointing device button.
`[Return]`	In examples, a key name enclosed in a box indicates that you press a key on the keyboard. (In text, a key name is not enclosed in a box.) In the HTML version of this document, this convention appears as brackets, rather than a box.
...	A horizontal ellipsis in examples indicates one of the following possibilities: Additional optional arguments in a statement have been omitted. The preceding item or items can be repeated one or more times. Additional parameters, values, or other information can be entered.
. . .	A vertical ellipsis indicates the omission of items from a code example or command format; the items are omitted because they are not important to the topic being discussed.
( )	In command format descriptions, parentheses indicate that you must enclose choices in parentheses if you specify more than one.
[ ]	In command format descriptions, brackets indicate optional choices. You can choose one or more items or no items. Do not type the brackets on the command line. However, you must include the brackets in the syntax for OpenVMS directory specifications and for a substring specification in an assignment statement.
\|	In command format descriptions, vertical bars separate choices within brackets or braces. Within brackets, the choices are optional; within braces, at least one choice is required. Do not type the vertical bars on the command line.
{ }	In command format descriptions, braces indicate required choices; you must choose at least one of the items listed. Do not type the braces on the command line.
bold type	Bold type represents the introduction of a new term. It also represents the name of an argument, an attribute, or a reason.
italic type	Italic type indicates important information, complete titles of manuals, or variables. Variables include information that varies in system output (Internal error number), in command lines (/PRODUCER= name), and in command parameters in text (where dd represents the predefined code for the device type).
Example	This typeface indicates code examples, command examples, and interactive screen displays. In text, this type also identifies URLs, UNIX commands and pathnames, PC-based commands and folders and certain elements of the C programming language.
UPPERCASE TYPE	Uppercase type indicates a command, the name of a routine, the name of a file, or the abbreviation for a system privilege.
-	A hyphen at the end of a command format description, command line, or code line indicates that the command or statement continues on the following line.
numbers	All numbers in text are assumed to be decimal unless otherwise noted. Nondecimal radixes---binary, octal, or hexadecimal---are explicitly indicated.