HP DECprint Supervisor (DCPS) for OpenVMS
Release Notes


Previous Contents


Chapter 4
Other Restrictions that Affect DCPS

This chapter contains information about other problems that are known to impact DCPS and patch kits (ECOs) that address some of these problems. Patch kits for supported versions of OpenVMS are listed, although there may be kits available for other versions.

You can obtain these patch kits (or an update to them):

4.1 DCPS Processes Consume CPU after Time Change

In certain situations, DCPS symbiont processes can consume excessive CPU time. For example, when the time is moved forward at the Standard Time/Daylight Savings Time adjustment, multithreaded processes such as DCPS went into a tight CPU loop. Stopping and restarting the processes resolved the problem.

This problem can happen again at the next Standard Time/Daylight Savings Time adjustment unless the following patch is applied:

If DTSS is used to synchronize time, the following DECnet patch should also be applied:

4.2 Starting Queue Causes Invalid Device Name Error

When initializing and starting an autostart DCPS queue that uses the Raw TCP protocol, the queue manager can fail with an "invalid device name" error.


    %%%%%%%%%%%  OPCOM  26-SEP-2002 09:33:42.58  %%%%%%%%%%% 
    Message from user SYSTEM on LATEST 
    %QMAN-I-QUENOTSTART, queue TEST4 could not be started on node LATEST 
 
    %%%%%%%%%%%  OPCOM  26-SEP-2002 09:33:42.58  %%%%%%%%%%% 
    Message from user SYSTEM on LATEST 
    -QMAN-I-QUEAUTOOFF, queue TEST4 is now autostart inactive 
 
    %%%%%%%%%%%  OPCOM  26-SEP-2002 09:33:42.58  %%%%%%%%%%% 
    Message from user SYSTEM on LATEST 
    -SYSTEM-F-IVDEVNAM, invalid device name 

The following patch kit fixes this problem:

4.3 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:

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, a queue running in a multistreamed process that is stopped with STOP /QUEUE /RESET and quickly started with START /QUEUE will hang. Also, the following message will sometimes 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.

4.4 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 kit fixes this problem:

4.5 Symbiont Aborts with Access Violation or Bad Parameter Error

The DCPS symbiont can abort with an ACCVIO or BADPARAM error, possibly also indicating the CMA (DECthreads) facility. Other software on your system, including HP TCP/IP Services for OpenVMS and anything layered upon DECthreads, may also fail.

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.

The following patch kits fix this problem:


Appendix A
Raw TCP/IP Port Numbers

When setting up a DCPS queue using a Raw TCP/IP connection, check the documentation for your network interface card (NIC), print server or terminal server to determine the number of its Raw TCP/IP port (if it has one). The Raw TCP/IP port must support bidirectional communication between the printer and your OpenVMS system.

Table A-1 shows the port numbers for some commonly-used devices.

Table A-1 Raw TCP / IP Port Numbers
  20nn DECserver terminal servers, where "nn" is the physical port number
  2501 DIGITAL LN17ps and DIGITAL Laser Printer LN17+ps
    Emulex NICs
  3001 DIGITAL Laser Printer LN15 and LN15+
    DIGITAL RapidPrint 500 print server
  6869 Compaq Laser Printer LNC02
    DIGITAL Laser Printer LN20, LN40 and LNC02
  9100 Compaq Laser Printer LN16, LN32 and LNM40
    GENICOM Intelliprint mL, LN and microLaser printers
    GENICOM RapidPrint MPS100 print server
    HP Color LaserJet printers
    HP LaserJet printers
    IBM InfoPrint printers
    Lexmark C, Optra, S, Optra T, T and W series printers
    Tektronix Phaser printers
    Xerox DocuPrint N printers
    HP JetDirect, Lexmark and XCD print servers
  9101 HP 9085 MFP


+DCPS default

Contents