HP-UX System Administrator's Guide: Configuration Management

4. Set the user’s TERM variable in the appropriate login script (either .profile for
Korn and POSIX shell users or .login for C shell users in their home directory)
to any of the names you uncovered in Step 2. For example:
# export TERM=wy100 (Korn or POSIX shell)
# setenv TERM wy100 (C shell)
The default versions of these scripts prompt the user for the terminal type upon
log in, so rather than editing the script, you could simply tell the user to respond
with the terminal name. For example:
TERM = (hp) wy100
You can also set the TERM variable with the /sbin/ttytype command.
Troubleshooting Terminals
There are a number of terminal-related problems that can occur. Many of these result
in a terminal that appears not to communicate with the computer. Other problems
cause “garbage” to appear on the screen (either instead of the data you expected or
intermixed with your data).
This section primarily addresses problems with alpha-numeric display terminals;
however, many of the steps discussed here can also be applied to problems with terminal
emulators such as HP AdvanceLink (running on a Vectra PC) or X Window terminal
processes (such as hpterm and xterm). Also see “Other Terminal Problems” (page 151).
Unresponsive Terminals
There are many things that can cause a terminal not to respond (no characters are
displayed except, perhaps, those which are displayed by the terminal’s local echo
setting). Here is a procedure you can use to find many of them.
Troubleshooting Terminals 145