OSF DCE Application Development Guide--Core Components

Using the DCE Serviceability Application Interface

— svc_c_route_nolog

However, most routing is done either by passing specially

formatted strings to dce_svc_routing() or by environment

variable values. See Section 4.3.4 for more detailed

information.

severity The available severity attribute constants are

— svc_c_sev_fatal

— svc_c_sev_error

— svc_c_sev_warning

— svc_c_sev_notice

— svc_c_sev_notice_verbose

For more detailed information, see Section 4.3.3.

action The available message action attribute constants are

— svc_c_action_abort

— svc_c_action_exit_bad

— svc_c_action_exit_ok

— svc_c_action_brief

For more detailed information, see Section 4.3.7.

debug level Nine different debug levels can be speciﬁed. For more

detailed information, see Section 4.3.12.

— message ID

This argument consists of the message’s code, as declared in the sams ﬁle.

As an example of how to use format speciﬁers in messages, consider the following

sams ﬁle fragment, in which we deﬁne a second message for the hello_svc.c

application:

start

code hel_s_testmessage

text "This message has exactly %d not %d argument(s)"

explanation "This message is to show how to pass arguments"

action "None required."

end

The message could be printed by a call like the following:

dce_svc_printf(DCE_SVC(hel_svc_handle, "%d%d"), hel_s_main,\

svc_c_sev_notice | svc_c_route_stderr,\

hel_s_testmessage, 2, 7);

Note the format speciﬁers passed in the format string to DCE_SVC, and the

argument values passed at the end of the argument list. This call would cause the

following message to be printed:

124245 Tandem Computers Incorporated 4− 19