This section explains points to note when using the remote debugger.
To use the remote debug function, there must be support for TCP/IP protocol in both the server and client.
This section explains points to note when using the Win32 remote debugger.
For details about common points with the normal debugger, refer to "2.8.7.2.2 Notes on handling Unicode", and "2.7 Notes".
Note the storage location for the resources that are required for debugging. For details, refer to "2.8.1.2 Storage location for resources when doing remote debugging".
Specify the application name and debugging information file storage folder according to the server folder conventions.
Specify the folder name and file name in the execution-time options according to the server folder conventions.
This section explains points to note when using the Solaris remote debugger.
The Solaris remote debugger decides the character code at execution- time using one of the following methods:
When starting remote debugging for general programs:
The operation is the same as for the character code for starting server remote debugger connector.
When starting remote debugging for programs that run in server environments such as Interstage:
The operation is the same as for the character code that runs on servers such as Interstage and Web servers.
In the Solaris remote debugger, note the following points when debugging Unicode programs:
Handling Unicode native characters
Unicode native characters are also displayed in the Data dialog box and Watch window. However, Unicode native characters cannot be input. To input Unicode native characters, specify them using hexadecimal format.
Batch debugging, automatic debugging, and output log
ASCII is also used as the coding system of command files and history files for Unicode. As a result, Unicode native characters are replaced with a "_" and output.
For details about points in common with the normal debugger, refer to the "NetCOBOL User's Guide for Solaris".
Note the storage location for the resources that are required for debugging. For details, refer to "2.8.1.2 Storage location for resources when doing remote debugging".
Specify the application name and debugging information file storage folder according to the server folder conventions.
Specify the folder name and file name in the execution-time options according to the server folder conventions.
Since the server file name and folder name are case sensitive, take care when you specify upper-case letters and lower-case letters.
If you omit the application name extension, an EXE extension will not be provided for the name. Solaris assumes no extension.
