1)  Good point on the math.

2)  I was hoping that outputting to a user space would be less overhead
than a DB file - but you may be right, probably not that significant.

Rob Berendt
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin

                    "Walden H.
                    Leverich"                 To:     
"'midrange-l@midrange.com'" <midrange-l@midrange.com>
                    <WaldenL@TechSoftIn       cc:
                    c.com>                    Fax to:
                    Sent by:                  Subject:     RE: Listing of 
objects and their owners

                    01/15/2002 11:40 AM
                    Please respond to

>From: rob@dekko.com [mailto:rob@dekko.com]
>1)  Gag and choke because we have over 400,000 objects in the outfile
created by DSPOBJD.

Given a max size of a user space is 16M and 16M/400K = 40bytes which is
less than the number needed for each object I'd guess, but it's just a
guess, that it would choke and die.

> 2)  Significantly perform better...

Why would you expect your application that uses an API that calls a MI
program to perform better than IBM's application that uses that same MI
program? Or to be more exact, QLILIST takes a long time, you can't avoid


Walden H Leverich III
Tech Software
(516)627-3800 x11

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.