I'm trying to run on Linux, a script (menu) that was conducted for the shell "oash"

to run the above script gives the following error:

/usr/lib/scosh/utilbin/oash: No suhc file or directory

in a desperate attempt, it copies a complete directory SCO UNIX

/usr/lib/scosh/

but in vain attempt, I kept giving the same error

will have a solution for this????

thanks in advance

I found a site that says:
I didn't find anything that gave information about how one would convert oash to a shell that Linux understands (e.g. bash).

However since bash is an enhanced version of the Bourne shell and depending on features used in your script it might be something as simple as changing the first line of the script (assuming it has something like "#!<pathto>/oash" to have instead "#!/bin/bash". This first line is called the interpreter line in scripts and it just specifies what shell the script should be run in.

I don't know that the oash binary if copied to Linux would work (based on above info about automation libraries I suspect it wouldn't).

However you might want to check the permissions on the oash file and parent directories to see if you have permission to execute it as the user that is running the script. Rather than running the script simply try to run the oash command itself. Also if you do NOT have permissions to the directory you put it in you might want to move the oash command to another directory and execute it from there. If that works then changing the interpreter line to "#!<newpathto>/oash" might resolve your problem.

By the way SCO is "closed source" commercial software so it isn't really proper to run its binaries on another platform even if they would work.

I agree with MensaWater, and will also add that trying to keep your script running with an old, soon-to-be out of business product (and closed-source to boot), isn't a good plan for the future.

Put some time in, and migrate your script to bash, and you'll have total portability across 99.9% of all *Nix systems. Perhaps if you post your script, we can look and see if there are any glaring problems with it running under bash.