Difference between revisions of "SET DOHISTORY"
From Recital Documentation Wiki
Yvonnemilne (Talk | contribs) |
Yvonnemilne (Talk | contribs) |
||
| Line 15: | Line 15: | ||
==See Also== | ==See Also== | ||
| − | + | [[RESUME]], [[SUSPEND]], [[SET DEBUG]], [[SET ECHO]], [[SET HISTORY]], [[SET PRINT]], [[SET STEP]] | |
| Line 34: | Line 34: | ||
[[Category:Documentation]] | [[Category:Documentation]] | ||
[[Category:Commands]] | [[Category:Commands]] | ||
| − | [[Category:Set_Commands]] | + | [[Category:Set_Commands|DOHISTORY]] |
Revision as of 12:23, 11 March 2009
Contents
SET DOHISTORY
Class
Error Handling and Debugging
Purpose
Determine whether commands from program files are recorded in history
Syntax
SET DOHISTORY ON | OFF | (<expL>)
See Also
RESUME, SUSPEND, SET DEBUG, SET ECHO, SET HISTORY, SET PRINT, SET STEP
Description
If SET DOHISTORY is ON, and HISTORY is ON, then commands executed in program files are recorded in the command history. This command is primarily used during program debugging. The commands executed in the program, while DOHISTORY is ON, can be listed with the LIST HISTORY command. If used in conjunction with the SET HISTORY TO FILE <.his filename> the program history can be stored in a text file. By default, DOHISTORY is OFF.
Example
set history on set dohistory on do testprg list history
Products
Recital Database Server, Recital Mirage Server, Recital Terminal Developer
