SQL/MP Reference Manual

HP NonStop SQL/MP Reference Manual—523352-013
L-52
LOG Command
)
LOCKLENGTH 6; —Lock length 6 bytes
LOG Command
LOG is an SQLCI command that starts or stops logging to a file. SQLCI logs the
commands you enter and the information the commands display. You can also use an
option to log only the commands. This option allows you to create an SQLCI OBEY
command file from the log file directly. SQLCI does not log the FUP, EDIT, PERUSE,
and TEDIT commands.
log-file
identifies the current log file and starts logging. For log-file, specify a device,
process, or disk file. You cannot log to any current output file (such as the INVOKE
TO, OUT, or OUT_REPORT file) or to any open file other than a terminal or
process. If you specify a nonexistent disk file, an EDIT file is created. When you
enter the LOG command, the previous log file is closed.
To stop logging and close the log file, omit log-file.
COMMANDS
allows SQLCI to log the commands only.
CLEAR
clears the new log file of all existing data before logging begins. If you omit this
option, logging information is appended to the file. CLEAR is ignored unless the file
is a disk or process file.
This information is written to the log file:

All text that SQLCI displays or prints, including output from commands such as
SHOW, data from SELECT commands, and diagnostic messages.

All lines you type (preceded by the current prompt).
The final version of a command is written to the log file without the extra characters
you enter while making changes with FC.
Example—LOG
This example starts logging SQLCI output to the file SUBV2.MAYLOG:
>> LOG SUBV2.MAYLOG;
LOG [ log-file [COMMAND[S] ] [ CLEAR ] ] ;