OSF DCE Application Development Guide--Core Components

OSF DCE Application Development Guide—Core Components
establish the application’s program name, that name would appear in
this field instead of the process ID. See Section 4.3.1 for further
information.
severity The severity level of the message (NOTICE in the example).
component The component name of the program that wrote the message (hel in
the example).
subcomponent The subcomponent that wrote the message (main in the example;
note that this program has only one subcomponent).
src_file The name of the C source file in which the dce_svc_printf() call
was executed.
src_line The line number, in the source file, at which the dce_svc_printf()
call is located.
thread_ID The thread ID of the thread that wrote the message, expressed as a
hexadecimal number (0xa444e208 in the example).
text The text of the message (Hello World in the example).
4.1.3 Serviceability Input and Output Files
Figure 4-1 shows the relationship of the various files, both source and sams output, that
go to make up the hello_svc application.
The two parallelogram-shaped objects represent the files that must be created by the
developer (you).
Rectangular objects with solid lines represent files that are generated by sams; the two
ovals represent programs: one is sams, the other gencat (which is implicitly run by sams
when message catalogs are generated).
The large rectangular object in dashed lines represents libdce, which contains the
serviceability library.
The diagram makes no attempt to show how hello_svc.c itself is compiled and linked,
nor how it runs. It is just a static map of the general place of serviceability in DCE
development.
Figure 4-1. Serviceability and DCE Applications
4− 12 Tandem Computers Incorporated 124245