Difference between revisions of "SET DOHISTORY"
From Recital Documentation Wiki
Yvonnemilne (Talk | contribs) |
Helengeorge (Talk | contribs) |
||
(2 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
− | |||
− | |||
− | |||
− | |||
==Purpose== | ==Purpose== | ||
Determine whether commands from program files are recorded in history | Determine whether commands from program files are recorded in history | ||
Line 28: | Line 24: | ||
==Products== | ==Products== | ||
− | Recital | + | Recital Server, Recital |
[[Category:Documentation]] | [[Category:Documentation]] | ||
[[Category:Commands]] | [[Category:Commands]] | ||
[[Category:Set_Commands|DOHISTORY]] | [[Category:Set_Commands|DOHISTORY]] | ||
+ | [[Category:Error Handling and Debugging]] | ||
+ | [[Category:Error Handling and Debugging Set Commands]] |
Latest revision as of 15:39, 23 November 2009
Purpose
Determine whether commands from program files are recorded in history
Syntax
SET DOHISTORY ON | OFF | (<expL>)
See Also
DB_SAVEHISTORY, RESUME, SET DEBUG, SET ECHO, SET HISTORY, SET PRINT, SET STEP, SUSPEND
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 Server, Recital