OSF DCE Application Development Guide--Core Components

OSF DCE Application Development Guide—Core Components
file messages as arrays in program memory is contained in the dcecmpmsg.c file
generated with the sams -o t option. To initialize the table before using it the application
must also call the dce_msg_define_msg_table( ) routine, described in Section 3.3.3. The
message routines will, when called, attempt to use the application’s message catalog; but
if it cannot be found, the in-memory table will be used instead.
3.2.2 The DCE Message Interface and sams Input and Output Files
Figure 3-1 shows the relationship of the various files, both source and sams output, that
go to make up DCE application code that uses the DCE messaging API.
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 executable utilities: 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 DCE
message API library.
This illustration makes no attempt to show how a DCE application that uses DCE
messaging should be compiled and linked, nor how it runs. It is merely a static map of
the general place of DCE application messaging in DCE development.
3− 6 Tandem Computers Incorporated 124245