|
DataMuseum.dkPresents historical artifacts from the history of: Rational R1000/400 Tapes |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about Rational R1000/400 Tapes Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - metrics - downloadIndex: R T
Length: 7014 (0x1b66)
Types: TextFile
Names: »RPC_RELEASE1_0_2_LPT«
└─⟦bad92a95e⟧ Bits:30000535 8mm tape, Rational 1000, RPC 1_0_2
└─⟦bb34fe6e2⟧ »DATA«
└─⟦a9a24a109⟧
└─⟦this⟧
Rational Remote Procedure Call Facility:
HP 9000 Series 300
Release Information
Rev1_0_2 Release
\f
Copyright 1991 by Rational
Part Number: 508-003259-003
April 1991 (Software Release Rev1_0_2)
Rational and R1000 are registered trademarks and Rational
Subsystems is a trademark of Rational.
UNIX is a registered trademark of AT&T.
Rational
3320 Scott Boulevard
Santa Clara, California 95054-3197
\f
Rev1_0_2 Release
1. Overview
The Rational Remote Procedure Call Facility: HP 9000 Series 300
(RPC) allows users to easily build programs hosted on an R1000
and an HP 9000 that communicate via remote procedure calls. For
example, the RPC facility allows an application running on one
host to access databases and software on another host.
RPC is based on the Ada procedural call model, extending calls
between hosts. In effect, it allows an application to make an
intersystem procedure call. This mechanism allows users to build
their own interfaces to remote resources.
Refer to the Rational Networking-TCP/IP Reference Manual, Volume
2, for more detail.
2. Views
The RPC product is released in three Rational Subsystems:
!Targets.Implementation.Transport
!Targets.Implementation.Rpc
!Targets.Implementation.Rpc_Example
* The Transport subsystem contains the implementation of the
transport layer in two views: Mc68020_Hpux_0_2 and
Mc68020_Hpux_Cdf_0_2. Two views are required because of HP
9000 Ada compiler dependencies; the former is compatible with
the HP 9000 Ada compiler, and the latter with the Rational
M68020/UNIX CDF.
* The Rpc subsystem contains the implementation of the RPC layer
in one view: Mc68020_Hpux_Cdf_0_2. There are no compiler
dependencies in this layer, so the same source code executes
when downloaded and compiled using the HP 9000 Ada compiler or
the Rational M68020/UNIX CDF compiler.
* The Rpc_Example subsystem contains a sample RPC application in
two views: R1000_0_2 and Mc68020_Hpux_Cdf_0_2. Both views are
provided so that users can demonstrate the RPC facility with
clients and servers running on R1000s and/or HP 9000s.
3. Limitations
* Package Transport
Only the subset of procedures necessary to support RPC is
implemented at this time. These procedures are:
RATIONAL April 1991 1\f
Rational Remote Procedure Call Facility:
HP 9000 Series 300 Release Information
Open
Close
Connect (Active Form)
Connect (Passive Form)
Disconnect
Is_Open
Is_Connected
Transmit
Receive
All Max_Wait parameters are ignored in this release and
default to Duration'Last. This has no impact on RPC but
affects users coding directly against package Transport.
All I/O calls in this package are blocking in this release.
This means that, if one task issues an I/O call, the entire
process is blocked until the I/O operation completes.
* Package Transport_Server
The Max_Servers parameter is ignored in all procedures in this
package, and the value defaults to one. That is, servers
implemented with this release of RPC are single-threaded and
only one client is serviced at a time. This is because package
Transport provides only blocking I/O.
* Package Rpc_Server
The generic procedure Serve_With_Username is not implemented
in this release.
* Package Complex_Service (included with the example)
The Value and Image functions are not implemented in this
release.
4. Known Problems
A bug causes the example server generated by the HP 9000 Ada
compiler to malfunction. This bug is manifested by the sample
client getting the exception Transport_Stream.Not_Connected when
running on the R1000. The workaround is:
1. Start the example server under the HP 9000 Ada debugger, Ada
Probe.
2. Kill the debugger using the UNIX Kill command on the
debugger's Process ID.
3. Kill the client job on the R1000, if necessary.
4. Restart the server on the HP.
2 April 1991 RATIONAL\f
Rev1_0_2 Release
5. Fixed Problems
In Rev1_0_1 of the RPC, if a server runs on a machine whose
Internet address has a high order byte greater than 127, the
client dies the first time that it requests service from that
server. Rev1_0_2 fixes this problem.
6. Compatibility
Other than the limitations described above, all specs released
with the RPC facility are compatible with the R1000 networking
product. Users can port code that has been implemented against
the R1000 networking product simply by recompiling.
7. Documentation
The RPC facility is documented in the Rational Networking-TCP/IP
Reference Manual, Volume 2.
RATIONAL April 1991 3\f
Rev1_0_2 Release
Contents
1. Overview 1
2. Views 1
3. Limitations 1
4. Known Problems 2
5. Fixed Problems 3
6. Compatibility 3
7. Documentation 3
RATIONAL April 1991 iii\f
Rational Remote Procedure Call Facility:
HP 9000 Series 300 Release Information
iv April 1991 RATIONAL\f