Although other monks have pointed out why it will be next to impossible to answer your questions, I will take a pre-caffeine stab in the dark and guess that the script's working directory is different when run under the scheduler than it is when run from the command line. Thus, perhaps it is "Searching..." for a file because it is looking in the wrong directory. Of course, it could be "Searching..." for Mr. Goodbar for all I know.