
[History]
[PDP-11/70]
[Contact]
[Disclaimer]





Rack 1 - TU16 9-track tapedrive
Rack 2 - 11/70 processor
Rack 3 - 11/70 memory box
Rack 4 - comms interface
Rack 5 - comms equipment
3x RM03 as storage sub-system
A DecWriter III (LA-120) as the console

1 - SQL Language User's Guide
2 - SQL Language Reference Guide
3 - User Friendly Interface
4 - Interactive Application Facility
5 - Report Writer / Text formatter
6 - Host Language Interface
7 - Database Administrators Guide
8 - Installation Guide
9 - Error Messages
Instructions.
It is assumed that the container file is attached in SIMH as rl0.
Create a privileged account, suggested is [4,10], [ORACLE] or [ORA414] if you
want to use a named directory :
cre/dir du0:[4,10], cre/dir du0:[ORACLE] or cre/dir du0:[ORA414]
set def du0:[4,10], set def du0:[ORACLE} or set def du0:[ORA414]
Mount the distribution RL02 pack :
allocate dl0:
mount/public dl0:oraclev4
Copy the code to the system disk :
copy dl0:[4,200]*.* *.*
Unmount the distribution disk :
dismount dl0:
Build the Oracle software :
@orbld
(When the build script asks the device, specify du0:, assuming you are
using either Johnny's or Mark Matlock's disk image on your PiDP-11/70.)
Two scripts are created, 'insoracle.cmd' and 'remoracle.cmd'.
The 'insoracle.cmd' is typically used from lb:[1,2]startup.cmd and
loads the ORACLE sofware into memory. Whereas 'remoracle.cmd' is typically
called from lb:[1,2]shutup.cmd' for an orderly removal of the software
from memory before system shutdown..
Furthermore, a global logical named 'sys$oracle is created and points
towards the install directory.
To make the Oracle HELP file part of the HELP system, edit
lb:[1,1]dcl.hlp and lb:[1,2]mcr.hlp. Add the name 'ORACLE' to the
keyword section, and '1 ORACLE' to the end of the file, followed by
'@ORACLE' on the next line.