| Previous | Contents | Index |
This section contains information about other problems that are known to impact DECprint Supervisor and remedial patch kits ("ECOs") that address some of these problems.
You can obtain these remedial patch kits (or an update to them)
Over time, DCPS print symbiont processes may consume increasing amounts of memory and pagefile space, resulting in system performance problems. This problem is seen only on OpenVMS Alpha V7.1-2 systems.
The following DECthreads patch kit fixes this problem:
All sites running DECprint Supervisor as a multistreamed process on OpenVMS V7.1 and earlier should install the Queue Manager Remedial Update.
The Queue Manager remedial update kits are:
This update corrects problems that cause the START/QUEUE command to hang under certain circumstances when operating with a multistreamed symbiont. The release notes provided with the kit describe all the problems fixed by this update. After installing this update, you need to reboot your system to enable these changes.
If this update is not installed you may encounter the following problem. If a queue running in a multistreamed process is stopped with STOP/QUEUE/RESET, then quickly started with START/QUEUE, it is possible that the start request will hang. In addition, sometimes the following message will be written to OPCOM:
%DCPS-F-STREAMUSE, Request 4 for Stream Id x ignored. Not consistent with symbiont state |
To recover, issue a Ctrl/Y to return to the DCL prompt, then issue a
STOP/QUEUE/RESET again, wait a few seconds, and try to start the queue
again. To avoid this problem, install the queue manager update.
3.3 Problem Starting Queues for LAT- and Direct-Connected Printers
There is an OpenVMS V7.0 terminal driver problem that may hinder you in using DCPS with LAT- and direct-connected printers. The symptom is that the associated queue cannot be started, with messages like the following being written to OPCOM:
%%%%%%%%%%% OPCOM 31-OCT-1995 21:53:55.73 %%%%%%%%%%% Message from user SYSTEM on FUNYET Queue SYS$PRINT: %DCPS-E-UNSUPPORTED, unsupported operation or function %%%%%%%%%%% OPCOM 31-OCT-1995 21:53:55.74 %%%%%%%%%%% Message from user QUEUE_MANAGE on FUNYET %QMAN-I-QUENOTSTART, queue SYS$PRINT could not be started on node FUNYET %%%%%%%%%%% OPCOM 31-OCT-1995 21:53:55.74 %%%%%%%%%%% Message from user QUEUE_MANAGE on FUNYET -SYSTEM-F-ABORT, abort |
The failure may be constant or intermittent. If you subsequently attempt to start the queue, you may succeed.
The following patch kits fix this problem:
There is an OpenVMS terminal driver problem that may result in your printer reporting I/O problems when connected to a serial port of your OpenVMS system. You may see the problem with OpenVMS Alpha V6.2 through V7.0, and with OpenVMS VAX V5.5 through V7.0, depending in part on what kind of serial port you are using.
The problem is that the terminal driver sometimes does not respond quickly enough to an XOFF request from the printer to prevent the printer from losing data.
This problem is fixed in OpenVMS Alpha V7.1.
The following patch kits fix this problem:
There is a DECthreads problem on OpenVMS VAX V7.0 and V7.1 systems that results in the DCPS symbiont aborting with an INSFMEM error. The DCPS symbiont consumes an increasing amount of memory over time, eventually aborting when it attempts to obtain more than the available dynamic memory. The probability of the symbiont aborting increases with each new print job that it processes.
The following patch kits fix this problem:
The DCPS symbiont can abort with an ACCVIO or BADPARAM error, possibly also indicating the CMA (DECthreads) facility, beginning 19 May 1997. Other software on your system, including DIGITAL TCP/IP Services for OpenVMS and anything layered upon DECthreads, may also fail after this date.
The problem is related to a long-standing OpenVMS restriction of fewer than 10,000 days in a delta-time value. POSIX-related software in particular, using the UNIX reference date of 1 January 1970, can encounter this limit on and after 19 May 1997. Refer to the OpenVMS web pages ( http://www.openvms.compaq.com ) for more information about the "Delta-Time Limit".
The following patch kits fix this problem:
The following sections provide information about using DCPS with
specific printers. The DECprint Supervisor for OpenVMS System Manager's Guide and DECprint Supervisor mlreference os_namefor OpenVMS User's Guide contain additional
printer-specific information.
4.1 HP LaserJet 2100
4.1.1 Media Size Not Selectable
The HP LaserJet 2100 printer cannot detect the size of paper in its trays. Therefore, the following restrictions apply when using DCPS with this printer:
To avoid printing on the wrong size paper, set the tray with the
default paper size "unlocked" and set all other trays "locked".
4.2 HP LaserJet 4050
4.2.1 Minimum Firmware Version
To use an HP LaserJet 4050 printer, it is recommended that the printer be running a minimum firmware version of 19991030 MB6.30. Earlier versions of firmware may cause problems such as misprinted or missing characters when using the DCPS ANSI translator, especially when printing jobs with landscape orientation or NUMBER_UP. This firmware version number is displayed as Firmware Datecode on the printer's configuration page.
If your printer is running an older version of firmware, contact HP and
request the proper version. The new firmware will be sent on a SIMM to
be installed in your printer.
4.3 HP LaserJet 8100 and 8150
4.3.1 Optional Mailbox
DCPS numbers the optional mailbox bins on the HP LaserJet 8000 printer
from 1-5, 1-7 or 1-8, depending on the particular option installed.
This is consistent with the numbers molded into the plastic beside the
bins. The printer's console, in contrast, refers to these same bins as
numbers two through nine. Refer to the HP LaserJet User Guide
for your printer model for more information about the numbering and
purpose of trays with different options and configurations.
4.3.2 Problems Starting Queues
Some models in this series may not allow DCPS jobs to start. To resolve
this, either set the printer to PostScript mode or suppress DCPS's
PostScript synchronization. See Section 15.2.11 in these Release Notes or
the DECprint Supervisor for OpenVMS System Manager's Guide for more information.
4.4 Lexmark Optra S and T Series
4.4.1 Problems Starting Queues
Some models in the Lexmark Optra S and Optra T series may not allow
DCPS jobs to start. To resolve this, either set the printer to
PostScript mode or suppress DCPS's PostScript synchronization. See
Section 15.2.11 in these Release Notes or the DECprint Supervisor for OpenVMS System Manager's Guide for more
information.
4.5 Tektronix Phaser
4.5.1 Printer Configuration Settings
You must change the following AppSocket settings when using Phaser printers with DCPS:
| AppSocket Setting | Value |
|---|---|
| Interpreter | PostScript |
| Filtering | Interpreter-Based |
This section describes changes included in DCPS V1.8. You can find more
information for several of these changes elsewhere in these release
notes.
5.1 DCPS Version 1.8 Changes
5.1.1 New Printer Support
DCPS V1.8 adds support for the following printers:
GENICOM LN21
GENICOM LN28
GENICOM LNM40
GENICOM microLaser 170
GENICOM microLaser 210
GENICOM microLaser 280
GENICOM microLaser 320
GENICOM microLaser 401
HP LaserJet 8000
Lexmark Optra S 1625
Lexmark Optra S 1855
Tektronix Phaser 780
You can find more information in Chapter 4 of these release notes.
5.1.2 Some DCPS Stapling Restrictions Removed
DCPS supports the stapling option on the LN32, LNM40, mL320 and mL401 printers.
In DCPS V1.7-1, you could not automatically staple jobs containing more than one file. Starting with DCPS V1.8, jobs with multiple files will be automatically stapled if requested.
In DCPS V1.7-1, you could not automatically staple PCL jobs. Starting with DCPS V1.8, PCL files will be automatically stapled if requested. If stapling is requested, PCL files will be translated to PostScript using the DCPS PCL4 translator, rather than being interpreted by the printer's native PCL interpreter. If your PCL file contains any PCL escape sequences introduced after PCL4, the sequences will be ignored.
Refer to DECprint Supervisor for OpenVMS User's Guide for information about using the stapling option
from DCPS.
5.2 DCPS Version 1.8 Fixes
The following problems are fixed in DCPS V1.8.
5.2.1 Symbiont Aborts When IP Names Are Used
When using DCPS V1.7-1 or earlier with DIGITAL TCP/IP Services for OpenVMS, V5.0, on Alpha systems, the DCPS print symbiont could abort when the TCP/IP host name for a printer was resolved to an address by a DNS server. This problem did not occur with TCP/IP Services V5.0 on VAX systems, or with TCP/IP Services V4.2 or earlier. This problem has also been resolved in Compaq TCP/IP Services for OpenVMS, V5.1.
OPCOM messages similar to the following were displayed:
%%%%%%%%%%% OPCOM 3-MAR-1999 15:38:25.08 %%%%%%%%%%%
Message from user SYSTEM on FUNYET
Process SYMBIONT_407: %SYSTEM-F-STKOVF, stack overflow, PC=00000000003237A4, PS=0000001B
%%%%%%%%%%% OPCOM 3-MAR-1999 15:38:25.14 %%%%%%%%%%%
Message from user SYSTEM on FUNYET
%QMAN-E-SYMDEL, unexpected symbiont process termination
%%%%%%%%%%% OPCOM 3-MAR-1999 15:38:25.17 %%%%%%%%%%%
Message from user SYSTEM on FUNYET
-SYSTEM-F-STKOVF, stack overflow, PC=0000000000000000, PS=00000000
%SYSTEM-F-STKOVF, stack overflow, PC=0000000000032F1C, PS=0000001B
Improperly handled condition, image exit forced.
Signal arguments: Number = 0000000000000003
Name = 0000000000000554
0000000000032F1C
100000000000001B
Register dump:
R0 = 0000000000000000 R1 = 0000000000000554 R2 = 0000000000010220
R3 = 0000000000020018 R4 = 0000000000000000 R5 = 0000000000011588
R6 = 0000000000000000 R7 = 000000000000000B R8 = 000000007AF2EFD8
R9 = 0000000000FB132C R10 = 000000007AF2F169 R11 = 000000007AF2F5E0
R12 = 00000000000230D8 R13 = 000000007B022330 R14 = FFFFFFFF8101A7C0
R15 = 0000000000000554 R16 = 0000000000000554 R17 = 0000000000000000
R18 = 000000000000000C R19 = 0000000000000001 R20 = FFFFFFFF83BB0000
R21 = FFFFFFFDFF7FE000 R22 = FFFFFFFF800D5160 R23 = 000000007FFA1FC0
R24 = 000000007AF2EFD8 R25 = 0000000000000001 R26 = 0000000000032F1C
R27 = 000000007B562E00 R28 = 100000000000001B R29 = 000000007AF2EFA0
SP = 000000007AF2EF90 PC = 0000000000032F1C PS = 100000000000001B
|
With some printers, including the LN32, LNM40, mL320 and mL401, DCPS sometimes paused for five to ten seconds between jobs when using a raw TCP/IP connection. The following error message would often appear before the delay:
%DCPS-W-NOT_READY, Printer is not ready |
With some printers, including the LN20, LN40 and LNC02, DCPS would return the message:
%DCPS-W-OFFLINE, Print Engine has gone off line |
when starting a job if the printer was in Energy Saving mode.
5.2.3 ANSI GSS Sequence Could Cause Symbiont Crash
When using the ANSI GSS escape sequence with a parameter of zero, the ANSI translator would crash and cause the print queue to stop. For example, the sequence:
<CSI><SP>C
|
would cause DCPS to crash with the following error messages:
%%%%%%%%%%% OPCOM 3-DEC-1999 11:48:09.85 %%%%%%%%%%% Message from user SYSTEM on RT495 Process SYMBIONT_49: %SYSTEM-F-INTDIV, arithmetic trap, integer divide by zero at PC=FFFFFFFF808A0AE8, PS=0000001B %%%%%%%%%%% OPCOM 3-DEC-1999 11:48:09.89 %%%%%%%%%%% Message from user QUEUE_MANAGE on RT495 %QMAN-E-SYMDEL, unexpected symbiont process termination %%%%%%%%%%% OPCOM 3-DEC-1999 11:48:09.89 %%%%%%%%%%% Message from user QUEUE_MANAGE on RT495 -SYSTEM-F-INTDIV, arithmetic trap, integer divide by zero at PC=0000000000000000, PS=00000000 |
When requesting a list of fonts from some printers, including the LN32
and LNM40, the list would either not print or fail with a PostScript
error. This would occur if a DCPS ANSI print job had been printed on
the printer since the last time it was powered on. ANSI fonts created
by DCPS have been fixed so that such font lists, including those
produced using the printer's console and user-written PostScript
programs that inquire about font information, now succeed.
5.2.5 Layup Usage and Printer Errors Can Cause Memory Leaks
DCPS symbiont processes would sometimes use increasing amounts of memory over time when you used layup files. This also occurred rarely for certain printer error messages.
Also see Chapter 3 for information about a memory leak in OpenVMS Alpha V7.1-2.
This section describes changes included in DCPS V1.7-1. You can find
more information for several of these changes elsewhere in these
release notes.
6.1 DCPS Version 1.7-1 Changes
6.1.1 New Printer Support
DCPS V1.7-1 adds support for the following printers:
Compaq Laser Printer LNC02
Compaq Laser Printer LNM40
The Compaq Laser Printer LNC02 is equivalent to the DIGITAL Laser Printer LNC02. References in the DCPS documentation to the DIGITAL Laser Printer LNC02 also apply to the Compaq Laser Printer LNC02.
You can find more information in Chapter 4 of these release notes.
6.1.2 Support for Stapling on LN32 and LNM40
DCPS V1.7-1 adds support for the optional stapling feature of the
Compaq Laser Printer LN32 and LNM40. Refer to DECprint Supervisor for OpenVMS User's Guide for
information about using the stapling option from DCPS.
6.1.3 Support for Process Software TCPware for OpenVMS Software
DCPS now supports your use of TCPware from Process Software in addition
to DIGITAL TCP/IP Services and Process Software MultiNet software to
provide IP connectivity. TCPware V5.3 or later is supported.
6.2 DCPS Version 1.7-1 Fixes
The following problems are fixed in DCPS V1.7-1.
6.2.1 Selecting LN32 Mailbox Causes Error
When the Compaq Laser Printer LN32 was set to jog (offset) output, selecting a mailbox as an output tray caused the print job to fail with the error:
%DCPS-E-OUTTRAYNOTAVL, No MAILBOX_n tray is installed on printer_name |
where n is the number of the mailbox tray selected and printer_name is the name of the printer.
DCPS jobs can now be sent to any mailbox regardless of the printer's
JOB OFFSET setting.
6.2.2 Selecting Paper Size FOLIO Causes Error
Starting with DCPS V1.6, selecting paper size FOLIO would result in the job failing with one of the following error messages:
%DCPS-E-PARSYNERR, Syntax error in the /PARAMETERS qualifier at or near PAGE_SIZE=FOLIO %DCPS-E-PARSYNERR, Syntax error in the /PARAMETERS qualifier at or near SHEET_SIZE=FOLIO |
| Previous | Next | Contents | Index |