OSF DCE Application Development Guide--Core Components

DCE Application Messaging

— dce_sprintf()

— dce_pgm_printf()

— dce_pgm_sprintf( )

— dce_pgm_fprintf()

• Message retrieval routines

These routines retrieve a speciﬁed message. If necessary, the message catalog is

opened.

— dce_msg_get_msg()

— dce_msg_get()

— dce_msg_get_default_msg( )

— dce_error_inq_text()

• Message table routines

Miscellaneous routines for manipulating in-memory message tables.

— dce_msg_deﬁne_msg_table( )

— dce_msg_translate_table( )

• DCE XPG4 routines

DCE versions of the XPG messaging routines catopen( ), catgets( ), and catclose( ).

— dce_msg_cat_open( )

— dce_msg_cat_get_msg( )

— dce_msg_get_cat_msg( )

— dce_msg_cat_close( )

Generally speaking, routines that retrieve or print messages will ﬁrst try to get a message

from the message catalog ﬁle (the routines deduce the correct message catalog from the

message ID that is passed to them). Routines will look for the catalog in the current

locale’s system-speciﬁc location for correctly installed message catalogs.

If the message catalog cannot be found, and an in-memory message table has been

deﬁned, the message will be retrieved from there.

The only exception to this message-ﬁnding algorithm occurs with

dce_msg_get_default_msg( ), which always attempts to retrieve the in-memory message

only.

The following sections describe each of the DCE messaging routines in detail. Complete

reference pages for the routines can be found in the OSF DCE Application Development

Reference.

124245 Tandem Computers Incorporated 3−9