RE: system-wide JVM (threads) Was: Friendly co-existance

> From: Fred Kulack
> 
> Or is this not really an option in your case because you really have
the
> need for multiple JOBs to
> do the main work?

I want an application server to start up.  This also fires up the JVM.
This JVM is then "registered" with the OS as a "named" JVM.

>From that point on, I can start an interactive job or a batch job and
"attach" to this named JVM, thereby accessing its objects.  This would
allow, for example, green screen access to session state information in
a servlet.  I could in fact have an RPG program that controlled my
servlet.

I could submit jobs to batch and identify the JVM.  This job could
create reports, convert them to spooled files, and then stick the IFS
file names back into the appropriate session object, without having to
create and manage data queues.

There are a number of capabilities I can think of where the ability to
have a job directly communicate with a running JVM would be beneficial.
Joe