.NET Framework and Mainframe Collide

Collisions generally have negative connotations, however in this case it is actually a good thing.

The mainframe world, all too often associated with legacy systems that exist in some dark corner of buildings continues to this day to provide the essential back bone for many corporations essential and business-critical applications. While some companies seek to migrate data out of mainframe investments into data bases such as Oracle, or often SQL Server there are plenty who'd rather leave these resources well alone and bring on stream more up to date interfaces to these data asources.

That said, development platforms such as Java and the .NET platform however enjoy the majority of developer focus today and resources such as DB2 z/OS and non relational mainframer esources such as VSAM, IMS and Adabas get left behind.

Our solution? Shadow for ADO.NET. Available for use with the Shadow z/Direct product line, DataDirect's mainframe integration software stack. We are very proud of the work we've done here, so let me call out some of the major features:

• Integration of mainframe DB2 and VSAM data
• 100% managed code provider
• Support for the .NET Framework 2.0, 3.0 and 3.5 on 32-bit and 64-bit platforms
• Support for ADO.NET 2.0 Common Programming Model
• Runtime compatibility with Visual Studio
• Support for a Metadata Collections based on the ANSI SQL Information Schema specification as well as collections specific to CICS and VSAM
• Support for common methodologies used to manage auto-generated values

Hungry for more ? Check out the Shadow for ADO.NET for details.