We're a consulting company in the US trying to help one of our customers
convert a set of applications from Adabas to IDMS. Our own experience
with these DBMSes is limited but, from what the customers says, the
application only access Adabas via about 300 Natural sub-routines and one
solution would be to rewrite these routines to change data base accesses
from Adabas to IDMS - we're not sure how true this is though.
Is there any consultant with strong IDMS skills on this list willing to
help us propose a solution to our customer? Please e-mail or call me
directly - thanks in advance.
Gilbert Saint-flour
Livingston, NJ 07039
(973) 992-9318
PS: in case you're wondering, the customer is moving the application from
an environment where they have Adabas to another environment which already
has IDMS; they want to avoid the Adabas license fees in the target
environment.
Steve Mason
GEEZLE, INC.
Don't forget that IDMS can also be implemented as a Relational Database, with SQL
as the method of access, if the SQL option has been purchased. Also, with the SQL
option installed, you can even access the network databases with SQL. It is a
quite powerful product.
The Tesseract package (HRMS/BENEFITS/Payroll) supported both Adabas and IDMS.
They did it using a black box module (linked into the I/O) to read/write.
The Tesseract package was written to read/write VSAM.
The blackbox was changed to support ADABAS/IDMS/IMS/DB2/VSAM.
The first thing to consider is the mapping from one schema to another.
I think ADABAS is Relational and IDMS is Network.
The next question is to find out if Natural will support IDMS.
If it does, then the subroutine change would be the best long term.
I would look at the ADABAS module in Natural to see how it works.
I would try convert one module to IDMS to get a handle on how hard it would be.