Fujitsu (ICL) IDMSX Modernization Options

Automated IDMSX Conversion

Market leaders in Fujitsu (ICL) VME migrations since 1997

A History of Innovation

Having performed hundreds of migrations and assessment projects since 1997, Modern Systems are without doubt the industry leaders in Fujitsu (ICL) VME migrations. Our experts have wide-ranging VME-specific language and database experience - responsible for migrating over 150 IDMSX schemas to relational databases, supporting full application (and data) migrations, in addition to data-only migration projects.
Some of the notable achievements include:
  • First IDMSX to Microsoft SQL Server Synchronization in 2000 – stayed in mission-critical twice-daily production use until 2015
  • First automated migration of ICL (Fujitsu) to IBM for UBS in 1998/1999 – 20% of global stock market trades migrated
  • First migration of ICL (Fujitsu) VME to Microsoft .NET in 2003
  • First daily synchronization of ICL (Fujitsu) IDMSX to Oracle databases for UK Government across 54 parallel services – 2006 to present
Some Key IDMSX Migration Benefits
  • Zero or minimal mainframe footprint (minimal risk and impact on the production system).
  • Handles both current and historic data via backups.
  • Creates a true SQL-based database from the IDMS definitions, not an IDMS emulation.
  • Mature data migration solution - operational on customer sites since 2000.
  • Highly performant & scalable, faster than any ETL (Extract Transform Load) process.
  • Enables one-way synchronization of IDMSX data with the target RDBMS, processing the IDMSX journals to generate the corresponding SQL DML
  • .

Our IDMSX conversion strategy includes the generation of a new relational database to replace the functionality, set relationships, indexes, and data structures that are currently part of the IDMSX network database. The new target database can reside on or off the mainframe, and can use any of the standard relational database management systems - Microsoft SQL Server, Oracle, IBM Db2, PostgreSQL or EnterpriseDB.

Modern Systems also supports the conversion of the applications that use the IDMSX database, including COBOL (with or without TPMS) and SCL, in addition to many specific 4GL products such as Application Master (AM) and DELTA.

Replacement of Database Functionality through IDMSX Conversion

Our IDMSX conversion solution provides a complete replacement for all IDMSX database functionality including multi-member sets, chained and sorted sets, bill-of-material structures, group and occurring fields, DBKEY usage, and more. Primary keys, foreign keys, and index definitions are automatically created, and all constraints are generated into the resulting DDL. Table spaces, indexes, table names, and column names are all generated according to your naming standards.

IDMSX Data Conversion

The IDMSX data extract and relational load process is simple, straight-forward, and fast. Modern Systems can provide a number of extract variations for sites that have special requirements for a short IDMSX data conversion window. Special Modern Systems workbenches provide additional capabilities for tailoring your data migration so that the new database meets your needs and requirements.

Visibility and Knowledge Building

Modern Systems also ensures that customer development teams have a full understanding of existing IDMSX and post-conversion relational databases. Our workbenches generate many reports and diagrams to assist with this knowledge-building process as part of the IDMSX conversion solution.

Sharing IDMSX Data Without Migration

Integrate IDMSX data with SQL Server, DB2 or Oracle data warehouses.
Get true business intelligence without disrupting the business.
We use our Mainframe DataShare technology to integrate IDMSX databases with SQL Server, Oracle, or DB2 data warehouses. High level tasks include:
  • Import the IDMSX schema & segments via DDL, automatically generate Relational schema from System Dictionary
  • Adjust Data Mapping rules and generate relational data model
  • Initial Data Load: transfer existing REPO backups to Windows, convert the IDMSX data and run the generated Oracle/SQL/DB2 Load scripts to populate the relational database
  • Ongoing Replication: transfer IDMSX Journals to Windows upon release, ‘roll forward’ the IDMSX updates against the relational database
  • Validation and verification: ensure referential integrity of the data in the IDMSX database is correct, and is maintained during the replication process
  • Prove integrity by implementing constraints to carry-forwards IDMSX integrity rules into relational database
  • Ensure row counts agree, validate that Set Membership and Sequence is the same and verify aggregate totals of fields match
2-MINUTE OVERVIEW: Mainframe DataShare

Additional IDMSX Conversion Resources

Share This