Feature - Serious File Error Event
A new event is added to support tracking of serious file errors.
When a serious file error occurs, the following event will be triggered:
File: COMPFILE
Program: FILERR
Type: IOERROR
Description: File Access IO Error
Variable 1: Record No (always 01)
Variable 2: Elliott WorkStation
Variable 3: Elliott User ID
Variable 4: EXE Process
Variable 5: File IO Error Code
Variable 6. Btrieve Error Code
Variable 7: File Name
Variable 8: File Description
Variable 9: Program
Variable 10: IO Data
See sample screens below:
![Image: https://support.elliott.com/assets/240834583/IOError-1.png](https://support.elliott.com/assets/240834583/IOError-1.png)
![Image: https://support.elliott.com/assets/240834589/IOError-2.png](https://support.elliott.com/assets/240834589/IOError-2.png)
These event request settings result in an email like this:
![Image: https://support.elliott.com/assets/240834603/IOError-3.png](https://support.elliott.com/assets/240834603/IOError-3.png)
Note
This event only gets triggered when a serious file error occurs, one from which the program cannot recover -- for example, when an Elliott program gets an error dialog like this:![Image: https://support.elliott.com/assets/240834691/IOError-4.png](https://support.elliott.com/assets/240834691/IOError-4.png)
Example
If you want to receive an email whenever a serious file error occurs in a Deferred Processing report, add a filter like this:
![Image: https://support.elliott.com/assets/240834747/IOError-5.png](https://support.elliott.com/assets/240834747/IOError-5.png)
Modified Programs: FILERR, NSIFH, NWSMHELP, NWSMMENU
JEG