[Info-vax] OpenVMS STARTUP Whitepaper
Phillip Helbig undress to reply
helbig at asclothestro.multivax.de
Fri Dec 11 12:46:52 EST 2020
In article <rr05p2$8bi$2 at dont-email.me>,
=?UTF-8?Q?Jan-Erik_S=c3=b6derholm?= <jan-erik.soderholm at telia.com>
writes:
> Den 2020-12-11 kl. 15:51, skrev Arne VajhÞj:
> > On 12/11/2020 7:55 AM, Craig A. Berry wrote:
> >> On 12/10/20 11:28 PM, David Jones wrote:
> >>> On Thursday, December 10, 2020 at 8:57:16 PM UTC-5, Stephen Hoffman wrote:
> >>>> SQLite can be useful for storing the data, particularly for those
> >>>> without Oracle licenses and that for whatever reason.
> >>>
> >>> Using Oracle in your startup sequencer means you have to start it before
> >>> you can run
> >>> the thing that starts it -- somewhat problematic. A cloud-based database
> >>> still needs the
> >>> network running. I link the startup driver application statically with
> >>> the sqlite3 library
> >>> and run it with the data file flagged as immutable (readonly, no locking).
> >>
> >> 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.
>
> 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.
Or to save license costs?
> If you are running DECnet, you can specify a remote file (just as when
> using FAL) in the attach and the Rdb code will detect that and connect
> the the remote RDBSERVER object without the application having to care.
> (I thinkthat also works for TCPIP, do not use this).
I think that it can be made to work with TCPIP.
> $ tcpip sh service rdbserver
>
> Service Port Proto Process Address State
> RDBSERVER 611 TCP RDB 0.0.0.0 Enabled
>
> $ ncp show object rdbserver
>
> Object Number File/PID User Id Password
> RDBSERVER 35 RDBSERVER.COM RDB$REMOTE <pw>
> $
>
> Anyway, RDBSERVER has nothing to do with SQL/Services that uses
> a different TCPIP port and another DECnet obbject.
Right.
> But yes, you can call RDBREMOTE for "file access", just as you can
> with FAL, since the application doesn't care.
Right.
> >
> > 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".
Right.
> > Will it work properly without the Rdb logicals being defined?
>
> No, you need at least some of the logicals setup by the startup file.
Right.
More information about the Info-vax
mailing list