Brian Donaldson wrote:

> I am not certain on what these limits are but you won't be able to process
> millions of entries inside a DBXBEGIN/DBXEND structure. Once the internal
> file gets full up an automatic DBXUNDO will take place and your Image
> procedure will return an error code (can't remember which error code).

The limit is hardcoded and used to be a maximum XM user transaction
size of 4 MB . It was increased to 32MB in release 6.5 and upper.
You may have to increase the XL userlogfile size on the volumeset
holding this database though in order to reach that size.
For more details see :

<http://docs.hp.com/mpeix/onlinedocs/30216-90291/00/00/43-con.html>

HTH,
Goetz

--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet?

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *