Re: RPG, Java and Classpath practices -- RPG400-L

× 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.

Subject: Re: RPG, Java and Classpath practices
From: Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
Date: Thu, 12 Jun 2008 10:07:38 -0500
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the AS400 / iSeries <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

DeLong, Eric wrote:

That would only be used the first time Java was invoked for a job. Once the JVM has started, it will not look at classpath again, afaik...

A job can have one and only one JVM ever. Once you start the JVM, that's it for the job. Back in the old days you could shut down the JVM and start a new one, but not any more. So the practical result is that you get one CLASSPATH per job.

Joe

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 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.