Test the end to end configuration: Difference between revisions

Revision as of 03:25, 19 November 2022

Subsections follow for the Janus Debugger and for the TN3270 Debugger. It is assumed that the Debugger Client is up and running.

Janus Debugger

1. Open the browser you just set up to use the Debugger as a proxy.

2. >Invoke the URL of a User Language-based page from your target Janus Web Server.

Note: If you normally use "https://%22 and not "http://%22 to begin the URL (that is, your Web Server is SSL-secured), and if you set up the debuggerConfig.xml file for SSL support, make sure that you use "http://" here now to access the secured web port.

The source code of the program should appear in the Source Code page of the Client with its procedure name displayed in the title bar, similar to the following Source Code display:

If instead, you receive a Communication Error message that reports an "error while communicating with the remote host," you may have an error in the debuggerConfig.xml 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.

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).

For an archive of information about features that are new or enhanced in the latest version of the Debugger Client, see the Release Notes.

TN3270 Debugger

1. From the Model 204 command prompt or within a BATCH2 input stream, start a TN3270 Debugger session:

TN3270 DEBUG ON janClientPort pcHost pcPort workerPort

where:

janClientPort	The name of the Janus client socket port that is defined for the `TN3270 Debugger` to use to contact the Debugger Client workstation. This port must be started.
pcHost	The workstation running the Debugger Client. This may be an IP number or a DNS name, as described earlier.
pcPort	The workstation port number on which the Debugger Client is listening. As described earlier, this is typically 8081.
workerPort	The port number in your Online that is defined for worker threads. This can be the same port number that provides worker threads for the Janus Debugger, as well.

For example:

>TN3270 DEBUG ON DEBCLIENT 198.242.244.234 8081 3226

2. Verify that you receive a message similar to:

*** MSIR.0915: Debugging is on; client is 198.242.244.234 port 8081,
sessionID: 00000069D812279

3. On the Debugger Client, verify that a "busy" cursor displays, as well as a Waiting for Online message in the Status bar:

Additional Audit Trail page messages identify the Debugger Server's port and the address of its Online host, the user number assigned to the logged-in Model 204 user, as well as the Model 204 version.

From this point on, any User Language program you initiate from the Model 204 command line will appear in the Source Code tab of the Debugger Client GUI for debugging, the procedure name will appear in the Client's title bar, and the "busy" cursor and Waiting for Online message will display between requests until your session ends.

4. Turn off the TN3270 Debugger by doing either of the following:

From the Model 204 command prompt (or at the end of your BATCH2 stream), issue:

TN3270 DEBUG OFF

You should receive this response in Model 204:

*** MSIR.0913: TN3270 Debugger is now off

On the Debugger Client, Online has disconnected displays in the Status area.

Log off of Model 204 (any logoff is an implied TN3270 DEBUG OFF).

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

5. Reissue the command from step 1 to restart the Debugger Client, and the Debugger Client is ready to use.

From the Client GUI, you can control the execution of your Model 204 application's User Language code (see Getting started).

For an archive of information about features that are new or enhanced in the latest version of the Debugger Client, see the Release Notes.

@@ Line 21: / Line 21: @@
 === TN3270 Debugger ===
-. <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>
+: 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="f_EmphRedMonoItal">janClientPort pcHost pcPort workerPort</span></p>
-<span class="f_ListContinue">where: </span>
+:: <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="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>
@@ Line 36: / Line 36: @@
 <span class="f_DefListDD">This port must be started. </span>
 |-
-| <span class="term">pcHost</span><span class="f_DefListDD"> </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="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="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><span class="f_Product">Janus Debugger,</span><span class="f_DefListDD"> as well.</span>
 |}
@@ Line 48: / Line 48: @@
 </div>
-<span class="f_ListContinue">For example: </span>
+:: For example:
 <p class="syntax">>TN3270 DEBUG ON DEBCLIENT 198.242.244.234 8081 3226 </p>
-. <span class="f_ListNum1">Verify that you receive a message similar to: </span>
+: 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>
-. <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>
+: 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>
+:: 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>
+:: 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>
-. <span class="f_ListNum1">Turn off the </span><var>TN3270 Debugger</var><span class="f_ListNum1"> by doing either of the following:</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>
@@ Line 73: / Line 73: @@
 <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.
+:: 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>
+: '''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>
-. <span class="f_ListNum1">Reissue the command from step 1 to restart the Debugger Client, and the Debugger Client is ready to use. </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.html|Getting started]]). </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 [[release_notes.html|Release Notes]].
+:: 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]].
 [[Category:Debugger Home]]

Test the end to end configuration: Difference between revisions

Revision as of 03:25, 19 November 2022

Contents

Janus Debugger

TN3270 Debugger

Navigation menu