topic TERM - Environment Variable in Operating System - HP-UX

TERM - Environment Variable

Nikee Reddy — Tue, 20 Apr 2004 15:22:39 GMT

Hello,

At present, we have 2 different kind of terminals, of which one of them support vt100 and the other support hpterm.

By default, when a admin user logon to the system, the TERM value is vt100.

venus:oracn2 > echo $TERM
vt100

What I have done is, I have created a file and inserted the following lines in it:

setenv TERM hpterm
clear

When I executed the file, the system is responding witht he following error message:

venus:oracn2 27> ./envterm
./envterm: setenv: not found.

But when I executed the follwoing command directly, it works fine:
setenv TERM hpterm
clear

What am I doing wrong in executing the file?

Thanks & regards,
Nikee

Re: TERM - Environment Variable

A. Clay Stephenson — Tue, 20 Apr 2004 15:26:46 GMT

setenv is not a POSIX or Korn shell command but rather a csh command. I suspect that you shell is csh but when you execute your file, it's executing as a POSIX shell.

Re: TERM - Environment Variable

Scott Palmer_1 — Tue, 20 Apr 2004 15:30:34 GMT

you should probably use the command
export TERM=hpterm

regards
Scott

Re: TERM - Environment Variable

Marvin Strong — Tue, 20 Apr 2004 15:31:05 GMT

setenv is part of csh

without a !#/usr/bin/csh line your script will run as posix, which does not understand setenv.

Re: TERM - Environment Variable

Marvin Strong — Tue, 20 Apr 2004 15:32:10 GMT

opps #!/usr/bin/csh

Re: TERM - Environment Variable

Sanjay_6 — Tue, 20 Apr 2004 15:32:37 GMT

Hi,

Have you tried evaluating TERM in your profile.

-----
# Set up the terminal:
if [ "$TERM" = "" ]
then
eval ` tset -s -Q -m ':?hp' `
else
eval ` tset -s -Q `
fi
stty erase "^H" kill "^U" intr "^C" eof "^D"
stty hupcl ixon ixoff
tabs
-----

Hope this helps.

Regds

Re: TERM - Environment Variable

Nikee Reddy — Tue, 20 Apr 2004 15:38:31 GMT

Hello,

I have entered the following lines in the file:
#!/usr/bin/csh
setenv TERM hpterm
clear

I could able to execute the file with out any problems, but when I ran the following command I still see the same value for TERM i.e. vt100

venus:oracn2 24> echo $TERM
vt100

It shoud suppose to show me as hpterm instead as vt100 !!!!!!!!

Regards,
Nikee

Re: TERM - Environment Variable

Marvin Strong — Tue, 20 Apr 2004 15:44:04 GMT

Sorry, I didn't mean to mislead you, adding that will make your script run because it is now running in csh, but it will not solve your problem. Do to the nature of what #! does.

Your best course of action is to create a condition in your .profile that sets determines your TERM. As mentioned above.

Re: TERM - Environment Variable

KapilRaj — Wed, 21 Apr 2004 00:35:42 GMT

I think what youm should do it to keep script1.sh as follows,

#!/usr/bin/sh
export TERM=vt100
clear

And it should be executed as follows

/home/kaps>. script1 #Please note the "DOT" in front

Regds,

Kaps

Re: TERM - Environment Variable

Peter Nikitka — Wed, 21 Apr 2004 04:31:44 GMT

Hi,

if you are running a csh / tcsh Shell, you must call

source script

to get the commands of script 'inline'
(not . script - this is for POSIX shells).
Otherwise the change of the environment
will not survive the newly created process...

If you want the changed value as a default,
put the commands in your ~/.chsrc

mfG Peter

Re: TERM - Environment Variable

Roberto Polli — Wed, 21 Apr 2004 05:05:06 GMT

You all are right, but just to make it clear to the author:

1- when you run a script you have to specify the interpreter
2- all the environment settings made into a script will remain _into_ the script because it's run into another shell (which inherits some properties and envs of the father shell) invoked on the first line, and that shell will close automatically at the end of the script
3- to run a script in the current shell and not in another one you should
3a- write it using the current shell commands
3b- invoke it using the command "source" for [t]csh; or ". " note the blank after the dot, for "bourne shells" as sh/ksh/ash; latest bash supports both methods

After doing that, please, look at http://www.tldp.org/HOWTO/Bash-Prog-Intro-HOWTO.html
it could be a starting point

Pax, R.