topic Re: Proper SYNTAX for EXPORTing variables in Operating System - HP-UX

Proper SYNTAX for EXPORTing variables

Michael Steele_2 — Thu, 02 Dec 2010 14:37:33 GMT

Hi:

ScritA calls ScriptB

In ScriptA
SERVER="mecury"
export SERVER

In ScriptB
echo $SERVER

And it prints nada.

What up?

Re: Proper SYNTAX for EXPORTing variables

Doug O'Leary — Thu, 02 Dec 2010 15:00:20 GMT

Hey;

Works for me...

$ cat A B
#!/bin/ksh

Server="mercury"
export Server

./B
#!/bin/ksh

echo $Server
$ ./A
mercury

You sure you're not stomping SERVER somewhere in ScriptB?

Doug

Re: Proper SYNTAX for EXPORTing variables

Pete Randall — Thu, 02 Dec 2010 15:14:14 GMT

What shell are you using?

Pete

Re: Proper SYNTAX for EXPORTing variables

James R. Ferguson — Thu, 02 Dec 2010 15:17:13 GMT

Hi:

Source 'ScriptA' so that a separate environment isn't created for it:

# . ./ScriptA
# ./ScriptB

...or for that matter, *within* 'ScriptB' do:

...
. ./ScriptA
...

Note that shell sourcing is done with a dot, followed by whitespace, followed by the script name.

Regards!

...JRF...

Re: Proper SYNTAX for EXPORTing variables

Dennis Handly — Fri, 03 Dec 2010 20:55:45 GMT

>SERVER="mecury"
>export SERVER

This is the old borne shell way of doing things. In a real shell you can use:
export SERVER="mecury"

Re: Proper SYNTAX for EXPORTing variables

Steven Schweda — Sat, 04 Dec 2010 23:16:22 GMT

Note that, as usual, showing an actual
failing test case instead of a vague
description ("ScritA calls ScriptB", where
"calls" is not well defined) would make this
problem easier to diagnose with less reliance
on guesswork/intuition.

Just a thought.