Exchange/SNA Manual

LOG Command
Exchange/SNA Commands
3–32 104700 Tandem Computers Incorporated
In addition to the commands themselves, the home terminal or input file
that was the source of the command is also logged. This allows you to
determine which of possibly several Exchange/SNA command
interpreters was the source of the command.
CO[NS]
specifies that messages sent from Exchange/SNA to the host system’s
console and messages sent from the host to the Exchange/SNA console
are to be logged.
AL[L]
specifies that all the above types of information are to be logged.
If you omit the LOGDATA parameter (and are not using the STOP parameter),
the type of information to be logged remains as last specified. If you have not
previously specified the type of information to be logged, Exchange/SNA line
server error and informational messages are logged ( type = DIAG).
ST[OP]
resets logging to its initial condition, which is that Exchange/SNA error and
informational messages are logged on the operator console, $0. If another logfile
had been specified previously, that file is closed. If another LOGDATA type had
been specified previously, type is set to DIAG.
Considerations The LOG command specifies the information to be logged and the file to receive the
information. With the LOG command, you can change the file that receives the logged
information and you can specify additional information to be logged. Logging,
however, always takes place, whether you use the LOG command or not. If you do
not use the LOG command, Exchange/SNA error and information messages are
logged on the operator console, $0.
To use the LOG command, the command interpreter must be connected to the line
server, and the command interpreter must be privileged with respect to the line server.
That is, the command interpreter must have the same accessor ID as the command
interpreter that started the line server. If the command interpreter is not privileged
with respect to the line server, an error message is displayed and the logging is not
changed.
Examples 1. This example shows the LOG command with the TO and LOGDATA parameters:
>LOG TO $s.#logit, LOGDATA ALL
SNCI44 LOG SWITCHED TO $S.#LOGIT
SNCI44 LOG LOGDATA OPTION RESET
2. This example shows the LOG command with the STOP parameter, which resets
logging to its default state:
>LOG STOP
SNCI44 LOG DISABLED