running java application on unix box

$ ./run_test.cmd
ksh: ./run_test.cmd: cannot execute

same result

run_test.cmd looks like this

SET JAVA_BIN="/usr/java1.4.1_05/bin"
SET ALT_HOME="/prod/iec/flt/ontyy/wld_flt3/altybin"
SET J2EE_JAR="${ALT_HOME}/seeRole/lib"
SET DEPLOY_JAR="${ALT_HOME}/seeRole/deploy/aler.jar"


set CLASSPATH=";${DEPLOY_JAR};${J2EE_JAR}/weblogic.jar;${J2EE_JAR}/ieff_acf_ient.jar;${J2EE_JAR}/ifff_ace_wls_client.jar"

${JAVA_BIN}/java -classpath .;${CLASSPATH}  com.run.ieff.fff.affrt.GetfffQueryElfRole

differ between windows and unix:  and ;, set and export
rename your file to

run_test.ksh

 run_test.kshshould look like this

#!/bin/ksh
#
#
export JAVA_HOME="/usr/java1.4.1_05/bin"
export ALT_HOME="/prod/iec/flt/ontyy/wld_flt3/altybin"
export J2EE_JAR="$ALT_HOME/seeRole/lib"
export DEPLOY_JAR="$ALT_HOME/seeRole/deploy/aler.jar"

export CLASSPATH=$CLASSPATH:$DEPLOY_JAR:$J2EE_JAR/weblogic.jar:$J2EE_JAR/ieff_acf_ient.jar:$J2EE_JAR/ifff_ace_wls_client.jar:

java -classpath $CLASSPATH  com.run.ieff.fff.affrt.GetfffQueryElfRole

... and give that file the mode 777 ( -rwxrwxrwx )

;JOOP!

>>cannot execute
This means that the permissions aren't set properly for the file.. You need to make the file executable for whatever user group needs to be able to run it.  sciuriware's suggestion makes the file read, write, and executable for everyone.  If that isn't what you want then you will need to try a different mode.

1 - execute
2 - write
3 - write/execute
4 - read
5 - read/execute
6 - read/write
7 - r/w/x

The mode applies to (owner)(group)(everyone).. so 777 means r/w/x for everyone..  144 means x for owner read for group and everyone else, etc..

If you use Ant, you can compile, run and much else on most platforms with no changes

how do i set the mode for the file

chmod o+w <filename>

Just do:

 $ . ./run_test.cmd

the first dot tells it to run the file...

same problem

$ run_test.ksh
ksh: run_test.ksh:  not found


made all the changes as u guys mentioned

What's the output of

ls -l *.ksh

?

$ ls -l *.ksh
-rw-r--r--   1 diecd01  dsdr         620 Oct 18 14:08 run_test.ksh

in the directory where your .ksh is you need to run

chmod 775 run_test.ksh

you can choose a different set of permissions but you need to see an x somewhere in the permissions so like:
xrw-r-r or xrw-xr-r--

then ./run_test.ksh

change the chmod to 775 but same problem

ksh: ./run_test.ksh:  not found

Please post result of

ls -l *.ksh

again

-rwxrwxr-x   1 diecd01  dsdr         851 Oct 18 14:28 run_test.ksh

does:

. ./run_test.ksh

work?

no even
../run_test.ksh does'nt work

Try using the full path to ksh

/usr/bin/ksh run_test.ksh

(or whatever)

>>  no even
>> ../run_test.ksh does'nt work

Space between the first dot, and the second...

. ./run_test.ksh

see?

now it finds the file (forgot the space between  the 2 dots)

but the error is like this

$ . ./run_test.ksh
ksh: ^M:  not found
ksh: ^M:  not found
ksh: ^M:  not found
ksh: ^M:  not found
ksh: ^M:  not found
ksh: CLASSPATH^M: is not an identifier

could anyone plz tell me what this error means

You don't need permissions if you use the "dot notation" :-)

Sorry, that should say:

  You don't need "execute" permissions if you use the dot notation...

Of course, you need "read" permissions ;-)

>> cat run_test.ksh | tr -d '\r' > run_test2.ksh

Or, you should be able to do:

dos2unix run_test2.ksh

to get rid of them :-)

what does this mean ..
. ./run_test.ksh
/usr/bin/.: Permission denied.

It means you need a comment line at the beginning idenifying which shell to execute:

#! /usr/bin/ksh

probably you killed the word ksh and put something else in there instead?

#!/bin/ksh

I have as the first line of the file .... but no still same results

#! /usr/bin/ksh
 even tried this but same result

try:

ksh run_test.ksh

sh run_test.sh
run_test.sh: ^M: not found
run_test.sh: ^M: not found
run_test.sh: JAVA_HOME=/usr/java1.4.1_05/bin^M: is not an identifier

changed it from ksh to sh

Hi,

Open your file in vi. you should be able to see the ^M characters. Simply delete them.

Siddhesh

wow one cigarette and 33 posts......

still any probs?

to explain the ^M
on windows linebreak is CRLF on linux just LF

so easiest way as metioned by Tim is to use dos2unix. so to sum up all you have to do:

dos2unix run_test.sh
chmod 775 run_test.sh
. run_test.sh

following shows how to change the eol characters:

http://www.technocage.com/~caskey/dos2unix/

hmmm my first post did solve 90% of the prob......
not even an assist...
:-(