Revision/Update Information: These release notes supersede all other documentation.
Operating System & Versions:
OpenVMS Alpha Version 6.1 or higher
OpenVMS VAX Version 5.5-2 or higher
Software Version:
DECprint Supervisor for OpenVMS,
Version 1.6
Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description.
Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from DIGITAL or an authorized sublicensor.
Copyright © Digital Equipment Corporation 1998. All Rights Reserved.
Copyright © GENICOM Corporation 1998. All Rights Reserved.
The following are trademarks of Digital Equipment Corporation: Alpha, DEC, DEClaser, DECnet, DECprint, DIGITAL, LN03Q, OpenVMS, PATHWORKS, PrintServer, ReGIS, VAX, VMS, and the :DIGITAL logo.
PostScript is a trademark of Adobe Systems Incorporated, which may be registered in certain jurisdictions.
AppleTalk, EtherTalk, LaserWriter, LocalTalk, and Macintosh are registered trademarks of Apple Computer, Inc.
MultiNet is a registered trademark of Process Software Corporation.
Hewlett-Packard, PCL and LaserJet are trademarks of Hewlett-Packard Company.
Proprinter is a registered trademark of International Business Machines Corporation.
Optra is a registered trademark of Lexmark International, Inc.
Colormate is a trademark of NEC.
TEKTRONIX is a trademark of Tektronix, Inc.
All other trademarks and registered trademarks are the property of their respective holders.
This document was prepared using DECdocument V3.2A.
| Contents | Index |
The primary source of information about DECprint Supervisor (DCPS) for OpenVMS, Version 1.6 is the following set of software manuals:
These release notes provide detail on the following:
For information on licensing requirements and the features available with each license, see the DECprint Supervisor Software Product Description (SPD 44.15.xx).
This section describes changes made to DCPS V1.6. You can find more
information for several of these changes elsewhere in these release
notes.
1.1 DCPS Version 1.6 Changes
1.1.1 OpenVMS VAX V5.5-2 and V6.0 Systems Supported
DECprint Supervisor for OpenVMS is now supported on systems running OpenVMS VAX V5.5-2 or later. DCPS V1.4 and V1.5 require a minimum operating system version for VAX systems of OpenVMS VAX V6.1.
The DEC C/C++ Run-Time Components kit must be installed before
installing DCPS on an OpenVMS VAX V5.5-2 or V6.0 system. See the
DECprint Supervisor for OpenVMS Software Installation Guide for more information.
1.1.2 New Printer Support
DCPS V1.6 adds support for the following printers:
You can find more information in Chapter 4 of these release notes.
1.1.3 New Paper Sizes
DCPS supports several new paper sizes, as listed in the table below. You can specify these sizes as the logical PAGE_SIZE value for any printer, and as the physical SHEET_SIZE value for the LNC02 printer.
| Size Name | Size (mm) | Size (inches) |
|---|---|---|
| FOOLSCAP | 203 x 330 | 8.0 x 13.0 |
| SPFOLIO | 216 x 315 | 8.5 x 12.4 |
| UKQUARTO | 203 x 254 | 8.0 x 10.0 |
* Sold in Europe and Asia Pacific areas. |
The following problems have been fixed in DCPS V1.6.
1.2.1 Every Page is Offset on LN40
If the Offset Stacking feature of the DIGITAL Laser Printer LN40 was enabled from the printer's console, DCPS jobs would print with each page offset from the previous page. This problem is fixed, with the following restrictions:
To avoid these restrictions, use the /COPIES or /JOB_COUNT qualifiers
with your PRINT command rather than the SHEET_COUNT parameter. Also, do
not specify a copy count other than 1 when producing a document on a PC.
1.2.2 VFC Files Consume Excessive CPU Time
Starting with DCPS V1.1, printing VFC-formatted files consumed
significantly more CPU time than printing similar non-VFC files. VFC
printing performance has been improved so that printing VFC files uses
approximately the same amount of time as printing non-VFC files.
1.2.3 Layup Files Installed in Incorrect Directory
When installing DCPS on a system on which DCPS was not running, you
were asked where to put DCPS layup files. If you chose a location other
than the default, DCPS would define the layup logical name DCPS$LAYUP
to this alternate location, but the layup files would be moved to the
default location. DCPS now validates the location you specify and
installs the layup files in that location.
1.2.4 LN20 13x19 Paper Tray Not Selectable
When printing to 13x19 (Universal) paper on the DIGITAL Laser Printer LN20, specifying the INPUT_TRAY parameter would cause the job to fail. Specifying the PAPER_SIZE parameter without also specifying INPUT_TRAY would print correctly.
For example, the following command:
$ PRINT /PARAMETERS=INPUT_TRAY=MULTIPURPOSE MY-RESUME.PS |
would return the error message:
%DCPS-F-UNKPAPSIZE, Unknown papersize in selected tray, cannot print job -DCPS-I-JOB_ID, for job MY-RESUME (queue SYS$PRINT, entry 27) on LN20 |
and the following command:
$ PRINT /PARAMETERS=(INPUT_TRAY=MULTIPURPOSE,PAGE_SIZE=13X19) MY-RESUME.PS |
would return the error message:
%DCPS-E-SIZNOTRAY, 13x19 size medium is not in the multipurpose tray in LN20. -DCPS-I-JOB_ID, for job MY-RESUME (queue SYS$PRINT, entry 29) on LN20 %DCPS-E-FLUSHING, Rest of Job (to EOJ) will be ignored |
Under some conditions, especially when the user deleted a currently printing job, the DCPS symbiont would fail. The resulting OPCOM message would be similar to the following:
%%%%%%%%%%% OPCOM 22-JAN-1997 15:02:28.11 %%%%%%%%%%% Message from user SYSTEM on ZIPPY Process SYMBIONT_21: %DCPS-F-INTERNAL_ERROR, Internal error detected at line 427 of file DCPS$:[BUILD.V13]DP_STMGT.C;1, Invalid state change, cannot continue |
The following sections identify the current restrictions that exist
with DECprint Supervisor. See DECprint Supervisor for OpenVMS System Manager's Guide and DECprint Supe rvisor for OpenVMS User's Guide for
printer-specific restrictions.
2.1 Job Remains in Starting State for Raw TCP/IP Queue
If you set up a DCPS queue that uses a raw TCP/IP connection and specify an incorrect TCP port number for the printer, any print jobs that you submit to the queue will remain in a starting state. DCPS cannot determine that you have provided an incorrect port number, because the network failure that it receives is no different than if the printer had been busy or offline.
Note that a print job in a raw TCP/IP queue may remain in a starting state for other reasons as well.
Check the documentation for your printer, network interface card, print
server, or terminal server to determine the correct TCP port number to
use. The TCP port number may also be listed in Table A-1, or in the
DECprint Supervisor for OpenVMS System Manager's Guide.
2.2 Connection Terminations for Raw TCP/IP Queue
You may get CONTERMINATED errors for long print jobs when using raw TCP/IP connections. For jobs that consist of a single file or only use the native PostScript capability of the printer (for example, they do not use native PCL), these errors are most likely to occur at the end of the job, with job trailer pages (if specified for the queue) and print job accounting (if enabled) being lost. For other jobs, these errors may occur in the middle of the job, with subsequent documents as well as the trailer pages and accounting information being lost. DCPS requeues the terminated jobs, placing them in a Holding state so that you can reprint them once you resolve the termination problem.
Some network devices, including the Hewlett-Packard JetDirect cards, drop a TCP/IP connection if they do not receive any input from the host system within a specified amount of time. This is a feature, meant to prevent host software from monopolizing the device. DCPS, however, waits for the printer to acknowledge that previous documents are printed before switching from PostScript to some other native printer language and also before printing a trailer page and gathering accounting information. Even though the printer may be busy, the NIC may not receive any more input from DCPS before the timeout is reached.
If your NIC allows you to alter the TCP/IP idle timeout value, you can work around this problem by disabling or increasing the timeout. Check your NIC documentation to determine if this is possible, and how to do it. Then release any requeued jobs for which desired output was lost, and delete the other requeued jobs.
Note that it is the length of a job in time (versus size) that is
important. For example, a very small PostScript program can take a very
long time to print. Hence, it is difficult to predict how large a
timeout is adequate.
2.3 NOT_READY Warnings for Unavailable Raw TCP/IP Printer
If a job is queued to a printer that uses a raw TCP/IP connection, and the printer is busy or offline, you will get NOT_READY warning messages for the printer.
If you believe or determine that the printer is busy, you can ignore
these messages. DCPS cannot, unfortunately, differentiate between the
printer being busy, offline, or otherwise unavailable.
2.4 Translators do not Generate Color PostScript
The translators provided with DCPS (for example, ReGIS) do not generate
color PostScript commands, even if your source file contains color
information. The colors are instead translated to various shades of
gray.
2.5 Job Trailer Page Jogs with Certain Printers
With certain printers, when job jogging is enabled to separate jobs by offsetting them, jogging occurs between the body of a job and its trailer page. This is because the printer treats the trailer page as though it were a separate print job.
Printers known to exhibit this behavior are:
An attempt to print an ANSI file containing a tray selection escape sequence might fail, depending on which printer you are using. If so, the job aborts with a PostScript configuration error, with the offending command being "setpapertray".
A workaround to this problem is to create and subsequently invoke a setup module that redefines the settoptray, setbottomtray, and setlcittray PostScript commands within the TRN$XLATE_DICT dictionary.
For example, for an HP LaserJet 4M Plus, you should create a setup module that contains the following definitions for settoptray, setbottomtray and setlcittray:
TRN$XLATE_DICT begin
/settoptray { statusdict begin 3 setpapertray end } def
/setbottomtray { statusdict begin 0 setpapertray end } def
/setlcittray { statusdict begin 1 setpapertray end } def
end
|
The first print queue in the process to use AppleTalk fails with the following error and the queue does not start:
%DCPS-W-ATK_FOR_VMS, Error connecting to AppleTalk for VMS driver |
If other queues using the AppleTalk interconnect are started on that same process this error is not reported. These queues will start, but jobs on these queues remain in the "starting" state.
If a queue using the AppleTalk interconnect is started before the AppleTalk network software is running, then the queue might start but will not be functional. This occurs when DCPS is running as a multistreamed symbiont and another print queue is running in the same process.
To recover from such an error, stop all queues supported by any currently running symbiont processes that have detected that the AppleTalk network software is not running (one error message is generated per symbiont process). Restart the AppleTalk software and the queues.
To avoid this problem, run the AppleTalk network software before
starting any DCPS print queues.
2.8 Some Printers Do Not Send Status Messages to the Host
Some PostScript printers, because of their internal architecture, report status information only to the printer console and not to the host system with which they are communicating. As a result, DCPS is not aware of some status conditions (for example, paper out, paper jam, page too complex, cover open, etc.) and cannot report them to you. Instead, the DCPS queue will enter the Stalled state if DCPS subsequently attempts to communicate with the printer. This subsequent attempt may come during the same job that first experienced the problem or in a later one.
The following is a list of some of the printers which exhibit this behavior:
When multinational characters are used in the PostScript
"printername", the printer name printed on the bottom of
separation pages may be printed in the wrong character set.
2.10 DDIF Printing Requires DECwindows Software or DECimage Application Services
To print DDIF encoded bitonal images, DCPS requires that either
DECwindows software or Version 3.1 of DECimage Application Services
(DAS) be installed on your system. DAS is only available on OpenVMS VAX
systems.
2.11 Compatibility of NUMBER_UP and PostScript Drivers
PostScript files created with the LaserWriter 8.0 or 8.1.1 driver or the Adobe 2.1.1 Windows driver in conjunction with the application may produce PostScript files that do not print as expected with NUMBER_UP greater than 1.
Symptoms include pages being clipped, printed outside of the NUMBER_UP
page spots, or being improperly scaled.
2.12 LIST Translator Ignores PAGE_SIZE Parameter
The LIST translator ignores the PAGE_SIZE parameter when formatting pages. It creates pages with maximum content at a size adequate for both A (Letter) and A4 paper:
It is still possible to use PAGE_SIZE and SHEET_SIZE parameters
together (with the DCPS-PLUS license) to scale the logical page onto a
different size sheet.
2.13 Embedded PJL Commands Discarded; Avoid Binary Mode
Drivers that create files for PJL printers, such as those for the DEClaser 5100 and the HP LaserJet IV family, include printer control commands in Hewlett-Packard Printer Job Language (PJL). DCPS filters out and discards that data. Therefore, printer options selected by such drivers do not affect the print job.
When using these drivers, do NOT select binary mode. It will insert
additional commands into the file that can cause incorrect behavior
when printing via DCPS. The exact form of behavior depends on which
printer is actually connected to the queue and whether or not the job
passes through a DCPS translator.
2.14 Unreliable Communication after Errors on Some Printers
Unexpected errors can occur at the end of a print job when printing to some printers using the AppleTalk interconnect. The printers which can exhibit problems include the LaserWriter Pro 600, LaserWriter Pro 630, the LaserWriter IIg, and the LaserWriter IIf. Generally, the unexpected error occurs when an explainable error occurred during the print job; for example, a PostScript error which causes the PostScript interpreter to "Flush to the EOJ", or a timeout error while waiting for manual feed. The behavior a user may see includes one of more of the following:
The user's part of the print job prints as expected. The unexpected
error occurs during the end of job processing (for example, getting the
page count or the job trailer page printed) done by the DECprint
Supervisor. Once the offending job is complete, subsequent jobs print
as expected. No system operator intervention is needed.
2.15 Deleting Job when Using AppleTalk
When printing using an AppleTalk interconnect, a request to delete a
job (DELETE/ENTRY) is accomplished by closing the connection to the
printer. The AppleTalk protocol does not provide for interrupting the
PostScript interpreter; therefore, the printer will continue to print
page descriptions that are contained in its buffer before it stops
printing the job. A job trailer page will not be printed.
2.16 Avoid STOP/QUEUE/RESET Usage for PrintServer Printer which is Rejecting Connections
If you issue a STOP/QUEUE/RESET command for a queue to a DIGITAL
PrintServer printer while there is a job in the "Starting"
state and while the printer is rejecting connections (because, for
example, the PrintServer is powered off or is booting), the queue will
stop. Occasionally the symbiont process will not terminate. Avoid
issuing this command until the PrintServer printer becomes available.
If the job is in the "Starting" state and also in the
PrintServer printer's job queue, a STOP/QUEUE/RESET will execute
correctly.
2.17 No Job Trailer Page on DELETE/ENTRY
If you issue a DELETE/ENTRY command when the printer is printing the
job trailer page, it is possible to delete the printing of this page.
Also, if you issue a DELETE/ENTRY command for a job printing on a
PrintServer printer after all the data for the file is sent, it is
possible that the job trailer page will not print.
2.18 Problems with PostScript Files when Printing with /COPIES
When you use the /COPIES qualifier with a PostScript file, DCPS surrounds each file with a PostScript "save" and "restore" to avoid exhausting virtual memory in the printer.
However, there are infrequent cases when the print job aborts with an invalid restore error message. If this occurs, use the /JOB_COUNT qualifier instead of /COPIES.
| Next | Contents | Index |