OSF DCE Application Development Guide--Core Components

Using the DCE Serviceability Application Interface
dcehelmsg.idx
dcehelmsg.sml
dcehelmsg.man
dcehel.cat
sams)
gencat
(executed by
dcehel.msg
sams
hel.sams
libdce
dce_svc_printf(HEL_S_HELLO_MSG);
hello_svc.c
dcehelmsg.h
dcehelmsg.c
dcehelsvc.c
dcehelsvc.h
dcehelmac.h
(DCE library)
..........................
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...........................
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
(message catalog)
(doc)
(doc)
(doc)
The sams output filenames are constructed as follows:
tech_name.comp_name.part_name.extension
where:
tech_name Is the technology name (optionally specified at the top of the hel.sams
file); by default it is dce.
comp_name Is the component name (specified at the top of the hel.sams file); in this
case, hel.
part_name Is a substring identifying the particular file; for example, svc or msg, and
so on. This piece of the name is omitted from the message catalog
filenames (in our example, dcehel.msg and dcehel.cat).
extension Is the file extension (preceded by a . (dot) character).
124245 Tandem Computers Incorporated 4− 13