Why does "just send us the file" take six to eight weeks per extract when an enterprise shares data with its ISV, and what changes when PropelZ from VirtualZ Computing runs on both sides of the feed, whether the data lives on IBM Z, IBM i, Linux, Windows or in a SaaS tenant? Every ISV runs on data its customers have to send it. Every enterprise sends its data to a long list of ISVs and service providers to get the service it already paid for. Both sides are waiting on the same file: a custom extract program somewhere in the customer's estate, and a one-off intake on the ISV's side that decodes a different layout from every customer. The enterprise isn't getting what it pays for. The ISV isn't delivering what it sold. Neither of them caused it. In this episode of Skyward Data, the podcast from VirtualZ Computing, founder and CEO Jeanne Glass and co-founder and CTO Vince Re take the file out of the middle: → Why "just send us the file" is a two-sided problem nobody has owned, and what it costs: six-to-eight-week extracts, months of backlog, jobs that break when a field changes, and on the mainframe, metered MIPS that raise the licence cost of everything else running → Send side: one product replaces tens of hand-built extracts from any system; the layout you already have, a COBOL copybook or a database table definition, is the spec → Receive side: one engine decodes every customer's data inside the ISV platform, on any system with a Java environment, and the customer installs nothing → Who owns the metadata: the customer declares what it will send, or the ISV publishes what it needs, and PropelZ supports both → The hybrid model: the ISV runs PropelZ by default; the customer runs it on its own side to filter before sending and cut the ISV's processing by roughly half → On the mainframe: zIIP-eligible so it doesn't drive the MIPS bill, or run on Linux, Windows or Linux on IBM Z, with round trips back to VSAM when you need them → Incremental every ten minutes without turning on CDC or journaling, and inventories of thousands of files run in parallel → How a top-tier global bank asked its banking platform ISV to use PropelZ, and the ISV built it into its platform as a container with no mainframe in its estate → A proof of concept of close to 10,000 datasets: Friday to Monday on the incumbent tool, a couple of hours on PropelZ PropelZ is VirtualZ Computing's patented, no-code data movement and decoding platform for IBM Z, IBM i, Linux, Windows, UNIX, VSE, VM and any Java-enabled environment. It reads VSAM, sequential, Db2, IMS, IDMS, copybook-described EBCDIC, database and delimited data in place, transforms it in flight, and delivers it in one hop to more than 100 JDBC targets and native connectors including Snowflake, Databricks, Splunk, Power BI, Vertex AI and SageMaker, at 56,000 records per second, mainframe to cloud. Topics: ISV data sharing, enterprise data sharing, customer onboarding, data extraction, IBM Z, z/OS, zIIP, IBM i, Linux, COBOL copybook, VSAM, Db2, SaaS data, data integration, PropelZ, VirtualZ Computing Listen to more Skyward Data episodes: https://virtualzcomputing.com/podcasts/
