| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 939.1 | Use Natural/Rdb | NOT003::DENTI | Ian Dent @NOT, Nottingham, UK | Fri Jun 21 1991 18:08 | 27 |
| Software AG have announced a version of Natural to run against Rdb
and/or RMS.
This is based on Natural V2 which is a very different beast to Natural
V1.
According to Software AG's marketing, the transfer from Adabas to
Rdb should be very easy with the same Natural code running against
each database.
The transfer of the data may be harder in that Adabas is not
relational. It supports repeating fields and repeating groups which
must be converted to Rdb structures in some way.
Natural itself could be used as the conversion tool as a program
can read from one database manager (adabas) and write to another
(Rdb).
Conversion generally consists of 2 phases: 1 is to get the programs
working correctly against the new database: 2 is to get them performing
as well as they used to.
It is likely that the same Natural programs written to run against
Adabas will run slower against Rdb if no changes are made. Changes
needed must be quantified somehow.
Ian
|
| 939.2 | What sort of migration program is required? | ZPOVC::MICHAELLEE | | Sat Jun 22 1991 05:03 | 11 |
| re:.-1
Thanks for the reply.
Could the program that reads from adabas and writes to Rdb be written
in Natural script or 3 GL language?
I supposed the Rdb database needs normalisation before using the above-
mentioned program.
Mike
|
| 939.3 | 3GL or Natural | NOT003::DENTI | Ian Dent @NOT, Nottingham, UK | Mon Jun 24 1991 16:10 | 21 |
|
Conversion program could be written in Natural V2 (read from Adabas
database and write to Rdb) or any Vax 3GL. Using the 3GL "direct
calls" need to be written to access the Adabas database. These calls
consist of setting up a lot of buffers and then calling Adabas.
A 3GL program could be written containing embedded SQL (for Rdb)
and direct calls (for Adabas).
Software AG also sell a product called Adasql which allows for SQL
statements to be embedded in Cobol, Fortran or PL/I programs and
run through a pre-compiler. This is unlikely to be of interest to
you as it requires Natural and Predict as pre-requisities. If Natural
must be purchased it may as well be used.
Rdb database does not have to be normalised. It could be any design
you like. Obviously, for ease of conversion of data from Adabas
to Rdb, it should be the same design as Adabas wherever possible.
Ian
|
| 939.4 | TYFYS::DATA_CONVERSION gone ?? | COPCLU::BRUNSGAARD | Who said I'm paranoid ??!? | Wed Jul 17 1991 11:46 | 7 |
| In .0 there is a notes file mentioned. Where did it go (or maybe the
note was not completly correct).
I get FILE NOT FOUND if I try to open it
Thans in advance
Lars
|
| 939.5 | Name correction | SHALOT::DUNCAN | Joe - CIS/EIC/DCC Groupworks Team | Thu Jul 18 1991 18:36 | 3 |
| That should be TYFYS::DATABASE_CONVERSION
Joe Duncan @ OPA
|
| 939.6 | Still doesn't work | COPCLU::BRUNSGAARD | Who said I'm paranoid ??!? | Fri Jul 19 1991 10:23 | 5 |
| But Joe, that is what was written in .0 wasn't it ??
Well anyway I still get FILE NOT FOUND.
Still confused
Lars
|
| 939.7 | I guess this counts as my mistake for FY92! ;-) | SHALOT::DUNCAN | Joe - CIS/EIC/DCC Groupworks Team | Fri Jul 19 1991 22:18 | 4 |
| Sorry about that, we left of the last letter. The name of the
conference is TYFYS::DATABASE_CONVERSIONS <- notice the use of plural!
Joe Duncan @ OPA
|