Technical data

5
Other Restrictions that Affect DCPS
This section contains information about other problems that are known to impact
DCPS and remedial patch kits (ECOs) that address some of these problems.
You can obtain these remedial patch kits (or an update to them)
• From an HP Customer Support Center
• From the HP IT Resource Center (ITRC) at http://www.itrc.hp.com
5.1 DCPS Processes Consume CPU
In certain situations, DCPS symbiont processes can consume excessive CPU time.
For example, in the southern hemisphere when the time was moved forward at
the October 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 is seen only on OpenVMS Alpha V7.3 and V7.3-1
systems.
This problem can happen again at the next daylight savings time adjustment
unless the following patch is applied:
• VMS731_TDF-V0100, for OpenVMS Alpha V7.3-1 systems
• VMS73_TDF-V0100, for OpenVMS Alpha V7.3 systems
5.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:
• VMS731_QMAN-V0100, for OpenVMS Alpha V7.3-1 systems
Other Restrictions that Affect DCPS 5–1