HPlogo Communicator 3000 MPE/iX Release 6.0 (Platform Software Release C.60.00): HP 3000 MPE/iX Computer Systems > Chapter 6 Data/Application Integration

DCE RPC Clients for FOS through MPE/iX

» 

Technical documentation

Complete book in PDF
» Feedback

 » Table of Contents

 » Index

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 first building an idl source file, for example foo.idl for DCE,and foo.nidl for NCS. When compiled with the idl compiler, the idl source file will create Server Client Stubs and an .h file (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 file (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 file will build a job file 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

These commands will execute the script /usr/bin/rpcd which will invoke the command file 'RPCD.PUB.SYS'.

The customer needs to run his applications as:

:Run foo;xl="dcexl.hpdce.sys othdxl.threads.sys"

OR

Link this program as follows:

:linkedit altprog foo.pub.sys;xl='dcexl.hpdce.sys,othdxl.threads.sys' 

Then run foo as a executable.

NOTE: For more information on application development, refer to the section, "Building DCE Programs," in the document, DCE for the HP 3000 (Second Edition.)

The following binaries are available as part of this submittal:

GETIP

Executable which gets a host's IP address.

HOSTNAME

Gets the host name.

IDL

The IDL compiler.

IPCS

Utility to get the status of IPC (Inter Process Communication) resource usage status.

LIBDCE

Archive library of DCE modules.

NSLOOKUP

Utility to get the name and IP address of a host. It also gives name and IP adress of DNS Server.

NIDL2IDL

Cross Compiler which will convert the existing NIDL source file to IDL compatible source.

OTHDXL

Contains the PASCAL implementation of the pthread intrinsic calls.

PS

Process/Session Status

RPCCP

Control Program executable to manage end point mapping.

RPCD

Script create a job file and streams it to run rpcd daemon

WHOAMI

Command to get user name.

Feedback to webmaster