On 8/24/2017 9:13 AM, גדי בן אבי wrote:
This is what SYSPRINT says:
------------------------------------------------------------------------------
DATE 08/24/17 TIME 16:08:40 SERVER Data SMP/E 36.79
<SERVER
host="10.202.14.11"
user="gadi_b"
pw="******">
<PACKAGE
file="/down_l/rakefet/2008571642_000010_PROD/order/GIMPAF.XML"
hash="855F7AE091F92690C9F01A40568F4FA0A9AB8266"
id="ST222133.order">
</PACKAGE>
</SERVER>
------------------------------------------------------------------------------
DATE 08/24/17 TIME 16:08:40 CLIENT Data SMP/E 36.79
<CLIENT retry="3"
javahome="/usr/lpp/java/J8.0_64"
classpath="/usr/lpp/smp/classes"
javadebugoptions="-Dcom.ibm.smp.debug=severe -showversion"
downloadmethod="https"
downloadkeyring="javatruststore">
</CLIENT>
DATE 08/24/17 TIME 16:08:40 SMP/E GIMJVCLT OUTPUT SMP/E 36.79
/bin/sh -c /usr/lpp/java/J8.0_64/bin/java -Dcom.ibm.smp.debug=severe
-showversi
n -cp /usr/lpp/smp/classes/ com.ibm.smp.GIMJVCLT
Yeah, that is strange, as I expect more information in SYSPRINT
following this output to explain the error. Could it be that SMP/E was
not able to start /bin/sh? Is the userid that is running the job able
to start the UNIX shell directly, for example from the TSO/E prompt?
As an experiment, try to logon to TSO/E with the userid running the job,
start OMVS, and execute this command from the OMVS shell (watch the wrap):
/usr/lpp/java/J8.0_64/bin/java -Dcom.ibm.smp.debug=severe -showversion
-cp /usr/lpp/smp/classes/ com.ibm.smp.GIMJVCLT
You should get a response like this:
smpeCC:00 smpeRoutine:GIMJVCLT smpeMsgLen:0000000005 smpeMsg:36.79
What response do you get?
If you get the expected response, you can reply with the "terminate"
command to stop SMP/E's Java program.
Kurt Quackenbush -- IBM, SMP/E Development
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
