[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

5171.0. "Telnetsym and TAB and NOTAB" by MUNICH::WOERLE () Wed Jan 29 1997 08:20

		hello,

I have a question about TELNETSYM and the setting of TAB/NOTAB.
Sorry if this is already asked in this conference but I haven't found no 
entries.

A great customer in Germany (called BMW) want to replace his LAT-Queues 
with TELNETSYM Queues. 
Now he wants to know if this could be a problem.
He has tested something and found a problem with TAB and NOTAB.

With Lat queues he has a LTA device and so he can set TAB/NOTAB like
$set terminal/perm/tab [notab]. This is necessary (according to the customer)
because he has some printers which cannot understand the TAB-escape sequence.
So with this qualifier he is able to control whether tab characters are 
converted to multiple blanks or not.

With TELNETSYM he cannot use this Qualifier.

Is there a possibility with TELNETSYM to control whether tab characters are
converted to multiple blanks or not ?


Many thanks in advance

Norbert Woerle, CSC Munich

T.R	Title	User	Personal Name	Date	Lines
5171.1		UTRTSC::KNOPPERS	Oswald Knoppers	`Wed Jan 29 1997 08:48`	13
	I don't think there is a way to do this with the telnet symbiont. Also I find it hard to believe that a company which makes modern cars like them uses printer which do not understand tab characters... You might try using an outbound TN device in combination with the normal print symbiont. This method however doesn't have much of error recovery though. Why do they want to stop using lat? Regards, Oswald
5171.2	What about dummy LAT devices?	CSC32::R_WILLIAMS		`Wed Jan 29 1997 10:04`	15
	Hi, The outbound TN device does not let you spool it yet (hopefully we will see this changed one day). You might want to try setting up a dummy lat device ans associate a telnetsym with it. See if it can give you what the customer needs. Creating a 'dummy' LAT device: $ mc latcp create port LTAnn: $ set device/spool=(yourtelnetsymquename, sys$sysdevice:) LTAnn: $ copy tobeprinted.stuff LTAnn:
5171.3		UTRTSC::KNOPPERS	Oswald Knoppers	`Wed Jan 29 1997 10:43`	7
	Re .2 You can try this but don't hold your breath. As I understand it, the replacing of tabs by spaces is done by the terminal driver. When using the telnet symbiont you won't get near to any code of the ttdriver. Oswald
5171.4	Thanx	MUNICH::WOERLE		`Fri Jan 31 1997 04:37`	21
	hello, many thanks for your replies. .1 "Why do they want to stop using lat?" I don't know but I think this is - like usual - a political decision. They want replace LAT with TELNETSYM and they want the same functionality like LAT. So for my opinion the Terminal- Settings on a LTA device like TAB/NOTAB doesn't work with TELNETSYM in the normal way. I will open an IPMT to ask Engineering if they have future plans to implement such things (perhaps with further UCX$telnetsym_... logicals). Otherwise they must test your hints. Many thanks again for your quick help. regards Norbert
5171.5	they want to change but nothing may be different!	UTRTSC::KNOPPERS	Oswald Knoppers	`Fri Jan 31 1997 06:55`	14
	They want to change but they want to have the same functionality they had in the first place. Well it doesn't work that way. The telnetsym doesn't use the terminal driver. So you don't get the features added lyke you have with the latsym. Another exampele is wrapping. The telnetsym doesn't do that either. I really sometimes don't understand customer.... I suggest you let them pay for any changes they want in the symbiont. Oswald