The JSMAIN process is responsible for handling the job/session logons.
JSMAIN handles the logon process and once the logon is successful creates
the job/session's CI.  The JSMAIN should then go into, I would think, a SON
wait until logoff.  I'm not aware of a reason that JSMAIN would be a heavy
CPU consumer unless you have a lot of logons or logoffs or you have a
streaming session device that keeps generating interrupts that cause the
JSMAIN to activate.  You can enter - SHOWPROC PIN=1;TREE;SYSTEM to identify
the session or job associated with that particular pin.

Steve

=================================
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: Holloway, Rich <[log in to unmask]>
To: <[log in to unmask]>
Sent: Thursday, January 13, 2000 1:52 PM
Subject: Pin 144 - JSMAIN


> Can somebody tell me what pin 144 with Cmd/Program JSMAIN is doing? I have
> been monitoring our production machine and when there is heavy CPU usage
and
> large queue length this process is quite busy. We have a 997/800 running
5.5
> PP 7.
>
> TIA,
>
> Rich Holloway
> Systems Administrator
> Providence Health Plans
> Phone: (503) 574-7457
> Fax: (503) 574-8614
> [log in to unmask]
> http://www.providence.org
>
> The opinions expressed are not necessarily those of my company. They
belong
> solely to me.
>
> If everything seems under control, you're just not going fast enough. --
> Mario Andretti