Difference between revisions of "SET DOHISTORY"

From Recital Documentation Wiki
Jump to: navigation, search
Line 1: Line 1:
=SET DOHISTORY=
 
 
 
 
==Class==
 
==Class==
 
Error Handling and Debugging
 
Error Handling and Debugging
Line 15: Line 12:
  
 
==See Also==
 
==See Also==
[[RESUME]], [[SUSPEND]], [[SET DEBUG]], [[SET ECHO]], [[SET HISTORY]], [[SET PRINT]], [[SET STEP]]
+
[[DB_SAVEHISTORY]], [[RESUME]], [[SET DEBUG]], [[SET ECHO]], [[SET HISTORY]], [[SET PRINT]], [[SET STEP]], [[SUSPEND]]
  
  
Line 23: Line 20:
  
 
==Example==
 
==Example==
<pre>
+
<code lang="recital">
 
set history on
 
set history on
 
set dohistory on
 
set dohistory on
 
do testprg
 
do testprg
list history</pre>
+
list history</code>
  
  

Revision as of 14:54, 15 April 2009

Class

Error Handling and Debugging


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 Database Server, Recital Mirage Server, Recital Terminal Developer