OSF DCE Application Development Guide--Core Components

OSF DCE Application Development Guide—Core Components
char *argtypes The format-specifier string for the message.
int argtypes_size The number of format specifiers for the message.
char *fac_name The component or subcomponent (‘‘facility’’) name
string.
char *message_text Message text string.
char *progname Program name string, set by the application’s call to
dce_svc_set_progname().
char *file Filename string identifying file from which entry
was read.
int line Line number in file from where the message was
printed.
int file_size Length of filename string.
4.3.7 Message Action Attributes
Routing and severity attributes affect what happens to the messages they are applied to,
and nothing else. However, there is an additional set of attributes that, when applied to a
message, mainly affect what happens to the program after the message is sent:
svc_c_action_abort Causes the program to abort (with core dump) as
soon as the message is output.
svc_c_action_exit_bad Causes the program to exit (with failure status) as
soon as the message is output.
svc_c_action_exit_ok Causes the program to exit (with successful status)
as soon as the message is output.
svc_c_action_brief Suppresses the standard prolog of the message. The
prolog of a serviceability includes all the
nonmessage information that is output before the
message text itself. The prologs of all messages can
be suppressed by setting the SVC_BRIEF
environment variable; see the next section.
4.3.8 Suppressing the Serviceability Message Prolog
You can suppress the prolog (nonmessage text) part of all serviceability messages
generated by an application by setting the value of the SVC_BRIEF environment
variable to 1.
The prolog of a serviceability consists of all the nonmessage information that is output
before the message text itself. For example, examine the following message:
4− 28 Tandem Computers Incorporated 124245