A later section describes the interaction of build descriptors and EGL preferences.
Breakpoints are remembered from one debugging session to the next, unless you remove the breakpoint.
You cannot set a breakpoint at a blank line or at a comment line.
The EGL debugger searches for the receiving program in every project in the workbench.
If the code forwards to a program, the debugger stops at the first statement in that program.
After either a show statement or a transfer statement of the form transfer to a transaction, the EGL debugger switches to the build descriptor for the new program or (if no such build descriptor is in use) prompts the user for a new build descriptor. The new program can have a different set of properties from the program that ran previously.
The EGL debugger searches for the receiving program in every project in the workbench.
If the code forwards to a program, the debugger stops at the first statement in that program.
After either a show statement or a transfer statement of the form transfer to a transaction, the EGL debugger switches to the build descriptor for the new program or (if no such build descriptor is in use) prompts the user for a new build descriptor. The new program can have a different set of properties from the program that ran previously.
The EGL debugger searches for the receiving program in every project in the workbench.
An exception is in effect if you issue the command step return in a validator function. In that case, the behavior is identical to that of a step into command, which primarily means that the EGL debugger runs the next statement and pauses.
You can add a breakpoint at these statements, for example, but a step into command merely continues to the subsequent statement, with no other effect.
Finally, if you issue the command step into or step over for a statement that is the last one running in the function (and if that statement is not return, exit program, or exit stack), processing pauses in the function itself so that you can review variables that are local to the function. To continue the debug session in this case, issue another command.
If you are debugging a program that is intended for use in a text or batch application in a Java environment, and if that program issues a transfer statement that switches control to a program that is also intended for use in a different run unit in a Java environment, the EGL debugger uses a build descriptor that is assigned to the receiving program. The choice of build descriptor is based on the rules described earlier.
A build descriptor or resource association part that you use for debugging code may be different from the one that you use for generating code.
The user ID and password used to access an SQL database are separate from the user ID and password used to make remote calls while debugging. To set the user ID and password for remote calls while debugging, see Setting preferences for the EGL debugger.
If the debugger runs EGL source code, you can run statements in that program by issuing the step into command from the caller. If the debugger calls generated code, however, the debugger runs the entire program; the step into command works like the step over command.
A value for system type is available in sysVar.systemType. Also, a second value is available in VGLib.getVAGSysType if you requested development-time compatibility with VisualAge Generator).
The system function VGLib.getVAGSysType returns the VisualAge Generator equivalent of the value in sysLib.systemType; for details, see the table in VGLib.getVAGSysType.
The EGL debugger uses a port to establish communication with the Eclipse workbench. The default port number is 8345. If another application is using that port or if that port is blocked by a firewall, set a different value as described in Setting preferences for the EGL debugger.
if (systemType not debug) sysLib.commit(); end
-Dcom.ibm.debug.egl.port=portNumber
Related concepts
Compatibility with VisualAge Generator
Character encoding options for the EGL debugger
VSAM support
Related tasks
Setting preferences for SQL database connections
Setting preferences for the EGL debugger
Setting the default build descriptors
Related reference
remoteComType in callLink element
sqlDB
sqlID
sqlJNDIName
sqlPassword
getVAGSysType()
systemType