Attempts to write to a log file, the name of which must have been given in the <ref sconf>system or global</r> configuration files. If the write succeeds the information logged is in the following form:
<pre>
$logged: Wed Jan 27 10:30:27 1999 <-- time of log
$outputwas: doco01/htm <-- file being output
$datafrom: mydata <-- user datafile
$templatewas: test1 <-- template used
$globalwas: (none) <-- global file used (if any)
VARIABLENAME1:VALUE <-- any variables you ask Zonk to log
VARIABLENAME2:VALUE <-- you don't have to specify any
</pre>
Note that any filenames shown are as given to the program, they may include full paths or they may assume a working directory.
If you don't specify any <var>variablename</var> parameters, just the system information will be logged. There is no limit to the number of <var>variablename</var> parameters that you can give.
If a variable is undefined or has a NULL value when you attempt to log it, that variable will be ignored, although the system information and any variables with values will still be logged.
The values of any variables specified is as they are at the place where the <lit>zonk log</lit> command is in the template. There is no restriction as to where you can place <lit>zonk log</lit> commands. If you place the command inside a loop then one log record will be written each time around the loop. You can have as many zonk log commands in one template as you like. Be aware though that excessive logging will noticeably slow down the processing of a template.
Log files can be read back in as part of a datafile (see <ref logs>user logs files</r>).
<sh>Example</sh>
<lit><zonk log town partyhost></lit>
will log the system information plus the current values of the variables 'town' and 'partyhost'.
