This is a tool for capturing the VistA errors at each site. These findings can be used locally and pushed to a central repository to help to prioritize the efforts to seal up the hot spots in the applications.
.01error text(+)0;1FREE TEXTBThis is the text captured with the error. It is a means of providing a common key for the errors to be clustered under. Each one will has a series of characteristics which will be captured for later analysis even after the error has been purged off of the ^%ZTER global. The first date and time is stored as will be the most recent occurrence.
1first date/time0;2DATE-TIMEThis is the first date and time that the error has occurred. It is of historic importance and can be used to find the causative event of the error that is being reported.
2most recent date/time0;3DATE-TIMEThis is the most recent time that the situation has happened. It is important in that it is the most likely to still be in the error trap global, ^%ZTER.
3routine name0;4FREE TEXTThis is the name of the routine in question. It will be parsed out of the error string in .01. This will make the errors much easier to cluster around the causitive routine. This may actually be amended from the error string presentation if the causative program is found to be different.
3.1application0;5POINTER9.4This field will help to identify who are the responsible parties for this problem. Eventually, as a package is identified, the primaries and secondaries will be notified of the problem automatically as the problem happens.
4frequency0;6NUMERICThis is the number of times that the error has been encountered, ever. See FREQUENCY DISTRIBUTION below for how the error is occurring during the run of the day.
5frequency distribution4;0MULTIPLE3.0775
6last global3;1FREE TEXTThis is the last global referenced with the first such error recorded. If subsequent errors are recorded, and have different globals listed, they will be recorded in the following detail under ERROR EVENTS.
7stack list6;E1,245FREE TEXTThis is generated from the GETSTK^XTERSUM function call. It is the chain of calling levels which were accessed to bring about the error.
8uploaded date/time0;7DATE-TIMEThis field holds the date/time that the Error Summary was set to a consolidation site. A message will be sent if this field in empty or less than the "Last seen" field.
10error events1;0MULTIPLE3.07701This is the $H date and the Sequence number of this error on that $H date. It provides an easy way to scan quickly historic occurrences of these errors. Long period failures will become more evident when they start showing up as reoccurring situations which will need to be dealt with.
20line of code2;E1,245FREE TEXTThis is the original line of code which caused this problem. It should be the same for all occurrences, but may reflect other failures on the same line.
31support personnel31;0MULTIPLE3.077031

Not Referenced