Prepare a Connection for Remote Debugging (OS/2, Windows)

Before you can begin debugging processes on a remote machine you must prepare the connection on both the local and remote machines. This means you must initialize the debugger remote probe on your remote machine and specify the remote host in the IDE on your local machine. These can be done in any order, the connection is established as soon as both parts are completed.

Note: Both the remote machine and the local machine must be running the same operating system for a connection to be established. For example, both the remote machine and the local machine must both be running OS/2.

You can establish a connection from a local machine running Windows NT if the remote machine is running either Windows 95 or Windows NT.

To specify a remote host in the IDE:

  1. Choose the Remote Hosts page of the host tab.
  2. In the Remote Hosts Specification view, click New. The default specification will appear.
  3. In the Unique Name field, enter the name you want to give the connection to the host. This will help you differentiate between different connections.
  4. Choose the communication protocol using the Communication Type pull-down menu.
  5. Enter any parameters required for the protocol in the entries under Communication Parameters.
  6. Click Connect to connect to remote host. The communication status field will read "Connected" when a connection is established.

To initialize the debugger remote probe:

  1. Enter vacprobe at a command line.
  2. Choose a communication protocol from the Protocol pull-down menu.
  3. Click Connect. A communication protocol parameters screen will appear.
  4. Enter any parameters required for the communications protocol in the screen.
  5. Click Connect on the communication protocol parameters screen to connect to your local machine. The message will read "Connected" when a connection is established.

If you experience communications problems while connecting or while debugging after you have established a connection, disconnect from either the IDE or the debugger remoter probe, wait at least 30 seconds, then re-connect.

Notes:

  1. For a TCP/IP based connection, one machine must be the TCP/IP Answer Port and the other machine must be the TCP/IP Originate Port. For more information, refer to Communication Types.
  2. Any number of connections between various remote machines and your local machine are supported. However, we recommend that only use one connection to each remote machine.
  3. Each connection you establish can support multiple debug sessions.


ngos2.gif (402 bytes) ngwin.gif (1069 bytes)Remote Debugging
ngos2.gif (402 bytes) ngwin.gif (1069 bytes)Communication Types


ngos2.gif (402 bytes) ngwin.gif (1069 bytes)Install the Debugger Remote Probe