HP 64783A, User Manual

Page: 119 / 816

log_commands to <filename>
2 Enter and execute commands to complete the desired task.
3 Stop logging commands by selecting File
→
Log
→
Stop. If using the command line,
enter the command:
log_commands off
The above commands provide a mechanism that logs commands, entered and
executed at the command line, to a file. Later, the command file can be executed by
the interface. The log_commands command does not appear on the softkeys. Type
it on the command line, or type the first few letters of the command and then press
<TAB>.
All commands entered on the command line after you type log_commands to
<filename> are logged to the <filename> until either the log_commands off
command is used or the interface is exited.
<filename> is any valid UNIX file name. File names may include path
information. If <filename> already exists, commands are appended to the current
contents of the file, unless the noappend option is used. If <filename> does not
exist, a new file is created.
File creation errors can sometimes be caused by write permission violations of
either files or directories. If you are having trouble creating a command file, make
sure you have the correct permissions.
Example To save a set of commands in the file STARTEMUL by logging commands while
executing them during an emulation session, enter the following commands in the
command line:
log_commands to STARTEMUL
# You can add a comment to a file while logging if you
# precede the comment with a pound sign.
# The Softkey Interface will
# ignore the rest of the line up to the line feed.
load configuration bigproject/config
load bigproject/program
trace after START
run from 2000h # Comments can follow on the same line
Chapter 3: Using the Emulator/Analyzer Interface
Creating and Executing Command Files
89