OSF DCE Application Development Guide--Core Components

Using the DCE Serviceability Application Interface

means that WARNING messages should show up in three places: twice to stderr, and

then once to the ﬁle /tmp/foo.

Note that a GOESTO speciﬁcation should be the last element in a multidestination route

speciﬁcation.

4.3.4.2 Routing by Environment Variable

Serviceability message routing can also be speciﬁed by the contents of certain

environment variables. If environment variables are used, the routes they specify will

override any conﬂicting routings speciﬁed by a routing ﬁle.

The routings are speciﬁed (on the basis of severity level) by putting the desired routing

instructions in the following environment variables:

• SVC_FATAL

• SVC_ERROR

• SVC_WARNING

• SVC_NOTICE

• SVC_NOTICE_VERBOSE

Each variable should contain a single string in the following format:

out_form:dest;[out_form:dest . . . ] [GOESTO:{sev | comp}]

where out_form and dest have the same meanings and form as described in Section

4.3.4.1. Multiple routings can be speciﬁed with semicolon-separated additional strings

specifying the additional routes, as shown.

4.3.4.3 Calling dce_svc_routing( ) to Set Routing

Message routing can be set up by the application itself, by calling the routine

dce_svc_routing( ) and passing to it a string formatted in the same way as a line of text

from a routing ﬁle. The routine must be called separately for each severity level. When

routing is speciﬁed this way, the routings so speciﬁed will override any conﬂicting

routings speciﬁed by environment variable or routing ﬁle (as described in the preceding

sections). This is especially useful for setting routes from command-line arguments.

For example, to set routing in this way for the hello_svc.c application described

previously, use the following code:

124245 Tandem Computers Incorporated 4− 25