I've seen similar erratic behavior when a phantom process set locks for a possible update, but then didn't clear the lock when no update occurred. I'm suggesting you have a locking issue but the out of memory behavior is identical - it waits for available memory before it can perform the next read. In our case the lock table was consuming the memory - with yours something else is consuming and not releasing the memory. HTH -Baker
<quote who="Kevin King"> > I am supporting a phantom program that uses PRINTs to output > information to _PH_ for a log. When this log starts getting near 3MB, > the phantom begins performing very strange. For example, sometimes a > READ in the phantom will be successful, but the variable that was read > is null (even though the record itself is intact). It seems like a > memory issue as restarting the phantom (and getting a new log) seems > to clear everything up. > > Does anyone have any experience to support or discredit this theory? > > -Kevin ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
