DEBUG command: Difference between revisions
No edit summary |
|||
| (2 intermediate revisions by 2 users not shown) | |||
| 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 [[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> | ||
| 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, | <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]] | ||
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.