How do I migrate my IMS DB and IMS TM (DC)?

Using IMSql, the gold standard for IMS migration to Azure, your transition remains smooth and stress free

logo .net Azure

Key features of IMSql

Supports both IMS/DB and IMS/DC (or TM)
Access to legacy data through read-write relational views
Smooth integration of new technologies through the IMS queueing mechanism
Non-transformational: the source code remains unaltered and data is migrated as is
Checkpoint and restart
GSAM support
Supports calls to CBLTDLI, PLITDLI and EXEC DLI statements

IMS migration to Azure

Raincode IMSql is the gold standard for both IMS /DB migration and IMS /TM migration to Azure.

IMS is a two-headed beast made of a hierarchical database manager (IMS/DB) and a transaction processing manager based on queues (IMS/DC). Using IMSql, rehost your IMS systems to .NET Core and Azure. Your mainframe applications remain completely untouched and are recompiled ‘as is’ for .NET framework or .NET Core. They interact with IMSql just as they did with IMS/DB and IMS/DC on the mainframe.

IMSql migrations are non-transformational. Your original code is not translated or modified, it is preserved ‘as is’ when you deploy on the target platform. This innovative technology covers both IMS/DC and IMS/DB and migrates them seamlessly to Microsoft SQL Server and Azure, with no code transformation.

IMS/DC systems beyond a few hundred MIPS require more than a minimal IMS layer on top of an existing CICS emulator. IMSql is not a derivation of an existing CICS emulator: it was created from the ground up, for the most demanding IMS installations. IMSql is fully scalable, both vertically and horizontally, your applications are no longer restricted to the constraints of a mainframe.

IMSql leverages Microsoft SQL Server, as not only a database but also as a transaction processor and an execution platform. Unload your mainframe data and upload it onto Microsoft SQL Server. Map IMS concepts such as transactions and queues directly onto SQLServer equivalent concepts.

IMSql defines SQL views based on copybooks, so that the migrated segments can be used with plain SQL statements for ad hoc queries or new applications.