4 namesend activity trace log – Reliant Octel 200 and Octel 300 Message Servers PB6001401 User Manual
Page 334
7-40
Installation and Maintenance Volume
Octel Overture 200/300 Serenade 3.0
PB60014–01
7.4
NAMESEND ACTIVITY TRACE LOG
The Namesend Activity Trace Log collects Namesend propagation transaction data for Digital
Networking in a log file on the Octel Overture 200/300. This log includes all activity associated with
names propagation, including the following:
-
Recorded names received from and propagated to a location using Namesend
-
Additions, deletions, and modifications to the queue of names that are pending propagation, the
Netnames Table, and the Dial-by-Name Directory.
.
Refer to the Networking Volume, Digital Networking for information about Namesend.
Use the
LOG PR NAM
command for different combinations of print options and filters that can be
specified to consolidate information and focus on specific types of Namesend activities to be displayed.
To use the LOG command for Namesend Activity Trace activities, at the @ prompt, type
LOG PR NAM
Enter
@LOG PR NAM
Specify Print Option(s):
”S”tart
Refer to the Log Command section for an explanation of LOG print options.
In addition to the LOG print options that control the output format, you can enter specific filters and
arguments to limit the output to only those activities that match the set of search criteria. Filters need not
be specified; in some cases, filters can be partially specified. Only the values that match the specified
filters are displayed. The following filters are available:
-
Task,
TA [TASK]
. This filter is for technical support use.
-
Type,
TY [TYPE]
. This filter displays a specific type of Namesend activity. Enter one of the types
listed in Table 7-6 to specify a specific type to filter.
Table 7-6 Namesend Activity Types
Type
Description
QUEUED
Names in queue that are pending propagation
DEQUEU
Names deleted from the queue pending propagation
NAM_RCV
Names that were received at this location
NAM_SND
Names that were propagated automatically
RBLD
The queue of names was propagated again because of a restart
or reload.