OSF DCE Application Development Guide--Core Components

OSF DCE Application Development Guide—Core Components

The sams output ﬁlenames are made up of the following pieces:

tech_name + comp_name + part_name + extension

where:

tech_name Is the technology name (optionally speciﬁed at the top of the hel.sams

ﬁle); by default dce.

comp_name Is the component name (speciﬁed at the top of the hel.sams ﬁle); in this

case, hel.

part_name Is a substring identifying the particular ﬁle; for example, svc or msg, and

so on. This piece of the name is omitted from the message catalog

ﬁlenames (in our example, dcehel.msg and dcehel.cat).

extension Is the ﬁle extension (preceded by a . (dot) character).

The ﬁles dcehelmsg.man (generated by sams -p d hel.sams) and dcehelmsg.sml

(generated by sams -p p hel.sams), which are shown in Figure 3-1, were not generated

by the following command:

sams -o thmc hel.sams

They could have been generated by executing this command:

sams -o dp hel.sams

These are automatically generated documentation ﬁles (their nature and purpose were

previously described) that have nothing to do with the operation of the interface itself.

A deﬁnitive description of sams and the contents of sams ﬁles can be found in the

sams(1dce) reference page.

3.3 DCE Messaging Routines

There are several different DCE messaging routines. It is possible for an application to

accomplish all of its messaging tasks with only one or two of these routines

(dce_printf() and dce_error_inq_text()); additional routines allow applications to

perform manipulations on message tables, open and close message catalogs explicitly,

retrieve messages without printing them, and so on. The complete list of routines is as

follows:

• Message output routines

These routines retrieve and output a speciﬁed message. If necessary, the message

catalog is opened.

— dce_printf()

— dce_fprintf( )

3− 8 Tandem Computers Incorporated 124245