| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | error events | 0;1 | FREE TEXT | B | This is the list of captured errors of this type in the form of +$H:NN where $H is the +$Horolog day count, and NN is the sequence number that records the nnth error for that day. So if the error is still available, then, the details can be collected. This scheme will ensure that each occurrence is unique. | |
| 1 | date/time of error | 0;2 | DATE-TIME | D | This is the date and time as described in the error report, but converted to FileMan format. | |
| 2 | line if different | 1;E1,245 | FREE TEXT | This is the offending line of code as captured by the interpreter. | ||
| 3 | last global if different | 2;1 | FREE TEXT | |||
| 4 | $zhorolog detail | 0;3 | FREE TEXT | |||
| 5 | user duz | 0;4 | FREE TEXT | This is the user who experienced the problem. This will make it easier for us to check if this is a needs problem or a training problem. | ||
| 6 | stack path | 6;1 | FREE TEXT | This is the path by which the error level of execution was accessed. It is a series of segments, each representing a level of execution in the model as it was being performed. Occasionally this list of segments will exceed the string length so some judicious exiting has been done to keep the stack list manageable. Should the list need to be trimmed, segments will be taken out of the middle of the stack to accommodate the string limits. These omissions are marked with an ellipsis "..." where a segment or segments have been deleted. A segment looks like this; LABEL[+offset]^RTN:command step The set of segments is wrapped in square brackets and stored in its entirety in the event node for comparison with other events. | ||
| 11 | user name | 3;1 | POINTER | 200 | USER | User Pointer who was on when the error occurred. |
| 12 | option used | 3;2 | POINTER | 19 | This is the POINTER to the Option File that was being used at the time of the error. | |
| 13 | option name | 3;3 | FREE TEXT | This is the name of the option pointed to in field 2. | ||
| 14 | task referenced | 3;4 | POINTER | 14.4 | This is the task being performed (if it was a task). | |
| 15 | global volume | 3;5 | FREE TEXT | This is the Global Volumes being accessed when the task started. | ||
| 16 | routine volume | 3;6 | FREE TEXT | This is the Routine Set being used when the Error Occurred. | ||
| 17 | host cpu | 3;7 | FREE TEXT | This is the Name of the CPU the program was running on. | ||
| 18 | rpc broker state | 3;8 | FREE TEXT | This is the description of the Broker Task being performed. | ||
| 19 | uploaded | 0;5 | BOOLEAN | 0:No 1:Yes | This field tells if this error has been reported to a central repository. |
Error: Invalid Global File Type: 3.07701