Virtual Storage Access Method

It's not like you absorb all the things that we're talking about here and you're done.

Data has a life cycle.

You need new fields in that data.

You need to do new things with it.

All of a sudden, you've got a whole nother ball of wax there because I'm not suggesting that other platforms aren't trustworthy.

What I'm suggesting is that now instead of all your controls and kind of proof points being in one place where you can put your fingers on them, now you have to think about a handful of things and you have to think about where else did that data go and what other formats.

And it was a, pretty simple VSAM file on the mainframe and then it turned into Snowflake and Databricks and Postgres and all these other forms that are the same data that maybe aren't being governed the same way.

So that's a more secondary problem in a lot of sites.

And I think, part of it is because these things can just be so different.

If you're coming from a VSAM file at the customer site and you need to get that to some type of database structure, I mean, that can be, we used to use the word impedance mismatch.

There's just no easy way to connect these things together.

And I think that's where the problem is.

Yeah, I think, well, first of all, it starts with the fact that we can access just about any type of data.

So, you know, whatever the customer's got, we'll probably be able to work with it unchanged.

You know, so if it's sitting, if his data is sitting in a VSAM file or on a tape or whatever it is, we can work with that.

So it's not like we're going to impose some new, get your data in this format and we can work with it.