Alas, termcap pre-dates the standard xterm, it may not exist in the standard
termcap. Looking through my files, I see that the xterm definitions I came
up with were trashed in my (pre-backup, Norton caused) drive crash sometime
back. There are some xterm definitions on iiug at
http://www.iiug.org/software/archive/termcaps_xterm. Give the iiug version
a shot and let me know if it works for you, if not, let me know which keys
or features do not and I'll have a look at those.

So to get this all working, copy/paste the definition from the iiug site
into the end of your termcap file, call them special names - like xterm1,
xterm2 or Phred whatnot - set your TERM environment variable to that value
(xterm1, xterm2, Phred) and try dbaccess.

A better answer would be to copy them to your very own termcap file
andrews_termcap (or whatnot) and set your TERMCAP variable to point to
andrews_termcap (including path) - just to avoid mucking up the "pristine"
distribution copy of termcap. The termcap file itself is probably fine,
it's just a question of what gnome is sending when you hit the return key.
To track that specific one, do:

cat > junk
[ENTER]
CTRL-D

od -cx junk will show you the octal and character representation of what
Gnome/ssh is sending when you press the Enter key. From there you can
wander into the termcap file and make that agree with it.

You will see entries like ku=\EOA (KeyUp=Escape-O A) which means that the
terminal filter is expecting the keyboard to send that sequence when the up
arrow is pressed. There may be a corresponding sequence that the filter is
supposed to send when it is attempting to tell the terminal to perform
something - like nl=^J (Newline = down arrow). Sequences which are not
spelled out are assumed to be the defaults or are inherited from a previous
definition.

If you're not into working through all of that, let me know and I would be
interested in working with you to resolve any non-working features/keys.

Documentation for the codes is sparse, 'man terminfo', oddly enough,
provides the best list I've seen lately. I can't remember where the
original termcap keys/features were spelled out.

j.

-----Original Message-----
From: informix-list-bounces (AT) iiug (DOT) org
[mailto:informix-list-bounces (AT) iiug (DOT) org]On Behalf Of Andrew2006
Sent: Thursday, December 27, 2007 10:12 AM
To: informix-list (AT) iiug (DOT) org
Subject: Re: dbaccess - return key does not work?


On Dec 27, 3:09 pm, "Jack Parker" <jack.park... (AT) verizon (DOT) net> wrote:
The arrow keys do work. The Enter keys do not work. They have the same
effect as "down arrow".

My TERM is currently set to xterm. I run dbaccess by opening a console
in Gnome and sshing into another Linux box where dbaccess is
installed. The relevant environment variables on the dbaccess box are:
INFORMIXTERM="termcap"
TERM="xterm"
TERMCAP="/opt/informix/etc/termcap"

As Ctrl-M also appears to be mapped incorrectly (it performs "down
arrow"), it looks like the termcap file may be foobared.

Nevermind. In the meantime I can work around it, but it would be nice
if worked as intended ...

Many thanks

Andrew
_______________________________________________
Informix-list mailing list
Informix-list (AT) iiug (DOT) org
http://www.iiug.org/mailman/listinfo/informix-list

On Dec 27, 5:20 pm, "Jack Parker" <jack.park... (AT) verizon (DOT) net> wrote:
Jack,

This is the result of testing what ssh is sending as "Return":
$ od -cx junk
0000000 \n \0
000a
0000001

I created a termcap in my home directory and pointed the environment
variable TERMCAP at this.

This contains the following termcap snippet from the iuug site:
<termcap>
vs|xterm|vs100|xterm terminal emulator (X window system):\
:cr=^M:do=^J:nl=^J:bl=^G:le=^H:ho=\E[H:\
:co#80:li#65:cl=\E[H\E[2J:bs:am:cm=\E[%i%d;%dH:nd=\E[C:up=\E[A:
\
:ce=\E[K:cd=\E[J:so=\E[7m:se=\E[m:us=\E[4m:ue=\E[m:\
:md=\E[1m:mr=\E[7m:me=\E[m:\
:ku=\E[A:kd=\E[B:kr=\E[C:kl=\E[D:kb=^H:\
:k0=\E[11~:k1=\E[12~:k2=\E[13~:k3=\E[14~:k4=\E[15~:\
:k5=\E[17~:k6=\E[18~:k7=\E[19~:k8=\E[20~:k9=\E[21~:\
:kf=\E[6~:kg=\E[5~:\
:kY=\E[216z:kZ=\E[222z:\
:ta=^It:sf=\n:sr=\EM:\
:al=\E[L:dl=\E[M:ic=\E[@:dc=\E[P:\
:MT:ke=\E[?1l\E>:\
:is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l:\
:rs=\E[r\E<\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l:xn:\
:AL=\E[%dLL=\E[%dM:IC=\E[%d@C=\E[%dP:\
:ti=\E7\E[?47h\E(B\E)0:te=\E[2J\E[?47l\E8:\
:hs:ts=\E[?E\E[?%i%dT:fs=\E[?F:es:ds=\E[?E:\
:gs=^n:ge=^o:gb=lmkjqx:
</termcap>

I tried the following replacements for the "nl=^J" entry:
- "nl=\n"
- "nl=\0"
- "nl=000a"

reloading dbaccess each time. None of them changed how the Enter key
works.


Have just noticed another version of Informix on the dbaccess box in a
directory called: informix_10.0UC5
If I run dbaccess from here then the Return key works as expected. /
informix_10.0UC5/etc/termcap is identical to /informix/etc/termcap.
The bug must therefore be in the version of dbaccess inside /informix/
bin/.
Is there a command you can run to find the version of dbaccess you're
using?

dbaccess -v OR dbaccess -V to see your version.
Did you try vt100 just for poos and giggles, sometimes that's a nice
generic TERM setting.
Norma Jean
..
..
..
..
================================================== ==========
The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader
of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any reproduction,
dissemination or distribution of this communication is strictly
prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Tellabs
================================================== ==========

Norma Jean already answered the other part, her suggestion for vt100 is also
a good one (I always try wyse-50 and ansi as well). Sounds also as though
you have isolated the issue as something else, which is intriguing. I look
forward to hearing the version numbers in question and other's thoughts.

The 0000000 is the octal address from od, the \n is what your enter key sent
and the 000a is the octal representation of the string. So \n (linefeed) is
the value you would be looking for.

I was too lazy to look up the proper code for you before (actually I did,
but did not believe that @8 was actually it, so I didn't boot my linux box
to check - I have done so now and find the $INFORMIXDIR/etc/termcap entry
there contains an xterm entry (below) - which does in fact have an entry for
@8. (@8=\EOM or Escape O M). Typing that manually I do not get a \n in the
resulting file. I too am using ssh, but from cygwin, I am using ansi for my
TERM. Mine also produces \n for both Enter keys.

Looking at termcap, @8 is not typically spelled out, which would indicate
that most terminals produce the same value, which I would actually expect to
be \r (Carriage Return). I must have something wrong somewhere - K and
returns have always been an issue between me and termcap. Mucking about
with @8, I get no results from changing it (or nl for that matter). I do
get expected results from swapping kd and ku - so it is using my termcap.
Hmm, playing around with all of them (nw, nl, cr, @8) none of them have
effect - must be something magical about the return key that I am missing.
Anyone?

j.

xterm|vs100|xterm terminal emulator:\
:am:km:mi:ms:xn:bst:\
:co#80:it#8:li#65:\
:@8=\EOM:AL=\E[%dLC=\E[%dPL=\E[%dMO=\E[%dB:\
:IC=\E[%d@:K1=\EOq:K2=\EOr:K3=\EOs:K4=\EOp:K5=\EOn:\
:LE=\E[%dD:RI=\E[%dC:UP=\E[%dA:\
:ac=``aaffggjjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{|| }}~~:\
:ae=^O:al=\E[L:as=^N:bl=^G:cb=3\E[1K:cd=\E[J:ce=\E[K:\
:cl=\E[H\E[2J:cm=\E[%i%d;%dH:cr=\r:cs=\E[%i%d;%dr:\
:ct=\E[3g:dc=\E[P:dl=\E[M:do=\n:eA=\E(B\E)0:ho=\E[H:\
:ic=\E[@:k0=\EOy:k1=\EOP:k2=\EOQ:k3=\EOR:k4=\EOS:\
:k5=\EOt:k6=\EOu:k7=\EOv:k8=\EOl:k9=\EOw:k;=\EOx:\
:kb=\b:kd=\EOB:ke=\E[?1l:kl=\EOD:kr=\EOC:ks=\E[?1h:\
:ku=\EOA:le=\b:mb=@:md=\E[1m:me=\E[m:mr=\E[7m:nd=\E[C:\
:r1=\E>\E[1;3;4;5;6l\E[?7h\E[m\E[r\E[2J\E[H:\
:r2=@kf1=\EOP:rc=\E8:\
:.sa=!!! MUST CHANGE BY HAND
!!!\E[0%?%p1%p6%|%t;1%;%?%p2%t;4%;%?%p1%p3%|%t;7%;%?%p4% t;5%;m%?%p9%t^N%e^O%
;:\
:sc=\E7:se=\E[m:sf=\n:so=\E[7m:sr=\EM:st=\EH:ta=\t:\
:up=\E[A:

DB-Access Version 10.00.UC5I1. The return key works fine.



Jack,

This is the result of testing what ssh is sending as "Return":
$ od -cx junk
0000000 \n \0
000a
0000001

I created a termcap in my home directory and pointed the environment
variable TERMCAP at this.

This contains the following termcap snippet from the iuug site:
<termcap>
vs|xterm|vs100|xterm terminal emulator (X window system):\
:cr=^M:do=^J:nl=^J:bl=^G:le=^H:ho=\E[H:\
:co#80:li#65:cl=\E[H\E[2J:bs:am:cm=\E[%i%d;%dH:nd=\E[C:up=\E[A:
\
:ce=\E[K:cd=\E[J:so=\E[7m:se=\E[m:us=\E[4m:ue=\E[m:\
:md=\E[1m:mr=\E[7m:me=\E[m:\
:ku=\E[A:kd=\E[B:kr=\E[C:kl=\E[D:kb=^H:\
:k0=\E[11~:k1=\E[12~:k2=\E[13~:k3=\E[14~:k4=\E[15~:\
:k5=\E[17~:k6=\E[18~:k7=\E[19~:k8=\E[20~:k9=\E[21~:\
:kf=\E[6~:kg=\E[5~:\
:kY=\E[216z:kZ=\E[222z:\
:ta=^It:sf=\n:sr=\EM:\
:al=\E[L:dl=\E[M:ic=\E[@:dc=\E[P:\
:MT:ke=\E[?1l\E>:\
:is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l:\
:rs=\E[r\E<\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l:xn:\
:AL=\E[%dLL=\E[%dM:IC=\E[%d@C=\E[%dP:\
:ti=\E7\E[?47h\E(B\E)0:te=\E[2J\E[?47l\E8:\
:hs:ts=\E[?E\E[?%i%dT:fs=\E[?F:es:ds=\E[?E:\
:gs=^n:ge=^o:gb=lmkjqx:
</termcap>

I tried the following replacements for the "nl=^J" entry:
- "nl=\n"
- "nl=\0"
- "nl=000a"

reloading dbaccess each time. None of them changed how the Enter key
works.


Have just noticed another version of Informix on the dbaccess box in a
directory called: informix_10.0UC5
If I run dbaccess from here then the Return key works as expected. /
informix_10.0UC5/etc/termcap is identical to /informix/etc/termcap.
The bug must therefore be in the version of dbaccess inside /informix/
bin/.
Is there a command you can run to find the version of dbaccess you're
using?
_______________________________________________
Informix-list mailing list
Informix-list (AT) iiug (DOT) org
http://www.iiug.org/mailman/listinfo/informix-list

On Dec 27, 10:09*pm, "Jack Parker" <jack.park... (AT) verizon (DOT) net> wrote:
Jack,

The version numbers of the two dbaccess programs is the same. Also the
md5sum of the binaries are the same. I've also checked that one is not
a symlink to the other. Will look into this more tomorrow...

Many thanks for all the time you've put in to this!

Andrew

Andrew,

Termcap has always been near and dear to my heart, especially since there
are elements about it that don't match my understanding.

If the dbaccess binaries are the same, then we are back to environment.
hmmm. what about your PATH? is there a third dbaccess binary out there
somewhere? Just for grins, from within dbaccess you can escape to the shell
with a "!sh", do that and echo your environment into something that you can
check later and compare between the two - perhaps there is a different
environment getting loaded when you run dbaccess.

I'm headed off for the rest of the week at some point tomorrow, away from
email. I won't be ignoring you, just not here.

j.

---

Jack,

The version numbers of the two dbaccess programs is the same. Also the
md5sum of the binaries are the same. I've also checked that one is not
a symlink to the other. Will look into this more tomorrow...

Many thanks for all the time you've put in to this!

Andrew
_______________________________________________
Informix-list mailing list
Informix-list (AT) iiug (DOT) org
http://www.iiug.org/mailman/listinfo/informix-list

Jack, Andrew,
Could there be an stty setting in the way? I know on solaris sometimes
my .profile (ksh) or .cshrc (csh) can have unexpected stty settings
(unexpected for me, but perhaps good for some application or someone).
An unexpected STTY setting can hose up my backspace key or my kill key
so I have to do a couple stty settings to get things "out of the way"
and then my normal key expectations start working.
Just a thought,
Norma Jean
..
..
..

================================================== ==========
The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader
of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any reproduction,
dissemination or distribution of this communication is strictly
prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Tellabs
================================================== ==========

.... and a good one to boot.

j.

-----Original Message-----
From: Sebastian, Norma J. [mailto:NormaJean.Sebastian (AT) tellabs (DOT) com]
Sent: Thursday, December 27, 2007 9:25 PM
To: Jack Parker; Andrew2006; informix-list (AT) iiug (DOT) org
Subject: RE: dbaccess - return key does not work?


Jack, Andrew,
Could there be an stty setting in the way? I know on solaris sometimes
my .profile (ksh) or .cshrc (csh) can have unexpected stty settings
(unexpected for me, but perhaps good for some application or someone).
An unexpected STTY setting can hose up my backspace key or my kill key
so I have to do a couple stty settings to get things "out of the way"
and then my normal key expectations start working.
Just a thought,
Norma Jean
..
..
..

================================================== ==========
The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader
of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any reproduction,
dissemination or distribution of this communication is strictly
prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Tellabs
================================================== ==========

On Dec 27, 2007 3:24 AM, Andrew2006 <mymatebob (AT) googlemail (DOT) com> wrote:
I agree with the general consensus that the problem is most likely
related to terminal handling.

One option no-one else mentioned is setting INFORMIXTERM=terminfo and
then using
the terminfo entries instead of the termcap entries. You might then
need to set TERMINFO=/where/you/terminfo/files/are (but probably would
not).

This isn't necessarily a slam dunk - the Informix termcap file is a
weird and wonderful thing (but not necessarily updated very often -
I'd be mildly surprised if it had been updated in the current
millennium, but I might be doing people an injustice).


--
Jonathan Leffler #include <disclaimer.h>
Email: jleffler (AT) earthlink (DOT) net, jleffler (AT) us (DOT) ibm.com
Guardian of DBD::Informix v2007.0914 -- http://dbi.perl.org/
NB: Please do not use this email for correspondence.
I don't necessarily read it every week, even.

On Dec 28, 12:11 am, "Jack Parker" <jack.park... (AT) verizon (DOT) net> wrote:
Jack,

I ran dbaccess in non-menu mode, escaped to shell and output my
environment by typing "set <return>" and "export <return>". I copied
the output to a text editor.
The two different locations of dbaccess had identical environments
except for the PPID and TERMCAP (which I had set differently for each
one).

Norma Jean - I'll look into editing the STTY.
Jonathon - will try setting the TERMINFO.

Cheers all,

Andrew