OSF DCE Administration Guide--Core Components

Managing DCE Host Services and Host Data
You can specify multiple target servers as a space-separated list. Specify each server by
supplying either the RPC string binding that describes the server’s network location
(string_binding_to_server) or a namespace entry of the server
(RPC_server_namespace_entry). When specifying multiple servers, you can mix the
forms in the same list.
A serviceability_routing_specification is a space-separated list of serviceability routing
elements. No spaces are allowed within the specification of an individual routing
element. Each routing element is a substring consisting of four fields containing
Portable Character Set (PCS) data, as follows (shown in string syntax form):
severity:output_form:destination[: application-defined]
where:
severity A message severity level: FATAL, ERROR, WARNING,
NOTICE,or NOTICE_VERBOSE.
output_form Specifies how messages of the associated severity level
should be processed, and must be one of the following:
BINFILE Write these messages as binary log
entries
TEXTFILE Write these messages as human-
readable text
FILE Equivalent to TEXTFILE
DISCARD Do not record these messages
STDOUT Write these messages as human-
readable text to standard output
STDERR Write these messages as human-
readable text to standard error
Files written as BINFILEs can be read and manipulated
with a set of log file APIs, which are described in the .
The BINFILE, TEXTFILE, and FILE output_form
specifiers may be followed by a 2-number specifier of the
form
.gens.count
where:
gens Is an integer that specifies the number of files
(that is, generations) that should be kept
count Is an integer specifying how many entries (that
is, messages) should be written to each file
The multiple files are named by appending a . (dot) to the
simple specified name, followed by the current generation
number. When the number of entries in a file reaches the
maximum specified by count, the file is closed, the
124243 Tandem Computers Incorporated 9− 11