OSF DCE Application Development Guide--Core Components

Using the DCE Serviceability Application Interface

• svc_c_debug4

• svc_c_debug5

• svc_c_debug6

• svc_c_debug7

• svc_c_debug8

• svc_c_debug9

4.3.12.2 Routing Debug Messages

Routing for serviceability debug messages can be speciﬁed in any of four ways:

• By calling the dce_svc_debug_routing() routine

• By the contents of the SVC_CMP_DBG environment variable (where CMP is the

three-character serviceability name of the component, in uppercase)

• By the contents of the routing ﬁle dce-local-path/svc/routing

• By one of the message’s attributes (as coded in the sams ﬁle)

In all but the last method, the routing is speciﬁed by the contents of a specially formatted

string that is either included in the value of the environment variable, is part of the

contents of the routing ﬁle, or is passed to the dce_svc_debug_routing( ) routine.

The general format for the debug routing speciﬁer string is

component:sub_comp.level,. . .:out_form:dest [out_form:dest . . . ][GOESTO:{sev | comp}]

where:

component Speciﬁes the component name.

sub_comp.level Speciﬁes a subcomponent name, followed (after a dot) by a

debug level (expressed as a single digit from 1 to 9). Note that

multiple subcomponent/level pairs can be speciﬁed in the string.

The meanings of the remaining elements of the string are the same as those for the

identically named elements in Section 4.3.4.

Multiple routings for the same group of subcomponents can be speciﬁed by adding

semicolon-separated strings of the following format:

out_form:dest

to the speciﬁcation, in a form analogous to that followed for specifying production

(nondebug) message routes, shown previously.

The following string would, when passed to dce_svc_debug_routing(), set the debug

level and routing for all hel subcomponents:

124245 Tandem Computers Incorporated 4− 37