aclin@blackjack.dt.navy.mil (Charissa S. Aclin) (10/26/90)
I'm using Informix 2.10.03K remotely from my Macintosh via the "rlogin" command. My problem concerns the arrow keys on my Mac keyboard not working properly. (I'm using the newest of the extended keyboard line.) The left arrow key acts like the "return" key, and the other don't do anything except cause the "bong" noise to occur when they are pressed. My terminal setting on the Informix machine (SGI Personal Iris) is set for a vt100. If anyone out in netland has had this or a similar problem and knows what I may be doing wrong, please let me know. Thanks in advance. Charissa Aclin aclin@blackjack.dt.navy.mil
smfst2@unix.cis.pitt.edu (Seth M Fuller) (10/27/90)
In article <aclin.656939012@blackjack> aclin@blackjack.dt.navy.mil (Charissa S. Aclin) writes: >I'm using Informix 2.10.03K remotely from my Macintosh via the "rlogin" >command. My problem concerns the arrow keys on my Mac keyboard not >working properly. (I'm using the newest of the extended keyboard line.) >The left arrow key acts like the "return" key, and the other don't do >anything except cause the "bong" noise to occur when they are pressed. >My terminal setting on the Informix machine (SGI Personal Iris) is set >for a vt100. If anyone out in netland has had this or a similar >problem and knows what I may be doing wrong, please let me know. >Thanks in advance. > >Charissa Aclin >aclin@blackjack.dt.navy.mil We had a similar problem with Informix 2.10.03D-K on Unisys 5000/50's over a network. What happened was that Informix wasn't waiting long enough to get the entire string sent by the arrow or function key (these were on Unisys's clone of vt200 terminals which use the same arrow keys as vt100's, also this was in seven bit mode). The first character of any function or arrow key on vt's is an escape and Informix would take this as its accept key (which is by default escape), instead of waiting for the entire string. This may be what is happening to you. Informix 4.00 is supposed to have a parameter that can be tuned that determines how long Informix waits to make sure it has gotten a complete key-sequence. Of course performance would suffer if this was tuned too high. I haven't tested this yet. I believe Informix is planning on porting to Unisys 5000's sometime after we put a man on Pluto, so I don't know when I will get to test it. Hope this helps (maybe what you need is an upgrade). Seth M. Fuller
davek@informix.com (David Kosenko) (10/29/90)
In article <53593@unix.cis.pitt.edu> smfst2@unix.cis.pitt.edu (Seth M Fuller) writes: >Informix 4.00 >is supposed to have a parameter that can be tuned that determines how >long Informix waits to make sure it has gotten a complete key-sequence. It does. The parameter is set via an environment variable, DBESCWT. The value you set for that specifies in seconds how long to wait after an escape is entered to see if there are subsequent characters in the sequence. The maximum value for this is 60. As setting this value higher will result in a noticeable delay when an escape alone is typed (the default ACCEPT key), you may want to remap the ACCEPT key using the OPTIONS command. We in the field have found that setting this value to 2 (i.e. wait 2 seconds after an escape to see if any other characters come in) seems to clear up the "misinterpretation" problem while not affecting the ACCEPT process too noticeably. Dave -- Disclaimer: These opinions blah blah blah. ************************************************************************** Up on the watershed, standing at a fork in the road; you can stand there and agonize, 'til your agony's your heaviest load. -E. Saliers