| Title: | DEC Rdb against the World |
| Moderator: | HERON::GODFRIND |
| Created: | Fri Jun 12 1987 |
| Last Modified: | Thu Feb 23 1995 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1348 |
| Total number of notes: | 5438 |
<<< BEAGLE::USER06:[NOTES$LIBRARY]RDB_VMS_COMPETITION.NOTE;1 >>>
-< Rdb/VMS against the world >-
================================================================================
Note 653.0 ADABAS/RDB/DBase IV No replies
CGOO01::LMILLER "hasten slowly" 25 lines 17-MAY-1990 23:41
--------------------------------------------------------------------------------
I have a prospective Government client who is looking for a solution to the
following situation in his environment:
He would like to extract data from files in ADABASE (on the IBM host)
and Clipper/DBase IV (on a PC). The extractions would be used to
create a report. He has Natural on the IBM.
He does not yet have any Digital solutions but has heard some of our
messages (such as DECDecision) and is interested in purchasing
whatever is required to make this happen.
Obviously we would like to control the whole thing - I would like
to suggest CDD+ RDB/VMS with DECdecision (I know Natural/RDB
is in it's infancy) and then with RDB/VMS SQL Services talk to DBase IV.
However I have heard that ADABAS has a SQL - (I read it somewhere)
- how would this SQL 'talk' to RDB (if it can) - and is it still
a viable product.
Ideally it should be an ALL Digital solution - but I would rather
try and get a foot in the door - and then follow with the rest of
the troops.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 653.1 | Use Network and Adabas direct calls | NOT003::DENTI | Ian Dent, Nottingham, UK | Fri May 18 1990 11:39 | 38 |
ADASQL product from Software AG allows a "super-subset" of standard
ANSI SQL to be embedded into Fortran, Cobol or PL/I programs. This
is implemented as a pre-compiler that takes the 3GL source and
generates Adabas "direct calls".
An Adabas direct call is the lowest level of access to the database
and consists of a call to a Software AG supplied library routine
passing a load of parameters (e.g. details of command to be executed,
buffer for returning the requested data, etc.). This interface is
documented by Software AG and a few customers use it for fast access
to the database.
Natural actually generates Adabas direct calls internally for its
access to the Adabas database.
Software AG also supply a set of Net-work products which allow the
direct calls to Adabas to be passed between systems. These Net-work
products include ones for communication between Vaxes using Decnet
and for communication from VMS to IBM using SNA/Gateway or Hyperchannel
(3rd party hardware).
In order to allow access to an IBM Adabas database from an application
on the Vax:-
Write the application in Cobol using Adabas direct calls. Use the
Net-work (SNA/Gateway) product to pass these direct calls to the
Adabas database on the IBM and receive the requested information
back into the Cobol program. Use SQL in the Cobol program to access
the Rdb database.
In order to avoid using direct calls the ADASQL product could be
used. However this requires Predict, Software AG's data dictionary,
to be present on the Vax which itself requires that Natural is present
on the Vax. Therefore if ADASQL was proposed the customer would
have to take the full Software AG product set and may choose to
use SAG products (e.g. Natural) rather than DEC's.
Ian Dent
| |||||
| 653.2 | Need More DEC | CGOO01::LMILLER | hasten slowly | Fri May 18 1990 19:36 | 10 |
Thanks that helps clarify several points.
However, that could open a Pandora's box, even though we would
REALLY like to get a VAX in there, we would like to "control" the
database and hence muscle in even more. I guess I'll have to put
on my creative propeller hat and see if we can come up with something
more "US" (Dec).
Linda
| |||||