Terminal emulation settings help rlogin AIX to SCO

UNIX for Beginners Q & A UNIX for Dummies Questions & Answers
1

I use a program called TinyTerm to access our AIX machine. It works fine except for when I rlogin into our SCO unix server. Backspace doesn't delete, ctrl-c doesn't work (delete key does same thing), and the most annoying thing is vi acts very wierd. I have to press the down arrow like 3 times to go down to the next line and when moving the cursor left and right. It makes editing files annoying at best and dangerous as well.

I know their are many settings for emulation and it can be tricky. How do you go about finding which terminal settings you need anyway?

:wall:

2

It is likely that your TT is getting corrupted through the AIX.

What is the emulation you are using on the terminal? And what is the ttytype that the AIX is working with? And what with the SCO?

3

I am using SCOANSI to access the AIX server and then rlogin'ing into the SCO server. How do I find the tty types for the servers?

4

Is there a reason not using X (like xterm, dtterm...) to access you aix from your sco?
Wait...
Are you talking of access from a PC?

5

On both the AIX and the SCO box, type:

echo $TERM
stty -a

This will give you the basis to match the SCO keymapping to the AIX key mapping with stty commands and an approprate value for $TERM in the SCO users login profile. The arrows in vi usually needs a list of "map" commands in a .exrc file in each users home directory (see man ex ) if they don't work after sorting out the stty settings. You may already have a suitable .exrc file on your AIX box.

6

here is the output:

AIX:

$ echo $TERM                                                             
ansi                                                                     
$ stty -a                                                                
speed 9600 baud; 0 rows; 0 columns;                                      
eucw 1:1:0:0, scrw 1:1:0:0:                                              
intr = ^C; quit = ^\; erase = ^H; kill = ^U; eof = ^D; eol = ^@          
eol2 = ^@; start = ^Q; stop = ^S; susp = ^Z; dsusp = ^Y; reprint = ^R    
discard = ^O; werase = ^W; lnext = ^V                                    
-parenb -parodd cs8 -cstopb hupcl cread -clocal -parext                  
-ignbrk brkint ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl -iuclc  
-ixon -ixany -ixoff imaxbel                                              
isig icanon -xcase echo echoe echok -echonl -noflsh                      
-tostop echoctl -echoprt echoke -flusho -pending iexten                  
opost -olcuc onlcr -ocrnl -onocr -onlret -ofill -ofdel tab3              
$

SCO

Isabel! -->#echo $TERM                                                         
ansi                                                                           
Isabel! -->#stty -a                                                            
speed 38400 baud;   ispeed 38400 baud;   ospeed 38400 baud;   line = 0(tty);   
intr = DEL; quit = ^\; erase = ^H; kill = ^U; eof = ^D; eol = ^@;              
swtch = <undef>; susp = <undef>; start = ^Q; stop = ^S;                        
-parenb -parodd cs8 -cstopb hupcl cread -clocal -loblk                         
-ortsfl -ctsflow -rtsflow                                                      
-ignbrk brkint ignpar -parmrk -inpck istrip -inlcr -igncr icrnl -iuclc         
ixon ixany -ixoff                                                              
isig icanon -xcase echo -echoe echok -echonl -noflsh                           
-iexten -tostop -xclude                                                        
opost -olcuc onlcr -ocrnl -onocr -onlret -ofill -ofdel tab3                    
-isscancode                                                                    
-autoe -ed_emacs -ed_vi -ed_history                                            
Isabel! -->#

Do I need to make the 2 servers TERM settings match each other? If so where do I do that? Also, is there a possibility that changing such settings would affect applications/scripts? If so, should I just make 2 different profiles on the emulation client.. one for each server and quit doing rlogin? Yes, access is from pc's.

7

I would go and download putty :
PuTTY: a free telnet/ssh client

8

The idea is you can save separate sessions with different settings, there is a "function keys and keypad" vt100. linux, VT400... and SCO...

9

I got putty. It doesn't look right at all with putty. I know I can have seperate sessions with our terminal emulation program but I like starting one session on AIX and then rlogin to SCO. I just want bot term's to act the same.

10

You don't need to make every key match, only those which you use. In your case the vast majority of the common keys are mapped the same.

To fix the Interrupt Key, place this command in the users login profile.

stty intr "^C"

If your SCO box has a separate system console and the key mapping works, be sure to exclude the console from any key mapping changes.

11

OK, but why does in vi do I have to hit the down arrow 3 times to move down one line. Its the same for left right and up.

12

If you have an account on your AIX server where vi works, is there a .exrc file in the home directory for that account? If there is, copy it.
If not, you need to create one on the SCO server. It just maps the scan codes created when you press an arrow key to the manual control codes expected by vi (the same ones you would type if you didn't use the arrow keys).

Ps. I haven't seen a terminal set to "ansi" for at least 15 years. This must be an unusual application.