Re: Variable Length fields -- MIDRANGE-L

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

Simon,

At 09:31 AM 4/9/00 +1000, you wrote:

The system uses about 25 bytes per overflow to track the variable pieces. There is a
flag associated with the fixed length part and each overflow part indicating whether
overflow has occurred and the linkage data is stored with the overflowed part.

Is there a limit to the number of times a variable length field can overflow?

If many records are fragmented then a reorg is required to fix the fragmentation which will also improve performance.

Would that be a standard RGZPFM or is there a special command / parm to do that?

-mark

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.