IDMS migration
IDMS migration
Unlock business logic trapped in IDMS and migrate to open, relational architectures.

IDMS is in our DNA
Network-model databases hold decades of business rules. We convert IDMS data and the programs that navigate it to relational systems such as Db2, SQL Server or Oracle — or retain existing access patterns where that is the right call.
What we convert
- IDMS databases to relational tables in Db2, SQL Server or Oracle
- IDMS DML calls in COBOL programs to SQL data access
- IDMS-based online and batch workloads, including the JCL that runs them
How we do it
Every engagement follows the same proven path: an in-depth analysis of the current environment, a complete inventory of programs, databases and integration points, automated conversion, and functional, performance and regression testing before cutover.
Test your IDMS knowledge
Try two of the challenges we use when we talk shop:
- Know IDMS? Take the DBA Challenge — a 1211 return code with the area only 60% full.
- Know IDMS? Take the Developer Challenge — the most efficient way to erase every occurrence of a record within an Area.
Other conversion paths
TELON ➜ CICS · COBOL · DB2TELON migrationDecommission generated code and replace it with maintainable, standards-based COBOL, CICS programs and BMS maps.
Easytrieve ➜ COBOLEasytrieve migration100% automated conversion of reports and extracts to COBOL with full functional equivalence.
Natural / Adabas ➜ COBOL · Java · RDBMSNatural / Adabas migrationAssess with NatMiner, then convert to functionally equivalent COBOL DB2 or Java on a relational database.
Mantis / Supra ➜ COBOL · DB2 · SQLMantis / Supra migrationA COBOL replacement with no run-time libraries — on z/OS DB2, SQL Server, Oracle or PostgreSQL.
Datacom / IDEAL ➜ COBOL · DB2 · SQL ServerDatacom / IDEAL migrationIDEAL, DBNTRY and Datacom converted with automated tools — reusing your COBOL business logic.
Take the next step
Moving off IDMS? Schedule a no-cost call to review your databases and programs.