The remote debugger can debug programs that run on different computers on the network.
In this section, the two computers on the network are expressed as follows:
Computers that run COBOL programs : server
Computers that display the COBOL debugger window : client
The remote debugger supports Windows and Solaris as the server OS. If the server is Windows, use the Win32 remote debugger. If the server is Solaris, use the Solaris remote debugger.
The functions of remote debuggers can vary depending on the server OS. In cases where remote debuggers must be distinguished from one another, the remote debugger that is called is as follows:
Solaris remote debugger if the server OS is Solaris
In the following explanation, it is assumed that the server is Windows.
If the server is Solaris, refer to the parts related to "NetCOBOL User's Guide for Solaris" where necessary.
Note
To use the remote debug function, there must be support for TCP/IP protocol in both the server and client.
The following cost reductions and improvements in development can be achieved by introducing the remote debugger.
You can debug COBOL programs that run in server environments such as Interstage and Web servers from the client environment that you normally use.
In this way, cost reductions and improvements in development can be achieved without having to set up an expensive server environment for each developer and having several developers having to debug at the same time.
If the server is Solaris, you can now debug using the same operation as the Windows edition COBOL debugger.
There are two ways to use and debug programs that run on Solaris on the Windows client.
Introduce the expensive Windows X windows server, and use screen mode for the svd command.
Using a TTY terminal, use line mode for the svd command.
The remote debugger does not need the expensive X windows server, and shares the same operation as the Windows edition COBOL debugger. For these reasons, it can be used to achieve cost reductions and improvements in development.
When you do remote debugging, you must store the resources that are required for debugging in either the server or the client, or both.
The resources that are required for debugging are shown in table below.
Debug resource | Client | Server |
|---|---|---|
Executable programs | - | Yes |
Dynamic link library (*1) | - | Yes |
Shared object file (*2) | - | Yes |
Debugging information file | - | Yes |
Source file | Yes (*5) | - |
Library text | Yes (*5) | - |
Screen form descriptor | Yes (*5) | Yes |
File descriptor (*3) | Yes (*5) | Yes |
Subschema descriptor (*4) | Yes (*5) | - |
Command file | Yes (*5) | - |
History file | Yes (*5) | - |
*1: Server is Windows
*2: Server is Solaris
*3: Server is Windows or Solaris
*4: Server is Windows
*5: Character code of resources in the client is always ASCII
For details on how to create a program that can be debugged with a remote debugger, refer to the "NetCOBOL User's Guide" for the appropriate system on the server side.
