My understand of the JSMAIN is that when a job or session is initiated that
a JSMAIN process is created in the B-queue by either the JOB or SESSION
process to handle the logon. Once the logon is successful, JSMAIN creates
the CI as its SON process and then goes into a WAIT state until the job or
session logs off and then it dies and cleans up. So seeing a JSMAIN in the
B-queue would be normal and other than an additional process on the system
should cause no overhead.
Now on to memory. It is rare to find an HP3000 that can't benefit from
additional memory. However, we have observed systems that the memory
loading issues were caused by job mix. In these cases additional memory
often doesn't correct the problem even it the HP3000 benefits from the
memory increase. If the additional memory doesn't address the problem you
may want to look at HP's Workload Manager product. We have observed a
number of sites, especially on mid-size to large HP3000s, where Workload
Manager has made a significant improvement in the performance of the system.
=================================
Steve Cole
Outer Banks Solutions, Inc.
[log in to unmask]
www.outerbankssolutions.com
Phone: 919.231.2171 Fax: 919.231.7077
Sales: 800.558.5336
=================================
----- Original Message -----
From: Rick Clark <[log in to unmask]>
To: <[log in to unmask]>
Sent: Thursday, October 28, 1999 4:32 PM
Subject: Re: JSMAIN.PUB.SYS
> David,
>
> I understand that this is not much info, and I guess I am feeling more
> like L.A.Barnes' little guy banging my head against the computer
> today...... It has been one of those dazes!
>
> After further research, it turns out that a few more lines of code were
> added to a huge COBOL program that when installed, the system takes a
> nose dive. When removed, the system operates normal. We are thinking
> that this additional code, when multiplied by 500+ users stored in
> memory, caused the HP3000 performace bottlenecks. It is my understanding
> that the 3000 systems, once it reaches a certain 'boiling' point, will
> drop in performance. Not a gradual curve, but a drop.
>
> Bottom line is, we are buying more memory. This I hope will resolve our
> problem.
> I'm not convinced this is the problem, but it doesn't hurt. What I am
> questioing now is that the Configuration guide (1995) shows the 959ks
> has a max of 2048 memory. We were told that it is capable of 8gb and
> that MPE/iX has a limit of 3.75gb. Is this true? What is the true max
> amount of memory I can install in the system?
>
> Thanks again in advance.
>
> Rick Clark
> Senior Systems Analyst
> WW&R
> Cleveland, Ohio
>
>
> David Gale wrote:
> >
> > Rick,
> >
> > unfortunately system performance has many more variables and I am afraid
the
> > information you have provided doesn't provide an imediate answer. JSMAIN
> > does not appear to be a resource hog at his point.
> >
> > I will say that in the past when a sudden change of performance was
noticed,
> > and there didn't seem to be a change in anything else, the first thing I
> > looked at was disc space. Make sure you are not using more than 85% on
your
> > volume sets.
> >
> > To really get a good look at performance issues, you need a good tool.
<plug
> > alert> I favor the Lund Performance Tools myself <end-plug>. You really
need
> > something that not only tells you the current pulse points of your
system
> > but allows you to capture trending information.
> >
> > There could be any number of problems therefore I cannot with honesty
give a
> > better opinion of your problem.
> >
> > Good Luck!
> >
> > Dave Gale
> >
> > > -----Original Message-----
> > > From: Rick Clark [mailto:[log in to unmask]]
> > > Sent: Thursday, October 28, 1999 10:26 AM
> > > To: [log in to unmask]
> > > Subject: JSMAIN.PUB.SYS
> > >
> > >
> > > What is this program? We are running extremely slow the past few days
> > > and nothing has changed that could have caused this (at least that is
> > > what they are claiming). I am looking at the SHOWQ;ACTIVE and noticing
> > > in the B queue one PIN consistently. This turns out to be
> > > JSMAIN.PUB.SYS
> > >
> > >
> > > Q PIN JOBNUM Q PIN JOBNUM
> > >
> > > B 856
> > > C M2652 #S1449
> > > C U1263 #S1642
> > > C U1108 #S1531
> > > C U1452 #S1599
> > > C U2146 #S1442
> > > C U2709 #S837
> > > C U2747 #S1626
> > > C U2883 #S1459
> > > D U186 #J1221
> > > D U2547 #J1116
> > >
> > >
> > > ------QUANTUM-------
> > > QUEUE BASE LIMIT MIN MAX ACTUAL BOOST TIMESLICE
> > > ----- ---- ----- --- --- ------ ----- ---------
> > > CQ 152 200 1 2000 68 DECAY 200
> > > DQ 202 238 2000 2000 2000 DECAY 200
> > > EQ 240 253 2000 2000 2000 DECAY 200
> > >
> > > PUB SYS:DO SHOWP
> > > PUB SYS:SHOWPROC ;PIN=856;SYSTEM
> > > QPRI CPUTIME STATE JOBNUM PIN (PROGRAM) STEP
> > >
> > > B100* 0:00.010 WAIT 856 (JSMAIN.PUB.SYS)
> > > PUB SYS:
> > >
> > > Thanks in advance....
> > >
> > >
> > > Rick Clark
> > > Senior Systems Analyst
> > > WW&R
> > > Cleveland, Ohio
> > >
|
