Overview
It is an accepted fact that relational database
architecture has won the battle for supremacy in the world of database design.
Any organisation currently making use of IDMS databases must have a succession
plan in place that addresses the issue of a future where IDMS will be replaced
by one of the dominant players in the relational database world.
MigrationWare
provides a powerful solution to those companies wishing to migrate their systems
dependent on IDMS databases, to a relational database alternative, whether DB2,
Oracle, SQL Server or any other leading RDBMS. As with most MigrationWare
conversion solutions, the approach to IDMS database migrations free companies
from run-time components or “black-box” technology.
The migrated application is
therefore delivered in a form that positions the company to take full advantage
of the native technologies available on the target platform. In order to reduce
the impact on the application being converted the MigrationWare approach seeks
to minimise the amount of change required within the business logic by
introducing an I/O module concept that removes from it all data access logic
placing it into a separate data access layer.
Existing data structures that are
understood by the application therefore remain unchanged resulting in the
program architecture and logic flow likewise remaining unchanged whist all the
benefits associated with running against a RDBMS database will accrue to the
migrated application. The MigrationWare approach to IDMS database migration
address the complexities associated with concepts that are unique to IDMS and
that find no equivalent in the relational database world.
Such concepts as DB Keys, sets ordered by
next and prior currencies, multimember sets, and area sweeps amongst others are
fully dealt with ensuring full compatibility with the IDMS environment and thus
ensuring the functional equivalence of the migrated systems. Benefits Migrating
away from IDMS database systems represents a migration away from a “burning
platform” that exposes business to increasing risks and spiraling costs.
Migrating to an open and contemporary RDBMS database is both a strategic move,
removing substantial risks, it is also a cost efficient alternative to the IDMS
environment.
Migrating according to the MigrationWare approach ensures no new
proprietary layers are introduced to add complexity or cost to the migrated
environment, and that the impact on the application being migrated is kept to a
minimum thus ensuring that the application can be migrated with minimum effort
and with lower costs.
MigrationWare provides a highly automated approach to IDMS
database migrations, but also acknowledges that manual intervention is required
to address some of the areas where the divergence between IDMS and RDBMS’s are
greatest.
Thus MigrationWare’s approach to IDMS migrations includes both
automation tools as well as an important services component that ensures support
throughout the migration project ensuring a successful project.
The introduction
of an I/O module architecture segregates the technical environment according to
function and this allows possible future changes in database technology to be
undertaken non intrusively simply by replacing the existing I/O modules with I/O
modules appropriate for the new database. |
|
Key features
• Completely automatic translation of application source code.
•
Introduced separation of business logic from data access logic • Supports
deployment onto both EBCDIC and ASCII
• No black boxes or run-time dependencies
• No license or maintenance fees Conversion execution MigrationWare will work
with you to deliver according to a plan best suited to your needs. This may
range from a turnkey solution to a conversion service only.
The standard
MigrationWare offering based on the provision of a conversion service would
require the client to deliver to MigrationWare the IDMS database dictionary
information plus all related source code which will include programs copybooks
and any other related data.
MigrationWare would then undertake the conversion of
the programs and database structures and achieve an error free clean compiling
environment. The converted programs would then be provided to the client for
subsequent testing and implementation. Should any issues surface, which require
MigrationWare’s involvement, MigrationWare will remain active in a support role
throughout the testing phase.
Pricing
Each project is unique with differing
requirements volumes, schedules and deadlines. It is therefore usually
impossible to supply a fixed pricing structure.
A final quote is only provided
after initial interaction with the client and when MigrationWare has fully
understood the scope of the project and the client’s required involvement from
MigrationWare. |