Just went through a LOT of this, here's some thoughts:
Check the workstations WAIT setting. Used to be default 4 - some of the
newer installations seem to have 0 in the RBase.cfg file.
Are you doing any INSERT ..SELECT.. 's? This type of insert places a full
table lock and other stations will get the WAITING FOR RESOURCES message.\
Overall, look for anything that would cause concurrency issues and table
locks.
Also we are trying to replicate what we think is a bug that involves
corrupted indexes. It seems (untested at this point) that if a workstation
is trying to complete a command and has to wait for resources, if the
command fails to acquire the resources it may corrupt relative indexes. It
seems almost as if the index file gets updated BEFORE the actual
INSERT/UPDATE/DELETE, and if the command fails to complete (like when it
cannot get the required locks) and times out then the index is not being
"un-updated" and the data gets out of sync with the index file. If it's
true and we can replicate it, I'm sure the folks at RDCC will be on it like
hair on a gorilla. Then again, maybe it's something wrong on this end.
Hope it helps.
----- Original Message -----
From: "Manuel de Aguiar" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, June 14, 2001 10:20 AM
Subject: MESSAGE-- WAITING FOR RESOUCES....
> Hello Everyone,
>
> I have a customer that is suffering from what they call:
> THE RED BAR
>
> It is the RBase for DOS error message display at the bottom
>
> waiting for resourcess a 5% ..........
>
>
> Sometimes is better and sometimes is worse. Can anyone enumerate some of
> the conditions that will cause this message to occurr?
>
> TIA
> Manuel
>
