cancel
Showing results for 
Search instead for 
Did you mean: 

QSH command not found

blaw
Active Participant
0 Kudos

We Noticed the a problem on our v5R4 iseries after an IPL this weekend

in both our development system and production system.

If I try to start JSPM via:

QSH CMD('/usr/sap/rp1/DVEBMGS00/j2ee/JSPM/go') get an error

go command not found.

If I try to start the SDM via

./StartServer.sh ; get the same error command not found

I can do a java -version with qsh and get a result java

version "1.4.2";

Tried using the go from 885063 and sidadm is the owner

Does anyone have any idea's how to resolve this issue or other test to

run.

qsh: 001-0014 Command /usr/sap/rp1/DVEBMGS00/j2ee/JSPM/go not found.

Press ENTER to end terminal session.

Regards,

Brian

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Brian,

have you checked if the executable flag is set on the shell scripts?

E.g. do an ls -l with QSH in the directory of your JSPM. You should see a row like:

-rwxrwxrwx 1 <sid>adm <sid>group 3107 Jul 7 10:13 go

if you don't see x-es you have to set the executable permission by:

chmod 777 go

You have to be the owner of the file or QSECOFR for that.

HTH,

Christoph

blaw
Active Participant
0 Kudos

Yes I did check - I signed on as sidadm which is the owner and I can chmod 755 and 777 with that id.

I am thinking it has to do with the QIBM Java directory. the go command and the SDN fails on all j2ee system since the IPL this weekend. I was told nothing was changed or added.

I tried starting the ddm service and tcp netsvr also.

Regards,

Brian

Former Member
0 Kudos

Hi,

Did you check Note 885063 - iSeries: JSPM Support with NW04s

regards,

kaushal

Former Member
0 Kudos

Hi Brian,

ideas for debugging that issue: put an "echo test" into the first line of the go script. If you then see the echo output you'll know that at least the script was executed. Then one would have to debug into the script. If not even the echo is done, it is maybe a good idea to check the authorities along the path to the go script. You can do that by creating a little test script (with the same authorities as go) which just echoes something and try to place it in the directories further up the path.

IF nothing helps you might want to consider opening a ticket at SAP?

BR,

Christoph

Answers (2)

Answers (2)

Former Member
0 Kudos

Reading your question

"QSH CMD('/usr/sap/rp1/DVEBMGS00/j2ee/JSPM/go') not found"

one simple answer may be did you put rp1 in UPPER CASE? I think it is case sensitive?

Try

QSH CMD('/usr/sap/RP1/DVEBMGS00/j2ee/JSPM/go')

worth a go.

Michael

blaw
Active Participant
0 Kudos

I opened a message with SAP and suggest I go to IBM because they found that When using the PASE environment (logon with RP1ADM and CALL QP2TERM)

the JSPM starts fine after entering /usr/sap/RP1/DVEBMGS00/j2ee/JSPM/go.

Opening the PMR.

Thanks,

Brian