OSF DCE Application Development Guide--Core Components

OSF DCE Application Development Guide—Core Components
_______________________________________________________________________________
Server ‘‘Implementation’’ Library Routine Purpose
_______________________________________________________________________________
Remotely sets serviceability
message routing.
com _svc_set_route( ) dce_svc_routing()
_______________________________________________________________________________
Remotely sets serviceability
debug message routing.
com _svc_set_dbg_route( ) dce_svc_debug_routing( )
_______________________________________________________________________________
Remotely sets serviceability
debug message levels.
com _svc_set_dbg_levels() dce_svc_debug_set_levels()
_______________________________________________________________________________
Returns a listing of all
components that have been
registered with the
dce_svc_register( ) routine.
com _svc_inq_components( ) dce_svc_components( )
_______________________________________________________________________________
Returns the message table
registered with a given
component.
com _svc_inq_table() dce_svc_table( )
_______________________________________________________________________________
Returns a list of routings in
effect for a component.
com _svc_inq_routings() dce_svc_routings( )
_______________________________________________________________________________
Remotely controls the
behavior of the serviceability
message filtering routine (if
one exists).
com _svc_filter_control() dce_svc_filter()
_______________________________________________________________________________
Returns operating statistics.com _svc_inq_stats( ) dce_svc_inq_stats()
_______________________________________________________________________________
4.3.14.1 Basic Steps in Setting Up the Remote Interface
To make the interface available, the developer must do the following:
1. Coding steps
• Define the server implementation routines for the remote operations.
• Initialize the serviceability interface manager entry point vector (manager
EPV) with the implementation routines.
2. Build steps
• Process the service.idl file to produce the following:
— Client stub
This will be linked into the client object. The client itself can contain calls
to the remote routines, expressed by their interface names.
— Server stub
This will be linked into the server object (just as its ‘‘own’’ stub(s) are) to
produce the server executable. Note that the server stub is generated with
the -no_mepv IDL option, which allows the implementation routines to be
named anything that suits the developer. This is why the EPV must be
explicitly initialized with the implementation routines’ addresses.
4− 40 Tandem Computers Incorporated 124245