FILE RESIZING

I am working at a developer site using AREV2.12 to produce mainly standalone PC Runtime versions. Often on runtime sites a GFE is caused after records in a Table are deleted. Arev does not compress the empty frames automatically, which I am told leads to GFE?s, when the table is reused. Is there a way of combating this? We can live with this for now but we are moving to OI. Will this still be a problem or does OI do an automatic Table resize when records are deleted? I note the FIX_LH routine is provided but we do not wish to have to get 'PC Illiterate' users to run this every time they delete records. The file resize may of course not be the cause of the GFE?s but it would be nice to eliminate it from the list of suspects if we can. What is it that kicks file resizing into action on a standalone system? Sizelock is set to 0 originally. Does record deletion change this setting?

Maybe someone else may jump in, but deleting items from a Table does not cause GFEs. For sure, it is not a normal behavior. If it were we would all be in trouble .

If it's happening in your environment, are you sure that you don't have a GFE somewhere in your table. You might try looking for it. For example, do a Select on the file may help identify the bad frame within your Table,

Select "Your Filename" Average Size id-supp det-supp

When it hits a GFE, look at the message for the frame number with the GFE and fix it.

HTH, someone else may have other suggestions, but again deleting in itself should not cause GFEs.

Ray

rayc@symmetryinfo.com onmouseover=window.status=imagine … ;return(true)"

Symmetry Info

Ray Chan ~ Symmetry Info

Thanks Ray. I am sure you are right. After all if you presize a file prior to creating records then you would always get GFE's which is obviously untrue. However, I want to prove this to my client by getting the file size down quickly so that the real cause of the GFE's becomes apparent. I still don't know what event kicks a file resize into action. I suppose these files have just grown with time, creating overlays. When records are cleared out perhaps the contraction of the overlay is when the system is vulnerable to an external spike or similar, which may be when it happens.

[notag]We would be more tempted to suggest that this is a WINx problem with the workstation not properly configured to disable write behind caching [<i>et al</i>].

[<A HREF="http://www.sprezzatura.com" onMouseOver="window.status='Click here to visit our web site?';return(true)">The Sprezzatura Group</A>]

[<I>World Leaders in all things RevSoft</I>]

[<img src="http://www.sprezzatura.com/zz.gif">]

[<script language="javascript">function openNewPage () {window.location.href=(document.TOCNavigator.pageToGoTo.options[document.TOCNavigator.pageToGoTo.selectedIndex].value);document.TOCNavigator.pageToGoTo.selectedIndex="0";}end hiding from non-JS browsers –></script>] [<FORM ACTION "" METHOD=GET NAME="TOCNavigator" <SELECT NAME="pageToGoTo" SIZE=1 onChange="openNewPage()"> <OPTION>Pull down this menu to choose whereabouts on the Sprezz site to go <OPTION VALUE="http://www.sprezzatura.com">Home Page <OPTION VALUE="http://www.sprezzatura.com/whatsNew.htm">What's New (Thanks Mr Clark) <OPTION VALUE="http://www.sprezzatura.com/senl.htm">SENL <OPTION VALUE="http://www.sprezzatura.com/patches.htm">Download S/LIST <OPTION VALUE="mailto:support@sprezzatura.com">Send mail to support at Sprezzatura <OPTION VALUE="mailto:sales@sprezzatura.com">Send mail to sales at Sprezzatura </SELECT> </FORM>] [/notag] </QUOTE> —- === At 24 JUN 2001 04:09AM John Godfrey wrote: === <QUOTE>Thankyou Sprezz, that's another pint(s) I owe you! But back to my question on the basic principles of OI/Rev. All things being OK on the hardware side. What event kicks a file resize into action? For instance, on a network is the job done at indexing time, or after deletions. And why does it not always happen. When does this occur on standalone PC's? At the moment 'we' have to remotely log into customer sites and compress the tables for them. Can I deduce that resizing should always happen after a deletion and if it does not then there is something wrong with the hardware? Should one create and save a dummy record to get resizing to kick into action? Should file compression be part of a standard daily maintenence routine? I am intrigued, this information will be valuable in drawing up customer procedures. </QUOTE> —- === At 25 JUN 2001 08:37AM The Sprezzatura Group wrote: === <QUOTE>[notag]Well to quote R29 (a RevSoft bulletin available in our KnowledgeBase download <g>) [<i>Threshold, a measure of the primary space used, can also be specified to optimize file performance. Threshold can be set during file creation, or any time thereafter. Threshold is the percentage of primary space that must be filled to trigger file expansion. File contraction occurs when primary space utilization falls 10 percent below the threshold level.</i>] [<A HREF="http://www.sprezzatura.com" onMouseOver="window.status='Click here to visit our web site?';return(true)">The Sprezzatura Group</A>] [<I>World Leaders in all things RevSoft</I>] [<img src="http://www.sprezzatura.com/zz.gif">] [<script language="javascript">function openNewPage () {window.location.href=(document.TOCNavigator.pageToGoTo.options[document.TOCNavigator.pageToGoTo.selectedIndex].value);document.TOCNavigator.pageToGoTo.selectedIndex="0";}end hiding from non-JS browsers –></script>]

[<FORM ACTION "" METHOD=GET NAME="TOCNavigator"

<SELECT NAME="pageToGoTo" SIZE=1 onChange="openNewPage()">

<OPTION>Pull down this menu to choose whereabouts on the Sprezz site to go

<OPTION VALUE="http://www.sprezzatura.com">Home Page

<OPTION VALUE="http://www.sprezzatura.com/whatsnew.htm">What's New

<OPTION VALUE="http://www.sprezzatura.com/senl.htm">SENL

<OPTION VALUE="http://www.sprezzatura.com/patches.htm">Download S/LIST

<OPTION VALUE="mailto:support@sprezzatura.com">Send mail to support at Sprezzatura

<OPTION VALUE="mailto:sales@sprezzatura.com">Send mail to sales at Sprezzatura

</SELECT>

</FORM>] [/notag]

[notag]Additionally….

Resizing might not work exactly as you are expecting. The system mostly expands and contracts by a single group, very rarely will it ever do two groups. It never does any more than that.

The reason for this limitation is that the resizing happens on each file access, which happens on the workstation. NLM and NT Service excluded, of course, as this was all written in 1986 or so.

Unused overflow frames will sit around until used again without doing a compress. However, the system does have track of them and uses them first.

[<A HREF="http://www.sprezzatura.com" onMouseOver="window.status='Click here to visit our web site?';return(true)">The Sprezzatura Group</A>]

[<I>World Leaders in all things RevSoft</I>]

[<img src="http://www.sprezzatura.com/zz.gif">]

[<script language="javascript">function openNewPage () {window.location.href=(document.TOCNavigator.pageToGoTo.options[document.TOCNavigator.pageToGoTo.selectedIndex].value);document.TOCNavigator.pageToGoTo.selectedIndex="0"}end hiding from non-JS browsers –></script>] [<FORM ACTION "" METHOD=GET NAME="TOCNavigator" <SELECT NAME="pageToGoTo" SIZE=1 onChange="openNewPage()"> <OPTION>Pull down this menu to choose whereabouts on the Sprezz site to go <OPTION VALUE="http://www.sprezzatura.com">Home Page <OPTION VALUE="http://www.sprezzatura.com/whatsnew.htm">What's New <OPTION VALUE="http://www.sprezzatura.com/senl.htm">SENL <OPTION VALUE="http://www.sprezzatura.com/patches.htm">Download S/LIST <OPTION VALUE="mailto:support@sprezzatura.com">Send mail to support at Sprezzatura <OPTION VALUE="mailto:sales@sprezzatura.com">Send mail to sales at Sprezzatura </SELECT> </FORM>][/notag] </QUOTE> —- === At 25 JUN 2001 10:41AM John Godfrey wrote: === <QUOTE>Thankyou all very much. I am now in a position to set up some R & D to prove resizing does not cause GFE's. As we all know, just saying that it doesn't is not good enough. </QUOTE> —- === At 27 JUN 2001 07:57AM Dave Harmacek wrote: === <QUOTE>Resizing only changes the primary space (.LK) file size, not the overflow area (.OV) (like Sprezz said). You may want to consider a redesign where a transaction file can be loaded with data, then copied to their final destination. Then, do a CLEARFILE. a clearfile (cleartable command) essentially rewrites the DOS files, both .LK and .OV, clears any GFE's and reduces the size to the minimum. I wouldn't tinker with Threshhold settings. </QUOTE> —- === At 28 JUN 2001 04:02AM John Godfrey wrote: === <QUOTE>Thankyou. It does appear that we have been very cavalier with our PC settings, and we need to draw up some hard and fast setup rules for our outstationed clients. </QUOTE> View this thread on the Works forum...