[WDSCI-L] resolving filters versus opening members

[Kelly Cookson <KCookson@xxxxxxxxxxxx>]

Periodically our development environment (a partition on an iSeries) gets
hit pretty hard, causing delays even in Access for Windows green screens.
When this happens I seem to get long delays and error messages saying the
server has stopped responding in WDSCi.

Is this a real correlation, or just coincidence? That is, would an iSeries
system getting hit hard for processing resurces cause WDSCi to more
frequently return server stopped responding errors?  I would like to whether
this is something related to my having a lower-end PC or something related
to how WDSCi interacts with a busy iSeries regardless of PC capability.

Thanks,
Kelly