[Info-vax] OpenVMS STARTUP Whitepaper

[Arne Vajhøj]

On 12/11/2020 11:12 AM, Jan-Erik Söderholm wrote:
> Den 2020-12-11 kl. 15:51, skrev Arne Vajhøj:
>> On 12/11/2020 7:55 AM, Craig A. Berry wrote:
>>> I believe in the case of Rdb there is no start-up because there is no
>>> service -- you just link your code against the libraries and run it in
>>> the context of whatever process.  In other words, the same way you are
>>> running SQLite.
>>
>> Rdb use file access (unless using the using one of the remote network
>> protocols that rely SQL service or a thin JDBC driver server).
> 
> SQL/Services is for the SQL/Services API (as used by ODBC drivers),
> JDBC from Java based clients or OCI from clients that thinks they are
> accessing an Oracle Classic database.

JDBC native driver (type 2) does not require the server.

JDBC thin driver (which Oracle calls type 4 even though it to me seems 
more like a type 3) does require the server.

> Then you can run "RDBSERVER" using it's own protocoll. That s mainly for
> VMS-2-VMS access such as when you want the single-node optimazitions
> within a cluster and having the other cluster nodes access Rdb remotely
> instead of direct shared access (involves more cross-cluster locking).
> Doesn't have to be a cluster, of course.

That type of pro/con is beyond my current Rdb knowledge
(I have not worked with it professionally since 1998).

>> But will Rdb work properly without the RDMS_MONITOR and RMU processes 
>> running?
> 
> No, your application will not do anything with the data without having
> an "OK" from the monitor. You send an "attach request" (well, the code
> in the sharable images does) to the monitor and the monitor says "OK".

>> Will it work properly without the Rdb logicals being defined?
> 
> No, you need at least some of the logicals setup by the startup file.

That is what I thought.

Rdb is not really like SQLite.

Arne