FS100 occurs during WRITE statement to dictionary. (AREV Specific)
At 29 DEC 2003 11:06:11AM Craig X Tildesley wrote:
This one is far too obscure for me to disect.
WRITE to dictionary with a symbolic field. The only way to make it succeed is to remove DICT.MFS from the filehandle. This particular dictionary is quite "loaded" with a 63k %fields% record but I have had it occur on dictionaries with perhaps 2 dozen items.
Can anyone plz tell me what it is looking for but can't find?
At 29 DEC 2003 11:48AM Warren wrote:
What are you trying to write to the Dict?
Could be that @RECORD, @DICT, @ID etc. are being overwritten or not set to the proper values…
What happens if you call a subroutine or function from the symbolic to do the update?
At 29 DEC 2003 11:59AM The Sprezzatura Group wrote:
Are you using a network product? This could help debugging….
The Sprezzatura Group
World Leaders in all things RevSoft
At 29 DEC 2003 01:27PM Richard Hunt wrote:
If I understand you correctly… you are saying the size of the "%FIELDS%" row is 63k? If so, then I believe that is not normal!
I have dictionaries with 100 items, and the size of the "%FIELDS%" row is like 3k.
Since AREV has a 64K variable limit, your "%FIELDS%" row might be exceeding that.
At 30 DEC 2003 02:36AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
The size of %FIELDS% will depend on the length of the dictionary item names and the lengths of any user defined conversions. We have seen this blow out at ] 1,000 dictionary items before but the poster says that this has happened on smaller files too. We're thinking it'll be more like a read triggered by DICT.MFS failing. Is the field in this case indexed?
World Leaders in all things RevSoft
At 30 DEC 2003 04:56AM Craig X Tildesley wrote:
Yes we have lots of dictionary items which is pushing the 64k limit but I can successfully create the item I'm trying to WRITE using DICT. This error occurs on an NT service network and a single user system on a hard drive. Its a completely new field and so can't be indexed.
To clarify the program is writing a symbolic field rather than a symbolic field doing the writing.
I'm certain that the installation program which is copying in the dictionary items using a WRITE is screwing DICT.MFS but I don't know how. I have no idea what variables DICT.MFS relies on which when modified incorrectly would cause a read failure.
At 30 DEC 2003 06:22AM The Sprezzatura Group wrote:
OK on the NT Service network, create an lh2.log file and look at this to try to work out what read/write is failing (an FS100 can be caused by a read or a write).
The Sprezzatura Group
World Leaders in all things RevSoft
At 13 JAN 2004 06:12AM Craig X Tildesley wrote:
The mystery is solved. A subroutine CALLed from the dictionary was in mixed case. No idea why it compiled ok using DICT or worked when COPYed.
At 02 FEB 2004 05:02PM Larry Wilson wrote:
You also have to update the other .DICT files that DICT.MFS updates for the write with DICT.MFS disabled to work. I think I have an article about that in my knowlege base on my website; if I don't, please call or write.
Larry Wilson
972-768-2965