TN3270 DEBUG on web threads

From m204wiki
Revision as of 14:32, 25 April 2023 by Ekern (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

If you license the TN3270 Debugger, you can use the TN3270 DEBUG ON command to debug Janus Web Server threads. This may be useful if you need to avoid changing the proxy server settings on your web browser.

You invoke a Janus Web procedure from your browser, a TN3270 DEBUG ON command you embedded in the procedure starts the Debugger, and you work with your source code in the Debugger Client as usual. The thread you are debugging counts as one of your TN3270 Debugger authorized "seats."

Using the TN3270 DEBUG command to invoke debugging requires no additional configuration of the Debugger. You must make sure, however, that no proxy server is defined for the browser with which you send a request to the Janus Web Server.

To debug a Janus Web thread:

  1. In the Janus Web program you want to debug, insert a TN3270 DEBUG ON command to invoke the Janus Debugger. The command must not be placed between explicit BEGIN and END User Language statements.
  2. Start the Debugger Client.
  3. Make sure the Client is not automatically maintaining a proxy server for you:
    1. From the File menu, select Preferences.
    2. Make sure the Automatically Maintain IE proxy settings checkbox is clear.
  4. In the browser you use to invoke debugging, confirm that the Debugger Client is not defined as a proxy server.
  5. From your browser, invoke the URL for the web program that contains the TN3270 DEBUG ON command. The browser pauses in a loading state, and the web program is sent to the Debugger Client Source Code page.
  6. Work with the procedure code in the Client as usual.
As the code is evaluated, output destined for a web page goes to a Web Buffer page in the Client:
When code execution completes, output (including error messages and Web Buffer contents) is sent to the browser instead of to the Model 204 "terminal." At this point, the connection to the web thread is closed and the debugging session ends. It is not necessary to provide an explicit TN3270  DEBUG OFF command.

You can also embed TN3270 DEBUG SUSPEND and RESUME commands in the procedures that are included in your program to take advantage of those features. And you can similarly embed a TN3270 DEBUG OFF command or invoke its equivalent programmable command turnOffDebugging from a Client button or hot key.

Once debugging is on and the Client has the web thread source code, TN3270 DEBUG command input from the command line at the Model 204 host has no effect on debugging the command line thread is separate from the web thread.