VSAM2DB2

DB2 versus VSAM

The advantages of DB2 vs VSAM are well-known by everyone:

• the DB2 Request is easier to write: You specify what you want, never the way to access the data.
• At the same time, you can access the Database by Ad-Hoc Queries.

Migration From VSAM to DB2 without VSAM2DB2

But they are a lot of reasons not to migrate to DB2
A tricky Data conversion in fact you must:

• take in account all VSAM organizations (KSDS, ESDS, RRDS and AIX)
• convert unreliable VSAM data and manage records having multiple occurrences fields

a very laborious program conversion in which you have to:

• Rewrite VSAM commands in DB2 orders, often heavy and complex
• Convert, at the same time, all the programs (Batch and CICS)associated to the migrated VSAM file

Migration From VSAM to DB2 with VSAM2DB2

For Data

You need to define under VSAM2DB2 (running in TSO environment) the VSAM files you need to migrate in DB2. Automatically VSAM2DB2 will convert these files in DB2 tables

For Programs

VSAM Programs are not to be modified or recompiled, only a VSAM2DB2 control table has to be defined:
At execution time, for your old programs accessing the new DB2 tables, a Transparency interface will translate automatically, VSAM requests in static DB2 orders.

VSAM2DB2 handles:

• the conversion from VSAM files to DB2 tables.
• the transparency of your old programs without any modification or recompiling.