Technical data

5.3 DCPS Processes Consume Memory and Pagefile
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:
• VMS712_PTHREADS-V0300, for OpenVMS Alpha V7.1-2 systems
5.4 Problems Starting Queues with Multistreamed Symbionts
All sites running DCPS as a multistreamed process on OpenVMS V7.1 and earlier
should install the Queue Manager Remedial Update.
The Queue Manager remedial update kits are:
• ALPQMAN02_071, for OpenVMS Alpha V7.1 systems
• ALPQMAN05_070, for OpenVMS Alpha V7.0 systems
• ALPQMAN03_062, for OpenVMS Alpha V6.2 systems
• ALPQMAN04_061, for OpenVMS Alpha V6.1 systems
• VAXQMAN02_071, for OpenVMS VAX V7.1 systems
• VAXQMAN04_070, for OpenVMS VAX V7.0 systems
• VAXQMAN05_062, for OpenVMS VAX V6.2 systems
• VAXQMAN03_070, for OpenVMS VAX V5.5-2 through V6.1 systems
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, the start request will hang.
In addition, sometimes the following message will be written to OPCOM:
%DCPS-F-STREAMUSE, Request 4 for Stream Id n 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.
5.5 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:
5–2 Other Restrictions that Affect DCPS