OSF DCE Application Development Guide--Core Components

OSF DCE Application Development Guide—Core Components
unsigned_char_t *my_route = "NOTICE:STDOUT:-;TEXTFILE:/tmp/my_log";
unsigned_char_t *error_route = "ERROR:TEXTFILE:/tmp/errors_%ld";
dce_svc_routing(my_route, &status);
if (status != svc_s_ok)
{
printf("dce_svc_routing failed\n");
exit(1);
}
dce_svc_routing(error_route, &status);
if (status != svc_s_ok)
{
printf("dce_svc_routing failed\n");
exit(1);
}
4.3.4.4 Additional Routing by Attribute
Limited additional routing for messages can be specified by attribute, either in the
message definition itself in the sams file or as part of the argument list to
dce_svc_printf(). Two routing attribute specifiers are available:
svc_c_route_stderr Route the message to standard error.
svc_c_route_nolog Discard the message.
Note also the svc_c_action_brief attribute, which is described in Section 4.3.7.
4.3.5 Table of Message Processing Specifiers
As was seen, message processing can be specified either by text strings (read from an
environment variable or routing file, or passed to a routine) or, to a limited degree, by
attribute in the message definition or when the message is output. Table 4-2 shows all
the available types of serviceability message processing; the name by which it is
specified in strings, and the attribute (where it exists) by which it is specified in message
definitions and calls are both given, along with the meaning of each.
TABLE 4-2. Serviceability Message Processing Specifiers
4− 26 Tandem Computers Incorporated 124245