DEBUG command - Revision history

DCameron: /* Usage notes */

2019-02-11T15:49:08Z

Usage notes

← Older revision		Revision as of 15:49, 11 February 2019
Line 39:		Line 39:
	</ul>		</ul>
	<p>		<p>
	After you issue <var>DEBUG</var>, <var class="product">Model 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 since-last statistics.</p>		After you issue <var>DEBUG</var>, <var class="product">Model 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>		<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>		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>

DCameron: /* Usage notes */

2019-02-11T15:46:43Z

Usage notes

← Older revision		Revision as of 15:46, 11 February 2019
Line 39:		Line 39:
	</ul>		</ul>
	<p>		<p>
	After you issue <var>DEBUG</var>, <var class="product">Model 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>		After you issue <var>DEBUG</var>, <var class="product">Model 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 since-last statistics.</p>
	<p>		<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>		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>

ELowell: /* Usage notes */

2017-03-23T17:03:55Z

Usage notes

← Older revision		Revision as of 17:03, 23 March 2017
Line 45:		Line 45:
	If the subsystem is not in <var>AUTOSTART</var> mode, then it must be started before the <var>DEBUG</var> command is run. </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>
	<p>		<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, ~~as described in~~ [[Application Subsystem development]].</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: User commands]]
	[[Category: Subsystem commands]]		[[Category: Subsystem commands]]
	[[Category:Commands]]		[[Category:Commands]]

ELowell at 16:39, 23 March 2017

2017-03-23T16:39:16Z

← Older revision		Revision as of 16:39, 23 March 2017
Line 48:		Line 48:

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

ELowell at 16:17, 22 March 2017

2017-03-22T16:17:34Z

← Older revision		Revision as of 16:17, 22 March 2017
Line 47:		Line 47:
	<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, as described in [[Application Subsystem development]].</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, as described in [[Application Subsystem development]].</p>

	[[Category: ~~General user~~ commands]]		[[Category: User commands]]
	[[Category:Commands]]		[[Category:Commands]]

JAL: misc formatting

2016-11-30T17:08:26Z

misc formatting

← Older revision		Revision as of 17:08, 30 November 2016
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>See the name of the subsystem procedure that is about to be included</li>		<li>See the name of the subsystem procedure that is about to be included</li>
Line 38:		Line 39:
	</ul>		</ul>
	<p>		<p>
	After you issue DEBUG, <var class="product">Model 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>		After you issue <var>DEBUG</var>, <var class="product">Model 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 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.</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>		<p>
	If the subsystem is not in AUTOSTART mode, then it must be started before the DEBUG command is run. </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>
	<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 [[Application Subsystem development]].</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, as described in [[Application Subsystem development]].</p>

	[[Category: General user commands]]		[[Category: General user commands]]
	[[Category:Commands]]		[[Category:Commands]]

JAL at 20:14, 21 January 2014

2014-01-21T20:14:14Z

← Older revision		Revision as of 20:14, 21 January 2014
Line 31:		Line 31:
	The DEBUG command allows you, without stopping and restarting the subsystem, to:		The DEBUG 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 in which subsystem procedures are run~~</p>~~		</ul>
	</li>		<p>
	</ul>		After you issue DEBUG, <var class="product">Model 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>After you issue DEBUG, <var class="product">Model 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 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.</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 DEBUG 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 the DEBUG command is run. </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~~ [[Application Subsystem ~~Development~~]] ~~SOUL/User Language topic~~.</p>		If the subsystem is not in AUTOSTART mode, then it must be started before the DEBUG command is run. </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 [[Application Subsystem development]].</p>

	[[Category: General user commands]]		[[Category: General user commands]]
	[[Category:Commands]]		[[Category:Commands]]

ELowell: /* Usage notes */

2013-07-19T21:22:17Z

Usage notes

← Older revision		Revision as of 21:22, 19 July 2013
Line 40:		Line 40:

	<li>		<li>
	<p>Change the order ~~of execution of~~ subsystem procedures </p>		<p>Change the order in which subsystem procedures are run</p>
	</li>		</li>
	</ul>		</ul>

ELowell: /* Usage notes */

2013-07-19T21:04:18Z

Usage notes

← Older revision		Revision as of 21:04, 19 July 2013
Line 44:		Line 44:
	</ul>		</ul>
	<p>After you issue DEBUG, <var class="product">Model 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>After you issue DEBUG, <var class="product">Model 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>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>		<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 DEBUG 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>If the subsystem is not in AUTOSTART mode, then it must be started before the DEBUG command is run. </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 class="book">Model 204~~ User Language ~~Manual</var>~~.</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 [[Application Subsystem Development]] SOUL/User Language topic.</p>
	[[Category: General user commands]]		[[Category: General user commands]]
	[[Category:Commands]]		[[Category:Commands]]

JAL at 01:20, 20 April 2013

2013-04-20T01:20:18Z

← Older revision		Revision as of 01:20, 20 April 2013
Line 46:		Line 46:
	<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>		<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>
	<p>If the subsystem is not in AUTOSTART mode, then it must be started before execution of the DEBUG command. </p>		<p>If the subsystem is not in AUTOSTART mode, then it must be started before execution of the DEBUG command. </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 class="book">Model 204 User Language Manual</var></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 class="book">Model 204 User Language Manual</var>.</p>
	[[Category: General user commands]]		[[Category: General user commands]]
	[[Category:Commands]]		[[Category:Commands]]