Not really...

You're using an operating system that is about 25 years old. And, on any Solaris 5.x system, you shouldn't be using /usr/bin/awk or /bin/awk (I've forgotten which it was in Solaris 5.0) unless you're using it to run code that you copied from a UNIX System V or earlier AT&T UNIX system.

You have shown us two code segments. And, you've told us you're concerned about how variables are being used. But, whether you set a variable named logdata or you save the output in a file named file, you haven't shown us what output is stored there, you haven't told us what output you want to store there, and you haven't shown us any code that uses the data once it is saved (so we don't know whether a variable, a file, or a pipeline reading it directly would make more sense).

The two code segments you showed us:

Code:

var12=$(ps -ef | grep apache | awk '{print $2,$4}')

and

Code:

while read userpid username
do 
logdata=$(ssh -n $username@dell.sys.com pwdx $userpid | awk '{print $2}')
done < $var12

could easily be combined without using any variables or files (except to store the final output) and getting rid of one invocation of awk with:

Code:

ps -ef | grep apache | while read junk userpid junk username junk
do 	ssh -n $username@dell.sys.com pwdx $userpid | nawk '{print $2}'
done > file

I never used the bash that came with Solaris 5.0, but the grep could also be removed from the pipeline using bash built-ins. I could easily do it with the ksh on Solaris 5.0, but I don't know what parameter expansions were available in bash at that time.