[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference 7.286::postscript_printing

Title:Digital PostScript printers and their associated software
Moderator:REGENT::LASKOHER
Created:Wed Jan 24 1990
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:7230
Total number of notes:31971

7076.0. "A modern printer environment" by SWETSC::WESTERBACK (Panta rei) Mon Feb 10 1997 08:47

	Hi,

	I wonder if someone could give advise on our printer environment.

	Traditionally we've had Printservers and LAT printers, LN03/LN03R 
	and a few Declaser 2250's. All set up via DCPS (1.1 presently).

	Now things are changing... Two major things:

	1) Smaller field offices have been converted to TCP/IP. No LAT
	available anymore. So we have to use telnet symbiont instead, and
	as far as I understand this means a printer is either ANSI or PS,
	not possible to print e.g. text files on a LN03R. (Even if we had
	LPS printers available, there are no nodes to boot them from in
	these small offices, and MOP can't get there from our main office)

	2) Print services for PC users are being transferred from VMS/Pathworks
	systems to Windows NT office servers. This means only printers
	which have their own IP addresses (LPS) can be served. Not LAT queues 
	(in the main office) nor telnet queues (field offices).

	As I understand it, we can get around problem 1 by having two printers,	
	one ansi and one PS in each office. And problem 2 can be solved by
	keeping at least one VMS Pathworks system as server to LAT or telnet
	queues.

	But as the LN03's are wearing out, what is the long term solution?
	I've read about LN14 and LN17ps, and various options, but it's not
	quite clear to me if/how they offer us what we need. 

	Can these printers have their own IP address, and be used with
	(a new version) of DCPS? So that one printer is enough for all kinds
	of printing? And in that case they should be able to be served
	from the WNT server also?

	Other thoughts on a good printer environment?


	Rgds,
	Hans Westerback
	CCS Sweden
	
	
T.RTitleUserPersonal
Name
DateLines
7076.1Windows NT will do itRDVAX::LEVYRun Like an AntelopeMon Feb 10 1997 09:1825
    I can't comment on all of your information, but there is one major
    misunderstanding here.
    
>	2) Print services for PC users are being transferred from VMS/Pathworks
>	systems to Windows NT office servers. This means only printers
>	which have their own IP addresses (LPS) can be served. Not LAT queues 
>	(in the main office) nor telnet queues (field offices).
>
>	As I understand it, we can get around problem 1 by having two printers,	
>	one ansi and one PS in each office. And problem 2 can be solved by
>	keeping at least one VMS Pathworks system as server to LAT or telnet
>	queues.
    
    You're stuck in a VMS mentality, it seems.  The DEClaser 3500, for
    instance, does a very good job of operating in a Windows NT environment
    with TCP/IP.  Telnet not needed.  The printer can be assigned an IP
    address and the NT queue can communicate with it that way.
    
    The only reason to keep VMS/PATHWORKS around is if you have a need to
    run legacy VMS apps and want the same system to operate as your PC
    file/print server.  If this need does not exist, Windows NT does a fine
    job of ANSI/PS printing to these printers.
    
    	dave
    
7076.2Stuck whether I like it or not...;-)SWETSC::WESTERBACKPanta reiMon Feb 10 1997 16:137
    Yes, I'm indeed stuck in VMS thinking. That's necessary because we
    still need to print from many VMS applications. Maybe that wasn't
    emphasized in my base note, but of course it's essential that our
    solution supports both VMS and PC printing. Can VMS (DCPS) use the 3500
    for ANSI/PS printing? Does the same go for  LN17ps?
    
    Hans
7076.3I like being stuck in OpenVMS thinking!FUNYET::ANDERSONWhere's the nearest White Castle?Mon Feb 10 1997 17:3912
OpenVMS and DCPS can indeed use the DEClaser 3500 and LN17ps for ANSI and
PostScript printing.  DCPS will translate text or ANSI documents to PostScript
first.

Note that DCPS uses LAT or AppleTalk to these printers today.  DCPS V1.4,
currently in field test, will be able to use TCP/IP to the LN17ps and other
printers that have bidirectional TCP/IP stacks on them.

You can also use the TCP/IP Services (UCX) LPR or Telnet queues to these
printers today, but you will not be using DCPS and its features.

Paul
7076.4It works...we do it when we mustRDVAX::LEVYRun Like an AntelopeTue Feb 11 1997 07:535
    ...and since the printer can talk LAT without a terminal server, as can
    VMS, you are in good shape!
    
    	dave
    
7076.5DEClaser 3500 and 5100 NICs do NOT support bi-di TCP/IPHANNAH::SCHULLMANDan SchullmanTue Feb 11 1997 10:5010
RE: .3

> Note that DCPS uses LAT or AppleTalk to these printers today.  DCPS V1.4,
> currently in field test, will be able to use TCP/IP to the LN17ps and other
> printers that have bidirectional TCP/IP stacks on them.

NOTE that the DEClaser 3500 NIC does *NOT* support bi-di TCP/IP (even though
it DOES support bi-di LAT).

						--Dan S.
7076.6SWETSC::WESTERBACKPanta reiTue Feb 11 1997 11:3924
	Thanks for your replies so far!

	Let's see if I have understood correctly:


	For WNT:

	Both 3500 and LN17ps can be used by NT, as they have their own 
	TCP/IP address. 


	For VMS:

	Both 3500 and LN17ps can use LAT and DCPS to print ANSI/PS.

	Where there is no LAT, only TCP/IP, both printers can use
	LPD or telnetsym and print PS. When DCPS 1.4 is released it
	will be possible to use it for LN17ps only to print ANSI/PS.

	3500 and TCP/IP only: I see there's a 3500A. Can it receive
	both ANSI or PS and print it OK? Which symbiont is used?  

	Rgds,
	Hans		
7076.7Can LAT get from system to printer?SHRMSG::HOWARDBenFri Feb 21 1997 14:0720
    .6 is correct as I understand it.  However, "where there is no LAT",
    might be interpreted differently by different people.  In our building,
    there supposedly is no LAT in most of it.  However, all the LAT is done
    by the printers and the VMS systems, so there is no problem.  The key
    would be whether LAT is going to get through the gateways between the
    field offices and the main office.  I think it is primary the
    DECservers that the LAT haters want to get rid of, since they are
    difficult to manage.  
    
    (I'm not sure what a 3500A is.) For a while, I used UCX LPD to print to
    the 3500's.  It worked ok, but I couldn't get header pages to work with
    DQS, and of course no DCPS features like LANDSCAPE, 2-up, or duplex (I
    don't think 3500's do duplex anyway).  If these features are in the
    PostScript of the document, then they work ok.  
    
    If you are going to buy printers, then the LN17 seems a better choice
    than the 3500 for several reasons: DCPS over IP, duplex (with option),
    ability to login to the printer, probably faster. 
    
    Ben