DCE Application Programming Guide

NonStop DCE Application Development

Environment

HP NonStop DCE Application Programming Guide—429551-003

1-2

Application Development Environment

The DCE application development environment consists of APIs and development

tools for these OSF DCE components:

•

DCE functions to provide facilities that apply to more than one DCE component:

DCE attribute interface functions

These functions allow applications to define and access attribute types

(schema entries) in a schema of your choice. They are based on the Extended

Registry Attribute (ERA) interface, which defines and accesses attribute types

in the register database schema.

DCE configuration functions

These functions return information based on the contents of the local DCE

configuration file, which is created during the DCE cell-configuration or

machine-configuration process.

DCE backing store functions

These functions enable you to maintain typed data between program

invocations. Use the backing store functions in servers, clients, or stand-alone

programs that do not involve remote procedure calls (RPCs).

DCE messaging interface functions

These functions provide access to message catalogs, to specific message

texts and message IDs, and to in-memory message tables.

DCE server functions

These functions are used by servers to register themselves with DCE;

registration includes the RPC run-time code, the local endpoint mapper, and

the DCE namespace. Functions are also available to set up DCE security so

that servers can receive and invoke authenticated RPCs.

DCE serviceability functions

These functions are intended for use by servers that export the serviceability

interface defined in the service.idl file. A set of DCE serviceability macros

can also be used for diagnostic purposes and to create a serviceability handle.

DCE host demon API

These functions give management applications remote access to various data,

servers, and services on DCE hosts.

•

The DCE remote procedure call (RPC) facility, which consists of:

The RPC Interface Definition Language (IDL) compiler called idl, which

converts an interface definition written in IDL into various output files including

client and server stubs. The stubs hide the intricacies of RPCs from the

application code.