RE: Web service wizard fails to bring up a service -- this time withexceptions

Thought?

classpath not set or JT400.jar not in the classpath, or, more likely,
old version of JT400.jar on the classpath. Note that JTOPEN.jar can be
substituted (perhaps SHOULD be substituted for JT400.jar.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James H. H.
Lampert
Sent: Wednesday, September 22, 2010 4:12 PM
To: Midrange Systems Technical Discussion
Subject: Re: Web service wizard fails to bring up a service -- this time
withexceptions

James H. H. Lampert wrote:

I'll know more after lunch.

I've been told by my contact in Rochester that the warning messages that
Mr. Helgren pointed out are probably not relevant.



I've just successfully externalized and called a functionally identical
program on our V6 box, accessing structurally identical files, to the
situation on the customer box, and everything worked perfectly.

The only difference is that I've been using the "Deploy new service"
wizard (accessed through the "Deploy" button on "Manage Deployed
Services"), rather than the "Create Web Services Server" wizard.

It seems to me that the most interesting bit out of that whole
peroration that was in the customer box's log was:

/www/WSERVICE/webservices/temp/WTWSQTHDRR_1285175825985/services/WTWSQTH
DRR/iseries/programcall/base/RuntimeContext.java:217:

cannot find symbol symbol : method setCCSID(int) location: class
com.ibm.as400.access.AS400ConnectionPool
toolboxConnectionPool_.setCCSID(connPoolCCSID_); ^ 1 error

Any thoughts on what could cause something that works beautifully here
to refuse to even externalize out in the real world?

--
James H. H. Lampert
Touchtone Corporation