SIRIUS DEBUG, SIRDEBUG, or SIRIUSDEBUG command: Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (replace Sirius with TN3270)
 
(9 intermediate revisions by 3 users not shown)
Line 1: Line 1:
Starts and stops the <var class="product">[[Debugger|Sirius Debugger]]</var> (for debugging 3270, BATCH2, or other non-web
<p class="note"><b>Note:</b> This is a <var class="product">[[Sirius Mods]]</var>-only command prior to Version 7.5 of <var class="product">[[Model 204]]</var>. <br/>As of V7.6 of <var class="product">Model 204</var>, the <var>TN3270 DEBUG</var> synonym is available for the command.</p>
applications), and can also be used for debugging programs served by <var class="product">[[Janus Web Server]]</var> threads.
 
Starts and stops the <var class="product">[[Debugger|TN3270 Debugger]]</var> (for debugging 3270, BATCH2, or other non-web applications), and can also be used for debugging programs served by <var class="product">[[Janus Web Server]]</var> threads.
Connects to a Debugger Client on a workstation, from where debugging is
Connects to a Debugger Client on a workstation, from where debugging is
orchestrated via the Client GUI.
orchestrated with the Client GUI.


The commands <code>SIRIUSDEBUG</code>, <code>SIRDEBUG</code>, and <code>SIRIUS DEBUG</code>
The commands <code>SIRIUSDEBUG</code>, <code>SIRDEBUG</code>, and <code>SIRIUS DEBUG</code>, and <code>TN3270 DEBUG</code> are interchangeable, and a mixture of them is used on this page.
are interchangeable, and a mixture of them is used on this page.
The general form of the command is:
The general form of the command is:
===Syntax===
 
  SIRDEBUG {ON onParams | OFF | SUSPEND | RESUME | STATUS | CLIENTCOMMAND cmdStr}
==Syntax==
<p class="syntax"><span class="squareb">{</span> <span class="literal">SIRIUS DEBUG</span> <span class="squareb">|</span> <span class="literal">SIRIUSDEBUG</span> <span class="squareb">|</span> <span class="literal">SIRDEBUG</span> <span class="squareb">|</span> <span class="literal">TN3270 DEBUG</span> <span class="squareb">}</span>  -
<span class="squareb">{ </span><span class="literal">ON</span> <span class="term">onParams</span> <span class="squareb">|</span> <span class="literal">OFF</span> <span class="squareb">|</span> <span class="literal">SUSPEND</span> <span class="squareb">|</span> <span class="literal">RESUME</span> <span class="squareb">|</span> <span class="literal">STATUS</span> <span class="squareb">|</span> <span class="literal">CLIENTCOMMAND</span> <span class="term">cmdStr</span> <span class="squareb">}</span> </p>


Where:
Where:
<ul>
<ul>
<li>The <var>ON</var> subcommand starts a <var class="product">Sirius Debugger</var> session (it requires [[#SIRIUS DEBUG ON|additional
<li>The <var>ON</var> subcommand starts a <var class="product">TN3270 Debugger</var> session (it requires [[#SIRIUS DEBUG ON|additional parameters]]).
parameters]]).
It can also be used for debugging <var class="product">Janus Web Server</var> threads. </li>
It can also be used for debugging <var class="product">Janus Web Server</var> threads.
 
<li>The <var>OFF</var> subcommand stops a debugging session.
<li>The <var>OFF</var> subcommand stops a debugging session. </li>
 
<li>The <var>SUSPEND</var> and <var>RESUME</var> subcommands discontinue and continue a
<li>The <var>SUSPEND</var> and <var>RESUME</var> subcommands discontinue and continue a
debugging session.
debugging session. </li>
 
<li>The <var>STATUS</var> subcommand gets a status report about the worker threads for the
<li>The <var>STATUS</var> subcommand gets a status report about the worker threads for the
<var class="product">[[Debugger|Janus Debugger]]</var>, the <var class="product">Sirius Debugger</var>, or both.
<var class="product">[[Debugger|Janus Debugger]]</var>, the <var class="product">TN3270 Debugger</var>, or both. </li>
 
<li>The <var>CLIENTCOMMAND</var> subcommand sends a command to the Debugger Client (it requires [[#SIRIUS DEBUG CLIENTCOMMAND|additional
<li>The <var>CLIENTCOMMAND</var> subcommand sends a command to the Debugger Client (it requires [[#SIRIUS DEBUG CLIENTCOMMAND|additional
parameters]]).   
parameters]]).   
</ul>
</ul>


This command will perform no useful processing unless a site is authorized
This command will perform no useful processing unless a site is authorized
for the <var class="product">Sirius Debugger</var> (and for <var class="product">Janus Web</var> threads, <var class="product">Janus Debugger</var>).
for the <var class="product">TN3270 Debugger</var> (and for <var class="product">Janus Web</var> threads, <var class="product">Janus Debugger</var>).
For more information, see the <i>[http://sirius-software.com/maint/download/jdebugr.pdf Janus/Sirius Debugger User's Guide]</i>.
For more information, see the <var class="book">[[Media:JdebugrNew.pdf|Janus/TN3270 Debugger User's Guide]]</var>.


====SIRIUS DEBUG ON====
===SIRIUS DEBUG ON===
To initiate a Sirius Debugger session, you issue the SIRIUS DEBUG ON command from
To initiate a TN3270 Debugger session, you issue the <var>SIRIUS DEBUG ON</var> command from
the Model 204 command prompt or within a BATCH2 input stream. The command
the Model&nbsp;204 command prompt or within a BATCH2 input stream. The command
requires the parameters described below that identify the network ports and the
requires the parameters described below that identify the network ports and the
workstation used in your debugging session. The values of these parameters are
workstation used in your debugging session. The values of these parameters are
established during product installation:
established during product installation:
<p class="syntax">SIRIUS DEBUG ON [*|janClientPort [.|pcHost [pcPort [workerPort]]]]
<p class="syntax"><span class="squareb">{</span> <span class="literal">SIRIUS DEBUG</span> <span class="squareb">|</span> <span class="literal">SIRIUSDEBUG</span> <span class="squareb">|</span> <span class="literal">SIRDEBUG</span> <span class="squareb">|</span> <span class="literal">TN3270 DEBUG</span> <span class="squareb">}</span>  -
[*|<span class="term">janClientPort</span> [.|<span class="term">pcHost</span> [<span class="term">pcPort</span> [<span class="term">workerPort</span>]]]]
</p>
</p>
where:
Where:
<dl>
<table>
<dt>janClientPort
<tr><th>janClientPort</th>
<dd>The name of the Janus client socket port that is defined
<td>The name of the Janus client socket port that is defined for the TN3270 Debugger to use to contact the Debugger Client workstation.
for the Sirius Debugger to use to contact the
<p>
Debugger Client workstation.
As of Sirius Mods version 7.9, the default value is an asterisk (<tt>*</tt>), which means to use a Janus port whose definition includes the <var>MASTER</var> parameter. Such a port can be accessed on a Debugger connection request without specifying its port name on the <var>SIRIUS DEBUG ON</var> command.</p>
<p>
This port must be started.</p></td></tr>
   
   
As of Sirius Mods version 7.9, the default value is an
<tr><th>pcHost
asterisk (*), which means to use a Janus port whose
<td>The workstation running the Debugger Client. This may be an IP number or a DNS name, as described during product installation.
definition includes the MASTER parameter. Such a port
<p>
can be accessed on a Debugger connection request
As of Sirius Mods version 7.9, the default value is a period (<tt>.</tt>), which means to use the IP address of the machine on which the <var>SIRIUS DEBUG ON</var> command is issued.</p></td></tr>
without specifying its port name on the SIRIUS DEBUG
ON command.
   
   
This port must be started.
<tr><th>pcPort
<td>The workstation port number on which the Debugger Client is listening. As described during product installation, this is typically <code>8081</code>.
<p>
The Model&nbsp;204 User&nbsp;0 parameter <var>[[SDEBGUIP parameter|SDEBGUIP]]</var> sets the default value of this port. Valid values for this parameter, which is also resettable by the system manager, range from 0 to 65535. If 0, no default is set, and the parameter's value must be explicitly specified in the <var>SIRIUS DEBUG ON</var>
command. A <code>VIEW SDEBGUIP</code> command returns the current setting of <var>SDEBGUIP</var>.</p>
   
   
<dt>pcHost
<p class="note"><b>Note:</b> As shown in an example below, to omit an explicit
<dd>The workstation running the Debugger Client. This may
specification of <var class="term">pcPort</var> (letting it default to the
be an IP number or a DNS name, as described during
setting of <var>SDEBGUIP</var>) but still provide an explicit
product installation.
value for <var class="term">workerPort</var>, use an asterisk (<tt>*</tt>) for the
missing <var class="term">pcPort</var> specification to indicate the
respective position of the parameter values. </p></td></tr>
   
   
As of Sirius Mods version 7.9, the default value is a
<tr><th>workerPort
period (.), which means to use the IP address of the
<td>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.
machine on which the SIRIUS DEBUG ON command is
<p>
issued.
The Model 204 User&nbsp;0 parameter <var>[[SDEBWRKP parameter|SDEBWRKP]]</var> sets the default value of this port. Valid values for this parameter, which is also resettable by the system manager, range from 0 to 65535. If 0, no default is set, and the parameter's value must be explicitly specified in the <var>SIRIUS DEBUG ON</var> command. A <code>VIEW SDEBWRKP</code> command returns the current setting of <var>SDEBWRKP</var>.</p>
<p>
<dt>pcPort
For example: </p>
<dd>The workstation port number on which the Debugger
<p class="code">SIRIUSDEBUG ON DEBCLIENT 198.242.244.235 8081 3226</p>
Client is listening. As described during product
<p>
installation, this is typically 8081.
After issuing the command, you receive a message similar to this: </p>
<p class="output">&#x2a;&#x2a;&#x2a; MSIR.0915: Debugging is on; client is 198.242.244.235 port 8081, sessionID: 00000069D812279 </p>
As of Version 7.0 of the Sirius Mods, the Model 204
<p>
User 0 parameter SDEBGUIP sets the default value of
If you had set the workstation and worker port numbers with the <var>SDEBGUIP</var> and
this port. Valid values for this parameter, which is also
<var>SDEBWRKP</var> User&nbsp;0 parameters, as revealed by a <var>VIEW</var> command: </p>
resettable by the system manager, range from 0 to
65535. If 0, no default is set, and the parameter's value
must be explicitly specified in the SIRIUS DEBUG ON
command. A VIEW SDEBGUIP command returns the
current setting of SDEBGUIP.
Note: As shown in an example below, to omit an explicit
specification of pcPort (letting it default to the
setting of SDEBGUIP) but still provide an explicit
value for workerPort, use an asterisk (*) for the
missing pcPort specification to indicate the
respective position of the parameter values.
<dt>workerPort
<dd>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.
As of Version 7.0 of the Sirius Mods, the Model 204
User 0 parameter SDEBWRKP sets the default value of
this port. Valid values for this parameter, which is also
resettable by the system manager, range from 0 to
65535. If 0, no default is set, and the parameter's value
must be explicitly specified in the SIRIUS DEBUG ON
command. A VIEW SDEBWRKP command returns the
current setting of SDEBWRKP.
For example:
<p class="code">SIRIUS DEBUG ON DEBCLIENT 198.242.244.235 8081 3226</p>
After issuing the command, you receive a message similar to this:
<p class="output">&#x2a;&#x2a;&#x2a; MSIR.0915: Debugging is on; client is 198.242.244.235 port 8081,
sessionID: 00000069D812279
</p>
If you had set the workstation and worker port numbers with the SDEBGUIP and
SDEBWRKP User 0 parameters, as revealed by a VIEW command:
<p class="code">VIEW SDEBGUIP,SDEBWRKP</p>
<p class="code">VIEW SDEBGUIP,SDEBWRKP</p>
<p class="output">SDEBGUIP 8081 SIRIUS DEBUG DEFAULT GUI PORT NUMBER
<p class="output">SDEBGUIP 8081 SIRIUS DEBUG DEFAULT GUI PORT NUMBER
SDEBWRKP 3226 SIRIUS DEBUG DEFAULT WORKER PORT NUMBER
SDEBWRKP 3226 SIRIUS DEBUG DEFAULT WORKER PORT NUMBER
</p>
</p>
The previous DEBUG ON command could be simplified:
The previous <var>DEBUG ON</var> command could be simplified:
<p class="code">SIRIUS DEBUG ON DEBCLIENT 198.242.244.235</p>
<p class="code">SIRIUSDEBUG ON DEBCLIENT 198.242.244.235</p>
<p>
In this case, you receive different confirmation messages:
In this case, you receive different confirmation messages: </p>
<p class="output">&#x2a;&#x2a;&#x2a; MSIR.0942: Sirius Debugger GUI port defaulted to 8081
<p class="output">&#x2a;** MSIR.0942: Sirius Debugger GUI port defaulted to 8081
&#x2a;&#x2a;&#x2a; MSIR.0942: Sirius Debugger Worker port defaulted to 3226
&#x2a;** MSIR.0942: Sirius Debugger Worker port defaulted to 3226
&#x2a;&#x2a;&#x2a; MSIR.0915: Debugging is on: client is 198.242.244.235 port 8081,
&#x2a;** MSIR.0915: Debugging is on: client is 198.242.244.235 port 8081, sessionID: sessionID: 00000069D812279</p>
sessionID: sessionID: 00000069D812279
<p>
</p>
You can also use asterisks to indicate that the port defaults are to be taken. These
You can also use asterisks to indicate that the port defaults are to be taken. These
two commands are equivalent:
two commands are equivalent: </p>
<p class="code">SIRIUS DEBUG ON DEBCLIENT 198.242.244.235 * *
<p class="code">SIRIUSDEBUG ON DEBCLIENT 198.242.244.235 * *
SIRIUS DEBUG ON DEBCLIENT 198.242.244.235
SIRIUSDEBUG ON DEBCLIENT 198.242.244.235 </p>
</p>
<p>
You receive an error message if you use either of the above commands without
You receive an error message if you use either of the above commands without
having set the default port values. To take the GUI port default but specify a value
having set the default port values. To take the GUI port default but specify a value
for the worker port, you must use an asterisk in the GUI port position:
for the worker port, you must use an asterisk in the GUI port position: </p>
<p class="code">SIRIUS DEBUG ON DEBCLIENT 198.242.244.235 * 3226</p>
<p class="code">SIRIUSDEBUG ON DEBCLIENT 198.242.244.235 * 3226</p></td></tr>
</dl>
</table>
   
   
You can further simplify the connection command by taking advantage of the
You can further simplify the connection command by taking advantage of the
janClientPort and pcHost parameter defaults (added in Sirius Mods 7.9). If the
<var class="term">janClientPort</var> and <var class="term">pcHost</var> parameter defaults (added in Sirius Mods 7.9). If the <code>DEBCLIENT</code> port is defined with the <var>MASTER</var> parameter, and <var>SDEBGUIP</var> and <var>SDEBWRKP</var> are as above, these commands are equivalent:
DEBCLIENT port is defined with the MASTER parameter, and SDEBGUIP and
SDEBWRKP are as above, these commands are equivalent:
<p class="code">SIRIUS DEBUG ON * .
<p class="code">SIRIUS DEBUG ON * .
SIRIUS DEBUG ON
SIRIUS DEBUG ON
</p>
</p>
On the Debugger Client, Connection from Online displays in the Status bar after
On the Debugger Client, <code>Connection from Online</code> displays in the Status bar after
the DEBUG ON command is issued. This indicates that the Debugger is "on" and
the <var>DEBUG ON</var> command is issued. This indicates that the Debugger is "on" and
awaiting the next program to debug.
awaiting the next program to debug.
   
   
After the command runs successfully, any User Language program you initiate from the
After the command runs successfully, any <var class="product">SOUL</var> program you initiate from the <var class="product">Model 204</var> command line will appear in the Source Code tab of the Debugger Client GUI for debugging.
Model 204 command line will appear in the Source Code tab of the Debugger Client GUI
for debugging.


====SIRIUS DEBUG CLIENTCOMMAND====
===SIRIUS DEBUG CLIENTCOMMAND===
Available as of version 7.8 of the <var class="product">Sirius Mods</var>, <var>SIRIUS DEBUG CLIENTCOMMAND</var> lets you send a command string to be executed by the Debugger Client. The parameter of <var>SIRIUS DEBUG CLIENTCOMMAND</var> is the command string you want to send.  If it contains more than one word, enclose it in apostrophes.
Available as of version 7.8 of the <var class="product">Sirius Mods</var>, <var>SIRIUS DEBUG CLIENTCOMMAND</var> lets you send a command string to be executed by the Debugger Client. The parameter of <var>SIRIUS DEBUG CLIENTCOMMAND</var> is the command string you want to send.  If it contains more than one word, enclose it in apostrophes.


<p class="syntax"><span class="literal">SIRIUS DEBUG CLIENTCOMMAND</span> <span class="term">cmdStr</span> </p>
<p class="syntax"><span class="squareb">{</span> <span class="literal">SIRIUS DEBUG</span> <span class="squareb">|</span> <span class="literal">SIRIUSDEBUG</span> <span class="squareb">|</span> <span class="literal">SIRDEBUG</span> <span class="squareb">|</span> <span class="literal">TN3270 DEBUG</span> <span class="squareb">}</span>
<span class="literal">CLIENTCOMMAND</span> <span class="term">cmdStr</span> </p>


Examples:
Examples:
<p class="code">SIRIUS DEBUG CLIENTCOMMAND clearWatch   
<p class="code">SIRDEBUG CLIENTCOMMAND clearWatch   
   
   
SIRIUS DEBUG CLIENTCOMMAND 'Addwatch %watchthis'   
SIRDEBUG CLIENTCOMMAND 'Addwatch %watchthis'   
   
   
SIRIUS DEBUG CLIENTCOMMAND 'Macro mymacro %s'
SIRDEBUG CLIENTCOMMAND 'Macro mymacro %s'
</p>
</p>


If the <var class="product">Sirius Debugger</var> is not currently in a session, issuing <code>SIRIUS DEBUG CLIENTCOMMAND</code> has no effect and receives a harmless error message.  
If the <var class="product">TN3270 Debugger</var> is not currently in a session, issuing <code>SIRIUS DEBUG CLIENTCOMMAND</code> has no effect and receives a harmless error message.  


You can also send a command string to be executed by the Debugger Client with the <var>[[DebuggerTools class|DebuggerTools]]</var> <var>[[ClientCommand (DebuggerTools subroutine)|ClientCommand]]</var> and <var>[[Command (DebuggerTools subroutine)|Command]] methods.  
You can also send a command string to be executed by the Debugger Client with the <var>DebuggerTools</var> class <var>[[ClientCommand (DebuggerTools subroutine)|ClientCommand]]</var> and <var>[[Command (DebuggerTools subroutine)|Command]]</var> methods.  


[[Category:Commands]]
[[Category:Commands]]
[[Category:User commands]]
[[Category:User commands]]

Latest revision as of 19:51, 20 May 2015

Note: This is a Sirius Mods-only command prior to Version 7.5 of Model 204.
As of V7.6 of Model 204, the TN3270 DEBUG synonym is available for the command.

Starts and stops the TN3270 Debugger (for debugging 3270, BATCH2, or other non-web applications), and can also be used for debugging programs served by Janus Web Server threads. Connects to a Debugger Client on a workstation, from where debugging is orchestrated with the Client GUI.

The commands SIRIUSDEBUG, SIRDEBUG, and SIRIUS DEBUG, and TN3270 DEBUG are interchangeable, and a mixture of them is used on this page. The general form of the command is:

Syntax

{ SIRIUS DEBUG | SIRIUSDEBUG | SIRDEBUG | TN3270 DEBUG } - { ON onParams | OFF | SUSPEND | RESUME | STATUS | CLIENTCOMMAND cmdStr }

Where:

  • The ON subcommand starts a TN3270 Debugger session (it requires additional parameters). It can also be used for debugging Janus Web Server threads.
  • The OFF subcommand stops a debugging session.
  • The SUSPEND and RESUME subcommands discontinue and continue a debugging session.
  • The STATUS subcommand gets a status report about the worker threads for the Janus Debugger, the TN3270 Debugger, or both.
  • The CLIENTCOMMAND subcommand sends a command to the Debugger Client (it requires additional parameters).

This command will perform no useful processing unless a site is authorized for the TN3270 Debugger (and for Janus Web threads, Janus Debugger). For more information, see the Janus/TN3270 Debugger User's Guide.

SIRIUS DEBUG ON

To initiate a TN3270 Debugger session, you issue the SIRIUS DEBUG ON command from the Model 204 command prompt or within a BATCH2 input stream. The command requires the parameters described below that identify the network ports and the workstation used in your debugging session. The values of these parameters are established during product installation:

{ SIRIUS DEBUG | SIRIUSDEBUG | SIRDEBUG | TN3270 DEBUG } - [*|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.

As of Sirius Mods version 7.9, the default value is an asterisk (*), which means to use a Janus port whose definition includes the MASTER parameter. Such a port can be accessed on a Debugger connection request without specifying its port name on the SIRIUS DEBUG ON command.

This port must be started.

pcHost The workstation running the Debugger Client. This may be an IP number or a DNS name, as described during product installation.

As of Sirius Mods version 7.9, the default value is a period (.), which means to use the IP address of the machine on which the SIRIUS DEBUG ON command is issued.

pcPort The workstation port number on which the Debugger Client is listening. As described during product installation, this is typically 8081.

The Model 204 User 0 parameter SDEBGUIP sets the default value of this port. Valid values for this parameter, which is also resettable by the system manager, range from 0 to 65535. If 0, no default is set, and the parameter's value must be explicitly specified in the SIRIUS DEBUG ON command. A VIEW SDEBGUIP command returns the current setting of SDEBGUIP.

Note: As shown in an example below, to omit an explicit specification of pcPort (letting it default to the setting of SDEBGUIP) but still provide an explicit value for workerPort, use an asterisk (*) for the missing pcPort specification to indicate the respective position of the parameter values.

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.

The Model 204 User 0 parameter SDEBWRKP sets the default value of this port. Valid values for this parameter, which is also resettable by the system manager, range from 0 to 65535. If 0, no default is set, and the parameter's value must be explicitly specified in the SIRIUS DEBUG ON command. A VIEW SDEBWRKP command returns the current setting of SDEBWRKP.

For example:

SIRIUSDEBUG ON DEBCLIENT 198.242.244.235 8081 3226

After issuing the command, you receive a message similar to this:

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

If you had set the workstation and worker port numbers with the SDEBGUIP and SDEBWRKP User 0 parameters, as revealed by a VIEW command:

VIEW SDEBGUIP,SDEBWRKP

SDEBGUIP 8081 SIRIUS DEBUG DEFAULT GUI PORT NUMBER SDEBWRKP 3226 SIRIUS DEBUG DEFAULT WORKER PORT NUMBER

The previous DEBUG ON command could be simplified:

SIRIUSDEBUG ON DEBCLIENT 198.242.244.235

In this case, you receive different confirmation messages:

*** MSIR.0942: Sirius Debugger GUI port defaulted to 8081 *** MSIR.0942: Sirius Debugger Worker port defaulted to 3226 *** MSIR.0915: Debugging is on: client is 198.242.244.235 port 8081, sessionID: sessionID: 00000069D812279

You can also use asterisks to indicate that the port defaults are to be taken. These two commands are equivalent:

SIRIUSDEBUG ON DEBCLIENT 198.242.244.235 * * SIRIUSDEBUG ON DEBCLIENT 198.242.244.235

You receive an error message if you use either of the above commands without having set the default port values. To take the GUI port default but specify a value for the worker port, you must use an asterisk in the GUI port position:

SIRIUSDEBUG ON DEBCLIENT 198.242.244.235 * 3226

You can further simplify the connection command by taking advantage of the janClientPort and pcHost parameter defaults (added in Sirius Mods 7.9). If the DEBCLIENT port is defined with the MASTER parameter, and SDEBGUIP and SDEBWRKP are as above, these commands are equivalent:

SIRIUS DEBUG ON * . SIRIUS DEBUG ON

On the Debugger Client, Connection from Online displays in the Status bar after the DEBUG ON command is issued. This indicates that the Debugger is "on" and awaiting the next program to debug.

After the command runs successfully, any SOUL program you initiate from the Model 204 command line will appear in the Source Code tab of the Debugger Client GUI for debugging.

SIRIUS DEBUG CLIENTCOMMAND

Available as of version 7.8 of the Sirius Mods, SIRIUS DEBUG CLIENTCOMMAND lets you send a command string to be executed by the Debugger Client. The parameter of SIRIUS DEBUG CLIENTCOMMAND is the command string you want to send. If it contains more than one word, enclose it in apostrophes.

{ SIRIUS DEBUG | SIRIUSDEBUG | SIRDEBUG | TN3270 DEBUG } CLIENTCOMMAND cmdStr

Examples:

SIRDEBUG CLIENTCOMMAND clearWatch SIRDEBUG CLIENTCOMMAND 'Addwatch %watchthis' SIRDEBUG CLIENTCOMMAND 'Macro mymacro %s'

If the TN3270 Debugger is not currently in a session, issuing SIRIUS DEBUG CLIENTCOMMAND has no effect and receives a harmless error message.

You can also send a command string to be executed by the Debugger Client with the DebuggerTools class ClientCommand and Command methods.