HP DECprint Supervisor (DCPS) for OpenVMS

This manual contains information about the current release of DCPS.

Revision/Update Information: These release notes supersede all other documentation.

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

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

Hewlett-Packard Company Palo Alto, California

© Copyright 2005 Hewlett-Packard Development Company, L.P.

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.

Printed in the U.S.

The DECprint Supervisor documentation set is available on CD-ROM.

Contents

Intended Audience

These release notes describe new features, bug fixes, usage hints, restrictions and other useful information for this release of DECprint Supervisor. System managers and users should review this document for new information about installing and using this release of DCPS.

Document Structure

These release notes contain the following chapters and appendices:

• Chapter 1 describes changes included in DCPS V2.5.
• Chapter 2 provides information about using DCPS with specific printers.
• Chapter 3 identifies current restrictions that exist with DCPS V2.5.
• Chapter 4 contains information about OpenVMS operating system problems that are known to impact DCPS.
• Appendix A lists commonly-used port numbers used when setting up IP printers.

Related Documents

The primary source of information about DCPS is the following set of software manuals:

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.5.

For additional information about HP OpenVMS products and services, visit the following World Wide Web address:

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

Reader's Comments

HP welcomes your comments on this manual. Please send comments to either of the following addresses:

Internet	openvmsdoc@hp.com
Mail	Hewlett-Packard Company OSSG Documentation Group, ZKO3-4/U08 110 Spit Brook Road Nashua NH 03062-2698

How to Order Additional Documentation

For information about how to order additional documentation, visit the following World Wide Web address:

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

Part numbers for DCPS-related documentation are listed in the Ordering Additional Documentation appendix of the Software Installation Guide, System Manager's Guide and User's Guide.

Conventions

The following conventions are 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.
[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.
( )	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 text	This typeface represents the introduction of a new term. It also represents the name of an argument, an attribute or a reason.
italic text	Italic text 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).
UPPERCASE TEXT	Uppercase text indicates a command, the name of a routine, the name of a file, or the abbreviation for a system privilege.
Monospace text	Monospace type indicates code examples and interactive screen displays.
-	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.

This section describes changes included in DCPS V2.5. You can find more information for several of these changes elsewhere in these release notes.

1.1 DCPS Version 2.5 Changes

DCPS V2.5 adds support for the following printers:

HP Color LaserJet 3000
HP Color LaserJet 3800
HP Color LaserJet 4610
HP Color LaserJet 4700
HP Color LaserJet 4730 MFP
HP LaserJet 1300
HP LaserJet 1320
HP LaserJet 4240
HP LaserJet 5200
Xerox DocuPrint N4525

DCPS now works with remote LPD queues and with more printers that support LPD.

1.1.2.1 Spooling Overview

Remote LPD queues, and many LPD printers, require the size of the job to be known before the job is sent. DCPS can now produce a temporary spool file so the size can be determined. By default, DCPS LPD jobs will use the pre-V2.5 behavior, so specific action must be taken to send DCPS LPD jobs to remote LPD queues or LPD printers that require it. Spooling can be specified for the whole system or for individual queues by defining logical names.

Because spooling requires an extra step to create the temporary spool file, you should enable spooling only for printers that require it. Common reasons to use spooling are:

• You are printing to a remote LPD queue on another system.
• Your printer does not print anything when using DCPS LPD without spooling.
• Your printer is a larger multi-function device that does not work with DCPS when using the Raw TCP protocol, or LPD protocol without spooling. These devices often have their own internal queues that accept jobs for later printing.

To enable spooling, define one of the following logical names. Neither of these logical names are defined by default.

• DCPS$SPOOL
  When defined, all LPD jobs from all queues will create a temporary spool file before being sent to the printer or remote queue.
• DCPS$queue-name_SPOOL
  When defined, LPD jobs from this queue will create a temporary spool file before being sent to the printer or remote queue.

To specify where temporary spool files will be created, the following logical name is used. This logical name is always defined.

• DCPS$SPOOL_DIRECTORY
  Spool files will be created in this directory and deleted after being sent to the printer or remote queue. Print jobs are not spooled unless spooling is enabled with one of the two logical names above.
  You will be asked for the location for your DCPS spool directory when installing DCPS if it is not already defined. The default location is SYS$COMMON:[DCPS$SPOOL], but you should specify a location on a non-system disk that is available to all queues for which spooling is enabled. This directory is protected such that only the DCPS print symbiont process and privileged users can view the spool files.

Error messages you can receive while using spooling are:

Table 1-1 Spool File Error Messages

Error Message	Description
SPOOLBADDEVICE	Error in DCPS$SPOOL_DIRECTORY device name
SPOOLBADDIR	DCPS$SPOOL_DIRECTORY directory not found
SPOOLERROR	Error creating spool file in DCPS$SPOOL_DIRECTORY
SPOOLFILENOOPEN	Error opening spool file
SPOOLNOLOGICAL	Logical name DCPS$SPOOL_DIRECTORY is undefined
SPOOLNOPRIV	No privilege to write to DCPS$SPOOL_DIRECTORY
SPOOLNOWRITE	DCPS$SPOOL_DIRECTORY device is write-locked

1.1.3 Improved Installation Procedure

When installing DCPS V2.4 with the POLYCENTER Software Installation Utility (PCSI), the installation procedure required all DCPS queues in the cluster to be stopped before proceeding with the installation. Now, you are given choices including stopping only the queues that will be affected by the installation.

1.1.4 Flag Page Improvement

DCPS separator pages display information about the printer in the lower right-hand corner of the page: the product name and, if different, the printer name. (The product name cannot be customized, but the printer name can be changed for each printer.)

Now, the printer name is displayed in parentheses to differentiate it from the product name.

1.2 DCPS Version 2.5 Fixes

The following problems are fixed in DCPS V2.5.

1.2.1 Problems Starting Queues and Deleting Jobs

In DCPS V2.3 and V2.4, problems might arise when a Raw TCP job was in Starting state:

• If the job was aborted with a DELETE /ENTRY command, DCPS would take a long time to delete the job.
• If the queue was stopped with a STOP /QUEUE /RESET command, starting this or other queues would then sometimes fail with the following error:

  %DCPS-F-STREAMUSE, Request 4 for Stream Id n ignored. Not consistent with symbiont state

Now, starting jobs will abort quickly when requested, and stopping the queue will not cause the STREAMUSE error when subsequently starting queues.

1.2.2 Job Fails when Selecting Trays

In DCPS V2.4, requesting a tray by specifying the INPUT_TRAY parameter could result in the job failing with a INTRAYNOTAVL error message. For example, specifying /PARAMETERS=INPUT_TRAY=TRAY_2 when printing to an HP LaserJet 8150 printer would result in the following error messages:

%DCPS-E-INTRAYNOTAVL, No tray_2 tray is installed on HP LaserJet 8150 -DCPS-I-JOB_ID, for job MYJOB (queue HP8150_RAW, entry 245) on HP8150_RAW %DCPS-E-FLUSHING, Rest of Job (to EOJ) will be ignored -DCPS-I-JOB_ID, for job MYJOB (queue HP8150_RAW, entry 245) on HP8150_RAW

This problem would occur when selecting trays on the following printers:

HP LaserJet 2100
HP LaserJet 2200
HP LaserJet 8000
HP LaserJet 8100
HP LaserJet 8150

If the LaserJet 9000 printer was set to staple jobs by default, the DCPS STAPLE=NONE parameter would have no effect and DCPS jobs would always be stapled. Now, overriding the printer's default staple setting by specifying STAPLE=NONE correctly produces a non-stapled job.

This problem was fixed for other printers in DCPS V2.4, but the problem remained for the LaserJet 9000 printer.

1.2.4 LPD Jobs Fail with PostScript Error

If the logical name DCPS$queue-name_PRODUCT_NAME was not defined for an LPD queue, print jobs could fail with a PostScript "checkconfiguration" error. As with any PostScript error with LPD jobs, if PostScript error reporting was not enabled on the printer, the job would fail with no error indicated.

Now, if the logical name is not defined, DCPS assumes it is an "unrecognized" printer and the job will not fail with this error.

1.2.5 AppleTalk File Omitted from Kit

The AppleTalk file DCPS$BE_APPLETALK.EXE was inadvertently omitted from the DCPS V2.4 PCSI kit for OpenVMS Alpha and VAX. This file is now included in the DCPS V2.5 kit.

1.2.6 Performance on Integrity Systems

When running on OpenVMS I64, DCPS V2.4 symbiont processes could use large amounts of CPU time when printing. Performance in V2.5 has been greatly improved.

1.2.7 Incorrect OLDSETUP Message During Startup

When starting DCPS in "setup" mode, it was possible to incorrectly receive a message indicating your startup command procedure was newer than your setup file. The following message could be displayed even if the startup file had not been changed since the setup file had been created:

%DCPS-W-OLDSETUP, setup file older than startup file

The result was that a new setup file was created and the commands to start queues in DCPS$STARTUP were executed. Although all queues were correctly started, this caused a slower startup compared to the desired behavior of using information in the setup file. This check is now handled correctly.