When you use the EGL debugger outside of Rich UI, you can specify the type of character encoding to use while debugging. Character encoding controls how the debugger represents character and numeric data internally, how it compares character data, and how it passes parameters to remote programs, files, and databases. To change these options, see Setting preferences for the EGL debugger.
If you choose this setting and do not specify a conversion table, the debugger chooses an appropriate conversion table when you call a remote program or access a remote file or database. For more information on conversion tables, see callConversionTable.
If you choose EBCDIC character encoding and do not specify a conversion table, the debugger does not use a conversion table when you call a remote program or access a remote file or database. The program name, library name, and any passed parameters are encoded according to EBCDIC character encoding.
If your Java Runtime Environment does not support the selected character encoding, you will see a warning message when the debugger starts. If you choose to continue debugging, the debugger will return to the default encoding type.
You can not change character encoding during a debugging session. You must restart the debugger for a change in character encoding to take effect.