RE: Housekeeping

That lpar is all Domino. That lpar is running NO 'traditional' apps.
Domino
Server
ARCHIVE1
COMMUNITYSERVER
GDDATA
GDSHELP
GDSSALES
LDAP01
NOTES01
QUALITY

ARCHIVE1 has archives of all email that has been inactive for x days. We
tried to keep that on 'cheap' Windows and Linux hardware but the response
time was not good enough. Could have something to do with going from
dozens of disk arms to one.
CommunityServer is for our Sametime.
GDDATA is for many of our Domino based databases.
GDSHELP a different set of Domino based databases.
GDSSALES ...
LDAP01 is one of our Domino based ldap servers.
NOTES01 is our primary email server.
QUALITY is our main Domino based workflow server.
We could easily have ran them as one or two Domino servers. But it's
easier to break them apart. Thus they will run in different subsystems.
If http goes nuts for GDDATA, and I can't get the domino command TELL HTTP
QUIT to kill it, I can bounce just that Domino server without killing off
our primary email server.

Current
Subsystem/Job User Type CPU % Function
ARCHIVE1 QSYS SBS .0
ADMINP QNOTES BCI .0 PGM-ADMINP
AMGR QNOTES BCI .0 PGM-AMGR
AMGR QNOTES BCI .0 PGM-AMGR
CALCONN QNOTES BCI .0 PGM-CALCONN
CLDBDIR QNOTES BCI .0 PGM-CLDBDIR
CLREPL QNOTES BCI .0 PGM-CLREPL
COLSRV400 QNOTES BCI .0 PGM-COLSRV400
COMPACT QNOTES BCH .0 CMD-QDOMCLNCMP
...
All jobs in a Domino subsystem are tightly connected. If you try ENDJOB
on any one of them the server goes nuts and dies. Kills all jobs in that
subsystem. Do semaphores and threads mean a lot to you? However, it will
only affect the domino jobs in that subsystem.


Rob Berendt