I asked what operating system and shell you're using. You have now shown us which OS you're using, but not which shell.

I asked what your shell script really was and what output was produced when you ran it. You have not done either of those. With the code you have shown us, running that code (assuming there is no utility in your PATH named RUN_FILE, that the variable RUN_FILE was not inherited in the environment, and that you ran that code using a shell that uses Bourne shell syntax) would produce output similar to:

Code:

tester: line 1: RUN_FILE: not found
1=
for RECS_REC in ; do
find /*Rele**..**..* -not -name '*.' | while read rname; do
echo 
BCODE='SETUP FAILED'
echo ****************************************************************************
echo mv  /file_error
mv  /file_error
RUN_FILE=TRUE
echo RUN_FILE 2=
done
done
echo  3=

If there is a utility named RUN_FILE in your PATH, a variable named RUN_FILE has been exported to your environment and initialized with a value similar to RUN_FILE, and you ran the script with a Bourne compatible shell, you'd get output similar to:

Code:

RUN_FILE 1= RUN_FILE
for RECS_REC in ; do
find /*Rele**..**..* -not -name '*.' | while read rname; do
echo 
BCODE='SETUP FAILED'
echo ****************************************************************************
echo mv  /file_error
mv  /file_error
RUN_FILE=TRUE
echo RUN_FILE 2= RUN_FILE
done
done
echo  RUN_FILE 3= RUN_FILE

neither of which look anything like the output you say that code produces.

You say: "pipe forces a subshell to be created and once the loop completed.
the result of the variable which i got in inside the loop is reset after the loop.", but there is no pipeline in the code you showed us. The only pipe symbol in your script is inside a double-quoted string that is printed by the first echo in your script.

There is no way on earth to create a shell script where the command:

Code:

echo $RUN_FILE 3=$RUN_FILE

is going to print:

Code:

RUN_FILE 3=FALSE

The expansion of $RUN_FILE could produce RUN_FILE if something in your script had set RUN_FILE=RUN_FILE, but there is no code anywhere in your script that does that. The expansion of $RUN_FILE could produce FALSE if something in your script had set RUN_FILE=FALSE, but there is no code anywhere in your script that does that. There is no way that two expansions of the same variable in a single echo statement will produce different results.

And, the command that was in your script:

Code:

echo $RUN_FILE 3=$RUN_FILE"

is only sort of doing what you might have wanted it to do because the mismatched double-quote at the end of the line is matching another mismatched double-quote character somewhere else in your script. (In this case it is matching the double quote at the end of line #2 in your script.)

If you won't tell us what shell you're using (including its release number), show us the actual code you're running, show us the actual output that your code is producing, and CLEARLY explain what you are trying to do that is not working; we are wasting our time trying to help you.