hp DECprint Supervisor (DCPS) for hp OpenVMS

Release Notes

January 2003

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 hp OpenVMS, Version 2.2

Operating System: hp OpenVMS Alpha, Version 6.2, 7.2-2, 7.3 or 7.3-1
hp OpenVMS VAX, Version 5.5-2, 7.2 or 7.3

Hewlett-Packard Company Palo Alto, California

Confidential computer software. Valid license from HP and/or its subsidiaries 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.

Neither HP nor any of its subsidiaries shall be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for HP products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty.

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

Contents Index

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.

Note

Starting with DCPS V2.0, the need for DCPS-OPEN and DCPS-PLUS licenses has been eliminated. The right to use all features of DCPS is now included with the OpenVMS operating system license.

Document Structure

These release notes contain the following chapters and appendices:

Chapter 1 describes changes included in DCPS V2.2.
Chapter 2 provides information about using DCPS with specific printers.
Chapter 3 identifies current restrictions that exist with DCPS V2.2.
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.
Appendix B lists files installed by DCPS V2.2 on OpenVMS Alpha systems.
Appendix C lists files installed by DCPS V2.2 on OpenVMS VAX systems.

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

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.openvms.compaq.com/

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.

Chapter 1
DCPS Version 2.2 Information

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

1.1 DCPS Version 2.2 Changes

1.1.1 New Printers Supported

DCPS V2.2 adds support for the following printers:

GENICOM Intelliprint mL260
HP Color LaserJet 2500
HP Color LaserJet 5500
HP LaserJet 4200
HP LaserJet 4300
HP LaserJet 5100
HP LaserJet 4100 MFP
HP LaserJet 9000 MFP
Lexmark C750

1.1.2 Autostart Queues Supported

DCPS now supports the autostart feature for execution queues. To make a DCPS queue be an autostart queue, specify AUTOSTART_ON in the P2 parameter to DCPS$EXECUTION_QUEUE in DCPS$STARTUP.COM. For example:

$ IF .NOT. SETUP_MODE THEN @SYS$STARTUP:DCPS$EXECUTION_QUEUE - COLOR_PRINTER - AUTOSTART_ON=(FOO,BAR)::"IP_RawTCP/hp5500.lkg.dec.com" - DCPS_LIB

In this example, the execution queue COLOR_PRINTER, printing to the printer at hp5500.lkg.dec.com over raw TCP, is set to autostart on nodes FOO and BAR.

Please note the following details concerning autostart:

The same procotol and device is used on all nodes. You must ensure the printer device is available on any node specified in the autostart list.
DCPS does not check the node name(s) you specify to determine if it is an existing node name. Be sure to specify the node name correctly.
You must ensure that DCPS is installed and configured on every node specified in the autostart list.
DCPS autostart queues are activated for autostart when DCPS$STARTUP is run, unless it is being run in setup mode. (See Section 1.1.4 for more information about running the DCPS startup procedure in setup mode.)
AUTOSTART_ON may be abbreviated as AUTO.
Do not use double colons (::) when specifying nodes in the autostart list. A double colon must be used to separate the list of autostart nodes and the rest of the P2 parameter.

1.1.3 Port Number Made Optional

Previously, if you were using raw TCP to print, a port number had to be specified in the P2 parameter to DCPS$EXECUTION_QUEUE in DCPS$STARTUP.COM. Port 9100 is now assumed if no port number is specified.

1.1.4 New Setup Mode for Startup Procedure

The DCPS startup procedure, DCPS$STARTUP, can now be run in a shortened "setup" mode. This mode would most commonly be used if your queues are autostart queues, and you wanted to speed up the execution of DCPS$STARTUP. In setup mode, logical names needed by DCPS are defined, but no queues are created, modified or started.

To run DCPS$STARTUP in setup mode, pass SETUP as the P1 parameter. For example,

$ @SYS$STARTUP:DCPS$STARTUP SETUP

To define logical names, DCPS$STARTUP now creates a "setup file" each time it runs in normal (non-setup) mode. This file is called DCPS$STARTUP_SETUP.COM and is run when DCPS$STARTUP is later run in setup mode. The setup file should not be modified and is only for use by DCPS$STARTUP.

Please note the following details concerning setup mode:

When run in setup mode, all commands in DCPS$STARTUP.COM are executed, except for initializing or modifying queues with calls to DCPS$EXECUTION_QUEUE and DCPS$GENERIC_QUEUE. All other code, such as creating LAT devices or defining queue-related logical names such as DCPS$queuename_NO_SYNC will be executed.
If the setup file does not exist when DCPS$STARTUP is run in setup mode, startup will run in normal mode and a setup file will be created.
DCPS$STARTUP will display whether it is running in setup or normal mode.
If running in setup mode, DCPS$STARTUP will display the creation date of the setup file it is using.
If running in setup mode, and DCPS$STARTUP.COM has been modified since the setup file was created, an informational message will be displayed. Startup will continue in setup mode, ignoring changes to the procedure made in the portion of DCPS$STARTUP that does not run in setup mode. In this case, DCPS$STARTUP.COM should be reviewed to see if any changes affecting queues were made, and run again in normal mode so a new setup file can be created.
To use DCPS$STARTUP in setup mode, you must copy the new DCPS$STARTUP.TEMPLATE to DCPS$STARTUP.COM and incorporate your site-specific modifications.

1.1.5 New Generic HP Class of Printer

If you try to print to a printer model unsupported by DCPS, the printer is classified as an "unrecognized" printer and while printing is attempted, it may not be successful.

DCPS now has a "generic HP" class of printer to help in printing to new HP printer models. When printing to an HP printer not recognized by DCPS, a set of paper sizes, tray names and commands to select those trays, known to work with HP printers, are used. Therefore, features not available with an "unrecognized" printer are probably available with an "generic HP" printer. These features include tray selection and use of the printer's native PCL interpreter.

If a printer is being treated as a "generic HP" printer, an OPCOM message will be issued similar to the one used with "unrecognized" printers:

%%%%%%%%%%% OPCOM 14-NOV-2002 16:25:43.37 %%%%%%%%%%% Message from user SYSTEM on FUNYET Queue NEW_PRINTER: %DCPS-W-HPGENERIC, Product name hp LaserJet 9999 not recognized; assuming HP Generic

1.2 DCPS Version 2.2 Fixes

The following problems are fixed in DCPS V2.2.

1.2.1 Tray Name Restored

In DCPS V2.1, the output tray SIDE was inadvertently removed from the possible trays on the HP LaserJet 8000, 8100 and 8150 printers. This tray was still selectable with the name STACKER, but is now selectable by either name.

Chapter 2
Printer-Specific Information

The following sections provide information about using DCPS with specific printers. The System Manager's GuideSystem Manager's Guide and User's GuideUser's Guide contain additional printer-specific information.

2.1 Problems Starting Queues

Some HP printers do not respond to the DCPS synchronization request at the beginning of a job. Therefore, you must define the logical name DCPS$queuename_NO_SYNC before queues to these printers are started, or DCPS jobs will not start. See Section 3.2 in these Release Notes or the System Manager's GuideSystem Manager's Guide for more information. The printers for which you must define the logical name are:

HP Color LaserJet 2500
HP Color LaserJet 5500
HP LaserJet 4200
HP LaserJet 4300

It is also recommended that the printer's personality setting be set to PS (PostScript).

Note

Setting the printer's personality to PS (PostScript) alone will not solve the problem for these printers. This problem is expected to be resolved in a future version of printer firmware.

2.2 HP Color LaserJet 2500

The HP Color LaserJet 2500 printer cannot detect the size of paper in its trays, even if the size has been specified via the printer's console. Therefore, the following restrictions apply when using DCPS with this printer:

It is not possible to select media by paper size.
If paper of a different size than the default is loaded in a tray, its size will be considered as the default size. For example, if the default printer paper size is letter, a legal-size document will be truncated to letter size when printing on legal size paper.

2.3 HP LaserJet 4200, 4300 and 9000 MFP

Output trays STACKER and STAPLER refer to the same physical tray, included with the printer's optional finisher.

The preferred way to specify stapling is with the DCPS parameter STAPLE, which offers four different staple positions and takes page orientation into account when determining staple position. Therefore, when specifying stapled output with the STAPLE parameter, use OUTPUT_TRAY=STACKER.

If you specify OUTPUT_TRAY=STAPLER, the printer will staple output by default and place the staple in the printer's default staple position. Job burst and flag pages, if any, will be stapled to your job.

Not all staple positions are possible given the printer's paper feed direction and page orientation specified. Also, the HP LaserJet 9000 offers more possible stapling positions than the LaserJet 4200 and 4300 printers, which can staple only at the top left for portrait output and top right for landscape output.

Contents

Index

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