Re: SQL stored procedure takes longer to run in batch than interactively.

I will pass this on to the decision makers.  Thank you for the info.

On 5/15/2025 13:53, Rob Berendt wrote:

That's like obscenely low. I can only guess that someone confused Max
Active and thought it meant maximum number of jobs in the subsystem and not
the maximum number of threads.

Defined Max Allocated Pool -Paging Option--
Pool Size (M) Active Size (M) ID Defined Current
*MACHINE 18676.89 +++++ 18676.89 1 *FIXED *FIXED
*BASE 59159.04 9106 59159.04 2 *CALC *CALC
*INTERACT 94850.05 5216 94850.05 3 *CALC *CALC
*SPOOL 2464.95 104 2464.95 5 *FIXED *FIXED
*SHRPOOL1 71345.05 558 71345.05 4 *CALC *CALC

DSPSBSD SBSD(QBATCH)
1. Operational attributes
Maximum jobs in subsystem
is much lower than the Max Active from above.


On Thu, May 15, 2025 at 1:33 PM Bobby Adams <bobby_adams@xxxxxxx> wrote:

Yes. Ours is below. I do not know how or why the values were set, but
if you have questions I will ask.

+++++ *MACHINE
1118 *BASE
10 2 QBATCH QSYS
10 *SHRPOOL10
10 2 QCMN QSYS
3 2 QPGMR QSYS
15 *SPOOL
2272 *INTERACT

On 5/15/2025 13:15, Glenn Gundermann wrote:

I'm confused. You have Max Active set to 10?

Our values look like this:

+++++ *MACHINE
2400 *BASE
5600 *INTERACT
15 *SPOOL

Yours truly,

Glenn Gundermann
Email: glenn.gundermann@xxxxxxxxx
Cell: (416) 317-3144

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.