[SOLVED] script not exporting variables

divyashree · 06-07-2011, 03:08 AM

I have sles 10 . A user has a default shell of tcsh. I want to run a script which has to use ksh . In that script only some variables are exported, which will be used in subsequent scripts which are called inside it.

But the variables are not exported.

I am unable to find whether its a conflict of shell or what ??

I tried with debug mode, it only displays the command but not execute anyone ..

evo2 · 06-07-2011, 03:36 AM

Is this simply a case of the script being executed instead of sourced? If not, could you reproduce the problem with a minimal version of your script(s) and post here?

Cheers,

Evo2.

divyashree · 06-07-2011, 04:10 AM

Quote:

Originally Posted by evo2

Is this simply a case of the script being executed instead of sourced? If not, could you reproduce the problem with a minimal version of your script(s) and post here?

Cheers,

Evo2.

It contains only some variables exported as:

PHP Code:



#!/bin/ksh 
 
. /user/tmmltst/.profile 
export LOCAL=PLMDTST 
export DB_VENDOR=ORA 
export MTI_ROOT=/user/omfprod 
##export LM_LICENSE_FILE=/user/omfprod/install/licenses.mti 
export LM_LICENSE_FILE=8575@plmpox01 
export ORACLE_HOME=/user/oraclnt/OracleHomeClnt 
export LD_LIBRARYN32_PATH=$MTI_ROOT/bin:/user/oraclnt/OracleHomeClnt/lib32:/user/omfprod/lib32:$LD_LIBRARYN32_PATH 
export ORACLE_SID=PLMDTST 
export TWO_TASK=PLMDTST 
export JAVA_HOME=/usr/java/jre1.6.0_14 
export PATH=/usr/java/jre1.6.0_14/bin:$ORACLE_HOME/bin:$PATH 
umask 002; 
 
#export Project_List="3790 3990 3750 3770" 
 
export Project_List="3790 3990 3750 3770" 
 
export sqluser="tmmltsdb/oracle" 
export TC_USER="tmmltst" 
export TC_PASS="tmmltst" 
 
. /user/tmmltst/cusdir/Pdf/ALL_CATIA_PLM_PDF.sh

catkin · 06-07-2011, 10:49 AM

What are you doing/seeing that leads to the conclusion "the variables are not exported"?

divyashree · 06-07-2011, 11:56 PM

Quote:

Originally Posted by catkin

What are you doing/seeing that leads to the conclusion "the variables are not exported"?

Beacuse echo $VARIABLE doesnot return any values..

catkin · 06-08-2011, 12:17 AM

If I understand correctly a tcsh user runs the ksh shell script (first lines illustrated in the OP) which goes on to run other scripts (calling method and language not known; depth of calls not known) which at some depth echo $VARIABLE does not work ...

It might help to know the missing details.

divyashree · 06-08-2011, 12:27 AM

Quote:

Originally Posted by catkin

If I understand correctly a tcsh user runs the ksh shell script (first lines illustrated in the OP) which goes on to run other scripts (calling method and language not known; depth of calls not known) which at some depth echo $VARIABLE does not work ...

It might help to know the missing details.

I commented the line calling other scripts, and the same result.

grail · 06-08-2011, 12:36 AM

Please confirm at what point are you performing the echo?

I will reiterate what catkin has said but with an example:

Primary script (prim.sh):

Code:

#!/bin/ksh

. /user/tmmltst/.profile
export LOCAL=PLMDTST

/user/tmmltst/second.sh

Secondary script (second.sh):

Code:

#!/bin/ksh

echo $LOCAL

Then you run the script like:

Code:

./prim.sh

Is this the correct version of events (although simplified)?

divyashree · 06-08-2011, 01:12 AM

Quote:

Originally Posted by grail

Please confirm at what point are you performing the echo?

I will reiterate what catkin has said but with an example:

Primary script (prim.sh):

Code:

#!/bin/ksh

. /user/tmmltst/.profile
export LOCAL=PLMDTST

/user/tmmltst/second.sh

Secondary script (second.sh):

Code:

#!/bin/ksh

echo $LOCAL

Then you run the script like:

Code:

./prim.sh

Is this the correct version of events (although simplified)?

No actually I do echo outside the script in the shell, after executing the script ..

grail · 06-08-2011, 01:27 AM

Then this would be your problem ... the moment the script finishes executing all variables will be lost.

divyashree · 06-08-2011, 01:37 AM

Quote:

Originally Posted by grail

Then this would be your problem ... the moment the script finishes executing all variables will be lost.

No, but if I am running with pure ksh or pure sh shells, then it's not loosing values outside of the script.

colucix · 06-08-2011, 02:15 AM

If the default shell is /bin/tcsh, the ksh script cannot be sourced because in that case the sha-bang will be treated as a comment and ignored and the export statements will return a command not found error. Your only option is to change the ksh script to the C-shell equivalent, using setenv in place of export and again by sourcing it instead of executing.

evo2 · 06-08-2011, 02:20 AM

Quote:

Originally Posted by divyashree

No actually I do echo outside the script in the shell, after executing the script ..

Ahh, so my initial suspicion was correct.

Evo2.

divyashree · 06-08-2011, 03:09 AM

Quote:

Originally Posted by colucix

If the default shell is /bin/tcsh, the ksh script cannot be sourced because in that case the sha-bang will be treated as a comment and ignored and the export statements will return a command not found error. Your only option is to change the ksh script to the C-shell equivalent, using setenv in place of export and again by sourcing it instead of executing.

If the values will not inherit, how they will be passed to the scripts called inside the main one ?

colucix · 06-08-2011, 03:29 AM

These two statements are in sharp contrast to each other:

Quote:

Originally Posted by divyashree

No actually I do echo outside the script in the shell, after executing the script ..

Quote:

Originally Posted by divyashree

If the values will not inherit, how they will be passed to the scripts called inside the main one ?

It's still not clear what is the sequence of events. Your first statement means you launch a script containing the export statements and then try to echo them after the script has terminated. In that case you will not see the changes since the parent shell does not inherit the child's environment. The second statement means you have a script which calls other scripts inside it: in this case the exported variables should be visible from the childs.

Here is a working example using a /bin/ksh script from a /bin/tcsh default shell:

Code:

$ cat > script.sh
#!/bin/ksh
export LOCAL=PLMDTST
export DB_VENDOR=ORA
export MTI_ROOT=/user/omfprod
./script_child.sh
$ chmod +x script.sh
$ cat > script_child.sh 
#!/bin/ksh
echo "The LOCAL variable is:     $LOCAL"
echo "The DB_VENDOR variable is: $DB_VENDOR "
echo "The MTI_ROOT variable is:  $MTI_ROOT"
$ chmod +x script_child.sh
$ ./script.sh
The LOCAL variable is:     PLMDTST
The DB_VENDOR variable is: ORA
The MTI_ROOT variable is:  /user/omfprod

Can you reproduce this behavior on your machine? Does it works exactly as in my example?