(GRX) Too many Free chain Builds

[Chris Sellitto]

Chris Sellitto wrote:
> To all,
> 
> My question is in regard to Free chains, and what the acceptable daily occurrence should be?  We have a Windows 200x server with approximately 80 Windows workstations running filePro 5.0.13 (we just downloaded the 5.0.14 upgrade which has yet to be installed).  I would say that the last several months, one of our files (which averages several thousand a day), generates a Free chain message (2-3 on average).  Currently this file has over a million records in it, but we do archive it on a monthly basis (to about 250 thousand records).  My question is, what could cause this many Free chains to occur in one day, and is there action we could take to alleviate, or eliminate it?  
> 
> Also could running dexpand to add several thousand records help?
> 
> Any suggestions would be greatly appreciated.
> 
Chris,

> I have struggled with this on occasion and have a few suggestions.  You 
> do not mention the OS so this is general.

> 1)  Make sure caching is off - I think, if memory serves, that is 
> important on some Windows based networks.

> 2)  Make sure any routine that adds or deletes records from a file is 
> very clear about not allowing break during the writing of the record. 
> Turn off the break key from the point of opening and locking the record 
> - until the delete if done and written.

> ADD MODE
> Adds are more problem.  Turn off the break key when writing the data at 
> the end of a record and do not turn it on until you reach the first 
> field on the new blank record.  That way if they hit the break during 
> the creation of a new record, it will not cause any damage and then they 
> can break once all logic and processing is complete and data entry is 
> returned to the user.

> 3) Make sure all hardware and networking is working properly.

> 4) Make sure the users do not exit incorrectly.  I have a great story 
> about this.  On a Unix system, we had a file that worked flawlessly for 
> many years.  Never a freechain issue ever.  Nothing changed to our 
> knowledge but all of a sudden we were getting freechain rebuilds twice a 
> day or more.  I looked at everything.  Finally we discovered the fault 
> and it was how a user was ending her session.  When she was done adding 
> records, instead of BREAK BREAK , exiting the menus until she logged 
> off, she was doing the following:  CTRL \ - to end the clerk sessions. 
> One of the managers had told her how to do this to get out of a 
> situation and she continued to use it whenever she wanted.  Well, at the 
> time it was difficult to stop this but current versions of filePro have 
> the PFQUIT=OFF, which will disable this keystroke.

> On windows you get a similar result from CLICKING the X in the upper 
> right hand corner.

> Make sure that all the training has been done to try to eliminate this 
> behavior.

> 5) Windows blue screens - make sure you have the users let you know if 
> crashes happen and with what frequencies.

> 6) Make sure all logic in filePro that writes to a record has locked the 
> record properly.

> Nancy

Nancy,

More great advice.  Especially suggestions number 3, and 4.  We here, have long suspected that
users are not exiting properly (we are on a Windows platform).  Despite all training to them, it
is still an issue (plus there is a frequent turnover rate, and new people are not being educated).
Also, we are going to be looking into our hardware/network integrity as well.  I will keep you all
posted once we find a solution.

Many Thanks again to all who took the time to answer my questions.

Christopher Sellitto
VP Computer Operations
Guaranteed Returns