DCPS Raw TCP/IP bidirectional protocol

[Hakan Zanderau ( Anders]

Now I'm getting a bit pissed off.....on your VMS SysMan.

The SysMan is a resource for the users, NOT the other way around. Without the users, the SysMan will be out of job.

Without knowing anything about your business...
It's the users that make the money !!

Could you tell me a little bit more about your problem. Are the 30 MFP:s for the VMS-users ?
What happens if you don't succeed in your tryings ?

Hakan

[Hoff]

Two options...

This starts with a managerial office visit for the system manager. Barring extenuating or conflicting circumstances and requirements, and as-yet unmentioned, this path can go as far as proceedings to fire the OpenVMS system manager and to hire a replacement, or to outsource the system management tasks. If you're not in a position to start this managerial process, then escalate this case and this conflict to your own manager. You're doing MASSIVELY more work here just to avoid making changes to an OpenVMS configuration.

The TCP stuff is basically the same as serial and parallel with a network connection interspersed, as those both chat. There are also open-source Postscript-compatible firmware options that get embedded in various printers around, too. Various vendors moved to open-source Postscript-compatible firmware. I'd be surprised if these packages were not available.

Here's a whole pile of client-side drivers:

http://gutenprint.sourceforge.net/p_Documentation.php

The OpenWRT and DDWRT open source projects also have embedded printer servers which might get you going, too. I'd expect that a few printers around will have technical documentation on the TCP port.

Here? I'd be having the visit with the system manager. He or she is costing your company some serious money here, and there better be a good reason for that.

[Hakan Zanderau ( Anders]

And let me know if there is ANYTHING I can do to help. I have supported DCPS since v1.0 when I worked at Digital/Compaq/HP Customer Support Center in Sweden.

Hakan

[J.Lorenzi]

Thank you all

The political aspect of the question is on progress, but a little on the OT side. The VMS admin job may be vacant soon, but we have no time to spare...
As someone said : failure is not an option ;-)

The purpose of the whole job is to get some better looking printings. We also want to use some duplexing and bin selection on the MFPs.

On the latest Toshiba MFP's, the Duplex/Input-Output bins are not drived by PS code, but are overrriden by PJL code.
In addition we have to add some EPS graphics (logos and some legal text) to the original printings. For these reasons, we cannot print using DCPS directly

As you may know now ,we cannot change anything to the VMS side, so we want to use an existing windows program to patch the ps files correctly, getting some keywords in the original printing. This program works fine, but we have to collect the original PS file from the VMS. That's the last step and the job will be done.

Hoff : I'm mining these ideas

Hakan : You may help me giving me some trace files of in/outs of a successfull transmission between DCPS and a PS printer

[Jon Pinkley]

I am not convinced this problem should be blamed on the VMS admin, unless they specified the replacement printers.

Just because a printer will work with Windows in no indication that it will work with DCPS.

What you apparently want to do is to have some black box that appears to VMS like a DCPS supported printer, and this box will magically transform the data, add EPS graphics background and then print to the MFP with its proprietary protocol.

If the version of DCPS loaded on the VMS system supports LPD, that will be the "easiest" way to get the postscript from the VMS system to the Windows PC, but that will require changes to the VMS print queue settings.

Otherwise, if you are trying to "emulate" a bidirectional DCPS supported printer, you have a much bigger task ahead of you.

If you are still committed to that task, then you need to become familiar with WireShark. If the VMS system has a recent version of TCPIP services, then it has the capability of capturing the Ethernet conversation between the VMS interface and the printer's ip (or MAC) address using tcpdump to a file. The file can then be analyzed with WireShark. Alternatively, everything can be done with WireShark as long as the Ethernet traffic can be seen on the Ethernet adapter that WireShark is using (this implies a HUB (repeater) or a SPAN/MIRROR port on a switch).

BTW, there are commercial products (non-DCPS) that run on VMS and support printing to "soft forms". And at least one product also has an optional product that runs on a PC, emulates a printer, and converts the print jobs to postscript. These can then be printed on any printer supported by Windows, and can even be emailed. It uses postscript comments embedded in the postscript generated by their VMS print symbiont to pass information needed for routing to email addresses, etc.

But that solution isn't free, and it would require changes on the VMS side.

How do you intend to control which EPS code is added to the document to be printed, or to select which bin to select, or whether duplexing will be done? Having separated queues for each possible combination doesn't scale. The way the product I am thinking of handles that is by using print parameters and /forms, and that does scale.

Jon

[Hakan Zanderau ( Anders]

Send me a mail at hakan(dot)zanderau(at)ha-solutions(dot)se

Hakan

[Camiel Vanderhoeven]

Could you use something like wireshark to monitor what response the real printer sends back?

[Jon Pinkley]

I thought you have DCPS installed. Has it ever worked with a supported printer? Have all those printers disappeared?

Sending you a trace probably won't be sufficient, you need to be able to see what happens under "abormal" conditions as well as the normal ones, so capturing the traces on your machine is going to be much more useful than anything someone else provides.

Jon