Debugging in a Distributed Processing Environment

You can interact with the runtime debugger and debug remote programs in two ways.

The first way is to view a debugger window on the server itself: This is accomplished by starting acuconnect with the -d flag, or example:

acuconnect -start -d.

When started with this flag, AcuConnect will run in the foreground. This means that all logging messages will be sent to the console or command line window. On UNIX, only one connection is allowed at a time. On Windows, multiple users can connect simultaneously. When a server runtime is started by AcuConnect, a debugger window will be displayed to the console. On Windows, multiple debugger windows can be opened for multiple connections. The server debugger is a fully functional.

The second way to debug a remote program is to direct the debugger window to be opened on a remote machine with a TTY, an xterm, or the thin client.

If you want to use an xterm, the remote runtime will create an xterm and use it for interaction with the runtime debugger. Alternatively, you can specify the name of a TYY that will be used by the runtime to interact with the debugger. You can also specify a Windows client machine and port number. The client runtime will then start an acuthin instance for interacting with the debugger. See ACUCONNECT_DEBUG_METHOD and ACUCONNECT_DEBUG_METHOD_STRING for specific instructions in implementing these options.