Rob,

I believe the multi-threaded restriction applies to jobs with a display
file. Which is most interactive jobs, but not necessarily all of them.
Rumor was that product planners decided the display file code was too
twisted and not strategic enough to justify the expense of going through
all the twists to make it multi-threadable.

Dan Kimmel

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, September 03, 2009 9:22 AM
To: Midrange Systems Technical Discussion
Subject: 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
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

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




This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].