I’m just hoping that we don’t have any further reminders for the rest of the week.

There were two problems that I was experiencing. The first was that F1-F4 were mapped differently, for what appears to be historical reasons (VT100 terminals did not have these keys). The other was that the telnet client needed to be in character mode, instead of line mode, and there was no easy way to do this in the Linux telnet client except through the user manually changing the mode.

So I used Expect to translate the F1-F4 keys to what the remote MSCA telnet server wanted, and then used C-Kermit as my telnet client. The scripts I wrote to perform these two steps are as follows:

 #!/usr/local/bin/kermit

 set telnet newline-mode nvt raw
 set telnet echo remote

 telnet /nowait host.company.com 12345

 quit

and

 #!/usr/bin/expect

 eval spawn -noecho "/usr/local/bin/ktelnet.sh"

 interact {
 "\033[[A" { send "\033[P" }
 "\033[[B" { send "\033[Q" }
 "\033[[C" { send "\033[R" }
 "\033[[D" { send "\033[S" }
 }

Unfortunately, Kevin failed to mention a potential downside of having one of these babies. Namely, your developers and consultants will assume (even more than they probably already do) that whatever junk code they throw at the machine will run flawlessly. And if it doesn’t, it must be the DBA or Unix team’s fault.