Xref: utzoo comp.unix.ultrix:7331 comp.os.vms:38982 comp.sys.dec:5815
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!bagate!cbmvax!grr
From: grr@cbmvax.commodore.com (George Robbins)
Newsgroups: comp.unix.ultrix,comp.os.vms,comp.sys.dec
Subject: Re: Shared Printers
Message-ID: <21830@cbmvax.commodore.com>
Date: 23 May 91 08:15:13 GMT
References: <174@motto.UUCP> <3196@shodha.enet.dec.com> <21789@cbmvax.commodore.com> <178@motto.UUCP>
Reply-To: grr@cbmvax.commodore.com (George Robbins)
Organization: Commodore, West Chester, PA
Lines: 27

In article <178@motto.UUCP> murray@motto.UUCP (Murray S. Kucherawy) writes:
> grr@cbmvax.commodore.com (George Robbins) writes:
> >The sharing of DECserver printer ports is via LAT,
> >DECnet/Ultrix is *not* needed
> >to get this functionality.
> 
> That's not what I had in mind.  Our printers are currently on the DECserver
> using LAT.  We want to take them off and put them on the VMS machine,
> but still allow the Ultrix machine and the other VMS machines to be able
> to use those printers.  All the machines are equipped with DECnet.
> 

Well, Multinet provides BSD compatible print spooling services.  I think most
of the competitive products do also, but who knows about UCX?  It should also
be possible to do something with the DECnet/Ultrix "TELL"/remote objects to
submit jobs that dump things in VMS queues.

Excuse me if I've overlooked something obvious.  We've used an assortment of
things here which have evolved over time.  I think we started with the tell
approach, then did a third-party thing when we got sunlink DNI (decnet for Sun)
where ultrix remoted printed to suns which remote printed to VMS, but now we
depend on the Multinet services.

-- 
George Robbins - now working for,     uucp:   {uunet|pyramid|rutgers}!cbmvax!grr
but no way officially representing:   domain: grr@cbmvax.commodore.com
Commodore, Engineering Department     phone:  215-431-9349 (only by moonlite)