Access
To define how debugger acts in the event of errors, select the Detection tab in the Debugger setup dialog box.
This configuration page is used to let the debugger know how it should react if it detects certain errors at runtime.
Displayed data
DB errors except *NOT_FOUND
These are errors concerning database access:
- SQL instructions: SQL error returning *SQLCODE < 0,
- Native file access instructions: error causing *RETURN_CODE to be reset to '1'.
Errors while calling program , loading DLLs, ...
These are errors that place a value other than 0 in *RETURN_CODE and concern the following instructions: CALL, EXECUTE_CMD, CALL_DLL, LOAD_DLL.
Important: For AS/400 server parts, if your program is generated with the generation characteristic "Generate I/O error" set to No or Read, these two error types cannot be managed by the debugger, as this will lead to a system execution error.
Middleware errors
These are middleware errors encountered at runtime.
Note: On all platforms except AS/400, execution errors that bring up an Adelia error window are systematically intercepted by the debugger which will ask you whether you want to suspend or continue processing, regardless of the specified detection type (Ignore, Display, Ask).
Data entry
Various options are proposed in order to manage the errors which may occur:
Ignore |
The debugger will not manage the errors encountered. |
Display |
The debugger will display a message (in the message box) specifying the type of error and the relevant 4GL line when an error is detected. |
Ask |
When it detects an error, the debugger will display a message specifying the type of error and the relevant 4GL line. It will ask the user whether they want to suspend execution for the instruction in question or continue executing the program. |