@LOG - Control logging

The @LOG statement controls the logging of the input in batch and interactive mode.

Operation	Operands	F mode, L mode
@LOG	[ {ALL | COMMANDS | NONE} ] [ {SYSLST | SYSLSTn} ]

ALL	All L mode input (text and statements) that is entered via RDATA or via the terminal is to be logged. In the case of inputs in the F mode's interactive mode, the input in the statement lines (separated into individual statements if the case of statement sequences) is logged.
COMMANDS	Only statements are to be logged.
NONE	Nothing is to be logged.
SYSLST	Log output is sent to SYSLST. This is the default setting when EDT is started.
SYSLST n	Log output is written to the file to which SYSLSTnn is assigned (values between 1 and 99 are permitted for n).

The default setting when EDT is started in batch mode is @LOG NONE if job switch 4 is set and @LOG COMMANDS if job switch 4 is not set. If EDT is called in interactive mode then @LOG NONE is set by default.

The definition of the output medium (SYSLST, SYSLSTnn) remains valid for subsequent @LOG statements unless these specify a different value.

Note

Statements and data input which are read from EDT procedures and executed are not logged by @LOG in either batch or interactive mode. The logging of such items must be requested explicitly by means of @DO ...PRINT or @INPUT ...PRINT.
In test mode, the @LOG statement is not just checked for its syntax. It is also executed (see @SYNTAX- statement).

Logging to list variables, which was possible in the predecessor version, is no longer supported. It is, however, possible to use the /ASSIGN-SYSLST command to assign a list variable to the system file SYSLST.