View source for Test the end to end configuration

__TOC__
<span class="f_Para">Subsections follow for the </span><var>Janus Debugger</var><span class="f_Para"> and for the </span><var>TN3270 Debugger</var><span class="f_Para">. It is assumed that the Debugger Client is up and running.</span>

=== Janus Debugger ===
# Open the <span class="f_ListNum1">browser you just [[Configure web browser (Janus Debugger only)|set up]] to use the Debugger as a proxy. </span>
# Invoke the URL of a User Language-based page from your target Janus Web Server. 

'''Note:'''<span class="f_ListNote"> If you normally use &quot;https://&quot; and not &quot;http://&quot; to begin the URL (that is, your Web Server is SSL-secured), and if you [[Customize debuggerConfig file|set up]] the debuggerConfig.xml file for SSL support, make sure that you use &quot;</span>'''http'''<span class="f_ListNote">://&quot; here now to access the secured web port. </span>
: The source code of the program should appear in the <var>Source Code</var><span class="f_ListContinue"> page of the Client with its procedure name displayed in the title bar, similar to the following </span><var>Source Code</var><span class="f_ListContinue"> display: </span>

: [[File:jdgui8_zoom60.gif|619x406px|jdgui8]]<span class="f_ImageCaption"> </span>

: If instead, you receive a Communication Error message that reports an &quot;error while communicating with the remote host,&quot; you may have an error in the <var>debuggerConfig.xml </var><span class="f_ListContinue">[[Customize debuggerConfig file|settings]]. If so, and you find the error, restart the Debugger Client and try the test URL again. For more information about error handling, see [[How the Janus Debugger handles communication breaks|How the Janus Debugger handles communication breaks]]. </span>

<span class="f_Para">The Debugger Client is ready to use. From the Client GUI, you can control the execution of your web application's User Language code (see [[Getting started (Debugger)|Getting Started]]). </span>

<span class="f_Para">For an archive of information about features that are new or enhanced in the latest version of the Debugger Client, see the [[Release notes for Debugger|Release Notes]]. </span>

=== TN3270 Debugger ===

: 1. <span class="f_ListNum1">From the </span><var>Model 204</var><span class="f_ListNum1"> command prompt or within a BATCH2 input stream, start a </span><var>TN3270 Debugger</var><span class="f_ListNum1"> session: </span>

<p class="syntax"><span class="f_CodeExList" style="font-weight: bold;">TN3270 DEBUG ON </span><span class="term">janClientPort pcHost pcPort workerPort</span></p>

:: <span class="f_ListContinue">where: </span>

<div style="text-align: left; text-indent: 0; padding: 0 0 0 0; margin: 10px 0 10px 30px;">

{|
|width="50%"| <span class="term">'''janClientPort'''</span><span class="f_DefListDD"> </span>
|width="50%"|
<span class="f_DefListDD">The name of the Janus client socket port that [[Define and start a client socket port (TN3270 Debugger only)|is defined]] for the </span><var>TN3270 Debugger</var><span class="f_DefListDD"> to use to contact the Debugger Client workstation. </span>

<span class="f_DefListDD">This port must be started. </span>
|-
| <span class="term">'''pcHost'''</span><span class="f_DefListDD"> </span>
| <span class="f_DefListDD">The workstation running the Debugger Client. This may be an IP number or a DNS name, as [[Perform preliminary tasks|described earlier]]. </span>
|-
| <span class="term">'''pcPort'''</span><span class="f_DefListDD"> </span>
| <span class="f_DefListDD">The workstation port number on which the Debugger Client is listening. As [[Perform preliminary tasks|described earlier]], this is typically 8081.</span>
|-
| <span class="term">'''workerPort'''</span><span class="f_DefListDD"> </span>
| <span class="f_DefListDD">The port number in your Online that [[Define and start the Debugger Server port|is defined]] for worker threads. This can be the same port number that provides worker threads for the </span><var>Janus Debugger,</var><span class="f_DefListDD"> as well.</span>
|}
</div>

: For example: 
<p class="syntax">>TN3270 DEBUG ON DEBCLIENT 198.242.244.234 8081 3226 </p>

: 2. <span class="f_ListNum1">Verify that you receive a message similar to: </span>

<p class="syntax"><span class="f_CodeExList">***</span> <span class="f_CodeExList">MSIR.0915:</span> <span class="f_CodeExList">Debugging</span> <span class="f_CodeExList">is</span> <span class="f_CodeExList">on;</span> <span class="f_CodeExList">client</span> <span class="f_CodeExList">is</span> <span class="f_CodeExList">198.242.244.234</span> <span class="f_CodeExList">port 8081,</span> <br />
<span class="f_CodeExList">    sessionID:</span> <span class="f_CodeExList">00000069D812279 </span></p>

: 3. <span class="f_ListNum1">On the Debugger Client, verify that a &quot;busy&quot; cursor displays, as well as a </span><span class="f_Monospace">Waiting for Online</span><span class="f_ListNum1"> message in the [[Status bar|Status bar]]: </span>

[[File:cliguinew8a_zoom60.gif|619x406px|cliguiNew8a]]<span class="f_ListContinue"> </span>

:: Additional <var>Audit Trail</var><span class="f_ListContinue"> page messages identify the Debugger Server's port and the address of its Online host, the user number assigned to the logged-in </span><var>Model 204</var><span class="f_ListContinue"> user, as well as the </span><var>Model 204</var><span class="f_ListContinue"> version. </span>
:: From this point on, any User Language program you initiate from the <var>Model 204</var><span class="f_ListContinue"> command line will appear in the </span><var>Source Code</var><span class="f_ListContinue"> tab of the Debugger Client GUI for debugging, the procedure name will appear in the Client's title bar, and the &quot;busy&quot; cursor and </span><span class="f_Monospace">Waiting for Online</span><span class="f_ListContinue"> message will display between requests until your session ends. </span>

: 4. <span class="f_ListNum1">Turn off the </span><var>TN3270 Debugger</var><span class="f_ListNum1"> by doing either of the following:</span>

* <span class="f_ListBul2">From the </span><var>Model 204</var><span class="f_ListBul2"> command prompt (or at the end of your BATCH2 stream), issue: </span>

<p class="syntax"><span class="f_CodeExList2">TN3270 DEBUG OFF</span></p>

: <span class="f_ListContinue2">You should receive this response in </span><var>Model 204</var><span class="f_ListContinue2">: </span>

<p class="syntax"><span class="f_CodeExList2">***  MSIR.0913: TN3270 Debugger is now off </span></p>
: On the Debugger Client, </span><span class="f_Monospace">Online has disconnected</span><span class="f_ListContinue2"> displays in the Status area.

* <span class="f_ListBul2">Log off of </span><var>Model 204</var><span class="f_ListBul2"> (any logoff is an implied TN3270 DEBUG OFF).</span>

: '''Note:'''<span class="f_ListNote"> Explicitly turning off the Debugger is necessary if you are using the </span><var>Janus Debugger</var><span class="f_ListNote"> as well as the </span><var>TN3270 Debugger</var><span class="f_ListNote"> for the same Online and worker port. To switch from a </span><var>TN3270 Debugger</var><span class="f_ListNote"> session to a </span><var>Janus Debugger</var><span class="f_ListNote"> session, you must explicitly drop the </span><var>TN3270 Debugger</var><span class="f_ListNote"> session. The </span><var>Janus Debugger</var><span class="f_ListNote"> automatically closes its connections and does </span>'''not'''<span class="f_ListNote"> require an explicit notification to switch or end a session. </span>

: 5. <span class="f_ListNum1">Reissue the command from step 1 to restart the Debugger Client, and the Debugger Client is ready to use. </span>
:: From the Client GUI, you can control the execution of your <var>Model 204</var><span class="f_ListContinue"> application's User Language code (see [[Getting started (Debugger)|Getting started]]). </span>
:: For an archive of information about features that are new or enhanced in the latest version of the Debugger Client, see the [[Debugger Release Notes|Release Notes]].

[[Category:Debugger Home]]