OpenVMS print queues being known by Window Domain

[Larry J. Griswold]

We are using CITRIX servers to make known to our Windows Domain the OpenVMS print queues.
We are looking into getting rid of the CITRIX servers and need the ability for the Windows Domain to see the OpenVMS print queues.

Can Advanced Server/Pathworks share these queues over a 7 campus topology. I read in the installation guide that the network can not be bridged. What consitutes a bridge (switch, routers,etc.)?

Larry

[Jan van den Ende]

Larry,

What problem are you trying to solve?
Are your printers physically connected to your VMS systems? Haven't seen that for some time...
Or is the intention to be able to use the printers both from VMS and from M$ ?

I _assume_ that at this moment you are using them both from Citrix and from VMS?

In that case, is there any reason NOT to continue doing it that way? I mean, accessing them both from VMS and from your Windoze environment. Whether you use a Citrix print server or another M$ windowing print server should not make much difference..


Hth.

Proost.

Have one on me.

Jan

[Larry J. Griswold]

We don't have any printers directly connected to the OpenVMS systems. They are all connected to the network via JETDIRECT boxes (for the IP address).

Each campus is in their own domain and we are not looking to put a printserver at each campus.

What I am looking for -

If someone has been able to use a application that serves all OpenVMS print queues to a set of IP subnets.
Does Pathworks do this?

[Doug Phillips]

Larry,

Have you looked at how LPD might work for you?

-Doug

[John Gillings · Accepted solution]

Larry,

No problem! I'd recommend DCPS to create the printer queues. It's licensed with OpenVMS, so just a matter of installing the kit.

To share printers with Windows systems, you'll then need to install Advanced Server. You'll need to purchase the appropriate licenses. It's then just a case of executing:

Admin> ADD PRINT QUEUE

to make your OpenVMS print queues visible to PCs anywhere on your network (/planet!).

Typically Advanced Server & DCPS perform and scale much better than Windows servers.

[Larry J. Griswold]

Doug,

The LPD printer setup was used here years ago and over the two years converted to MULTINET NTY printers.

John,

Thanks for the Advanced Server info. We are going price it and go from there.

[Jan van den Ende]

Moved away from LPD printers also.

The real bad thing is that setup modules and steering commands are seen as separate files, and treated as separate jobs.
If your _printer_ does a job separation reset, which it should surely do if serving multiple hosts, then the printer gets reset after you set it up, but before your actual job is printed.
LPD just ASSUMES that you behave M$-style: per printer a separate "driver", which really is a converter which builds a new file out of file-to-be-printed, with ALL steering commands IN THAT (spool-)FILE, and THAT gets sent to the printer.

LPD is really NOT compatible with the VMS print queue philosofy!

Proost.

Have one on me.

Jan

[Doug Phillips]

I agree about LPD. I've not used it unless I had to, and I've dumped it at first chance. It does make life less relaxing;-).

In Larry's case, it would be an option although Advanced Server would be better since he's in a Windows rather than *nix environment.

However, since he has TCP/IP but doesn't have AdvancedServer, I guess his budget will decide.

At least my mention of LPD shook loose some other replies to Larry's inquiry:-)

Doug

[Larry J. Griswold]

Thanks for all the information. We are going to research Advanced Server.