BEGIN:VCALENDAR
VERSION:2.0
METHOD:PUBLISH
CALSCALE:GREGORIAN
PRODID:-//WordPress - MECv7.36.4//EN
X-ORIGINAL-URL:https://virtualzcomputing.com/
X-WR-CALNAME:VirtualZ Computing
X-WR-CALDESC:No-code IBM Z data integration, live data access, cloud file storage, and z/OS storage modernization for AI, analytics, and enterprise applications.
X-WR-TIMEZONE:America/Chicago
BEGIN:VTIMEZONE
TZID:America/Chicago
X-LIC-LOCATION:America/Chicago
BEGIN:DAYLIGHT
TZOFFSETFROM:-0600
TZOFFSETTO:-0500
TZNAME:CDT
DTSTART:20260308T030000
RRULE:FREQ=YEARLY;BYMONTH=03;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
TZNAME:CST
DTSTART:20261101T010000
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
REFRESH-INTERVAL;VALUE=DURATION:PT1H
X-PUBLISHED-TTL:PT1H
X-MS-OLK-FORCEINSPECTOROPEN:TRUE
BEGIN:VEVENT
CLASS:PUBLIC
UID:MEC-88eea1bb782abfb771f48a71f368f3fa@virtualzcomputing.com
DTSTART;TZID=America/Chicago:20260923T000000
DTEND;TZID=America/Chicago:20260924T000000
DTSTAMP:20260925T005606Z
CREATED:20260925
LAST-MODIFIED:20260925
PRIORITY:5
SEQUENCE:15
TRANSP:OPAQUE
SUMMARY:Use Your Mainframe Data in the Cloud — Without Moving It: Live Access to Mainframe VSAM Data with Lozen
DESCRIPTION:“First, make a copy.”\nThat’s the reflex the moment anyone wants to use mainframe data in the cloud. Copy it to a lake. Copy it to a warehouse. Stand up a pipeline — ETL or change data capture — to keep the copy fresh, then spend the next year reconciling the copy against the original when they drift. Not because the data is hard to reach; the mainframe is right there. It’s because the reflex builds a second system: a duplicate to store, secure and govern, a pipeline to maintain, and a lag between what the business decides and what is actually true. The data you trust never left z/OS. Everything downstream is a shadow of it.\nThe workloads that need the data — analytics, dashboards, AI models, cloud applications — end up running on last night’s extract instead of the live system of record. And every new target that wants the data is another copy, another pipeline, another source of drift. Nobody set out to build it that way. The copy did.\nIn this recorded session, VirtualZ Computing founder and CEO Jeanne Glass and co-founder and CTO Vince Re take the copy out of the middle. With Lozen, cloud and distributed applications read and write live VSAM, QSAM and DB2 data directly on z/OS, in real time — the mainframe presented to your apps as native NFS. Nothing moves. Nothing is duplicated. The mainframe stays the single source of truth, and every workload works against the real data, right now. No pipeline to build, no code to write, no application changes, no journaling or CDC to switch on — and because it’s zIIP-eligible, you’re not paying for it in MIPS. They walk through where live, in-place access is the right call, where you’d still replicate, and how teams stand it up in hours.\nIf you’ve been told the only path to the cloud runs through a copy of your data, this is the session that shows you the other door.\nWhat is Lozen?\nLozen is VirtualZ Computing’s patented, no-code product for live, in-place mainframe data access. It installs on z/OS and presents live mainframe data — VSAM, QSAM, sequential files and DB2 — to cloud, distributed and AI applications as native NFS, so those applications read and write the real data where it lives, in real time. The mainframe remains the single source of truth: there is no extract, no replica, no pipeline and no application change. Lozen honors existing RACF, ACF2 and Top Secret security, and eligible work is dispatched on zIIP engines to contain MIPS cost.\nWhat you’ll see\n\nThe copy reflex and its real cost: why “first, make a copy” turns into a duplicate to secure, a pipeline to maintain, latency baked into every workload, and a year of reconciling numbers that should agree\nA cloud application reading and updating live mainframe VSAM data on z/OS in real time, with the data never leaving the mainframe\nHow Lozen presents mainframe data as native NFS, so cloud and distributed apps use the tools they already have — no custom parser, no code, no application changes\nRead and write, not just export: applications update the live system of record directly, and the mainframe stays authoritative\nWhere live, in-place access beats replication — real-time analytics, AI inference, operational lookups, modernization without rewrite — and where you’d still copy the data for bulk history and heavy analytics\nSecurity and cost: existing RACF/ACF2/Top Secret controls preserved, zIIP-eligible operation, and install-and-run deployment in hours, not months\n\nWho should attend\nEnterprise data platform owners, integration leads and mainframe architects; cloud and data platform leaders; AI and analytics owners; CIOs and chief data officers responsible for getting mainframe data into cloud, analytics and AI platforms on z/OS — anyone who needs current mainframe data in cloud applications but doesn’t want to build and manage another copy of it.\nHosts\nJeanne Glass, Founder and CEO, VirtualZ Computing\nVince Re, Co-Founder and Chief Technology Officer, VirtualZ Computing\nIn the customer’s words\n“Even with our complex AWS and mainframe environment, Lozen integrated smoothly — secure, real-time data access, everything worked on the first try.”\n— Gilberto Biondo, Sr. Specialized Solutions Architect, AWS\nWatch now →\n\nGiving cloud apps live access to mainframe data with Lozen\nQ. What does Lozen do?\nA. Lozen gives cloud and distributed applications live, real-time read and write access to mainframe VSAM, QSAM and DB2 data without moving or copying it. It installs on z/OS and presents the live data as native NFS, so applications use the real system of record in place — no extract, no replica, no pipeline.\nQ. How is Lozen different from copying mainframe data to the cloud?\nA. Copying builds a second system: a duplicate to store and secure, a pipeline to maintain, and a lag between the copy and the source that becomes drift. Lozen removes the copy entirely. Applications read and write the live data on z/OS, so there is one source of truth, no drift and no pipeline.\nQ. Can cloud applications write back to mainframe data with Lozen?\nA. Yes. Lozen provides real-time read and write access, not a one-way export. Cloud, distributed and AI applications can update the live mainframe data directly, and the mainframe remains the authoritative source of record.\nQ. Does Lozen require code changes, a pipeline or CDC?\nA. No. Lozen requires no application changes, no pipeline to build, and no change data capture, journaling or logging to switch on. It is install-and-run: applications mount the mainframe data as native NFS and use it in place.\nQ. Does Lozen move the data off the mainframe?\nA. No. The data stays on z/OS as the single source of truth. Lozen presents it live to cloud and distributed applications; nothing is extracted, replicated or staged, which means fewer copies to secure and a smaller compliance scope.\nQ. Is mainframe security preserved when apps access data through Lozen?\nA. Yes. Lozen honors existing mainframe security — RACF, ACF2 or Top Secret — so the data is protected exactly as it always was. Access is governed by the controls already in place on z/OS.\nQ. Does Lozen raise the mainframe MIPS bill?\nA. No. Eligible Lozen work is dispatched on zIIP engines, so live access does not drive up metered software costs. Where there is no zIIP in the configuration, VirtualZ provides tuning guidance.\nQ. When should you use live access instead of replicating mainframe data?\nA. Live, in-place access with Lozen fits workloads that need current data — real-time analytics and BI, AI and ML inference, operational lookups, and hybrid or distributed applications. Replication still fits bulk history and heavy analytics, and many enterprises use both. The point is to stop copying data that only needs to be read live.\nQ. How does Lozen help application migration or modernization?\nA. When an application is re-platformed or moved to the cloud, Lozen lets it keep reading and writing its live mainframe data in place — no data-layer rewrite, no freeze during cutover, and no forklift migration of the data alongside the app. The data stays on z/OS while the application modernizes around it.\nQ. How long does it take to install Lozen?\nA. Hours, not months. Lozen is install-and-run on z/OS. As with any deployment, the surrounding work — network access, certificates and connectivity — takes the usual time, but this is not a six-month proof of concept: install, configure and test, then give your cloud apps live mainframe data the same day.\n
URL:https://virtualzcomputing.com/events/live-mainframe-data-cloud-lozen-webinar/
CATEGORIES:Featured Col 1
LOCATION:Virtual
ATTACH;FMTTYPE=image/webp:https://virtualzcomputing.com/wp-content/uploads/2026/09/Webinar-Live-Mainframe-Data-Cloud-Lozen_872p-web.webp
END:VEVENT
END:VCALENDAR