Gary wrote:

> We have an HP3000 989/450.  We have what we consider a very serious problem
>  with it.  Evidently, the system is so fast and powerful that it is possible
>  to fill up certain system tables before it can post it all to disk.  When
>  this happens the system aborts.  HP has stated that they will not fix this
>  problem (and we are on CSS support) because evidently, they are reworking
>  the system tables in MPEiX 6.5 so they do not see a need to fix this
>  issue.

And Wirt writ:

>Ken Sletten found a very similar problem recently while he was integrating
>his new, massively resized databases with gigabytes of data that had long
>been archived. The details, as I understand them, are that he crashed his
>machine (a 959, I believe) by doing too many DBPUTs in a row, while doing
>nothing else. In that process, a table overflowed and the machine crashed,
>a condition that sounds very much the one Gary describes.

And I'll follow up my original post with:

The original question was about 989 class of machines and problems. But,
since we're going deeper ...

Backup+ also tends to run into these system limitations. (Should I put a
<plug> alert here? :-) These aren't hardware specific, but it is quite
true that the faster hardware will allow them to manifest much quicker.

Over the years, we've seen the ability to overrun the memory manager,
expose a problem with the ROC table scanning algorithm, exposed a
problem with MM posting data in a mapped file above the EOF, and the
most recent - filling up the pquad table when using a DLT8000 ... I
can go on. In all instances, HP has worked with us to resolve these
issues. In some cases, they've fixed problems in MPE. In others, it
was up to us to adapt because we were the only ones running into the
problem and is at times based on how "low" we access the OS.

They use as one of their criteria how many people/sites have reported
a problem. So, if you see these problems, report them. That will help
CSY adjust their priorities accordingly. And, it is worth discussing
them here (without pointing fingers!!!) such that everyone get have
a better idea of what's going on and how prevalent a problem may be.

Regards,


M. "shall I duck?"