DEBUG command: Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (Automatically generated page update)
 
 
(10 intermediate revisions by 4 users not shown)
Line 2: Line 2:
<dl>
<dl>
<dt>Privileges
<dt>Privileges
<dd>Defined in the subsystem definition, the user's SCLASS must be granted either TEST or DEBUG privileges.
<dd>Defined in the subsystem definition, the user's [[SCLASS]] must be granted either <var>TEST</var> or <var>DEBUG</var> privileges.
<dt>Function
<dt>Function
<dd>Displays and allows changes to a communication global variable
<dd>Displays and allows changes to a communication global variable
</dl>
</dl>
==Syntax==
==Syntax==
<p class="syntax">DEBUG <b>SUBSYS</b>TEM <i>subsysname</i> [<i>parameters</i>]
<p class="syntax">DEBUG <b>SUBSYS</b>TEM <span class="term">subsysname</span> [<span class="term">parameters</span>]
</p>
</p>
   
   
<b>Where:</b>
Where:
<table>  
<table>  
<tr>
<tr>
<th><var>SUBSYSTEM</var></th>
<th><var>SUBSYSTEM</var></th>
<td> indicates that the term following it is the subsystem name.</td>
<td>Indicates that the term following it is the subsystem name.</td>
</tr>
</tr>
   
   
<tr>
<tr>
<th>subsysname</th>
<th>subsysname</th>
<td> is the name of the application subsystem.</td>
<td>The name of the application subsystem.</td>
</tr>
</tr>
   
   
<tr>
<tr>
<th>parameters</th>
<th>parameters</th>
<td> specify subsystem-specific parameters.</td>
<td>Subsystem-specific parameters.</td>
</tr>
</tr>
   
   
</table>
</table>
==Usage notes==
==Usage notes==
The DEBUG command allows you, without stopping and restarting the subsystem, to:  
The <var>DEBUG</var> command allows you, without stopping and restarting the subsystem, to:  
<ul>  
<ul>  
<li>
<li>See the name of the subsystem procedure that is about to be included</li>
<p>See the name of the subsystem procedure that is about to be included</p>
</li>
   
   
<li>
<li>Include new subsystem procedures</li>
<p>Include new subsystem procedures</p>
</li>
   
   
<li>
<li>Change the order in which subsystem procedures are run</li>
<p>Change the order of execution of subsystem procedures </p>
</ul>
</li>
<p>
</ul>
After you issue <var>DEBUG</var>, <var class="product">Model&nbsp;204</var> displays the value of the subsystem [[Application_Subsystem_development#Communication_global_variable|communication global variable]] before each procedure is included and prompts you for changes. You also receive [[Using_system_statistics#User_since-last_statistics|since-last statistics]].</p>
<p>After you issue DEBUG, <var class="product">Model&nbsp;204</var> displays the value of the subsystem communication global variable before each procedure is included and prompts you for changes. You also receive since-last statistics.</p>
<p>
<p>Changes to the sequence of subsystem procedure execution affect only the programmer who makes the changes. More than one user can execute the DEBUG command against the same subsystem at the same time.</p>
Changes to the sequence in which subsystem procedures are run affect only the programmer who makes the changes. More than one user can run the <var>DEBUG</var> command against the same subsystem at the same time.</p>
<p>If the subsystem is not in AUTOSTART mode, then it must be started before execution of the DEBUG command.     </p>
<p>
<p>DEBUG alone does not allow you to make changes to the content of subsystem procedures. To make such changes, you need to stop the subsystem, or you need to use multiple procedure files and temporary groups, as described in the <var>Model&nbsp;204 User Language Manual.</var></p>
If the subsystem is not in <var>AUTOSTART</var> mode, then it must be started before the <var>DEBUG</var> command is run. </p>
[[Category: General user commands]]
<p>
<var>DEBUG</var> alone does not allow you to make changes to the content of subsystem procedures. To make such changes, you need to stop the subsystem, or you need to use multiple procedure files and temporary groups.
For more information, see [[Application Subsystem development#Debugging and testing facilities|Debugging and testing facilities]].</p>
 
[[Category: User commands]]
[[Category: Subsystem commands]]
[[Category:Commands]]
[[Category:Commands]]

Latest revision as of 15:49, 11 February 2019

Summary

Privileges
Defined in the subsystem definition, the user's SCLASS must be granted either TEST or DEBUG privileges.
Function
Displays and allows changes to a communication global variable

Syntax

DEBUG SUBSYSTEM subsysname [parameters]

Where:

SUBSYSTEM Indicates that the term following it is the subsystem name.
subsysname The name of the application subsystem.
parameters Subsystem-specific parameters.

Usage notes

The DEBUG command allows you, without stopping and restarting the subsystem, to:

  • See the name of the subsystem procedure that is about to be included
  • Include new subsystem procedures
  • Change the order in which subsystem procedures are run

After you issue DEBUG, Model 204 displays the value of the subsystem communication global variable before each procedure is included and prompts you for changes. You also receive since-last statistics.

Changes to the sequence in which subsystem procedures are run affect only the programmer who makes the changes. More than one user can run the DEBUG command against the same subsystem at the same time.

If the subsystem is not in AUTOSTART mode, then it must be started before the DEBUG command is run.

DEBUG alone does not allow you to make changes to the content of subsystem procedures. To make such changes, you need to stop the subsystem, or you need to use multiple procedure files and temporary groups. For more information, see Debugging and testing facilities.

Retrieved from "https://m204wiki.rocketsoftware.com/index.php?title=DEBUG_command&oldid=117200"