Our VSAM conversion strategy includes the generation of a new relational database to replace the functionality, redefinitions, type-of-record indicators, and other data element structures that are currently part of most VSAM files. 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, or IBM DB2.
We also handle the conversion of applications and languages that use VSAM files including COBOL, PL/1, Assembler, JCL and Procs for VSAM applications.
Replacement of Database Functionality through VSAM Conversion
Our VSAM conversion solutions provide a complete replacement for all legacy database functionality including multi-view records, occurring fields, indexes, and more. The resulting database is fully relational, primary 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.Learn More
VSAM Data Conversion
The VSAM data extract and relational load process is simple, straightforward, and fast. Modern Systems can provide a number of extract variations for sites that have special requirements for a short VSAM data conversion window. Special workbenches within DB-Shuttle provide additional capabilities for tailoring your data migration so that the new database meets your needs and requirements.Learn More
Visibility and Knowledge Building
Modern Systems also ensures that customer development teams have a full understanding of VSAM file structures and the post-conversion relational database. DB-Shuttle generates many reports and diagrams to assist with this knowledge-building process as part of the VSAM conversion solution.Learn More