Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Deleted: | ||||||||
< < | ||||||||
APPX ILF DebuggerEffective with Release 5.0.0, the original character mode ILF Debugger has been replaced with a GUI ILF Debugger. | ||||||||
Line: 23 to 22 | ||||||||
The following icons are used to mark ILF statements for the benefit of the application designer: | ||||||||
Changed: | ||||||||
< < | Identifies an ILF commnad what has a stop point (trap) enabled. | |||||||
> > | Identifies an ILF command that has a stop point (trap) enabled. | |||||||
Identifies the next ILF command line to execute. Identifies the next ILF command line to exectute and indicates that the line has a stop point (trap) enabled | ||||||||
Changed: | ||||||||
< < | Field values can also be viewed in a popup tooltip by moving the mouse pointer over any ILF statement which references fields. | |||||||
> > | Field values can also be viewed in a popup tooltip by moving the mouse pointer over any ILF statement which references a field. | |||||||
Toolbar Buttons |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX ILF Debugger | ||||||||
Line: 17 to 17 | ||||||||
Changed: | ||||||||
< < | If a runtime error causes the ILF debugger to be invoked, the statement which caused the error will be highlighted with a light blue background color. The next ILF line to be executed is marked with a blue and white icon and the line will have a blue background. The white arrow in the blue circle points to the statement to further hightlight it. | |||||||
> > | If a runtime error causes the ILF debugger to be invoked, the statement which caused the error will be highlighted with a light blue background color. The white arrow in the blue circle points to the statement to further hightlight it. In the example below, notice that the value for the fields for the current statement are displayed in the field value window on the bottom of the screen. | |||||||
Changed: | ||||||||
< < | ||||||||
> > | The following icons are used to mark ILF statements for the benefit of the application designer: | |||||||
Identifies an ILF commnad what has a stop point (trap) enabled. | ||||||||
Line: 29 to 29 | ||||||||
Identifies the next ILF command line to exectute and indicates that the line has a stop point (trap) enabled | ||||||||
Changed: | ||||||||
< < | The Toolbar contains several new icons. The Green Arrow will jump out of the trapped event point . The Red X will cancel the process as always. Single step will execute the next sequential instruction, same a the Return key. The Step Into will follow a child process. Step Return takes you to the next Return statement. There is a red/gray icon you can use to set and remove a trap. F3 can still be used to set and un-set traps as well. The Edit values icon will allow the current field value(s) to be modified. Inspect/Edit will allow you to enter a field and see its contents. View Process Stack will display the current process stack showing the Ap/Ver, Proc Type, Process Name, and invocation share class. Watch Variable allow you enter a field name and Appx will indicate when the contents of that field change. | |||||||
> > | Field values can also be viewed in a popup tooltip by moving the mouse pointer over any ILF statement which references fields. | |||||||
Changed: | ||||||||
< < | Scrolling the ILF Debugger using the up and down arrow keys is not permitted. | |||||||
> > | ||||||||
Toolbar Buttons | ||||||||
Added: | ||||||||
> > | The Toolbar contains a variety of buttons that facilitate debugging of a process: | |||||||
Go [Option 0]- Resume normal execution. Cancel [Ctrl+F8]- Abort process being debugged. | ||||||||
Line: 89 to 89 | ||||||||
Comments:Read what other users have said about this page or add your own comments. | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | The toolbar needs a button for: Execute Next [F9] - Set next statement to execute -- SteveFrizzell - 30 Sep 2008 | |||||||
-- SteveFrizzell - 26 Sep 2008 | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
| ||||||||
Line: 116 to 119 | ||||||||
| ||||||||
Added: | ||||||||
> > |
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX ILF Debugger | ||||||||
Line: 8 to 8 | ||||||||
Overview | ||||||||
Changed: | ||||||||
< < | The APPX ILF debugger is a powerful debugging tool that enables the APPX application designer to examine field values and to observe how field values change as individual ILF statements are executed. The APPX ILF Debugger is invoked as the result of executing a TRAP statement when testing a process or as the result of encountering a runtime error such as a Numeric Overflow. | |||||||
> > | The APPX ILF debugger is a powerful debugging tool that enables the APPX application designer to examine field values and to observe how field values change as individual ILF statements are executed. The APPX ILF Debugger is invoked as the result of executing a TRAP statement when testing a process or automatically as the result of encountering a runtime error such as a Numeric Overflow. | |||||||
Main Debugger Window | ||||||||
Changed: | ||||||||
< < | The main window of the ILF debugger displays the ILF statements which precede and follow the next line to be executed. The next ILF statement to execute is highlighted with a light blue background. If the ILF debugger is displayed as the result of encountering a TRAP statement, the next line to be executed will be the TRAP statement. | |||||||
> > | The main window of the ILF debugger displays the ILF statements which precede and follow the next line to be executed. If the ILF debugger is displayed as the result of encountering a TRAP statement, the next line to be executed will be the TRAP statement. In the example below, the TRAP statement is highlighted with a light blue background. The white arrow in the red circle points to the statement to further hightlight it. | |||||||
Changed: | ||||||||
< < | The ILF line(s) of code that are set for trapping will be marked with the red and white icon and the entire line will be have a pink background. The next ILF line to be executed is marked with a blue and white icon and the line will have a blue background. Traps may be set at run time by clicking on the desired line and then clicking on the Trap icon on the Toolbar. | |||||||
> > | If a runtime error causes the ILF debugger to be invoked, the statement which caused the error will be highlighted with a light blue background color. The next ILF line to be executed is marked with a blue and white icon and the line will have a blue background. The white arrow in the blue circle points to the statement to further hightlight it. | |||||||
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Changed: | ||||||||
< < | APPX GUI ILF Debugger | |||||||
> > | APPX ILF Debugger | |||||||
Changed: | ||||||||
< < | Effective with Release 5.0.0, the ILF Debugger has been replaced with a new GUI ILF Debugger. | |||||||
> > | Effective with Release 5.0.0, the original character mode ILF Debugger has been replaced with a GUI ILF Debugger. | |||||||
Overview | ||||||||
Changed: | ||||||||
< < | The GUI ILF Debugger is invoked automatically when ILF code is displayed at run time. ILF line(s) of code that are set for trapping will be marked with the red and white icon and the entire line will be have a pink background. The next ILF line to be executed is marked with a blue and white icon and the line will have a blue background. Traps may be set at run time by clicking on the desired line and then clicking on the Trap icon on the Toolbar. | |||||||
> > | The APPX ILF debugger is a powerful debugging tool that enables the APPX application designer to examine field values and to observe how field values change as individual ILF statements are executed. The APPX ILF Debugger is invoked as the result of executing a TRAP statement when testing a process or as the result of encountering a runtime error such as a Numeric Overflow. | |||||||
Changed: | ||||||||
< < | Toolbar Buttons | |||||||
> > | Main Debugger Window | |||||||
Changed: | ||||||||
< < | Go - Resume normal execution. | |||||||
> > | The main window of the ILF debugger displays the ILF statements which precede and follow the next line to be executed. The next ILF statement to execute is highlighted with a light blue background. If the ILF debugger is displayed as the result of encountering a TRAP statement, the next line to be executed will be the TRAP statement. | |||||||
Changed: | ||||||||
< < | Cancel - Abort process being debugged. | |||||||
> > | ||||||||
Changed: | ||||||||
< < | Single Step - Execute the current line and stop on the next line in the current routine. | |||||||
> > | The ILF line(s) of code that are set for trapping will be marked with the red and white icon and the entire line will be have a pink background. The next ILF line to be executed is marked with a blue and white icon and the line will have a blue background. Traps may be set at run time by clicking on the desired line and then clicking on the Trap icon on the Toolbar. | |||||||
Changed: | ||||||||
< < | Step Into - Execute a process or subroutine and stop on the first statement of the routine. | |||||||
> > | ||||||||
Changed: | ||||||||
< < | Step Return - Resume execution and stop on the next RETURN statement. | |||||||
> > | ||||||||
Changed: | ||||||||
< < | Step End - Resume execution of the current routine and stop on the last statement in the routine. | |||||||
> > | Identifies an ILF commnad what has a stop point (trap) enabled. | |||||||
Changed: | ||||||||
< < | Toggle Trap - Enable/Disable a trap on the current statement. | |||||||
> > | Identifies the next ILF command line to execute. | |||||||
Changed: | ||||||||
< < | Edit Values - Edit the value of the variables on the current statement. | |||||||
> > | Identifies the next ILF command line to exectute and indicates that the line has a stop point (trap) enabled | |||||||
Changed: | ||||||||
< < | Inspect/Edit Value - Inspect and/or edit the value of a specified variable | |||||||
> > | ||||||||
Changed: | ||||||||
< < | View Process Stack | |||||||
> > | The Toolbar contains several new icons. The Green Arrow will jump out of the trapped event point . The Red X will cancel the process as always. Single step will execute the next sequential instruction, same a the Return key. The Step Into will follow a child process. Step Return takes you to the next Return statement. There is a red/gray icon you can use to set and remove a trap. F3 can still be used to set and un-set traps as well. The Edit values icon will allow the current field value(s) to be modified. Inspect/Edit will allow you to enter a field and see its contents. View Process Stack will display the current process stack showing the Ap/Ver, Proc Type, Process Name, and invocation share class. Watch Variable allow you enter a field name and Appx will indicate when the contents of that field change. | |||||||
Changed: | ||||||||
< < | Watchpoint - Set or Clear watch points on individual variables
Main Debugger Window | |||||||
> > | Scrolling the ILF Debugger using the up and down arrow keys is not permitted.
Toolbar Buttons | |||||||
Changed: | ||||||||
< < | Identifies an ILF commnad what has a stop point (trap) enabled. | |||||||
> > | Go [Option 0]- Resume normal execution. | |||||||
Changed: | ||||||||
< < | Identifies the next ILF command line to execute. | |||||||
> > | Cancel [Ctrl+F8]- Abort process being debugged. | |||||||
Changed: | ||||||||
< < | Identifies the next ILF command line to exectute and indicates that the line has a stop point (trap) enabled | |||||||
> > | Single Step [RETURN] - Execute the current line and stop on the next line in the current routine. | |||||||
Changed: | ||||||||
< < | ||||||||
> > | Step Into [Option 1] - Execute a process or subroutine and stop on the first statement of the routine. | |||||||
Changed: | ||||||||
< < | The Toolbar contains several new icons. The Green Arrow will jump out of the trapped event point . The Red X will cancel the process as always. Single step will execute the next sequential instruction, same a the Return key. The Step Into will follow a child process. Step Return takes you to the next Return statement. There is a red/gray icon you can use to set and remove a trap. F3 can still be used to set and un-set traps as well. The Edit values icon will allow the current field value(s) to be modified. Inspect/Edit will allow you to enter a field and see its contents. View Process Stack will display the current process stack showing the Ap/Ver, Proc Type, Process Name, and invocation share class. Watch Variable allow you enter a field name and Appx will indicate when the contents of that field change. | |||||||
> > | Step Return [Option 2] - Resume execution and stop on the next RETURN statement. | |||||||
Changed: | ||||||||
< < | Scrolling the ILF Debugger using the up and down arrow keys is not permitted. | |||||||
> > | Step End [Option 3] - Resume execution of the current routine and stop on the last statement in the routine. Toggle Trap [F3] - Enable/Disable a trap on the current statement. Edit Values [F12] - Edit the value of the variables on the current statement. Inspect/Edit Value [F11] - Inspect and/or edit the value of a specified variable View Process Stack [Ctrl+1] Watchpoint [F10] - Set or Clear watch points on individual variables Execute Next [F9] - Set next statement to execute | |||||||
Watchpoints | ||||||||
Added: | ||||||||
> > | Watch points can be very helpful when debugging a process. An APPX watchpoint is a field name that you want APPX to "watch". Anytime the value of the field changes, APPX will invoke the ILF Debugger and alert you to the change in value. | |||||||
Process Stack | ||||||||
Added: | ||||||||
> > | When debugging a process, it is sometimes useful to be able to view the process stack. The process stack is simply a list of the "ancestor" processes of the process that is currently running. In the example below, the level 1 process is the current input process named DEBUG which displays the process stack list. The level 2 process is the process that is currently being debugged. In this example, the process being debugged is an input process in application DMO named PROSPECT FILE MAINTENANCE. The level 3 and higher processes identify the various processes in application design that were run to design and then test the PROSPECT FILE MAINTENANCE input process. | |||||||
Added: | ||||||||
> > | How to Revert to the Original ILF DebuggerIf you prefer to use the original character mode ILF Debugger, you can disable the GUI ILF Debugger and revert to the original ILF Debugger by setting the following environment variable: APPX_OLD_DBG=<any_value> The easiest way be ensure that this environment variable is set for all APPX sessions is to define it in the appx.env configuration file. Simply add the environment variable to the appx.env file. You may assign <any_value> to the variable to enable it. The example below assigns a value of 1 thereby enabling the original ILF debugger.#============================================================================= # Revert to original ILF Debugger #============================================================================= APPX_OLD_DBG=1 | |||||||
Comments:Read what other users have said about this page or add your own comments. | ||||||||
Line: 61 to 93 | ||||||||
-- SteveFrizzell - 26 Sep 2008 | ||||||||
Added: | ||||||||
> > | ||||||||
| ||||||||
Line: 81 to 115 | ||||||||
| ||||||||
Added: | ||||||||
> > |
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
APPX GUI ILF Debugger | ||||||||
Line: 6 to 6 | ||||||||
Effective with Release 5.0.0, the ILF Debugger has been replaced with a new GUI ILF Debugger. | ||||||||
Added: | ||||||||
> > | Overview | |||||||
The GUI ILF Debugger is invoked automatically when ILF code is displayed at run time. ILF line(s) of code that are set for trapping will be marked with the red and white icon and the entire line will be have a pink background. The next ILF line to be executed is marked with a blue and white icon and the line will have a blue background. Traps may be set at run time by clicking on the desired line and then clicking on the Trap icon on the Toolbar. | ||||||||
Changed: | ||||||||
< < | Toolbar Buttons | |||||||
> > | Toolbar Buttons | |||||||
Changed: | ||||||||
< < | Go - Resume normal execution
Main Debugger Window | |||||||
> > | Go - Resume normal execution.
Cancel - Abort process being debugged.
Single Step - Execute the current line and stop on the next line in the current routine.
Step Into - Execute a process or subroutine and stop on the first statement of the routine.
Step Return - Resume execution and stop on the next RETURN statement.
Step End - Resume execution of the current routine and stop on the last statement in the routine.
Toggle Trap - Enable/Disable a trap on the current statement.
Edit Values - Edit the value of the variables on the current statement.
Inspect/Edit Value - Inspect and/or edit the value of a specified variable
View Process Stack
Watchpoint - Set or Clear watch points on individual variables
Main Debugger WindowIdentifies an ILF commnad what has a stop point (trap) enabled. | |||||||
Identifies the next ILF command line to execute. | ||||||||
Added: | ||||||||
> > | Identifies the next ILF command line to exectute and indicates that the line has a stop point (trap) enabled | |||||||
The Toolbar contains several new icons. The Green Arrow will jump out of the trapped event point . The Red X will cancel the process as always. Single step will execute the next sequential instruction, same a the Return key. The Step Into will follow a child process. Step Return takes you to the next Return statement. There is a red/gray icon you can use to set and remove a trap. F3 can still be used to set and un-set traps as well. The Edit values icon will allow the current field value(s) to be modified. Inspect/Edit will allow you to enter a field and see its contents. View Process Stack will display the current process stack showing the Ap/Ver, Proc Type, Process Name, and invocation share class. Watch Variable allow you enter a field name and Appx will indicate when the contents of that field change. Scrolling the ILF Debugger using the up and down arrow keys is not permitted. | ||||||||
Added: | ||||||||
> > | WatchpointsProcess Stack | |||||||
Comments:Read what other users have said about this page or add your own comments. | ||||||||
Changed: | ||||||||
< < | -- SteveFrizzell - 26 Sep 2008 | |||||||
> > | -- SteveFrizzell - 26 Sep 2008 | |||||||
| ||||||||
Line: 50 to 79 | ||||||||
| ||||||||
Added: | ||||||||
> > |
|
Line: 1 to 1 | |||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Added: | |||||||||||||||||||||||||||||||||||||||
> > |
APPX GUI ILF DebuggerEffective with Release 5.0.0, the ILF Debugger has been replaced with a new GUI ILF Debugger.Toolbar ButtonsGo - Resume normal executionMain Debugger WindowIdentifies the next ILF command line to execute. The Toolbar contains several new icons. The Green Arrow will jump out of the trapped event point . The Red X will cancel the process as always. Single step will execute the next sequential instruction, same a the Return key. The Step Into will follow a child process. Step Return takes you to the next Return statement. There is a red/gray icon you can use to set and remove a trap. F3 can still be used to set and un-set traps as well. The Edit values icon will allow the current field value(s) to be modified. Inspect/Edit will allow you to enter a field and see its contents. View Process Stack will display the current process stack showing the Ap/Ver, Proc Type, Process Name, and invocation share class. Watch Variable allow you enter a field name and Appx will indicate when the contents of that field change. Scrolling the ILF Debugger using the up and down arrow keys is not permitted.Comments:Read what other users have said about this page or add your own comments. -- SteveFrizzell - 26 Sep 2008
|