Ekern at 14:32, 25 April 2023

2023-04-25T14:32:05Z

Ekern: Created page with "TOC If you license the `TN3270 Debugger`, you can use the
2022-11-08T03:45:53Z

Created page with "TOC If you license the <var>TN3270 Debugger</var>, you can use the If you license the <var>TN3270 Debugger</var>, you can use the TN3270 DEBUG ON command to debug <var>Janus Web Server</var> 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 <var>[[TN3270 DEBUG Syntax#TN3270 DEBUG ON|TN3270 DEBUG ON]]</var> 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 <var>TN3270 Debugger</var> [[Authorize the Debugger|authorized "seats."]]

Using the TN3270 DEBUG command to invoke debugging requires no additional [[Installation and Configuration|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: 

# In the Janus Web program you want to debug, insert a [[TN3270 DEBUG Syntax#TN3270 DEBUG ON|TN3270 DEBUG ON command]] to invoke the <var>Janus Debugger.</var> The command must '''not''' be placed between explicit BEGIN and END User Language statements.
# Start the Debugger Client.
# Make sure the Client is '''not''' automatically maintaining a proxy server for you:
## From the <var>File</var> menu, select <var>Preferences.</var> 
## Make sure the Automatically Maintain IE proxy settings checkbox is clear. 
# In the browser you use to invoke debugging, confirm that the Debugger Client is not [[Configure web browser (Janus Debugger only)|defined as a proxy server]].
# 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 <var>Source Code</var> page.
# Work with the procedure code in the Client as usual.
: As the code is evaluated, output [[Viewing the web output buffer|destined for a web page]] goes to a Web Buffer page in the Client: 

[[File:sirdebwebthrd3a_zoom70.gif|604x356px|sirdebWebThrd3a]] 

: When code execution completes, output (including error messages and Web Buffer contents) is sent to the browser instead of to the <var>Model 204</var> "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 [[TN3270 DEBUG Syntax#TN3270 DEBUG SUSPEND|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 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 <var>Model 204</var> host has no effect on debugging — the command line thread is separate from the web thread. 

[[Category:Debugger Home]]

TN3270 DEBUG on web threads - Revision history

Ekern at 14:32, 25 April 2023