Technical data

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
5.2.2 Delays and Errors with Raw TCP/IP Print Jobs
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 DCPS Version 1.8 Information