It sounds like you may have removed some of the <space> characters from the script I suggested???

Please show us the output from the command uname -a. We need to know what operating system (including the release number) that you are using?

What shell are you using (including version number)? If you don't know the version number, show us the output from the command:

Code:

shell --version

where shell is the name of the shell you are using.

Then run the command:

Code:

shell -xv script_name > log 2>&1

where shell is the name of your shell and script_name is the name of the file containing my script. Then show us the exact contents of the 1st 40 lines in the file named log (in CODE tags; not ICODE tags) and show us the output from the commands:

Code:

type combining.executable
printf '%s\n' "$PATH"
ls -l 0 1 log outfile
ls -l *header|head -n 20

(also in CODE tags).

----------------

I just saw your PS. If /bin/ksh isn't a valid path on your system, how did you run the script to produce files 0 and 1 and if trying to run my script produced that error, what else did you do that attempted to run combining.executable???

Please also show us the output from the commands:

Code:

ls -l "$SHELL"
type ksh

in CODE tags.