Shell Programming and Scripting

Looks like a carriage return at the end of the shebang (probably a result of editing in Windows).

Regards,
Alister

Try adding set -x to the top of your script below the #!/bin/sh line, run it again, and provide the output.

Code:

#!/bin/sh
set -x

If exec can't find the interpreter, none of the script executes, including set -x.

It's almost certainly a carriage return at the end of the interpreter line. Not only would it explain why the interpreter can't be found (it's looking for a file whose basename is sh<carriage return>), it also explains why there's no interpreter name before the first colon in the error message (after the bad interpreter name is printed, the cr returns the cursor to the beginning of the line and the subsequent characters in the error message overwrite it).

Regards,
Alister

Thanks Alister and all.
You were dead right. I had edited in Windows. After I edited with vi editor, the error never appeared again.
Still the below code did not take any effect :

Code:

sed -r '/^$|-|PRCSINSTANCE/d' $P_FILE

After I gave the same code to print the result to another file, it worked.

Code:

sed -r '/^$|-|PRCSINSTANCE/d' $P_FILE > $O_FILE

Thanks again to everyone who had assisted me so patiently. You all made my day!!!