Why does moving DB2 mainframe data to platforms like Snowflake still require weeks of manual COBOL copybook creation — and how can you skip that step entirely? VirtualZ Computing CTO Vince Re explains how PropelZ's automatic metadata discovery removes copybook work from database integration, so a DB2-to-Snowflake migration that used to take months can run in minutes.

Vince Re breaks down why copybook creation has quietly slowed mainframe database projects for decades, and how self-describing databases change the equation: PropelZ reads the table's own metadata automatically, so you write a SQL query and run the move instead of hand-building copybooks first. That makes deep COBOL expertise optional for database data movement, not a prerequisite.

In this episode of Skyward Data, the podcast from VirtualZ Computing:

- How automatic metadata discovery replaces weeks of manual copybook engineering for database integration - Why "write a SQL query and run it" is the modern alternative to copybook-first workflows - A real DB2 table migration that went from complex to straightforward - Why manual metadata management is the biggest adoption barrier for mainframe database projects - How the approach scales from a single table migration to billion-row analytics workloads

PropelZ moves and replicates IBM Z mainframe data — including DB2 — to cloud data warehouses like Snowflake, Databricks, Redshift, and BigQuery with no code and no homegrown pipelines, and is proven at 56,000 records per second, mainframe to cloud. It's part of VirtualZ Computing's no-code portfolio for enterprise mainframe data, alongside Lozen (live in-place data access), FlowZ (cloud storage for backup and archive), and Zaac (cloud and SAN as native z/OS storage).

Topics: DB2 migration, mainframe copybooks, metadata discovery, Snowflake, Databricks, IBM Z, z/OS, cloud data warehouse, SQL, no-code data integration, hybrid cloud.

Listen to more Skyward Data episodes: https://virtualzcomputing.com/podcasts/