Communicator 3000 MPE/iX Release 6.0 (Platform Software Release C.60.00) (30216-90269)

82 Chapter 6

Data/Application Integration

DCE RPC Clients for FOS through MPE/iX

by Sridhar Murthy T.R.

Commercial Systems Division

Overview

For the MPE/iX 6.0 release and later, the DCE RPC Client (Version

A.01.12) modules, will be included in the FOS. These DCE RPC

modules are based on OSF DCE 1.0.2. These changes will support

customers who were continuing to be dependent on NCS. NCS has been

obsoleted from 6.0 release.

A DCE/NCS application is developed by ﬁrst building an idl source ﬁle,

for example foo.idl for DCE,and foo.nidl for NCS. When compiled with

the idl compiler, the idl source ﬁle will create Server Client Stubs and

an .h ﬁle (DCE Stubs in the case of DCE idl and NSStubs for NCS idl.)

The DCE/NCS application must be linked with these stubs.

MPE/iX 6.0 release contains the utility NIDL2IDL which converts an

existing template ﬁle (for example, foo.nidl) to a DCE template(foo.idl.)

This application using the NCS calls must be ported to use the

appropriate DCE calls. Refer to NCS 1.5.1 in the DCE RPC Transition

Guide for more information.

NOTE CDS client on 6.0 will be available in a later release.

The following two products have been discontinued from 6.0.

B3824AA DCE/3000 CDS Server License

B3825AA CDE/3000 Security Server License

Technical Details

In order for the RPC library calls to succeed, the RPC daemon RPCD

must be running. This daemon can be started in two ways, from the

Command Interpreter or from the POSIX Shell.

To start the daemon from the MPE CI, enter the command:

:RPCD.PUB.SYS

This command ﬁle will build a job ﬁle and stream it to create the RPCD

daemon.

To start the daemon from the POSIX Shell, enter the following

commands:

$ export PATH=$PATH:/usr/bin

$ rpcd