Library /sys$common/syshlp/ncphelp.hlb CLEAR, LOGGING, Examples *Conan The Librarian (sorry for the slow response - running on an old VAX) |
NCP>CLEAR LOGGING CONSOLE ALL This command clears logging to the logging console, after which the logging console component is no longer recognized by the network. The logging console component must be in the OFF state to perform this command. NCP>PURGE LOGGING FILE EVENTS 2.* This command purges logging for all class 2 events to the logging file. NCP>SET LOGGING CONSOLE EVENT 4.* CIRCUIT SVA-0 NCP>CLEAR LOGGING CONSOLE EVENT 4.* CIRCUIT SVA-0 The SET command causes class 4 events for a specific source CIRCUIT SVA-0 to be logged to the logging console. The CLEAR command stops the logging of class 4 events for that specific source to the logging console. Note that since a specific source (CIRCUIT SVA-0) was indicated in the SET command, that source must also be specified in the CLEAR command. That is, a CLEAR LOGGING CONSOLE EVENT 4.* command would not have cleared these events since the source was not specified. NCP>CLEAR LOGGING MONITOR NAME This command removes the name of the monitor program. The logging monitor must be in the OFF state to perform this command. NCP>SET LOGGING CONSOLE KNOWN EVENTS SINK NODE LAMCHP NCP>CLEAR LOGGING CONSOLE KNOWN EVENTS SINK NODE LAMCHP The SET command causes all known events generated locally to be logged to the logging console on remote node LAMCHP. The CLEAR command stops the logging of events from the local node to the logging console of the remote node. Note that since a specific location for logging the events (SINK NODE LAMCHP) was indicated in the SET command, that sink must also be specified in the CLEAR command. In this case, the CLEAR LOGGING CONSOLE KNOWN EVENTS command would not have removed these events because the SINK was not specified.
|