|
|
DataMuseum.dkPresents historical artifacts from the history of: Rational R1000/400 |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about Rational R1000/400 Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - metrics - download
Length: 5120 (0x1400)
Types: Ada Source
Notes: 03_class, FILE, R1k_Segment, e3_tag, seg_04aa7a
└─⟦8527c1e9b⟧ Bits:30000544 8mm tape, Rational 1000, Arrival backup of disks in PAM's R1000
└─⟦cfc2e13cd⟧ »Space Info Vol 2«
└─⟦this⟧
WITH Interchange;
WITH Rpc;
WITH Transport_Defs;
WITH Time_Utilities;
PACKAGE Date_Defs IS
GENERIC
TYPE Stream_Id IS LIMITED PRIVATE;
WITH PROCEDURE Put (Into : Stream_Id; Data : Interchange.Time) IS <>;
WITH PROCEDURE Get (From : Stream_Id; Data : OUT Interchange.Time) IS <>;
WITH PROCEDURE Put_String (Into : Stream_Id;
Data : Standard.String) IS <>;
WITH FUNCTION Get_String (From : Stream_Id) RETURN Standard.String IS <>;
PACKAGE Interchange_Operations IS
PROCEDURE Put (Into : Stream_Id; Data : Time_Utilities.Time);
PROCEDURE Get (From : Stream_Id; Data : OUT Time_Utilities.Time);
PROCEDURE Put (Into : Stream_Id; Data : String);
PROCEDURE Get (From : Stream_Id; Data : OUT String);
END Interchange_Operations;
FUNCTION Network RETURN Transport_Defs.Network_Name;
-- The constant Network was replaced with this function so that the actual
-- network name value could be embedded in the body and reduce compilation
-- dependencies...LP
--
-- The two functions below Sparc_Socket and R1000_Socket return the
-- values to be used by the Server task when it is run from the Sparc
-- station or R1000, respectively.
--
-- The client task will use the correct socket value to communicate with
-- the Server. For instance, if the Server is running on the R1000 then
-- the client task would also use R1000_Socket. If however, the Server
-- is running on the Sparc_Station, it would use Sparc_Socket.
--
-- Function calls are used so that the actual socket values are embedded
-- in the package body to minimize recompilation dependencies should the
-- socket values require changing.
FUNCTION Sparc_Socket RETURN Transport_Defs.Socket_Id;
-- This function returns the socket value to be used by the Server when
-- run on the workstation.
FUNCTION R1000_Socket RETURN Transport_Defs.Socket_Id;
-- This function returns the socket value to be used by the Server when
-- run on the R1000.
-- The constant Socket was replaced with this function so that the actual
-- socket value could be embedded in the body and reduce compilation
-- dependencies...LP
--
Program : CONSTANT Rpc.Program_Number := 45;
Version : CONSTANT Rpc.Version_Number := 0;
PACKAGE Proc_Number IS
Date : CONSTANT Rpc.Procedure_Number := 0;
END Proc_Number;
PACKAGE Exception_Number IS
Overflow : CONSTANT Rpc.Exception_Number := 1;
Underflow : CONSTANT Rpc.Exception_Number := 2;
END Exception_Number;
END Date_Defs;
nblk1=4
nid=0
hdr6=8
[0x00] rec0=1b rec1=00 rec2=01 rec3=012
[0x01] rec0=06 rec1=00 rec2=04 rec3=07c
[0x02] rec0=18 rec1=00 rec2=02 rec3=02c
[0x03] rec0=11 rec1=00 rec2=03 rec3=001
tail 0x2174f21de867456e97a86 0x489e0066482863c01