× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Concur Buck! Thanks for the clarification.

Almost all my Java-programs are background running jobs. Unless I missed one.

But, for testing, I have to sign-off, and sign back on...

Duh, I should have just submitted it off to batch to test! I guess I am just use to testing interactive on our test box. Just an Old habit... <My Bad>

Forgot about the wrkjvmjob, to view, if I stop in debug. Which I was doing on my interactive 5250 session.

But, by running in interactively, I could verify how the environment variables were set after I was done running it.

Still for some unknown reason, I could NOT even add a "SEP", and got that meaningless error:
"**ERROR decoding EStdString**". No information in the Error-Log in RDI 9.5.1.


PS. Long story short, another developer not me, put an old depreciated jar in the root path, which cause all my problems... <sigh> Live & Learn...

-Ken Killian-


-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Buck Calabro
Sent: Wednesday, November 16, 2016 10:59 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] RDI 9.5.a "**ERROR decoding EStdSgring**"

On 11/16/2016 7:17 AM, Ken Killian wrote:
I continually have to sign-off 5250 session, because apparently, once the Java-Virtual-Machine is started, you could change the class path, but it appear to have ZERO EFFECT. So, I always have to sign off and back on when doing my testing for the correct classpath.

Yes, this is how JVM works under IBM i.
Java reads the environment variables at startup and only at startup.
Java starts up exactly one time per job.

I almost never run Java in an interactive job - I always SBMJOB to get a new, clean, known JVM state.

Did the exact same thing this morning, and now it works...

My only guess was that a different job gave a different JVM giving a different... something.

--
--buck

Visit wiki.midrange.com and register for an account. Edit a page that helps you, and because it's public, you'll help someone else, too!

--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.