Difference between revisions of "RPC HELP TRPCBroker DebugMode"

From VistApedia
Jump to: navigation, search
(Created page with "<h2>DebugMode Property</h2> <h3>Applies to</h3> TRPCBroker component Declaration property DebugMode: Boolean; Description The DebugMode des...")
 
Line 20: Line 20:
 
You will be prompted for the workstation Internet Protocol (IP) address and the port number. After entering the information, switch over to the client application and click on the OK button of the dialog window.
 
You will be prompted for the workstation Internet Protocol (IP) address and the port number. After entering the information, switch over to the client application and click on the OK button of the dialog window.
  
For more information, see How to Debug Your Application.
+
For more information, see [[RPC_HELP_Debug_How_To_Debug_Your_Application|How To Debug Your Application]].

Revision as of 17:18, 4 July 2015

DebugMode Property

Applies to

   TRPCBroker component

Declaration

   property DebugMode: Boolean;

Description The DebugMode design-time property controls how the VistA M Server process should be started. The default setting is False.

A setting of False starts the VistA M Server in the usual manner, as a background process.

For debugging purposes, it can be very helpful to set break points, run the server process interactively, and step through the execution. For those situations, set this property to True. When the TRPCBroker component connects with this property set to True, you get a dialog window indicating your workstation Internet Protocol (IP) address and the port number.

At this point you should switch over to the server, enter any break points that you wish, issue the debug command (e.g., ZDEBUG in DSM), and start the following server process:

   >D EN^XWBTCP

You will be prompted for the workstation Internet Protocol (IP) address and the port number. After entering the information, switch over to the client application and click on the OK button of the dialog window.

For more information, see How To Debug Your Application.