DataMuseum.dk

Presents historical artifacts from the history of:

Rational R1000/400

This is an automatic "excavation" of a thematic subset of
artifacts from Datamuseum.dk's BitArchive.

See our Wiki for more about Rational R1000/400

Excavated with: AutoArchaeologist - Free & Open Source Software.


top - download

⟦8c167f273⟧ TextFile

    Length: 1218 (0x4c2)
    Types: TextFile
    Notes: R1k Text-file segment

Derivation

└─⟦8527c1e9b⟧ Bits:30000544 8mm tape, Rational 1000, Arrival backup of disks in PAM's R1000
    └─ ⟦cfc2e13cd⟧ »Space Info Vol 2« 
        └─⟦8ba248a0e⟧ 
            └─⟦this⟧ 

TextFile

Rpc_Generator =>
Provides an interface that will generate and RPC server and client for
any Ada interface.  An R1000 body for the Ada spec, server spec and
body for the remote machine, and all definition and data interchange
packages are generated.  The user must fill in prompts for the remote
machine name and the socket id for use by this server.

For a given SERVICE package spec, the following Ada packages are 
genearated:

SERVICE'BODY:

  This is the implementation for the client interface.  For each
  subprogram in the specification, the body allocates a transport 
  stream, puts the procedure number and arguments into the stream,
  and gets the results. 

SERVICE_INTERCHANGE:

  Defines Get and Put operations for types not supported by the
  standard RPC Interchange package.  For example, if the service
  provides a subprogram which uses integer parameters, the client
  and server programs can use the integer Get and Put operations
  provided by the standard RPC Interchange package.  However,
  suppose the service defines a new record type and uses that type
  as a parameter to one of it subprograms.  In this case, Get and
  Put operations must be defined in the Service_Interchange package.