HP3000-L Archives

July 1996, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Stan Sieler <[log in to unmask]>
Reply To:
Stan Sieler <[log in to unmask]>
Date:
Wed, 3 Jul 1996 11:03:00 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (71 lines)
Mohan writes:
> JSMAIN's in the pool is always
>       min (job/session pool size, job/session limit - job/session count).
>
> That is, if pool size is 10, job limit is 10 and number of jobs
> running is 8, then there will be only 2 spare JSMAIN's in the pool and
> not 10.
 
Sounds like someone fixed it.  I looked at several dumps a year or two
ago (4.0?) and saw a bunch of unused JSMAINs on a couple of users machines
(100 in one case).
 
> $114 ($25) nmdebug > pm_ptree 27
>
> $27 (JOB.PUB.SYS)
>   $29 (JSMAIN.PUB.SYS)                  <-------- 10 spare JSMAIN's
>   $2a (JSMAIN.PUB.SYS)
...
> $115 ($25) nmdebug > e
> :limit 3                                <-------- Set Job Limit to 3
> :debug
>
> $116 ($25) nmdebug > pm_ptree 27
>
> $27 (JOB.PUB.SYS)
>   $22 (JSMAIN.PUB.SYS)                  <-------- 3 spare JSMAIN's
 
 
Hmm...I don't know what the JOBLIMIT was set at at those sites...maybe
it was rather high.
 
 
BTW, the equation you showed doesn't seem to take into account that you
can have more jobs running than the configured job limit.
 
You can have as many jobs & sessions running, TOTAL, as the sum of the
configured job limit + session limit.  Here's an example where the
sysgen job limit is 60, and the session limit is 60, yet I have 73
jobs running.
 
:showjob
...
#J75    EXEC        10S LP       WED 10:06A  PAUSE,MANAGER.SYS
#J76    EXEC        10S LP       WED 10:06A  PAUSE,MANAGER.SYS
 
73 JOBS (DISPLAYED):
    0 INTRO
    0 WAIT; INCL 0 DEFERRED
   73 EXEC; INCL 0 SESSIONS
    0 SUSP
JOBFENCE= 5; JLIMIT= 60; SLIMIT= 60
 
:limit 70,10
Maximum limits are 60 for JOBS and 60 for SESSIONS. (CIERR 3818)
 
 
 
> But I agree with you. Any value greater than 2 may not be required,
> since the chances of more than 2 jobs or sessions logging on at the
> "same time" are minimal, but then if at some site you expect a sudden
> burst of logons and you need a good response time for all these logons
> and you don't mind a few processes sitting idle during low activity
> period, then having a higher value for pool size may be advisable.
 
thanks, Mohan!
 
 
--
Stan Sieler                                          [log in to unmask]
                                     http://www.allegro.com/sieler.html

ATOM RSS1 RSS2