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

Conference lassie::ucx

Title:	DEC TCP/IP Services for OpenVMS
Notice:	Note 2-SSB Kits, 3-FT Kits, 4-Patch Info, 7-QAR System
Moderator:	ucxaxp.ucx.lkg.dec.com::TIBBERT

Created:	Thu Nov 17 1994
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	5568
Total number of notes:	21492

5324.0. "HP Printing and Telnet advice please" by ODIXIE::RREEVES () Mon Mar 10 1997 10:16

    I need a little advice. One of Digital's customer's where I perform 
    consulting is moving towards a predominantly IP solution for their 
    network protocol access to an Alpha 2100 A/250 running OpenVMS version 
    6.2-1h2. We currently run UCX verion 4.1 ECO Level 4. 
    
    We are migrating from a 3rd party package which provides printer
    connections to a Novell file server to IP printing . The new solution 
    will rely primarly on the new HP JETDIRECT EX Plus print servers 
    running TCP/IP. 
    
   My first question is should I use telnet or LPD to configured these
    queues (there will be about 300 printer queues) on the ALPHA ? 
    If I use Telnet is the port number 9100 (which is used on the HP 
    JetDirect cards) internal on the HP 5SIMX printers. 
    
    My second question is: I am getting some complaints from users after 
    switching from DEC Server 550's running LAT to DEC Server 900 GM's
    runnin TCP/IP Telnet for terminal connections. Specifically, the user's
    are complaining about the response being slower especially when
    attempting to CNTRL-C it seems that several more screens of data fly
    accross the terminal before the $ returns. 
    
    Should there be a precevied difference in speed when switching to 
    TCP/IP Telnet from LAT or can I adjust something to help improve
    this performance ?
    
    Thanks in advance for your advice.
    
    Regards,
    
    Ray

T.R Title User Personal
Name Date Lines

5324.1 some hints UTRTSC::KNOPPERS Oswald Knoppers Mon Mar 10 1997 10:29 40

T.R	Title	User	Personal Name	Date	Lines
5324.1	some hints	UTRTSC::KNOPPERS	Oswald Knoppers	`Mon Mar 10 1997 10:29`	40
	> My first question is should I use telnet or LPD to configured these > queues (there will be about 300 printer queues) on the ALPHA ? > If I use Telnet is the port number 9100 (which is used on the HP > JetDirect cards) internal on the HP 5SIMX printers. My advice would be to use telnet printing if possible. The telnetsymbiont is basicly the VMS printsymbiont modified. Just like latsym. So it is much more vms-like. The most common problems using telnet printing are: - when printing multiple jobs, subsequent jobs may print only after a couple of minutes (you will see an opcom message about the printer rejecting a connection). In this case you need to use the the UCX$TELNETSYP_IDLE_TIMEOUT logical. - when printing, you may get at the start of the job some garbage characters (usually << and >> signs). In this case you need to use the logical UCX$TELNETSYM_RAW_TCP. - when printing you may get empty pages before/between/after jobs. In that case use the UCX$TELNETSYM_SUPPRESS_FORMFEEDS logical. >Specifically, the user's are complaining about the response being slower >especially when attempting to CNTRL-C it seems that several more screens of >data fly accross the terminal before the $ returns. Thats the way it works. TCP/IP has a much bigger pipeline compared to lat. The bottleneck is usually the terminal itself (using for instance 19200 bps). This is why you get the above effect. > Should there be a precevied difference in speed when switching to > TCP/IP Telnet from LAT or can I adjust something to help improve > this performance ? I would not call this a performance problem. Regards, Oswald

>   My first question is should I use telnet or LPD to configured these
>    queues (there will be about 300 printer queues) on the ALPHA ? 
>    If I use Telnet is the port number 9100 (which is used on the HP 
>    JetDirect cards) internal on the HP 5SIMX printers. 

My advice would be to use telnet printing if possible. The telnetsymbiont
is basicly the VMS printsymbiont modified. Just like latsym. So it is much
more vms-like.

The most common problems using telnet printing are:

- when printing multiple jobs, subsequent jobs may print only after a
  couple of minutes (you will see an opcom message about the printer
  rejecting a connection). In this case you need to use the the
  UCX$TELNETSYP_IDLE_TIMEOUT logical.

- when printing, you may get at the start of the job some garbage
  characters (usually << and >> signs). In this case you need to use
  the logical UCX$TELNETSYM_RAW_TCP.

- when printing you may get empty pages before/between/after jobs. In that
  case use the UCX$TELNETSYM_SUPPRESS_FORMFEEDS logical.

>Specifically, the user's are complaining about the response being slower
>especially when attempting to CNTRL-C it seems that several more screens of
>data fly accross the terminal before the $ returns. 

Thats the way it works. TCP/IP has a much bigger pipeline compared to lat.
The bottleneck is usually the terminal itself (using for instance 19200
bps). This is why you get the above effect.

>    Should there be a precevied difference in speed when switching to 
>    TCP/IP Telnet from LAT or can I adjust something to help improve
>    this performance ?

I would not call this a performance problem.

Regards,

Oswald