Character encoding options for the EGL debugger

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.

The EGL debugger supports two different types of character encoding: the default encoding on your local system and Extended Binary Coded Decimal Interchange Code (EBCDIC). The default character encoding for the EGL debugger is the same as your local system's default encoding.
  • When the default character encoding is selected, the debugger represents CHAR, DBCHAR, MBCHAR, DATE, TIME, INTERVAL, NUM, and NUMC variables in the default format, typically ASCII. Comparisons between character variables use the ASCII collating sequence. Data must be converted to host format when calling remote programs and when accessing remote files and databases.

    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.

  • When EBCDIC character encoding is used, the debugger represents CHAR, DBCHAR, MBCHAR, DATE, TIME, and INTERVAL variables with EBCDIC encoding. NUM and NUMC variables are represented in host numeric format. Comparisons between character variables use the EBCDIC collating sequence. Data does not need to be converted to host format when calling remote programs or when accessing remote files and databases, but data is converted to the appropriate Java™ or ASCII format when making SQL calls or calls to local C++ routines. EBCDIC encoding is available in several languages.

    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.