On Mon, 18 Feb 2008 14:59:29 -0600, Pommier, Rex R. wrote:
>
>Apparently JAVA is a prerequisite for using SMP/E receive fromnts
>according to the user's guide. The memo to user's extension and the
>internet delivery checklist seemed to indicate that the only reason for
>needing java was to do the hash checking and the receive would just keep
>going without this particular check. Guess I read it wrong (not the
>first time that's happened...).
>
Not in my experience. An example with no Java objects in the product:
PAGE 0001 - NOW SET TO GLOBAL ZONE DATE 02/18/08 TIME 15:33:36
SMP/E 34.14 SMPOUT OUTPUT
SET BOUNDARY(GLOBAL).
GIM20501I SET PROCESSING IS COMPLETE. THE HIGHEST RETURN CODE WAS 00.
RECEIVE LIST ... .
GIM69223I SMP/E COULD NOT INVOKE A JAVA PROGRAM BECAUSE THE JAVA RUNTIME
LOCATION (THE JAVA HOME DIRECTORY) IS NOT
DEFINED.
GIM23411I DATA INTEGRITY VERIFICATION WILL NOT BE PERFORMED ON PACKAGE
xxxxx.gimzip BECAUSE ICSF IS NOT AVAILABLE AND
AN ATTEMPT TO USE AN ALTERNATE SERVICE HAS FAILED.
...
GIM20501I RECEIVE PROCESSING IS COMPLETE. THE HIGHEST RETURN CODE WAS 00.
GIM20502I SMP/E PROCESSING IS COMPLETE. THE HIGHEST RETURN CODE WAS 00.
SMP/E IS AT LEVEL 34.14.
>As far as the SMPJHOME and SMPCPATH DD's, I have the DDDEF's set up, but
>I thought they would just be used for the hash calculation. SMPJHOME is
>pointing to where JAVA will be if I ever get it installed...
>
I might expect that Java would be needed to install jars into the target
library for APPLY, but not for RECEIVE.
However, I have found that if SMPJHOME is absent, things work as above.
If it's present but invalid, the RECEIVE fails.
>Download the non-SMP/E version of JAVA to start with.
>
>Pick up a current version of the SMP/E 3.4 user manual and read about
>internet service retrieval.
>
>Make sure you set up the CLIENT DD correctly or add SMPJHOME and
>SMPCPATH DDs to your JCL or DDDEFs.
>
I believe CLIENT and server are necessary only for FROMNETWORK,
not for FROMNTS.
All that said, SMP/E's reporting in this situation seems inadequate.
Perhaps there's a message in SYSPRINT that should be reported as a
utility failure in SMPOUT. (I recall other cases where errors
reported in SMPRPT cause RC=8 with no other indication in SMPOUT.)
And, from an ISV's point of view, all this is complex enough that I
wish there were a standard Validation Procedure to verify the
customer's ICSF and Java setup. Any suggestions?
Thanks,
gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
