Domino 7.0.3 - Compact command queued

It seems Domino has been playing a joke on me, and has been queueing my
requests to compact mail databases instead of actually compacting them.

I found a notes.ini variable that I can set to make future compacts
happen immediately, but what about the queued ones? Updall is supposed
to take care of these, but it doesn't seem to.

Does anyone know where this queue is located, how I can view what
activities are in it, and how I can force updall to execute the commands
on my mark?

Matt Fries wrote:
> It seems Domino has been playing a joke on me, and has been queueing my
> requests to compact mail databases instead of actually compacting them.

If you do a "load compact " at the console there is
nothing queued.
How did YOU request your requests?

>
> I found a notes.ini variable that I can set to make future compacts
> happen immediately, but what about the queued ones? Updall is supposed
> to take care of these, but it doesn't seem to.
which ini variable?

updall and compact are two completely different tasks

>
> Does anyone know where this queue is located, how I can view what
> activities are in it, and how I can force updall to execute the commands
> on my mark?

Peter Howard wrote:
> Matt Fries wrote:
>> It seems Domino has been playing a joke on me, and has been queueing
>> my requests to compact mail databases instead of actually compacting
>> them.
>
> If you do a "load compact " at the console there is
> nothing queued.
> How did YOU request your requests?

In Domino Administrator, in the Files tab, I right-clicked on a mail
database, and chose Compact.

>>
>> I found a notes.ini variable that I can set to make future compacts
>> happen immediately, but what about the queued ones? Updall is supposed
>> to take care of these, but it doesn't seem to.
> which ini variable?

Debug_Compact_Immediately=1

I added that line, and even rebooted the whole OS, but it still queues
the darn Compact requests.

> updall and compact are two completely different tasks

Yes, I agree. When I noticed that my attempts at compacting were being
queued, I did a little research and found out that apparently this is a
feature. I think it is so user's can request a compact of their
database, and the compact runs at night when they aren't using the mail
database. The trouble is, updall is supposed to be the process that
starts these compacts, but I could never find out how. It didn't seem
like it did to me.

Strange thing is, that I swear I have been compacting databases using
the gui since April. Only recently did this start happening, and I'm not
sure why.


>> Does anyone know where this queue is located, how I can view what
>> activities are in it, and how I can force updall to execute the
>> commands on my mark?

Thanks for the tip about typing the command at the console. It does seem
to work immediately when I type the command. I would still like to have
the ability to compact immediately via the gui (for other
administrators) and I am curious as to where these commands are queued.