× 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.



We are doing data conversion of large amount of data and we are seeing very
interesting behavior if we are using long names when we do the writes.

All the tables are defined using DDL using both long names and short. If we
write to the tables using long names we see CPU shot straight up and
running iDoctor reveals that each write seems to be making function calls
to an internal system API that translates the long name to the short.

It would make sense to me that it would do this once but for every records?

To wirte 50,000 records using long names takes 8 seconds and 2 seconds
using short names. We have a very big machine.

Turn on Job Watcher and looked at CPU consumption. Huge spike straight up,
straight across and down for long names. Doesn’t even register for short
names.


Anybody else run into this?

We are V7R2.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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

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.