The main advantage is so two people can log on at the same time. If you only
have one JSMAIN one will have to be created for you before you can logon. If
you have a small pool then you don't have to wait for one to be created. But
having a pool of more than a few is not of much use since the OS will still
keep that many in the pool all the time. Its not like the VT servers where
you use the prebuilt servers first and the OS will not create a new one till
all of the pool has been exhausted. So for VTs you should have a few more
than you will ever need which cuts down on process create overhead. For
JSMAINS four or five on a very busy system will probably be enough to keep
anybody from having to wait for one to be created.

"Craig Lalley" <[log in to unmask]> wrote in message
news:Nq-dnR2mNdogZ1ajXTWcog@fidnet.com...
> With all the trash talking going on, I thought I would throw in a real
> question...
>
> In SYSGEN, MISC, SHOW.  See below.
>
>            JOB command       parameter      MAX       MIN     CURRENT
>       -----------------    ---------    -------   -------   -------
>       DEFAULT CPU LIMIT    cputime        32767         0         0
>       MAXIMUM LIMIT        maxlimit         999         0        60
>       POOL SIZE            pool             200         1         1
>
> The Pool controls the number of JSMAIN processes.   What is the advantage
of
> having two JSMAIN processes.
>
> They shouldn't have a parameter if they didn't want someone to twiddle
with it.
>
> -Craig
>
>
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Search - Faster. Easier. Bingo.
> http://search.yahoo.com
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
>

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *