Re: Multiple jobs running out of single JOBQ are very slow

*BASE does not necessarily mean QBASE.
QBASE is a subsystem. *BASE is a memory pool.
Changing your subsystem from *BASE to another memory pool involves
- Creating the secondary pool in WRKSHRPOOL.
- Adding it to your subsystem with
CHGSBSD SBSD(DUH) POOLS((1 *BASE ...) (2 *SHRPOOL3 ...))
- Tell tasks to run in the other pool with CHGRTGE SBSD(...) SEQNBR(...)
POOLID(2)
(See DSPSBSD option 7)
I have some systems that have zero batch jobs running. They have a
maximum of one or two 5250 sessions going, and that is rare. No ERP,
accounting, or other "traditional" applications. These are Domino
servers. I run these with QBASE and not QCTL. QCTL makes no sense in
that application. Granted, Domino runs a separate subsystem for each
domino server running and that may warrant memory pools. Still doesn't
justify QCTL in the least though.

But first, what are the tasks doing? Are they constantly looping like:
LOOPTAG:
CHKOBJ OBJ(MYLIB/TEMPFILE) OBJTYPE(*FILE)
MONMSG MSGID(CPF9801) EXEC(GOTO CMDLBL(LOOPTAG))
/* Now do real work */
If so, you need to find a more event driven method. Like a trigger, data
queue, etc.


Rob Berendt