%DCPS-F-CONTERMINATED error

[Ronald Y. Salem]

Hi All,
I just setup a xerox printer in OVMS DCPS V2.6. I also created a generic queue and send a print job in the generic queue. Unfortunately, when the print job is submitted - the execution queue will change its status to STOP and the message below is displayed.

$>
%DCPS-F-CONTERMINATED, Connection abnormally terminated
-DCPS-I-JOB_ID, for job DS8000 (queue VMSPTRSGP_8UP, entry 1505) on VMSPTRSGP
NFFM01:RYS$$$>

%DCPS-I-RELEASE, $SET QUEUE/RELEASE/ENTRY=1505 VMSPTRSGP_8UP to release for prin
ting
-DCPS-I-JOB_ID, for job DS8000 (queue VMSPTRSGP_8UP, entry 1505) on VMSPTRSGP
$>


Does anyone out there had encounter the same problem and how did you fix it?

I am running an OpenVMS V8.3 on DS25 Alpha server.

Any help would be appreciated.
Thanks.

regards,
ronald

[Wim Van den Wyngaert]

Try killing the symbiont process (SYMBIONT_* and restart the queue(s).

Wim

[Heinz W Genhart]

Hi Ronald

first of all welcome to the HP ITRC OpenVMS Forum.

Could you supply some more information?

Output from SHOW QUEUE VMSPTRSGP_8UP/full
would probably be helpful

Regards

Geni

[Ronald Y. Salem]

Hi,
Pls see below some output of show que/full.
Thanks.

$ sh que/all/full VMSPTRSGP
Printer queue VMSPTRSGP, idle, on NFFM01::"IP_RawTCP/172.10.11.111:9100",
mounted form DCPS$DEFAULT (stock=DEFAULT)
/BASE_PRIORITY=4 /DEFAULT=(FORM=DCPS$DEFAULT (stock=DEFAULT))
/NOENABLE_GENERIC /LIBRARY=DCPS$DEVCTL Lowercase /OWNER=[SYSTEM]
/PROCESSOR=DCPS$SMB /PROTECTION=(S:M,O:D,G:R,W:S) /SCHEDULE=(NOSIZE)

Also, I try to stop the symb* process and stop and start the queue but the same error had occurred.

[Heinz W Genhart]

Hi Ronald

as far as I can see (compared with own Queues) there seems nothing to be wrong with the queue definition.

Can you ping 172.10.11.111 ?
Does this Xerox printer listen to port 9100 ? or may this be the problem?

Regards

Geni

[Karl Rohwedder]

Ronald,

many of the XEROX printers are only supported via LPD protocol (in contrast to RawTCP).

Pls. check the SPD or try with LPD directly.

regards Kalle

[Ronald Y. Salem]

Hi Geni,
I was able to telnet via port 9100 and echo some of the command and it gets printed.
But within in DCPS, I always pointed to the same error.

By the way, do you know how to check whether the printer is enable to printer postscript?

[Heinz W Genhart]

Hi Ronald

Karl my be right. You can find this hint in this manual in Chapter 2.4
http://ftp.openvms.compaq.com/doc/82final/dcps/dcps026_release_notes.pdf

Regards

Geni

[Hakan Zanderau ( Anders]

Ronald,

I used to support DCPS when I worked at Digital/Compaq/HP.

All output from DCPS-symbiont will be PS.
( Not all, but close enough )

DCPS needs Bidirectional support with the printer. ( not all true, but close enough )

To check the communication, try telneting to the specified port ( and press T to invoke the PS-interpreter )

$ TELNET ipadress portnr
T

( if communication is OK, the printer will answer with )

%% [status: IDLE] %%

If this is not working, you can try to bypass the initial handshaking by defining the logical name NO_SYNC

$ DEFINE/SYS/EXEC DCPS$queuename_NO_SYNC 1

STOP/START the queue and try again.

If this is not working, try Karls suggestion and reconfig the queue to use LPD as transport. DCPS$STARTUP.TEMPLATE will tell you how.

regards,

Hakan Zanderau
HA-solutions

[Ronald Y. Salem]

Hi Hakan,
Thanks. I tried it before setting the NO_SYN to "TRUE" or 1, but I still get the same error. I read through the release notes of DCPS v2.6 and it seems like the printer I am using is not supported (Xerox DocuCentre C3300 printer).

I will try using LPD then.

regards,
ronald

[Hakan Zanderau ( Anders]

Ronald,

That a printer is not supported doesn't mean its not working.

During the initial handshaking DCPS asks the printer for its model and then loads the proper modules. If its not a supported printer, it loads the Unrecongnized modules.
You can print, but not use all special features like pick different trays......

When using LPD ( as transport ), you have to tell DCPS by a logical name the brand and model of the printer because it can't handshake the printer.
In your case DCPS will load the Unrecognized modules either way.

regards,

Hakan Zanderau
HA-solutions

[Hakan Zanderau ( Anders]

Are you sure your printer has PS. The spec says "PS (optional)" ?

regards,

Hakan Zanderau
HA-solutions

[Hakan Zanderau ( Anders]

Ronald,

Just to be sure......

Create a telnetqueue and print a .PS file.
If it succeeds both my questions will be answered..... has the printer the PS-option and is 9100 the correct port.

Look in SYS$HELP for PS-files.

regards,

Hakan Zanderau

[Hakan Zanderau ( Anders]

Ronald,

The internal LPD-queues in the Xerox LPD-server are PS,HPGL,PCL,AUTO.
If you specify anything else it will use the queue AUTO.

regards,

Hakan Zanderau
HA-solutions

[Bill Hall]

Ronald,

I have attached a text file with a snippet of DCL to add to your DCPS$STARTUP.COM procedure. You should also be using DCPS V2.6 ECO 3 for use with the Xerox copier/printers.

Essentially you have to use LPD, tell DCPS the Xerox is another supported printer and spool the output to the printer so an exact size of the output can be determined.

Bill

[Karl Rohwedder]

A side note:

There is an unofficial Eco 4 kit which fixes a problem of missing lines at the beginning when printing ascii-files with /PARMAM=NUMBER=n.

regards Kalle

[Hakan Zanderau ( Anders]

I'm sticking my neck out now, but...

I can't find anything that says you need DCPS v2.6-3 to make it work with Xerox-printers ( using LPD as transport ).

When using the "old/original" behavior ( Bidirectional handshaking ) could be another story......

However it could be a good thing to define the logical DCPS$queuename_PRODUCT_NAME

You can define it to anything. If DCPS doesn't recognize the logical as a supported printer it uses the Unrecognized modules

$ DEFINE/SYS/EXEC DCPS$queuename_PRODUCT_NAME "dummy"

Then restart the queue

Do a REPLY/ENABLE to see the messages from DCPS.

regards,

Hakan Zanderau
HA-solutions

[Bill Hall]

Hakan,

DCPS 2.6 ECO3 fixed multiple issues when printing to the Xerox WorkCentre Pro series of copier/printers. I recommended Ronald use the supported Xerox WCP 232 configuration with his "unsupported" Xerox as I have found this configuration to work with other newer "unsupported" Xerox color copier/printers.

Bill

[Ronald Y. Salem]

Thanks for all the reply.

I changed the printer from Xerox DocuCentre to HP Laserjet 4250, and now I am able to print PS using DCPS.

I try all the options presented, although there is a printout but it appears to be rubbish (different messages) resulting from the print command.

With this, I will closed this thread.

[Hakan Zanderau ( Anders]

FYI,

I will visit a local Xerox reseller next week and do some DCPS-tests......

I'll be back.....

Hakan Zanderau
HA-solutions

[Bill Hall]

Ronald,

I just checked a brochure for the DocuCentre-II C4300/C3300/C2200 and it implies that Postscript is an option for this printer. Can you verify your printer has the Postscript option installed? If it does not have Postscript, you will never get DCPS to print to it.

You may be able to print successfully using a telnet symbiont and a device control library based on PCL 4 or 5.

Bill

[Hakan Zanderau ( Anders]

Now I'm back from the Xerox reseller and I have talked to DCPS-engineering.

Using a TELNETSYM queue is NO problem at all ;-)

You need to use DCPS with LPD-option, define the logical PRODUCT_NAME with a supported model and define the logical SPOOL = TRUE

If the logical DCPS_LIB is defined use this shortcut. ( DCPS already started )

$ DEFINE/SYS/EXEC DCPS$queuename_SPOOL TRUE
$ DEFINE/SYS/EXEC DCPS$queuename_PRODUCT_NAME "Xerox WorkCentre Pro 275"
$ @SYS$STARTUP:DCPS$EXECUTION_QUEUE queuename "IP_LPD/ipaddress:lp" DCPS_LIB "" "" "" "" ""

You find all supported PRODUCT_NAME(s) in SYS$HELP:DCPS*.RELEASE_NOTES

regards,

Hakan Zanderau
HA-solutions