When CSH tells you "Command not found", it doesn't always mean that

Yesterday, I was working on a newly set-up environment and was blocked for quite a while by a small issue. The issue is that when I ran a command (say "mycmd") in CSH (I had to), CSH always reported ./mycmd: Command not found. But, obviously the command was there.

[root@CSH ~]# ./mycmd
./mycmd: Command not found.

At last, I happened to run it in my default shell BASH. Then, I was instantly reminded that I am running a 32-bit program on 64-bit platform without dependent libraries.

[root@BASH ~]# ./mycmd
-bash: ./mycmd: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory

What a pity that CSH had given such a misleading information. It seems to me that we shall avoid using CSH unless "being forced" to do so. What's your opinion?