In doing research to help speed up my java code, I've come accross
something I don't understand. It involves Java and multi-threaded AS/400
In quite a few places throughout the IBM documentation, paragraphs like
the following can be found telling how a Java program is to be run in a
multi-threaded job:

To run this program, use SBMJOB CMD(CALL PGM(YOURLIB/PGMNAME))
ALWMLTTHD(*YES). Any job that creates a Java virtual machine must be
multithread-capable. The only job on iSeries 400 that is
multithread-capable is a batch immediate (BCI) job. 

This example comes from a V5R1 document.  However, when I emulate it on
our V5R1 system, I don't end up with a multi-threaded, BCI, job.
Instead, regardless of whether or not the ALWMLTTHD(*YES) parameter is
included, I end up with a BCH job and a second, system generated BCI job
that does the Java work.  It's as if the ALWMLTTHD(*YES) parameter is

Further adding to the confusion -- and of more importance in my world --
when I run an RPG program that accesses Java methods, I can't locate any
system generated multi-threaded (BCI) job that does the Java work.  I
end up with only a single BCH (single threaded) job that seems to be
running both the RPG and Java code. 
So my questions are as follows:

1.      Where is the BCI job that executes RPG initiated Java code?  If
the answer is that there is no BCI job, how can the JVM function in a
non multi-threaded job?  
2.      Can Java code (inside or outside of RPG) be made to run in a
multi-threaded job without the need for the system to generate a
separate job to do the work (as the above documentation snipit seems to
suggest)?  If so, would it help to speed things up?


  This email is covered by the disclaimer linked below.
          You are urged to read the disclaimer.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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

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