V'()V

8HP DECprint Supervisor (DCPS) for OpenVMSA

HP DECprint Supervisor (DCPS) for OpenVMS

Release Notes

November 2005

>This manual contains information about the current release of DCPS.

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

"Software Version:7HP 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

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

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

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

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

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

1UNIX is a registered trademark of The Open Group.

Printed in the U.S.

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

,
OContents

Preface

Intended Audience

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

Document Structure

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

**Table 1 DECprint Supervisor Documentation**
* Software Installation Guide	$ Describes how to install DCPS.
% System Manager's Guide	K Describes how system managers, data center operators and application D programmers can create and manage DCPS print queues and solve printing problems.
User's Guide	E 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 D additional information about the features and requirements of DCPS V2.5.

Reader's Comments

BHP 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
H

How to Order Additional Documentation

GFor 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

2The following conventions are used in this manual:
Ctrl/ x A sequence such as Ctrl/N x indicates that you must hold down the key labeled Ctrl while 8 you press another key or a pointing device button.
[Return] K In examples, a key name enclosed in a box indicates that you press a J key on the keyboard. (In text, a key name is not enclosed in a box.)K
In the HTML version of this document, this convention appears as " brackets, rather than a box.
... G A horizontal ellipsis in examples indicates one of the following possibilities:
I
Additional optional arguments in a statement have been omitted.H
The preceding item or items can be repeated one or more times.M
Additional parameters, values, or other information can be entered.

( ) I In command format descriptions, parentheses indicate that you must B enclose choices in parentheses if you specify more than one.
[ ] N In command format descriptions, brackets indicate optional choices. You L can choose one or more items or no items. Do not type the brackets on M the command line. However, you must include the brackets in the syntax M for OpenVMS directory specifications and for a substring specification ! in an assignment statement.
| L In command format descriptions, vertical bars separate choices within L brackets or braces. Within brackets, the choices are optional; within M braces, at least one choice is required. Do not type the vertical bars on the command line.
{ } L In command format descriptions, braces indicate required choices; you N must choose at least one of the items listed. Do not type the braces on the command line.
bold text G This typeface represents the introduction of a new term. It also C represents the name of an argument, an attribute or a reason.
italic text N Italic text indicates important information, complete titles of manuals H or variables. Variables include information that varies in system output (Internal error4 number), in command lines (/PRODUCER== name) and in command parameters in text (whereF dd represents the predefined code for the device type).
UPPERCASE TEXT M Uppercase text indicates a command, the name of a routine, the name of 9 a file, or the abbreviation for a system privilege.
Monospace text M Monospace type indicates code examples and interactive screen displays.
- K A hyphen at the end of a command format description, command line or I code line indicates that the command or statement continues on the following line.
numbers L All numbers in text are assumed to be decimal unless otherwise noted. I Nondecimal radixes---binary, octal or hexadecimal---are explicitly indicated.

Chapter 1
DCPS Version 2.5 Information

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

1.1 DCPS Version 2.5 Changes

1.1.1 New Printers Supported

2DCPS 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

1.1.2 Enhanced LPD Support

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

1.1.2.1 Spooling Overview

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

FBecause spooling requires an extra step to create the temporary spool Dfile, 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.H
Your printer does not print anything when using DCPS LPD without spooling.I
Your printer is a larger multi-function device that does not work E with DCPS when using the Raw TCP protocol, or LPD protocol without D spooling. These devices often have their own internal queues that ! accept jobs for later printing.

1.1.2.2 Enabling Spooling

GTo 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 I all queues will create a temporary spool file before being sent to the printer or remote queue.I
DCPS$queue-name_SPOOL
When defined, E LPD jobs from this queue will create a temporary spool file before , being sent to the printer or remote queue.

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

1.1.2.3 Spooling Errors

<Error messages you can receive while using spooling are:

o ( &
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 7 Error creating spool file in DCPS$SPOOL_DIRECTORY
SPOOLFILENOOPEN Error opening spool file
SPOOLNOLOGICAL 4 Logical name DCPS$SPOOL_DIRECTORY is undefined
SPOOLNOPRIV 3 No privilege to write to DCPS$SPOOL_DIRECTORY
SPOOLNOWRITE 1 DCPS$SPOOL_DIRECTORY device is write-locked
E

**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	7 Error creating spool file in DCPS$SPOOL_DIRECTORY
SPOOLFILENOOPEN	Error opening spool file
SPOOLNOLOGICAL	4 Logical name DCPS$SPOOL_DIRECTORY is undefined
SPOOLNOPRIV	3 No privilege to write to DCPS$SPOOL_DIRECTORY
SPOOLNOWRITE	1 DCPS$SPOOL_DIRECTORY device is write-locked

1.1.3 Improved Installation Procedure

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

1.1.4 Flag Page Improvement

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

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

1.2 DCPS Version 2.5 Fixes

.The following problems are fixed in DCPS V2.5.U

1.2.1 Problems Starting Queues and Deleting Jobs

FIn 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.C
If the queue was stopped with a STOP /QUEUE /RESET command, C starting this or other queues would then sometimes fail with the following error:
"
C %DCPS-F-STREAMUSE, Request 4 for Stream Id n ignored. ' Not consistent with symbiont state

GNow, starting jobs will abort quickly when requested, and stopping the Dqueue will not cause the STREAMUSE error when subsequently starting queues.J

1.2.2 Job Fails when Selecting Trays

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

"
J %DCPS-E-INTRAYNOTAVL, No tray_2 tray is installed on HP LaserJet 8150 N -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 N -DCPS-I-JOB_ID, for job MYJOB (queue HP8150_RAW, entry 245) on HP8150_RAW

HThis 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

1.2.3 Stapling Error

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

HThis 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

BIf the logical name DCPS$queue-name_PRODUCT_NAME was not Bdefined for an LPD queue, print jobs could fail with a PostScript H"checkconfiguration" error. As with any PostScript error with HLPD 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 E"unrecognized" printer and the job will not fail with this error.R

1.2.5 AppleTalk File Omitted from Kit

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

1.2.6 Performance on Integrity Systems

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

1.2.7 Incorrect OLDSETUP Message During Startup

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

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

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

h k

Contents

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

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