Technical data

%%%%%%%%%%% 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:
• ALPTTDR01_070, for OpenVMS Alpha V7.0 systems
• VAXTTDR01_070, for OpenVMS VAX V7.0 systems
5.6 I/O Errors for Serially-Connected Printers
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:
• ALPOPDR02_070, for OpenVMS Alpha V7.0 systems
• ALPOPDR04_062, for OpenVMS Alpha V6.2 systems
5.7 Symbiont Aborts with Insufficient Dynamic Memory Error
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:
• VAXCMAR01_071, for OpenVMS VAX V7.1 systems
• VAXCMAR01_070, for OpenVMS VAX V7.0 systems
Other Restrictions that Affect DCPS 5–3