×
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.
Hi Rob
I think the idea is to have an index of the same name as the original
PF, with the same format level ID - that index is going to be created
over a rename of the original PF.
Then there is no need to recreate any programs using that file "name".
We saw a similar technique when looking at using Unicode in our tables.
And you'd need to convince any CMS not to check this dependency, right?
I think I have it right - others doing modernization can leap into the
circle and comment further, please!
Vern
On 8/1/2019 6:02 AM, Rob Berendt wrote:
<snip>
and the physical file is not keyed). If the physical file is keyed, I'd suggest to create an additional index with this key and replace the keyed native I/O access onto the physical file with a (native) I/O access on the new index.
</snip>
I don't understand.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.