×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
What kind of performance are you seeing with the added call to C to
generate the XML?
I am wondering if you are seeing the job run much longer versus the same
job without the XML generation. Our statistics:
With no XML: 0:58 elapsed 0:19 CPU
With XML, no write to QTEMP file: 1:51 elapsed 0:58 CPU
With XML and write to QTEMP file: 2:09 elapsed 1:14 CPU
These are very generic statistics from joblogs and not from performance
data analysis. The write to QTEMP did include the SEQONLY parm on the
OVRDBF to transfer records in groups (aka "blocking factor".)
Rick Beethe
Manager of Application Development
Computer Research, Inc.
10170 Church Ranch Way, Suite 300
Westminster, CO 80021
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.
midrange.com
