JSMAIN is the parent process of the CI and of several networking
servers.  It is the child process of SESSION.pub.sys for sessions
and of JOB.pub.sys for jobs.  There can be a pool of JSMAINs
for faster logons.

Its classic role is to detect <cr> at a terminal and issue the
prompt to logon.  It also deals with STARTSESS and VTSERVER
logons, and processes some of the CI commands related to jobs
(ABORTJOB, BREAKJOB, RESUMEJOB, etc.).  JSMAIN also builds
the CI's variable table, opens cataloged UDC files, and
orchestrates logoffs (local and remote).

I am not a performance person, but I thought JSMAIN demoted
itself to the CQ when it is the parent of the CI.  If this
is still true then the JSMAIN in question is not the parent
of a CI.  Do a SHOWPROC 856;tree;system to verify this.

Maybe this helps some,

Jeff Vance, CSY

> 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
...