Multithreading: Batch vs. interactive.

I am under the assumption that running a multithreaded application in an
interactive job is forbidden. Trying to find something at IBM that simply
comes out and says that.

Also under the impression that if you want a batch job to run a
multithreaded application you have to specify
SBMJOB ALWMLTTHD(*YES)
or an appropriately configured *JOBD.

The reason that I ask is that IBM is recommending that, after upgrading to
8.5 of Domino, you switch from running
RUNDOMCMD SERVER(...) CMD(CALL PGM(COMPACT) PARM(...))
to
RUNDOMCMD SERVER(...) CMD(CALL PGM(COMPACT) PARM(...)) BATCH(*YES)
ALWMLTTHD(*YES)

They do not allow you to control which job queue or whatever to use on
RUNDOMCMD. You eventually figure out that they use the job queue
associated with the job description QDFTJOBD. Well, running everything in
a single string QBATCH when you have 11 domino partitions and your erp and
what not is vicious. You can run multiple COMPACTs and the same time
(just not on the same server). You cannot run COMPACT and FIXUP and
UPDALL at the same time for one particular server. So I want each domino
server to run with more control. All servers do a COMPACT at the same
time. When each server finishes their COMPACT run the FIXUP, when each
server finishes the FIXUP run the UPDALL. When that is done start the
server back up. One server may be done with this whole stream long before
another server is. I used to have this down pat before the BATCH(*YES)
ALWMLTTHD(*YES) requirement.

So based on some rudimentary work management concepts, I figure IBM has
RUNDOMCMD BATCH(*YES) ALWMLTTHD(*YES) set up to do a SBMJOB
ALWMLTTHD(*YES), defaulting to the QDFTJOBD job description. I am trying
to figure out that if I blow by IBM's 8.5 recommendation and continue to
run
RUNDOMCMD SERVER(...) CMD(CALL PGM(COMPACT) PARM(...))
but, from a job that has been started with SBMJOB ALWMLTTHD(*YES) if I
would be ok.

What does my esteemed colleagues think?

Rob Berendt