Stan wrote:

>This should work safeley *provided* that you also decrease the job limit by
the
>same amount.  MPE sizes the JMAT by the *sum* of the session limit and job
>limit.  (That's why a STREAM ; HIPRI job can startup even if you are at the
>max configured number of jobs.)  If you don't keep the sum the same, you
>run the risk of unexpected things happening (I haven't tried it, and don't
>plan to try it).


I did test this, and do to a limited JPCNT table, you can only gain the
difference between the job limit and the number of jobs executing. For
example on the system I tested, the configured maximums were 60 sessions and
60 jobs. Raising the job limit with DEBUG to 500 still only let me get a
total of 120 jobs and sessions running. As for what happens when that limit
is reached, I got a "Can't initiate new sessions now. (CIERR 80)" message at
the terminal, and a "UNABLE TO OBTAIN "JPCNT ENTRY" on the console, but no
other *strange* results.

Mike Hornsby
[log in to unmask]