Re: RUNJVA redux

[Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>]

I looked on my completely as delivered system (V7) that has no work 
management or other modifications to it, and cannot find a spot where 
there is a limit of four jobs.  Most of the job queue entries are 1 or 
*NOMAX, although I did not look at QSNADS or a couple of the other 
subsystems that were not running.

There very well have been a default of two like that in the days of old, 
but at least I now understand the reference.

Thanks.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 2/1/2013 9:54 AM, Thorbjørn Ravn Andersen wrote:
> I know that the i is very capable of doing a lot of work with a lot of jobs,
> so I may very well be wrong.
>
> I just happened to run into - a long while back when my beard was less grey
> - a situation where this was a bottleneck.
>
> Am I right when saying that the_default_  configuration of this job queue
> thing is four slots, and you need a system administrator to change it?
>
>
> -----Original Message-----
> From:java400-l-bounces@xxxxxxxxxxxx  [mailto:java400-l-bounces@xxxxxxxxxxxx]
> On Behalf Of Dan Kimmel
> Sent: 1. februar 2013 15:56
> To: Java Programming on and around the IBM i
> Subject: RE: RUNJVA redux
>
> Yeah, I'm confused by that, too. I run java either in QUSRWRK (QUSRNOMAX
> *JOBQ) or I build my own subsystem with *NOMAX as the number of jobs and
> *NOMAX as the number of jobs from the jobqueue. I build my own subsystem for
> servers like Tomcat as I've found a dedicated memory pool yields performance
> improvement. I can run any number of java jobs (with QSH, even) without
> tying up any scarce resources other than processors and memory.
>
> -----Original Message-----
> From:java400-l-bounces@xxxxxxxxxxxx  [mailto:java400-l-bounces@xxxxxxxxxxxx]
> On Behalf Of Jim Oberholtzer
> Sent: Friday, February 01, 2013 5:40 AM
> To: Java Programming on and around the IBM i
> Subject: Re: RUNJVA redux
>
> Job Slots?  Clearly we know the IBM i can run many hundreds of thousands of
> jobs, so I am curious about the term and how it applies?  Where is the
> limitation on jobs to default to four?
>
> Jim Oberholtzer
> Chief Technical Architect
> Agile Technology Architects
>
>
> On 2/1/2013 4:51 AM, Thorbjørn Ravn Andersen wrote:
> > >  There is one distinct advantage of using the RUNJVA command instead of
> > >  "java -cp ...".  The latter require QSH for interpretation which in
> > >  turn take up a job slot.  This is important on the i because the
> > >  default setup is (to my
> > >  understanding) only four such slots, hence taking up a valuable resource.
> > >
> > >
> > >
> > >
> > >     -----Original Message-----
> > >  From:java400-l-bounces@xxxxxxxxxxxx
> > >  [mailto:java400-l-bounces@xxxxxxxxxxxx]
> > >  On Behalf Of Kelly Beard
> > >  Sent: 31. januar 2013 20:28
> > >  To: java400-l
> > >  Subject: RUNJVA redux
> > >
> > >  Thorbjorn's solution appears to be the correct one.  If I specify
> > >  CLASS(Balancer) instead of CLASS(Balancer.jar), it works fine.  I'm
> > >  not really interested in use the RUNJVA command, but wanted to learn the
> "other"
> > >  way of running Java on the 400.
> > >
> > >  So, thanks to everyone for their contributions of notes about the
> > >  idiosyncrasies of RUNJVA.
> > >
> > >  --
> > >  Kelly Beard
> > >  --
> --