DiscoverSkyward Data
Skyward Data
Claim Ownership

Skyward Data

Author: VirtualZ

Subscribed: 2Played: 2
Share

Description

Conversations That Power Smarter Data Strategies for AI, Cloud, and Innovation. Skyward Data brings you exclusive conversations with experts shaping the future of enterprise data. Discover how organizations are transforming data access, storage, and AI integration to fuel faster innovation and smarter decisions.

Each episode explores how to unlock the full power of your enterprise data—whether it lives on IBM Z, in the cloud, or deep in decades-old tape archives. We dive into real-world stories, bold ideas, and practical strategies for making mainframe and legacy data instantly accessible for AI, analytics, compliance, and modernization.

If you're building smarter systems, training better models, or powering transformation with trusted data—Skyward Data is your guide.

No fluff. No jargon. Just smart conversations about enterprise data, done right.

Learn more at virtualzcomputing.com

#AI #Mainframe #EnterpriseData #HybridCloud #DataAccess #SkywardData #VirtualZComputing

145 Episodes
Reverse
How do you get mainframe files into Amazon S3, Azure Blob or Google Cloud Storage without staging, FTP scripts or a gateway server? In this episode, VirtualZ Computing founder and CEO Jeanne Glass talks with co founder and CTO Vince Re about FlowZ, VirtualZ's patented, no-code software that lets existing z/OS jobs read and write cloud object storage directly, with a small change to their JCL. Vince was the first Distinguished Engineer in CA Technologies history and helped bring Linux to the mainframe. He explains why mainframe file transfer still runs through so many steps, and what changes when the application's own reads and writes go straight to the cloud. In this episode: - Why the first mainframe file transfer tools staged data on gateway servers, and why later tools still read and write the data three or four times - Why "object storage is just an API" turns into a programming project once you deal with authentication, credentials and more than one cloud provider - How the one JCL change works for any application using standard QSAM, VSAM or z/OS UNIX file access, with policies that send files to one destination or several - Running FlowZ like any other mainframe software: a started task, credentials kept in crypto hardware, and clear errors on the z/OS console for automation tools - Where to start (backups and audit data), how to avoid cloud egress charges, and when FlowZ isn't the right fit - IBM DFDSS backups written straight to Amazon S3, with an average volume taking about a minute over a consumer-grade gigabit connection Key questions answered: 1. How do you write mainframe files to Amazon S3, Azure Blob or Google Cloud Storage? With FlowZ, you make a small change to the job's JCL so the file points at FlowZ. The application keeps doing normal reads and writes, and FlowZ sends the data straight to the bucket, with no staging, FTP scripts or gateway server.  2. Do you need to write code to connect z/OS to cloud object storage? No. FlowZ already handles each cloud provider's authentication and APIs, so there's no code to write or maintain. Destinations and credentials are set with FlowZ's configuration utility, and credentials are stored in the mainframe's crypto hardware.  3. Can you back up mainframe volumes to the cloud? Yes. FlowZ works with IBM DFDSS, so backup output can go straight to cloud object storage, and FlowZ can tag the data so lifecycle policies move older backups to lower-cost tiers such as Amazon S3 Glacier. Hosts: Jeanne Glass, Founder and CEO, VirtualZ Computing Vince Re, Co-Founder and Chief Technology Officer, VirtualZ Computing Try FlowZ or schedule a briefing: https://virtualzcomputing.com/flowz   VirtualZ Computing builds patented mainframe data access software, including FlowZ for reading and writing cloud object storage from z/OS, PropelZ for no-code data movement, and Lozen for live, in-place access to mainframe data.
Most enterprise data sharing tools were designed in the 1980s and 1990s, before TCP/IP was common and before the public cloud existed. In this episode of Skyward Data, Jeanne Glass, founder and CEO of VirtualZ Computing, explains why those tools can't keep up with today's demands, and why customers, outsourcers, systems integrators, and software providers are turning to PropelZ as the new standard for enterprise data sharing. Every business unit wants data for analytics, reporting, cloud, and AI. Partners and service providers need data feeds to run the platforms the business just bought. Software providers are waiting on their customers' data to go live. With legacy managed file transfer, ETL, and CDC tools, every one of those feeds has to be designed, built, and maintained by hand, with hop after hop between systems. Jeanne shares how VirtualZ co-founder and CTO Vince Re explains why the older tools struggle today. Vince is the original author of CA Top Secret, drove the vision behind most of what became Broadcom's mainframe portfolio, and was elected to the kernel.org team for his Linux-on-mainframe work. In this episode: Why data sharing tools from the 1980s and '90s don't scale to today's cloud, analytics, AI, and partner requirements Design, build, maintain vs. install and run: what "built today, for today" means How PropelZ, VirtualZ's patented enterprise data sharing technology, works: multiplatform (IBM Z, IBM i, Linux, UNIX, Windows, on premises or any cloud), any input to any output, one hop, filtering at the source, and no custom code Why a Fortune 500 retailer, its systems integrator, and its outsourcer, who already owned every legacy tool, each tested PropelZ and chose it: transfers that took 12 to 14 hours finished in 2 to 4 hours Sustained throughput of around 56,000 records per second, including 60.9 million records in 18 minutes How Zafin, an AI banking platform provider, runs PropelZ on Linux to take in mainframe data from its bank customers How Lozen, FlowZ, and Zaac bring the same built-today approach to data on IBM Z Learn more and see customer and partner validation: https://virtualzcomputing.com/evidence-validation/ Schedule a briefing: https://calendly.com/jeanne-glass-virtualzcomputing
Every plan to use mainframe data in the cloud starts the same way: "first, make a copy." In this Skyward Data episode, VirtualZ Computing Founder & CEO Jeanne Glass and Co-Founder & CTO Vince Re — the original author of CA Top Secret — explain how to give cloud, distributed, and AI applications live, real-time read and write access to mainframe VSAM data without moving or copying it, using VirtualZ Lozen.  Why does every mainframe-to-cloud project reach for a copy first? Because mainframe data is complex — VSAM, EBCDIC, mainframe-specific formats — so the reflex is to extract it, transform it, and replicate it to a data lake, warehouse, or database. But every copy is a duplicate to store, secure, and govern; a pipeline to build and maintain; and a source of drift from the live system of record. Vince shares how one financial-services company spent two years trying to make a change-data-capture (CDC) model work in production before giving up. Lozen takes the copy out of the middle. The data never leaves z/OS. Applications running in AWS, Azure, Google Cloud, or any distributed environment read and write VSAM, QSAM, sequential files, PDS, and GDG data using standard file-system calls — the mainframe presented as a standard NFS network drive, with no proprietary API and no application rewrite. Because there's only one copy of the data, you get real-time integrity on reads and writes: no stale data, no cross-platform locking, no reconciling updates back to the mainframe. Existing RACF, ACF2, and Top Secret security still governs every access — even from a remote cloud app — and the work is zIIP-eligible to contain MIPS.  Jeanne and Vince also cover a problem most teams miss: because mainframe data is shared data, moving one application off the mainframe usually forces you to move ten others that share its files. Lozen ends that — modernize one app and leave its data where it is. And they draw an honest line between live access and replication: use Lozen for real-time, file-system read/write access where the mainframe stays authoritative; use PropelZ (VirtualZ's no-code replication product) for SQL/relational access, tools like Tableau or Snowflake, or heavy AI query offload. Most large mainframe sites need both.  In this episode: • Why "just make a copy" is the reflex for mainframe data — and what it really costs • How Lozen gives cloud and distributed apps live read/write access to mainframe VSAM data with no movement • Real-time data integrity for reads and writes, with no locking or reconciliation headaches • How existing RACF/ACF2/Top Secret security is preserved and how Lozen is zIIP-eligible • The shared-data problem: modernize one app without moving the ten that share its files • Live access vs. replication — when to use Lozen and when to use PropelZ  If you're a mainframe architect, data platform leader, application modernization or migration lead, or an AI and analytics owner getting IBM Z data into the cloud, this conversation is for you.  See Lozen in action — including the AWS PartnerCast featuring Lozen with Rocket Enterprise Server and AWS services — and explore more at https://virtualzcomputing.com/lozen. Skyward Data is the podcast from VirtualZ Computing — the first woman-founded, woman-led, and Native American-founded and -led mainframe software provider. VirtualZ's no-code, install-and-run portfolio (PropelZ, FlowZ, Lozen, and Zaac) connects IBM Z mainframe data to cloud, AI, and analytics without rewrites, pipelines, or forced migrations.  Learn more: https://virtualzcomputing.com
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/
How do you move a million mainframe data sets from IBM z/OS to the cloud without a multi-year project? VirtualZ Computing Executive Chairman Marc Sokol and CTO Vince Re walk through the PropelZ Multiplexer — the component that turns a list of 100,000 or 1,000,000 files into a single, self-managing job. Moving mainframe data isn't the hard part. PropelZ does that at 56,000 records per second, mainframe to cloud. The timeline balloons because someone has to account for every data set, submit every transfer, and verify every result. The Multiplexer takes that manual effort off the plate: hand it the inventory and a parallelism ceiling, and it schedules every PropelZ transfer, monitors resource utilization minute by minute, and floats the number of parallel tasks up and down to match what your system, network, and target can actually absorb. In this episode of Skyward Data, the podcast from VirtualZ Computing: Why a data movement project measured in data sets, not terabytes, quietly becomes a multi-month or multi-year effort How the Multiplexer runs 100 PropelZ transfers in parallel and adapts the count in real time to zIIP utilization, available bandwidth, and target response — opening the throttle overnight and pulling it back during business hours The customer result: 9,000 mixed disk, tape, and GDG data sets that ran from Friday night to Monday morning on a competitor's product finished in a couple of hours with the PropelZ Multiplexer Why the 5% rule of thumb — a typical PropelZ operation uses about 5% of one zIIP engine — sets the ceiling and floor for how much parallelism your environment can sustain How single-pass, direct z/OS-to-target movement on zIIP processors avoids the multi-tier gateway architectures where failures are hard to trace How per-file status flows to a simple log and the operator console for integration with OPS/MVS, NetView, and other z/OS automation Using the same technique to split one multi-terabyte table into a hundred parallel operations Where this shows up: application modernization, virtual tape library relocation, daily partner data feeds, log files from dozens of LPARs, and feeding Databricks and Snowflake for AI and analytics PropelZ is VirtualZ Computing's no-code tool for extracting and transforming IBM Z mainframe data to any target. It's part of a four-product portfolio alongside Lozen (real-time read-write access to live mainframe data without moving it), FlowZ (mainframe files to cloud object storage), and Zaac (cloud and SAN presented as native z/OS disk and tape). Topics: PropelZ Multiplexer, mainframe data migration at scale, IBM Z, z/OS, parallel data movement, virtual tape library migration, GDG, VSAM, zIIP offload, mainframe to cloud, mainframe batch window, mainframe modernization, hybrid cloud data integration, Databricks, Snowflake, AI data pipelines. Listen to more Skyward Data episodes: https://virtualzcomputing.com/podcasts/
loading
Comments