A string search could be used to find XQ in all routines or an UNDEF in the definition of all errors. Once an error is identified, the report generator shows the following: Job Number Username IO value Date/Time UCI/Volume Set Error Type Last Global Reference Line of code that caused the error It then prompts for a listing of variables, enter ^L to list all or a letter, such as X, to list those starting with X. The listing can be printed to the screen or to an output device. You can page through the screen listing, one screen at a time, and enter ^Q to quit or enter ^ to exit at the end of each screen. A restore feature can be invoked by entering provided that the user is working in ^R programmer mode. Programmer mode is required as a protection against restoration of variables from within the menu system. To the extent possible, the environment at the time of the error is restored with the routine and local symbol table intact. Figure : Local Symbol Table Help Which symbol? > ? Enter: ^Q to EXIT ‘^’ to return to the last question Leading character(s) of symbol(s) you wish to examine $ to get a display of the $ system variables ^L to obtain a list of all symbols ^R to restore the symbol table and ... and enter direct mode After reviewing the error log, you are given the opportunity to examine the operating system’s error log. Now that most VistA applications record their errors in error log, however, Kernel’s there is less need to track VistA errors in the operating system error log. Figure : Choosing to Examine the Operating System’s Error Log—Sample User Dialogue Do you want to check the OPERATING SYSTEM ERROR TRAP too? NO// Interactive Print of Error Messages Option The Interactive Print of Error Messages [XUERTRP PRINT ERRS] option provides for an interactive print of the first of occurrences of an error is user selectable) over a “n” (where “n” specified date range.
A string search could be used to find XQ in all routines or an UNDEF in the definition of all errors. Once an error is identified, the report generator shows the following: Job Number Username IO value Date/Time UCI/Volume Set Error Type Last Global Reference Line of code that caused the error It then prompts for a listing of variables, enter ^L to list all or a letter, such as X, to list those starting with X. The listing can be printed to the screen or to an output device. You can page through the screen listing, one screen at a time, and enter ^Q to quit or enter ^ to exit at the end of each screen. A restore feature can be invoked by entering ^R provided that the user is working in programmer mode. Programmer mode is required as a protection against restoration of variables from within the menu system. To the extent possible, the environment at the time of the error is restored with the routine and local symbol table intact. Figure : Local Symbol Table Help Which symbol? > ? Enter: ^Q to EXIT ‘^’ to return to the last question Leading character(s) of symbol(s) you wish to examine $ to get a display of the $ system variables ^L to obtain a list of all symbols ^R to restore the symbol table and ... and enter direct mode After reviewing the error log, you are given the opportunity to examine the operating system’s error log. Now that most VistA applications record their errors in Kernel’s error log, however, there is less need to track VistA errors in the operating system error log. Figure : Choosing to Examine the Operating System’s Error Log—Sample User Dialogue Do you want to check the OPERATING SYSTEM ERROR TRAP too? NO// Interactive Print of Error Messages Option The Interactive Print of Error Messages [XUERTRP PRINT ERRS] option provides for an interactive print of the first “n” of occurrences of an error (where “n” is user selectable) over a specified date range.