HP DECprint Supervisor (DCPS) for OpenVMS

HP DECprint Supervisor (DCPS) for OpenVMS

Release Notes

May 2009

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

© Copyright 2009 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.

Contents

Preface

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:

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

For additional information about HP OpenVMS products and services, see the HP OpenVMS Systems website: 


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

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 Version 2.7 Information

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

1.1 DCPS Version 2.7 Enhancements

1.1.1 New Printers Supported

DCPS V2.7 adds support for the following printers:

HP
CM8050 Color MFP1
CM8050 Color MFP with Edgeline1
CM8060 Color MFP1
CM8060 Color MFP with Edgeline1
Color LaserJet CM1312 MFP
Color LaserJet CM2320 MFP
Color LaserJet CM3530 MFP
Color LaserJet CM6030 MFP
Color LaserJet CM6040 MFP
Color LaserJet CP1513
Color LaserJet CP1514
Color LaserJet CP1515
Color LaserJet CP1516
Color LaserJet CP1517
Color LaserJet CP1518
Color LaserJet CP1519
Color LaserJet CP2024
Color LaserJet CP2025
Color LaserJet CP2026
Color LaserJet CP2027
Color LaserJet CP3525
Color LaserJet CP6015
LaserJet M1522 MFP
LaserJet M2727 MFP
LaserJet M9040 MFP
LaserJet M9050 MFP
LaserJet P2055
LaserJet P3011
LaserJet P3015
LaserJet P4014
LaserJet P4015
LaserJet P4515


Ricoh
Aficio CL3500N
Aficio MP 161
Aficio MP 2510
Aficio MP 3500
Aficio MP 4500
Aficio MP 5500
Aficio SP 8100DN
Aficio SP C811DN


Xerox
Phaser 4510

1.1.2 USB Printing Supported

DCPS now supports printing to USB printers on systems running OpenVMS V8.3 or later.

To create a queue to a USB printer, use the protocol "USB" in the parameter P2 in DCPS$STARTUP.COM: 


    "USB/usb-device"

USB device names are of the type LPAn:. A USB printer will be recognized by OpenVMS at system boot time or when it is plugged in to the system. The printer should keep the same device name regardless of system reboots or the number of times the printer is powered off or disconnected from the system.

1.1.2.1 USB Software Requirements

You must install one of the following patch kits before installing DCPS V2.7 or later:

Table 1-1 USB Patch Kits
OpenVMS Version Patch Kit
OpenVMS I64 V8.3 VMS83I_USB-V0200
OpenVMS I64 V8.3-1H1 VMS831H1I_USB-V0100
OpenVMS Alpha V8.3 VMS83A_USB-V0100

You can obtain these patch kits (or an update to them):

1.1.2.2 USB Troubleshooting

USB devices are different than serial devices because of their "plug-and-play" behavior. Also, most USB printers do not return all the information DCPS expects concerning PostScript errors. Therefore, DCPS relies on the "offline" and "tray empty" information returned by the printer to send status information to the user. The following error messages are returned to the user's terminal and via OPCOM:

DCPS-I-TRAYEMP, Print Engine paper input tray is empty
Explanation: A paper tray is empty.
User Action: Put more paper in the tray.

SYSTEM-I-DEVOFFLINE, device is not in configuration or not available
Explanation: The printer is powered off or not connected.
User Action: Check the printer and cable.

SYSTEM-F-NOSUCHDEV, no such device available
Explanation: The printer device (LPAn:) does not exist.
User Action: Configure the device with UCM.

While troubleshooting a problem with a USB printer, and the printer is not responsive, it might be necessary to disconnect the USB cable for a few seconds, or power-cycle the printer, to return it to a normal state.

It might also be necessary to run the USB Configuration Manager (UCM) to view information about USB devices that have been connected to your system or to diagnose USB printer problems. The UCM utility is described in the HP OpenVMS System Management Utilities Reference Manual and does the following:

For example, you can perform the following command to display information about changes in the USB devices on your system during the time period in which you are interested: 


    $ UCM SHOW EVENTS /TYPE=ALL /SINCE=time

1.1.3 Printer Synchronization Removed

V2.7

Before DCPS V2.7, DCPS would send a query to the printer to see if the printer was busy with another job. This PostScript status query (Ctrl/T) would be sent at the very beginning of every job unless the queue was an LPD queue. DCPS would wait for the printer to respond with a "ready" status before continuing with the job.

Many printers do not respond to this query and, when printing to such a printer, the job would stall and produce no output. This problem was avoided by defining the logical name DCPS$queuename_NO_SYNC , which would cause DCPS to skip the query.

Since this query is usually unnecessary, the default DCPS behavior has been changed to skip the query. Therefore, the logical name DCPS$queuename_NO_SYNC is no longer used and is ignored by DCPS.

It is possible that some printers may require the old behavior in which DCPS sends the query and waits for the response. For such printers, the logical name DCPS$queuename_SYNC can be defined so that the query is sent.

Note

1 Added in DCPS V2.6 ECO 3

1.2 DCPS Version 2.7 Fixes

1.2.1 Stapled Jobs Fail

1.2.1.1 LPD Queues

V2.6 ECO 1

Print jobs would fail if stapling was requested for a job being printed on a DCPS LPD queue. If requested, a separator page would print, but user files would not. No error would be reported.

1.2.1.2 Xerox WorkCenter Pro Printers

V2.6 ECO 3

Print jobs would fail if stapling was requested for a job being printed on a Xerox WorkCentre Pro printer. If requested, a separator page would print, but user files would not. No error would be reported.

Jobs are now stapled, but because of the way these printers process jobs, requested job separator pages will be stapled to the user job.

1.2.1.3 HP Color LaserJet 9500 MFP Printer

V2.6 ECO 3

Print jobs could fail if stapling was requested for a job being printed on an HP Color LaserJet 9500 MFP printer. The following error message could be received even though the requested output bin supported stapled output: 


    %DCPS-E-STPOUTTRAY, Selected output tray does not support stapling 
    -DCPS-I-JOB_ID, for job STAPLE (queue HP9500MFP, entry 725) on HP9500MFP

1.2.2 HP LaserJet P2015 Duplex Jobs Fail

V2.6 ECO 1

Attempting to print a duplex job on the HP LaserJet P2015 printer would result in the error: 


    %DCPS-E-DPLXNOSUP, printer does not support duplex printing

1.2.3 Some Xerox Phaser 4500 Jobs Fail

V2.6 ECO 1

Some print jobs to the Xerox Phaser 4500 would fail, printing a separator page, if requested, but no user output. This problem was reported when using PlanetPress forms but could also occur in other environments.

1.2.4 ANSI LPD Output Formatted for Wrong Paper Size

V2.6 ECO 1

Output was formatted for the wrong size paper if the following were true:

The correct size paper would be used but the output would be formatted incorrectly. For example, if DCPS$SHEET_SIZE was set to "A4", the job would print on A4 size paper but would be formatted for Letter size paper.

V2.7

Output was also formatted for the wrong size paper when the above items were true and when NUMBER_UP was specified.

1.2.5 Jobs to PostScript Level 1 Printers Fail

V2.6 ECO 3

Starting with DCPS V2.6, jobs printed to PostScript Level 1 printers failed with the following error message: 


    %DCPS-W-SYNERR, syntaxerror: Input ended in string or procedure body - 
     offending command is --nostringval--

This problem affected the following printers:

1.2.6 HP LaserJet 9055 and 9065 MFP Output Tray Selection Fails

V2.6 ECO 3

Print jobs would fail if the output tray was specified when printing to the HP LaserJet 9055 MFP and 9065 MFP printers. If the printer was configured to print PostScript errors, a message similar to the following would be printed: 


    ERROR: syntaxerror 
    OFFENDING COMMAND: --nostringval-- 
 
    STACK: 
 
    /bin_1 
    -mark-

1.2.7 Installing from CD Fails

V2.7

When installing DCPS when booted from a read-only device, such as from the OpenVMS installation CD or DVD, an error would be returned and the installation could fail.

Before DCPS V2.6 ECO 3, the installation would fail: 


Examining system environment ... 
 
%DCL-W-UNDSYM, undefined symbol - check validity and spelling 
 \NUMBER_OF_NODES\

With DCPS V2.6 ECO 3: 


Examining system environment ... 
%SORT-F-OPENOUT, error opening * as output 
-RMS-E-WLK, device currently write locked

1.2.8 Information on LPD Banner Pages Missing

V2.7

Some printers can be configured to print LPD banner pages. The printer's LPD banner page is not printed by DCPS and is not the same as the job or file separator pages printed by DCPS. The printer uses data from the LPD job to include information about the job on the page, such as system name, user name and job name. DCPS did not send this information to the printer, so the system and user names displayed as "unknown" and the job name displayed as an internal representation of the job name.

DCPS now sends this information to the printer so the correct information is used on the printer's LPD banner page, if the printer is configured to print its own LPD banner page.

Next Contents