Name: Monitoring, Evolved
Uploaded: 2026-09-23T16:01:24.252Z
Duration: 2 h 13 min 20 s
Description: Monitoring, Evolved

Transcript for "Monitoring, Evolved": Good morning, everybody, and thank you for joining. We're gonna give everybody a couple minute one more minute just to log in. We're happy to have you today. So give us one more minute, and we'll just make sure everybody clicks in and lets everybody get settled in their seats, and we will get started. For everybody worldwide, it's great to have you on. We have our engineering team and our ZCOE team live on the Q and A chat. If you wanna say hi to everybody, you're more than welcome to say hi to any of our speakers or anybody you wish, and we will get started in just one second. Alright. I think we are ready to go. We are gonna keep it at slide number one. Alright. Good morning, everyone, and welcome. It is great to have you with us today. This is the OmegaMon Virtual Technical Summit, and the theme we've built today is right there on the screen, Monitoring Evolved, from Operational Visibility to Actionable Insight. The subtitle is the whole story of the day. Most of you already have visibility. We have dashboards, we have alerts, we have data, and oftentimes more data than anyone has time to read. What we're focused on today is the step after that, turning what you see into something you can act on quickly, confidently without disrupting the environments your business depends on. A quick word of thanks before we start. Today is IBM and Rocket Software together, a partnership that has been supporting the mainframe operation teams for a long time, and one that's grounded in the simple idea, modernization without disruption. So settle in, keep the chat window open. We want your questions as we go, and let's get started with the next slide, please. Let me take any moment to introduce myself properly. I am Saghi Amirsoleymani, general manager of the z Center of Excellence at Rocket Software, and an IBM champion. What the role really means day to day is that I spend my time with mainframe teams, teams like yours, teams running workloads that absolutely cannot go down on platforms they've been running beautifully for decades, with fewer specialists on staff every year and more demands every day. That's the reality of what I hear from every customer conversation. It's the reality that shaped our agenda that you'll see today. I'll say it upfront. I'm an optimist about this platform, and I love z. The z systems in your data centers are the most critical work today than they ever have been. The opportunity is is in front of us. It isn't replacing any of that. It's making it easier to operate, easier to understand, and easier for the next generation of your teams to pick up, and that's what it's about today. Next slide, please. I'm far from alone today. This is the group you'll be hearing from. Two things worth pointing out. This is a genuine IBM Rocket collaboration. Andy Bradfield and Ash K Mahay are here from IBM, so we're getting the product direction straight from the source. And the zCOE names you'll see are our solution advisors, the people who sit with customers through real migrations and real incidents. What they share today comes from the work with our customers. I'm especially pleased to have Richard Savish with us today from CSIS, an expert and a friend of his ECOE, running this in reproduction. 10 voices, one thread, helping you get more from what you have today. Next slide, please. Before, we hear from any of them, though, I wanna mark something very special to me, and very special to many of many of us. OmegaMon turns 50, half a a century of performance monitoring on a platform that runs the world's most critical workloads. Think about what that means. The software watching your transactions this morning has been doing that job for every generation of this platform, and it's still what your teams reach when something goes wrong at two in the morning. Not much in the industry gets 50. OmegaMon is still here because it's still earning its place, release after release, in environments where getting it wrong is not an option. So happy birthday, OmegaMon, and I want to thank all of you, our customers, and our engineering team who has been part of this story. Some of you have been with us for a very long time. But fiftieth isn't looking backwards. It's about looking at the next half of your life that I really care about today, a brand new way to see it. That's what the rest of this session is about. So next slide, please. And there's no one better to open this conversation than our first speaker and friend, Andy Bradfield. He's the vice president for IBM Z Hybrid Cloud at IBM. He is responsible for where the platform goes next, how do you get into the z hybrid cloud estates most of you already are running, and what IBM is investing in to make it work well rather than just work. I've asked Andy to set the stage, the direction of traveling as we're traveling on z, what he's hearing from clients, and why observability in AIOps has moved from nice to have to the central place of the platform. Fifty years in, and the most interesting part of the platform story is still ahead of it. Andy, over to you. Great. And thank you so much, Saghi, for, giving me the opportunity to to join you and the and the team here. I'm I'm thrilled to be here. As as Saghi mentioned, I'm the vice president for IBM z hybrid cloud, which consists of, managing development and product management for our AI ops, DevOps, and middleware portfolio at IBM. One of the things that I wanna really double down on is the partnership that Saghi mentioned. The partnership between IBM and Rocket Software has never been stronger in my opinion. I I'm really looking forward to hearing from some of the industry, preeminent experts in the space of enterprise observability. So, really, I encourage you to to lean in, hear what they have to say, ask questions, about, things that are on your mind. So let me just dive into some of the content. So mainframe, observability and and resiliency is what we're looking at in incredible detail, within our AI apps portfolio. The the trends emerging from the industry are are very clear. We're we're moving, to a space where we're converging on a single, operational model, around, reactive you know, moving away from reactive monitoring to predictive and, autonomous operations. As Saghi pointed out, the the issue isn't that, we don't have enough data. We have plenty of data. It's what can you do with that data? How can you, leverage the data to get to, those hidden signals and not become overwhelmed with the the data that you have in your environment? So as we as we look at these trends, I'll I'll just go, around the form here. The first one is, Otel. Otel, enables IBM z to become, you know, a first class citizen in the the hybrid observability space. I think that word hybrid is incredibly important because it's no longer that distributed and, mainframe are are separate entities. You have, hybrid applications that really cross that boundary, and it's no longer a a black box of mainframe data. You have to be able to have observability across that entire estate. And the OmegaMine is is one of the first to really embark upon this journey of of hotel. As you move on to, number two, we're shifting away from threshold monitoring. So the way I think about that is simply, relatively static, thresholds that, once reached, you you might do an action, And moving into a a space where we're adjusting based on AI and ML, driven observability to account for, things like seasonality. So we're we're shifting away from simple, what I think of as brute force, you know, monitoring, and and threshold reactions to things where we're we're having a much more behavior based observability and a consolidation, of tools. Number three is moving into, assistive, and, you know, moving from AI ops that is, assistive to predictive and driving, root cause analysis. So, again, think of the volume of data, and can we get into a situation where you, use that data and are able to to see around corners, be able to, predict things, before the proverbial, snowball turns into an avalanche? And number four is is human led, operations, moving to autonomous, intelligence systems that are self healing. Don't worry. The AI, despite what you are hearing, in the news sometimes, is not taking over, the job of of humans. Think of it as, it's it's still human in a loop. It's humans, being able to be more productive with the combination of, AI and and machine learning. So let's go a little bit, deeper here. So as we look at the AI capabilities, it's really transforming the industry and the user experience. And as as Saghi pointed out, we have, sometimes fewer experts that are being relied on for even more, of of the the system that we all rely on to to run our business. So the way we can think about this domain is, first, we have AI that predicts. And this is, this is machine learning, so it's recognizing, patterns in the data. So a classic example of this is, Netflix suggestions or something that you might see on a a shopping site like Amazon Prime, where, say, you know, other users, like, you bought this based on, these patterns in in the data. So this is not, you know, generating new data, or initiating actions. It's simply reacting to, learned patterns. So that was, incredibly valuable. That's but that's not the whole story. As we move on, to generative AI, this is really a a transformational, part of the journey where, you know, we're entering a space where brand new data is created. It's, created from learn patterns, so it's being built, together in some cases with, machine learning. It's it's not copied from previous examples, but it's it's transformed entire industries like, customer service. AI chats is is the next phase of this where we have assistance. So it's building upon prediction and creation, and moving, to that next step, which is interaction. This is a launch of days where, AI assistants have, you know, have the ability to understand natural language, provide curated responses. IBM Watson Assistant for z is a good example of a a curated response, along with, suggestions of, what might, the next next best action be. And now we're in a a world where, we have AI that works. So it's really bringing all of those things together. It's the culmination of this journey, where AI doesn't just predict or create or chat. It's AI that is able to bring all those things together and and take action, have initiative, still depending on, if the user requirements, have human in a loop, but it's able to actually do some work for you. So before we go into a little bit more depth in, in this space, I want to point out kind of the the higher level landscape here of how, the integration of a critical, resource of data like IBM OmegaMon, is to the the IBM strategy. So when we look at, OmegaMon, it's it's not just a a a foundational part of the strategy, but it's what delivers on that NorthStar vision of enterprise observability and how we can achieve that. You can see that not only does it have stand alone value, but it also feeds critical APM solutions like Instana. It feeds Concert, for z as well as, integrations to our AgenTek platform like Watson's system for z. So let me get into some specific examples now with the, the AI that that predicts. So machine learning, as as I mentioned, is an example where we have, you know, OmegaMind AI insights. So this discovers anomaly in the data anomalies in the data in d b two as an example. So, this is a a a great example in my view of of a product that can pay for itself over time because it's it's giving you that, insight and helping clients be able to, solve problems more quickly. Again, going back to the point that Saghi made about, the the the resources that are being asked to do so much, the better that you can predict, things in advance, the the more you're gonna be able to do, with with less. When we move on to generative AI, this is a a a great example where a counselor for z, has has been able to combine expert advice, supported by generative AI and IBM expertise and put both of those two things together to give, critical insights, into issues. And what is maybe the next best action that you ought to take, with not only, actionable, remediation advice, but also help you, with resolving issues faster. It it it also is a great on ramp for people to be able to, to acquire skills and and knowledge transfer faster. As we move to, AI that chats, so this is, an example, where Watson assistant for z, with, embedded into our IntelliMagic agent, is something that allows us to to help our performance, and capacity experts, easily cut through the number of, reports that are available in, IntelliMagic. And by by using natural language, able to describe exactly the report they're looking for and pull that report up, immediately. So, again, being able to to resolve issues and get to the data, that you need in in very, very quick order. And then finally, AI that works. So AI agents, again, Concert for Zia as an example, can, interact with operations agents. It can provide more information to identify root cause, remediate the incident, including taking action. So as an example, it can kick off, an Ansible work, workbook. It can open up a ServiceNow ticket, even, provide, you know, interaction from, data that's coming from, assistant for z, and use the underlying metrics from Omega Ma. So, hopefully, you can see all of these solutions are working together, excuse the pun, in concert to to be able to provide a a a much more, easily, maintainable system and, again, try to achieve that North Star of enterprise observability. So as Saghi pointed out, Omega Man, turns 50 years old in in October. It's something that is, remarkable. I think it's something we we all ought to celebrate. The the mainframe is is only getting better, and and it's through through the work that, that all of you are are helping lead. There's lots of examples from Grafana to OmegaMon AI, and and soon, continuing to to build upon this, agentic, journey, and and, again, combine a lot of those, examples of machine learning, and and chat and and, generated AI, building on those and delivering, capabilities for the platform. So in in closing, I I wanna just call out, an an IBM Red Paper that, my team has has put together. I really encourage you to to take a moment and read through this. It is it is our view of how you can achieve enterprise observability, simplify the mainframe operations. It's it's the experts that you all are familiar with and and talk to, on regular basis. So it's it's worth a read in in my view. But, again, lean in here. These are the experts. This is, an enduring platform, and and and one that, I'm incredibly proud to to work on with all of you. Saghi, back to you, and and thank you so much for the opportunity to to join the team here today. Andy, we really appreciate you, and thank you for your friendship and your partnership as always. So welcome back, everybody. It's me again for a quick minute of housekeeping before we go further. If you have any questions for Andy, he still is available in the chat as well if you want to ask him any questions, because I wanna make sure you get the most out of your day. And first, for the good news for anyone that's multitasking, and I know we often get interrupted. We are recording this session. We are collecting the q and a. We will have a newsletter that comes out, and there will also be links afterwards. So don't worry. We'll make sure that you don't miss a step. Second, this is, what I'd really like you to act on. On the right hand side of your screen, you'll see a q and a tab just, next to the chat. Please use it. Ask your question at any time it occurs to you. If it pops in your head, don't worry about the right moment. Just ask it. We will our team is monitoring the panel throughout, and we love your questions as they come in. So and we reserve some time at the end for live q and a if you need it. So honestly, the questions are the best part of the event for me. The sessions, we get the most out of those, and then we figure out what's happening in your environment, and we figure out how we can shape the next technical summit. So please make sure you ask as many questions as you can. Next one is and last. At the very end is a short post event survey that will pop up. I know Nobody loves a survey, and you only fill out a survey if it's bad news, but we really want you to fill it out with positive and negative or anything you want. This would generally shape what we do next, the topics, the depths of the speakers. If you like something, if you don't like something. So please, we'd love to hear from you. As you'll see from Guy, we are very customer centric, so that's why this is really important to us. So that's it. Let's get back to the good stuff. Next slide, please. Here's how the next stretch is gonna run. Seven items on the slide, but really, like, five blocks as they build into each other. We open here setting the context of where where OmegaMon is heading, then the web UI as you saw. Katie and I will walk you through, what why we've built it, what we did, and a live demo of the product. Then we go into product updates with Ash and the OmegaMon family release. Aleksandr and Christoph will take you through JVM, Kicks, and d v two integrations. Todd follows that with the practical side of things, with the best practices of moving to TEP and WebUI, drawn from our customers that are already ready to move. And then after that, my most special part, which is our customer success story with Richard. And it shows what we actually looks like in production. I believe customers speak better than we do. And then finally, with my most favorite person, Guy, close us out for the day, as the VP of engineering, to let us know exactly where we're headed and everything. So as I mentioned, questions are welcome throughout. Put them in the q and a panel, and we'll pull the common ones into our live blocks. And let's start with where most of you have questions today, the web UI. Next slide, please. So this is the part I've been looking forward to. Katie Wilde is joining me soon. In a second, you'll see her face. Katie is our senior solutions advisor in the ZCOE. She'll be driving the product live in a few minutes, which is the real reason why you want her in this segment rather than me. Here's the shape of the next stretch. About ten minutes of slides, then we'll go live. I want you to see the web UI running against real data. So I'll keep the setup deliberately short, and let the product do the talking. Ask the questions as you go. Our team and Sukh, who is our key developer, is in the chat and live ready for you if you have any questions as I'm speaking. So please feel free to ask as many questions as you want. Slide 17, please. Next slide. Alright. I wanna slow down here because this is the moment the rest of the web UI conversation is built around. Critical services start to slow down. Customers feel it. The business feels it. Everyone knows something is wrong. But the first question is still the hardest one. Where do I start? Because most of the most of the time, the problem is not that you have no data, as we've mentioned. The data is there. OmegaOne is collecting it across KIX, zOS, DB2, IMS, MQ, network storage, and Java. The challenge is that the context is scattered across tools, across systems, across domains, and in the middle of the incident, scattered across time zones, and scattered is the cost context. And what I wanna make real with a customer story that that because it stopped me when I heard about it. So a customer shared with me in a big retail company that when every system down event that they had in D V 2 at the center of the outage, when they looked back at the outage, they estimated the impact of D V 2 being down was roughly $6,000,000 a minute. $6,000,000 a minute. That is about $1,000,000 every ten seconds. Ten seconds can disappear right before the right person joins a bridge. Ten seconds can disappear while you're logging into another tool. Ten seconds can disappear while teams compare screenshots and try to decide what they're are they looking at the same problem? So when we talk about the web UI, I do not want you to think of a nicer screen. In environments like this, the interface is part of the incident response path. If a team can get the answer ten seconds faster, that can represent meaningful business impact, and that's what I want you to think about. That is the difference between monitoring as a place you go looking for answers and observability. As a shared language, the whole incident team can use it in a moment's instance. That is the frame of this slide. The chain along the bottom is not the product diagram. It's the path from confusion into control. A service is affected, the enterprise sees it, the specialist follows it follows it straight into the domain without changing tools or using or losing a thread. History explains it, and teams resolve it faster. That is the difference we are trying to create. No more alerts, no more dashboards for the sake of having a dashboard, but the same trusted data connected into one shared path to resolution. So the bridge call starts with a common picture, not a debate over whose screen is right. So that is the problem. Now let's let's show you how the web UI helps compress the path into three short stops, then we'll go live. Next slide, please. Three short stops of this product. Where does the web UI fit? That's how the new interface sits along what your teams run today. And I answer the question upfront because it's the one I get most asked frequently. Nothing you rely on today will be switched off or replaced. You adopt everything at your own pace, and the IBM team is here every step of your journey whenever you are ready. What you stand up. What it takes to get it running. The monitoring servers are already already have what you already have. Which pieces you put on are generally optional. That question that you decide whether it's this quarter thing or something later on. And three outcomes that matter. What changes for your operation once the team share one view of a state? Three improvements your operations and application performance groups are feel directly. Then we'll go straight into the demo. Next slide, please. Where the web UI fits. Let me answer the question nobody else has typed. No. This does not replace your thirty two seventy interface. If you like to stay in that interface, it will not be migrated. The enhanced thirty two seventy UI keeps working as it does today and remains strategically interfaced alongside the web UI. That's not a grace period. It's a direction. If you've got people who genuinely master in thirty two seventy, as most of you do, they keep working the way they work. You can even paste an e thirty two seventy query right into the web UI if you feel more comfortable. It's the same browser, but trust me, when you start using the web UI, you won't go back. It's just faster and easier and customizable for you to use. The Tivoli enterprise portal continues to run too. Nothing switched off. I'll be straight with you. Future investment will go into the web UI. So TEP keeps on doing its job, but all new capabilities will go into your web UI. Second, and this is the one I hold on to, adopt at your own pace. Start with one team, one domain, one dashboard, and then widen it out from there. No cut over window. No migration project to fund. If it isn't useful, you stop. But if you find it's not useful, please contact our teams, and we will talk to you about it and make sure that it becomes useful to you and that we hear your pain points about using using it. But trust me, you will not go back. Third, nothing has changed underneath. Same agents, same monitoring servers, same data. It changes how you reach the data, not how it's gathered. Nothing to re instrument. So what does it take to stand up this? Next slide, please. Here's the answer to, what does it cost me to try? And the simple and it's smaller than most people expect. Two components to get started, two more only if you want long term history. So the OmegaMon gateway is the front door. It handles authentication. Brooke has access to monitoring servers sitting behind it. The admin UI is where you configure it. Server connections, the situation editor, queries, history collection, browser based. So your team isn't learning a new configuration discipline to get started. That's it. Those two against the monitoring servers you already have and already running. Now the optional pieces, because that's where the history story lives, the, the ODP streams historical data as we've talked to many times. ClickHouse is the time series store behind it. It serves both as near term history and long term history at speed, which means you did you get deep historical views without burning redundant zOS MIPS to produce them. For anyone in this session who defends the monitoring bill, this distinction matters. So two to start, two to go deeper. Pretty simple. Which brings us to what to what actually changes once it's running. Next slide, please. And here's what you get for that. Three outcomes, all on top of the data you already have. No new instrument required. First, you resolve incidents faster. Teams get to the platform without switching tools. Less downtime, better SLAs. Like I said, ten seconds saves a million dollars. Second, you run operations more efficiently. Less time hunting for information, more time fixing problems. And notice this, the same dashboard serve your daily checks and your live incidents. You're not building one set of views for good days and another set for bad days. The thing is your teams already have open what they need and what matters. Third, and this is what I hear most from leaders, you depend less on scarce skills. The browser based view open up estate teams who do not have Deepgram expertise. They let them be precise on what matters. They focus on what they wanna see. They put things in colors where they can focus on incidents. It means routine questions stop landing on them, so they're free to work on what they really can do. And for those of you bringing on to the platform, the ramp up is a lot shorter. Right? I learned how using this web UI with Syshelp in probably about thirty minutes. It's pretty simple. Faster resolution, more efficient operations, less dependence on a handful of people, and on the data you're already collecting. Now next slide, please. If you've looked at the web UI before and set it aside, this is a slide worth your attention. Four additions into two. Right? Scalable historical analytics, like I said, the Cliff House integration, time series dashboards, starter dashboards across the monitor domain. So you're not starting with a blank canvas. Right? Sometimes you just need someone to help you get started. So you could spot the peaks, the lows, the trends, the anomalies, compare the compare today against yesterday, last week, whatever range you pick. History collection configuration in a browser, configure your collection directly from the web UI. System inter attributes, intervals, filters, manage a collection that you can look at. Don't over collect. You wanna focus your attention so you can get right to the source. Remember that ten seconds matters. And secure Grafana Cloud connection. Four addition, all optional, all on the data you already have. Now that's enough time for me. As you see, the phenomenal Katie Wilde is also on the screen. So let's see it running. Katie, over to you. Thank you, Saghi. I am Katie Wilde. I'm from Rocket Software's Centre of Excellence team. In today's demo, I'll begin with a quick introduction to the web UI for anybody that hasn't seen this before. I'll then move into the latest version 2.2 features and show how they work together in a realistic customer scenario. We'll start with a single alert and follow the journey from detection to diagnosis to recovery and prevention. So more importantly, I'll show how the American WebUI helps teams spend less time searching for answers and more time resolving issues that affect the business. So let's start off with the enterprise overview that you can see here. This is the central starting point for your enrollment monitoring activities. Imagine it's a Friday afternoon and you're about to leave for the weekend. You don't have time to work through multiple tools looking for a problem. You need the system to show you what is important, what is healthy, and where to focus your attention. That is exactly the role of the enterprise overview. It brings critical performance information together across systems and sysplexes, giving operation teams one view of the health of the wider mainframe environment. You can also explore the individual and management agent dashboard by selecting the relevant tabs in the horizontal navigation here. The starter dashboard highlights key performance metrics such as key transaction performance, DB2 threads, storage data, JVM data, active situation, and alerts that have crossed predefined thresholds. The blue values you see here are actionable links. Rather than searching through multiple tools, I can jump directly from a high level alert to the support and performance data. For example, I can select this here the system CPU overview and this will open the related dashboard in a new tab. It's important to note here that this still retained the content of my investigation because it has opened in a new tab and we can go back to the previous tab and see where we left off. You can alternate the view so the information that is most important to you is exactly where you want it. In the same way, you can add, remove, or move the panels around to focus on the systems and workloads that are most relevant to your role. The WebUI also brings administration into the same experience. So from this dashboard here, I can open up the situation editor. We can select an existing situation and then new divided workflow here to manage the alerts and make changes. The benefit here is fewer clicks of all the latest performance data in one place and a barter path from an enterprise level signal to the evidence needed to diagnose the problem. So now let's bring in a customer scenario. Imagine customers are trying to make payments through their mobile banking application, transactions are beginning to queue, response times are increasing and the operation team needs to understand what is happening before customer frustration will come to wider service impacting to them. For many organizations this slow transaction is more than just a technical issue, it affects customers revenue and business operations every minute and set an account when critical services are affected. So we can see here on the enterprise overview dashboard that there is an alert showing that a pip transaction elapsed time had exceeded the defined threshold. Let's follow the evidence to understand what is contributing to the delay. You can also see here that the origin node identified the affected pit regions so I immediately know where the issue is occurring. Now let's click on the alert, open the affected region and move into the pit task summary. From there I can select the offending transaction and open its details. To this keep the alert at the centre of the story, I received an alert, identified the affected transaction and now I have evidence telling me where to Investigate next. The transaction details give me direct links into the related step systems. We can see that one of the resource types is 02 and the other is MQ. If we select the MQ transaction to investigate further we can scroll down and this we can review the associated details. We can see the elapsed time, the current state which is a suspended state, where it spends most of its time in the suspended time over here and we can see the statistics information for your live running transaction. If we scroll back up here we can see further MQ information, so for the MQ transaction we have two queues opened. When we click on the queue and go into the queue status details, this takes us into a minimum for MQ where an MQ programmer will be able to investigate this further with the information available such as the input opened or identify if it's related to a kit transaction that is looping. I can then return to the previous dashboard and select the DBT transaction to see the associated DBT thread information. This moves into activity thread details and we can see that the elapsed time metrics showing that it is doing something within DB2. This demonstrates a cross product journey. We've gone from PIC to MQ and PIC to DB2 all in one place. It follows me across products so I don't need to search subsystem again or rebuild the investigation. We can also currently see the active SQL statement which could help us to identify where the loop might have happened in the d b two system and also help the DBAs find the root cause. So we've investigated why one transaction was looping in m q and one in d b two all within the web UI. Now let us take preventive action so the customer can use the mobile banking again. So if we have a look at the MQ transaction which seemed to be taking up a lot of your time, I have the option to select the take action button and see the operational responses available. These include purge task, force purge task and activate trace. So the deal between MQ investigation helped me understand why the transaction was delayed and provided additional contact for the specialist teams. In this example a customer payment request have become sat in a loop and so by purging the offending transaction we can immediately remove a customer impact whilst preserving the evidence needed for later investigation. After the prepared action I refresh the view and confirm that the transaction has now cleared. You'll also see other workloads that are coming in and out which is normal but the looping one that we identified earlier is cleared. I'll also return back to the identified overview and confirm that the alert condition is no longer present allowing the customer workflows to continue. So the goal here is not simply to just monitor a problem, it is to identify it, understand it, resolve it and then return the business to normal operation as quickly as possible. The WebUI 2.2 now allows administrators to manage history collections directly from the browser. History collection captures selected and minimum monitoring data for historical analysis reporting and competitive planning. Previously this was managed through the IBM TEP or the enhanced 3,270 UI but it's now be directly done in the web UI. From this panel I can view, create, edit, start, stop or delete history collections for different monitoring agents. If I open edit you'll see the same familiar settings available in the other UIs including collection intervals, distribution options and filters. The same configuration is used when creating a new collection making it easy for assistant and management users to adopt web UI for day to day administration. Now let's move on to another enhancement in the web UI 2.2 and take a look at the time series dashboards. These dashboards use historical and made among data stored in the Rocket Software database through a made among data provider. This enables fast access to historical metrics and trends helping users analyze performance over time, investigate issues and better understand long term system behaviour. So the alert that was investigated before shows me what was happening now. The time series helps me understand what happened before. So for this incident, time series can help me answer three operational questions. Was it an isolated event? Had it happened before? And is it becoming more frequent? So let's select the time series where we'll find the event in the historical timeline, inspect the task detail summary and the spike more closely. This date range can be widened to understand a wider trend too. So in this example the historical trend suggests that this was an isolated event rather than part of a reoccurring pattern. That historical context turns earlier alert into a wider performance story and help determine whether preventive action is needed. The real strength of the time series dashboard is that they're not limited to a single technology or use case. So let's now take a look at some additional examples and see how a historical analysis can help uncover trend and further issues across the IBM's enterprise. Let's move on to the d b two top level time series dashboard. So here you can see useful d b two historical data and analysis such as the top 10 drive utilization. And then let's move on to the ZOS top level time series dashboard. We can see here that there was a show CPU spike, so let's go and have a look at the TS system CPU overview to investigate it in more detail. So this shows that there is a seamless drill down from the high level insight into detailed analysis. So if we have a look at another example here, we can compare the historical data with those from the previous five days. So on here, you can see it is comparing the data of the pitch region CPU utilization. The top chart is from today and then from the previous day, and then the last one is from the previous five days. So we can put all this data together so we can do some further analysis and spot any trends. Time series shows that we're no longer just monitoring a point in time, we're building a performance story that helps explain what changed, when it changed and where we focus next. So we started with a customer facing payment issue. In MNIT the American WebUI took us from enterprise wide detection through guided diagnosis and recovery. Then we used the historical evidence to determine whether the event was isolated or reoccurring all with less time spent searching and more time spent solving. That is the value of the American WebUI version 2.2. One alert, one investigation, one connected experience from detection to diagnosis to recovery to prevention. It was when the business critical services are affected every settlement's camps. If you would like any further support or a demonstration with the a matter of one web UI, please feel free to reach out to the z concierge team at zconcierge@rocketsoftware.com, and we'll be more than happy to help. I'll now hand it over to Ash K Mahay, who is a senior project manager from IBM who will be covering the Amadimon family updates. Thank you. Thank you there, Katie. Hello. This is Ash K Mahay as mentioned. I'm the IBM one of the IBM product managers at IBM, and I'll take you through some of the family updates. I won't cover many of them because there's some, demos or more details later on, with Alex and Christoph. So I'll just give you a quick high level overview. If you know me and you've seen me present before on-site or face to face, in conferences, I can tell I can talk for hours. But I've been only allowed fifteen minutes this time, so we'll go straight at it. So in the agenda, I'll give a brief introduction, but I wanna introduce some core update, for the, AmigaMon base and then some fixed packs that were recently released for AmigaMon for d b two. And if IMS so IMS is mentioned in the past, in one of the questions, so we'll talk about some of the IMS updates. AmigaMon AI for zOS, Kicks. I will mention briefly about messaging, but JBM is coming later. Alex will cover that. So some solution updates and life cycle, changes that I think you need to be aware of and how you can engage, the, CO team later on. So let's go to the next slide. So let's have a look at some quick, some AmigaMon fun facts. Are you aware as as, Saghi mentioned earlier, fiftieth year for AmigaMon. We are celebrating that, and I'm very proud to be one of the product managers for AmigaMon. But did you know that AmigaMon is actually older than the World Wide Web? In fact, it's older than the IBM PC, which came out in '81, sold it on Windows, is older than Linux. So I'd be you can see Amiga one's been around for a long time. And we it's it's not, just been in maintenance mode. We've delivered absolutely great update updates to the base. And soon as the zed 17 came out, the zed o s three base three dot one came out, we provided some great new updates and exploitation. I won't cover them all here because I'll be spending two, three hours otherwise, and we'll go on. So Amiga one, how does that name come about? So, we're not really a 100% sure, but Amiga is the last letter of the Greek alphabet and, signifies, it's the it's the last, and most, end of the, of the, requirements that you would have. And monitor, well, it's abbreviation for, or the mon piece is abbreviation of monitor. So add them together, you got me, gamon. I understand it was, when you first discussed at Share in a conference, many years ago and, started development in 1975 and released in October '76. So we're very close to that fifty year milestone. Initially, it was sold and promoted by Kendall Corporation, which is then acquired by IBM in 2004, and it's been part of the core IBM Zed AI ops portfolio ever since. And I've been working with the Amiga one for on and off for probably twenty plus years. So I've seen how this, product has evolved over time. And you've just seen the web UI, and, that's, that was released just over a year or so ago. And, we just released version two dot two in the last month, so please do have a look at what's involved in there. Okay. I wanted to cover the MIGO one configuration manager. You may have heard about this, and we do cover this in many of our MIGO one sessions. We've learned that some customers still prefer Palm Gen or working with Palm Gen. We do really encourage you to move to configuration manager simply because it's very simple to install. The AmigaMon when you use a configuration manager, we also provide you a migration option so you can migrate your Palm Gen configuration into configuration manager so you do not have to start from scratch. So, really, there's nothing really stopping you, I would say. So when you look at your next release updates, for Mega Man, if you're moving from five six to six one, we encourage you to encourage you to use the configuration manager as your option or your configuration tool to, move to the late later versions. What have we delivered recently, with the configuration manager? So this APAR lists, an an update. So we now also identify and highlight the deprecated parameters. So when you're moving, between releases, we will look we will review your configuration and highlight those parameters that you may have used in the past that are now deprecated. And then from there, you should you we will give you the best practices, which ones you should use or move to. So this will be defined or created when you run the generate job, and it could be if you're using the options of null USS. So if you've not heard of generate with options, it's worthwhile having a look at that on the documentation. There are some great updates with the options. So if, for example, you apply maintenance to AmigaMon and, you don't need to reload the, SMP datasets, you can just run the option with quick config and it will update just the configuration files rather than having to reload all of the SME datasets. So it's a very fast way of just making some mild minor changes to your configuration. If you don't have any, deprecated parameters as it says here, we will not provide you that, output in the, in the in the report. Okay? Some thirty seventy UI updates. Again, these are driven by client requests, similar to other most of the features and the functions you'll see later on. This APAR enables enables you to, stipulate which users can actually edit or read situations or read members in your third center UI or look at objects or edit objects in your third center UI before it's you have no access or all access. What we're doing now is giving you the option to enable some of your users, maybe if your Kix SME needs to just edit your Kix, stuff, you can, you can then sorry. I just thought I lost a minute. So you can, therefore, limit who can see that. Well, I've provided links in the slides so you can, review those later on. Single single Sysplex mode. This is, has been highly required requested from our, MSPs, those clients who are servicing other clients. So single sys Sysplex mode enables you to, share the single hub and, create and use multiple sorry. There's then you can use multiple, ether center UIs to connect to the same hub, interface. So you may want to provide us in a ether center UI for one client and a separate one for another client. So this this update, will help you with, servicing multiple clients. So, it's just been released. So, please do look at that. As Katie mentioned earlier, we do now provide in the e the WebUI the option to edit history collection. Before with the WebUI two dot one, you could edit situations. But now you with, WebUI two dot two, you have the option to edit, the history collection. I know you can see the APARS on where I can always show you the APAR numbers that you need in order to, enable that feature. Okay. For DB two, like I said, Alex and Christophe will cover these in later late later search slides. But one thing that I wanted to highlight is one of the things that I've actually been asking for in the past is, tablespace monitoring. So which are context into that into the tablespaces for DB two? And as you can see on the screenshot, and I'm glad, clients like this, you can see the, tablespace, the, tablespace IDs, and so on. And bear in mind, tablespaces really rely on these some datasets underneath the covers. So ensure that you have also the AmigaMon AI for storage agents installed so you can monitor the extents of your, tablespace, these are usage. So if you don't have the space on disk or the volume and, you want to grow your tablespace, of course, you will not have that space available to you because the V sum obviously may be running out of space. And you'll learn more about the end to end transaction flow analysis, from between KIX and DB2. This is great new update. It's I guess it's a further step forward in our correlation between the Amiga ones, and, Aleksandr and Christoph will cover these in more detail later on. Amiga one IMS. So we don't mention much about the AmigaMon IMS, on our on our sessions in the previous sessions, but I'd like to mention here at least that it's we're not ignoring it. This is one of our powerful agents on, in our portfolio. We've made some significant updates in the last twelve months. We get around, relating to performance, user experience, but also resiliency. This is driven by customer requirements and, engaging with clients. So if you are interested in helping us further enhance this product and have some feedback, please do share that with us. Reach out to us, and I would love to hear that from you. We you as I've shown earlier on, you're with the web UI. We do also have AmigaOne IMS dashboards out of the box that we share when, when you install the web UI. And, so IMS agents, and you can see details around the IMS transactions and so on and resources. With the APAR listed here, there's correlation between IMS API calls and JVM. So JVM is zedos, connect. If you have APIs that you, have initialized or you, utilize from, the IMS region. So those are IMS or API request calls. We now track those with AmigaMon for IMS as well and with AmigaMon for JVM if you're going the other way. And so this is a great new update that, the team has delivered in the last few months, in fact. And AmigaMon AI for KIX, one of our powerful agents and a recent fix pack three. And, again, Aleksandr will cover this in more detail. There's a a bend analysis, and you so you can look at the bends and summarize the bend details. And this, again, probably was driven by client requirements. The team continuously continuously delivers excellent updates in the in the fixed backs. As mentioned earlier in the d b two slide, that you have the application trace option so you can trace from KIX into d b two and, and in the reverse. And, also, if you want to trace a transaction or unit of work between KIX regions, we actually also enabled that through the, fix with the fix pack three. So we'll talk about that in a later, the slides. Okay. AmigaMon AI for zedos, fixed pack 10, was released a few months ago now. One of the updates which I like, is the improved GIS mock queue monitoring. Now if you see the slide here, you can see the job classes. But you as highlighted in yellow, those rows, those are that identifies that you have jobs waiting to be, processed by JES, although they are not in the queue. And so you may want to raise an alert or situation so that you can track those kind of scenarios. And then you also in this table, you can also see those jobs that are actually or how many jobs that are with type run equals hold. So those jobs will be sitting there on spool ready to run. And, if you have too many of those jobs rating to run, you wanna keep an eye on the spool usage as well just so you don't run out of spool. So there's many more capabilities available through this enhancement that you can now track. And AmigaMon for messaging. So AmigaMon for messaging is also available on the web UI. We provide several, Gafana dashboards now to part of their package. And as as as you can see the screenshots here, we give you queue statistics, queue status, and queue manager availability. Those are available out of the box, with these dashboards. We continue to grow that, so we will add more dashboards as we add updates to the AmigaMon for messaging product. What we do also do, is integrate or pull in SMF one one five records. So if you are interested in additional statistics from your queues, we now, one of our agents that utilize SMF records so we can, show those additional metrics to you in the UI. And, software solution updates or rather, any changes that you should be made aware of. So as of August 3 thirty fourth of this year, the AmigaMon version five five agents for ZOS networks and dashboard edition are now end of support. So if you are running on these versions of agents, we encourage you to migrate to the version six ones, as soon as possible. They are now end of support. We do have migration process of steps that need to be completed for you to have entitlement to the six one versions, please reach out to your IBM rep, and they will work with you to get the entitlement to the six one so you can download them from shop zed. So, hopefully, you are already running six one or in plan to move to the six one versions for ZRS and networks. If not, please, reach out, and, we'll help you get there. If you're on one of the older suites, so I've been zed service management suite version one. If it's one eight, one one dot seven, etcetera. Again, because the five five agents are part of those suites, these suites are also end of support. Now if you have entitlement to, service management suite one dot x, we can migrate that entitlement to a later version. Again, please reach out to, the IBM rep so that we can assist you with that. Okay. And I think now I rushed for this because I wanted to give more time to the team. So I'm gonna pass it back to Aleksandr and, Christoph to, take, to take you all through the new updates to JVM, the Kix Fix Packs that I mentioned earlier, and the d b two integration capabilities. Over to you, gents. Thank you, Ash. Hello, everyone. So I'm Aleksandr. I'm a senior solution adviser for the, Rocket Software. And, today, with Christoph, we're gonna be talking about, the Kicks and JVM and d b two enhancements, that we did. Okay. I'm Christoph. I'm a colleague of, Aleksandr. I'm covering the d b two part, whereas, Aleksandr is that guy that's it's, always blaming me for the bad d b two performance. And we want to get a little bit deeper inside into that, and so we are talking about the integration capabilities. Up to you, Aleksandr. Yeah. Finally, we can decide who's actually to blame. Is it KIX or is it the d b two? Right, Christoph? Right. Okay. So. the first thing I'm gonna be talking about is the latest and greatest with AmigaMon, AI for kicks, six dot one and the fixed pack three, which we recently, just released. So and we're really excited to to for you to hear about it. So let us start, with the TCPIP enhancements, that we did. So the enhancements, provides, additional visibility into the certificates used by the TCPIP services. So now you'll be able to display the, 32 character certificate label from the key ring. This basically identifies the server certificate used, during the SSL handshake, for the secure socket layer connection associated with your, KIX, TCP IP service. Right? So, the certificate label is available in few places as you can see in this example as well. So it's available on the TCPIP service summary, the TCPIP service detail workspace, and also you can do a find port, display as well. I think this makes sense as it's much easier to confirm which certificate is actually being used by the particular KIX TCP IP, without you needing to lift Omegamon and investigate the config configuration separately by looking into the SATs, seeing to SDSF, doing a CMT, and etcetera. So, yeah, this is here for you, that you can actually, use. Another one, improvement, that we've did is, of course, the one that Ash mentioned is the kicks, dumps and event summary workspace improvements. Right? So this enhancement should, hopefully, provide you with a quick and, consolidated view of, your event activity within your KIX regions, within your KIX environment. This new, little, dump summary panel, within the KIX and, KIX dumps and events summary workspace, now displays the summarized events information, helps helping, I don't know, operators, administrators, or basically anyone, who wants to figure out, what's happening, with their Kixes because, you know, we want to make sure that, Kix has zero transaction dumps and, zero systems as well. Events are summarized by a band code, transaction ID, and the program name as well, making it easier to spot the recurring issues, determine which application or maybe transaction are most frequently affected, by these, crazy, dumps. As you can see in a bit, bigger screen now, for each entry, OmegaMon shows both the total number of occurrences, since the last statistic reset, remember that, and then the number of occurrences during the last sixty minutes. Right? So you can have a look how your application was actually behaving in the last sixty minutes if you had any any dumps out there as well, and you can determine if everything's good, if everything's bad. You know, the customers won't be happy. I need to go to Christoph and then blame the DBT as always. You know? This is here for you as well. And, basically, this will allow you to distinguish, between the long term trends, you know, and then also the current problem activity, making it easier to prioritize your investigations and then, you know, respond to emerging issues, before impacting your users, your customers, because, you know, this is the more important things out there. You don't want to end up on BBC or Sky News with your Kix applications. And then to further accelerate your problem determination, we're still talking about a band a band summary. You can drill down even further directly into the desired bank code. And then for any bank code of interest, you can open a filtered Kicks event summary workspace just by double clicking on the bank code in the in that dumps and event, summary workspace or, from the kicks, that summary history as well. Right? And in this example, you can see I'm just viewing my Azure events, and I can already already see, loads of valuable information and statistics, for my investigation. I'm not finished with events. There's one more. Then in the event summary workspace, I just double clicked on my Azure and then just double clicked on that individual single Azure event as well. I double clicked or I can put s and hit enter. I opened the event detail panel, for that task. Right? This will give you even more information about your event and that particular task as well. Right? So the code, some general purpose register information as well, then you can go even further. You can navigate to a task history for that selected event just by typing o and hitting enter on it as well, and it will go straight into task history records. So it will it knows the task. It knows the abandoned. Hit o. Press enter. It will go into task history for that particular task as well. So you don't need to remember the task number. You don't need to remember which actually abandoned. You just put o against it, hit enter, and figure out where my issue went and why that event actually potentially could happen. Is it in a program tracking? Is it something to do with the timings and etcetera as well? So all that is available, that you can investigate further. Another really cool improvement that we did that came from one of our customers, as Ash K Mahay mentioned, is to improve the navigation and productivity. So now AmigaMon AI for kicks supports direct aliases coming and commands, from the Kicks level panels. So rather than navigating through multiple menus, maybe you you can't remember where what is, you can just from the command line, you can just tap storage or, for example, d b two c. Right? Hit enter, and it it immediately access the commonly used KIX monitoring administration workspace. So storage, you know, d b two connections and etcetera. This should provide you a faster and more effective way to reach the information, that you need, especially when you want you under pressure, you want to troubleshoot, or you want even to perform and analyze, those activities as well. So if you're unsure which commands are available, simply from the, Kicks level panel, type v dot a, hit enter, and you will view all of the available aliases, as well. So, again, enhancement should reduce the navigation time and help you both experience the new users access the key workspaces for you. Another great enhancement that we did, and I think this is very cool, is the how we can view the transaction activity. Is it supposed to be, transaction per minute, transaction by second? I mean, by default, transaction rates are shown, transactions per minute. Right? So however, you can change that view very simply. I just needed, to type options command, select the desired format, and click save. You know, you can put apply. It will save for this particular session only. But if you click save, it will, you know, retain, the same configuration until you decide to change it, later on as well. So before that, you need to go to a global, change, the TPS or transaction per minute now. Just type options, click save, and that's about it. You are now the TPS guy if, for example, you would love to view that particular information. We've done a lot of improvements in our, tracing capabilities, in our tracing workspaces. Right? So there are two major trace improvements. I'm gonna talk about the first one and then hand over to Christoph. But the one, that you can see in here is, the new plex white tab providing the, consolidated view of the trace activity across all KIX regions in for participating in that unit of work. Right? So remember, sometimes we will have TORS, AORs, FORs, then maybe some other case regions as well. Right? Now, with the tracing enabled, it will understand when the switch actually happened when it went into another region, it went back, and etcetera, as long as it's all within the same unit of work. Right? So, this enhancement, hopefully, will simplify that cross region diagnostics that we have with our Omicronia for kicks, help you identify the processing bottlenecks more quickly and gives administrators complete picture of how that whole workload is actually formed through your Kix Plexus as well. Because sometimes we even don't know how our KIX applications is behaving, which one is t o r, f o r, or where are my transactions spend most of its time as well. So we have that plex wide view, but now hear me out. We also have, the d b two and Kicks tracing enhancement. And I would like to hand over to Christoph, the d b two expert, who's gonna talk about, the another amazing enhancement that we did for our, tracing capabilities. Over to you, Christoph. Okay. Thank thanks, Aleksandr. I went too fast. Yeah. Before we go into the QIX specific part of this application tracing or combined tracing capability, let's have a quick look at DB2 application tracing in OmegaMon. You may know if you're a DB2 person or user of the OmegaMon DB2 30 to 70 interface that you can specify an application trace independent of, this correlation, into QIX. So there's an application tracing capability has been added two or three years ago to the enhanced 30 to 70. And what you do is you start on the DB two side in Omega one thirty to 70 interface to specify, options for an application trace. You always have to specify, some criteria for filtering. For example, which threats you wanna filter or you wanna trace. You always have to specify a plan name, one or more plan names, and you can optionally add, other criteria for threat filtering. You would also add, let's say, the level of detail. So what you wanna trace, at least SQL calls, you can add, locking or unlocking unlock requests to tracing if you want. And, what under the covers will happen when you start the trace, and the trace will be written to a vSAN dataset, is that, the omega one d b two, the data collector will go ahead, start performance traces in d v two accordingly. So it will take care of the, trace classes for according for the performance trace. And then it will catch the events when your threads qualify for this, application trace and write that to out to a vSAN dataset. At the end, you have the same interface, the enhanced 37 UI to see what was happening in the DB two subsystem at that level of detail that you specified. So, for example, you wanna track the SQL statements. You wanna see whether every individual SQL statement started a sort of scan activity on an object, how long that took, how many calls were made into d v two, etcetera. This is a feature which has been there for a while in d v two. So not specific to any, let's say, kicks related activities here. But now in the next step, we also have added or we have a similar capability as Aleksandr and all the KIX persons may know way better than me, to start application tracing also on the on the KIX side. I think the the mechanism is quite similar. You have to specify, criteria for filtering and KIX. It's not a plan ID. It's a transaction ID, for example, or one or multiple, transaction IDs that qualify this criteria, you can specify multiple traces at the same time. Correct me if I'm wrong, Aleksandr. And then you would specify the level of detail and the duration of the trace similar as in the d v two world. OmegaMon will, kicks will collect the trace data, and it will attach it to the, task history. So task history needs also to be active at that point. And, the same, as I say, equivalent approach here, the enhanced thirty two seventy UI gives you access to the task history. And if tracing was on, you see this here on the screenshot, there's an highlighted field, trace active, then you can have a deep dive into the QIX related activities. So also this is not that brand new, but now what is new is that we combine these two trace collections into one. And this is called the combined QIX and d v two application tracing. It's always starts from the QIX side. So, if you want to have a look at it, you need to navigate, through the, QIX enhanced thirty two seventy workspaces, navigate to task history, locate that little trace field. And then once you have that located and clicked on the QIX application tracing, you see a panel that has should have, and everything goes wrong it goes goes right, has a tab that is named combined. So a combined trace, it's hard to see it maybe in this screenshot here, but a combined trace exactly tracks what's happening on the Qix side. And when it calls DB2, makes a call into exec SQL or something like that, then it switches the context and then you see the, corresponding trace entries on the DB2 side taken from the DB2 application trace facility. So you can really see with every single activity, with every single call from, QIX into DB2, it may span, let's say, several calls. Yeah. But you see once you have this SQL statement executed, you see the related activities inside, DB2. So start of a scan, stop of a scan, do a sort, whatever. Yeah. And then, along with the time stamps. And if you have, specified sort and scan summary, you can also see which objects, which tablespaces or image indexes have been affected. There's also sometimes you see more information than that, in the, DB2 side, interestingly enough. But basically, yeah, you see this, entire flow of the transaction and of every single SQL trace. And the good thing is no special activities required besides starting the traces on the kick side as well as on the DB2 side. So we move over. Yeah. Maybe here you see some recommendations or some some, let's say, summary for your reference. Basically, start at DB2. My recommendation is we start at DB2. You define an ATF, application trace facility, then you start, Kicks. Always make sure that you have a kick start history on, pick that applications that you are or the transactions that you're interested on, then run your workload. And now navigation starts from Omicron Omicron for kicks located in task history and, see what is shown on the combined tab. This feature is very new. And in this case, I always, wanna say that we, from the DB two side, were quicker than the QIX colleagues. QIX has made that available in August 2026. So you need the most recent fixback, to have that capability. D v two made it available in July in the enhancement PDF, which is named here. And it it's just complementing a feature which has been there for a while, for a couple of years. So maybe you should have a look at it if you're using omega one KIX and d v two that you should enjoy having a capability to integrate TIX task history to d b two threat history and vice versa. So you can navigate from, a Kicks task in the task history to the d b two entry and then directly jump into the d b two account and record for, let's say, more detailed analysis of a KIX transaction of a or of a DB2 unit of work. So great news. And, we really encourage you and the customers really got we got the first, let's say, reactions by customers yet. First, interesting. They are interested, interested out in the field. And, you should also consider, if you're using both of them, Kixa and d v two to upgrade to the very latest and greatest fix specs and enhancements to releases. So with that great news, I go back to my KIX, SME here and leave it to you, Aleksandr. Thank you, Christoph. Yeah. So there you have it. We can finally determine, is it the slowdown in QIX or d v two with the stuff that Christoph showed? Okay. So now I'm really excited to present you Amiga Mone Air for GBM six dot one fix pack five. I know that development team works so hard, so I'm really excited to show you the latest and the greatest. And, of course, as any OmekaMon, all of our developers are working so hard, to make sure that you have the greatest capabilities out there and greatest metrics. So APM feature. Right? One of the most significant enhancements that we did in this release in the fixed pack five is the application performance monitoring or APM for our Java applications running both WebSphere Liberty or WebSphere application servers. Yeah. It can run WebSphere native, WebSphere Liberty, KXJ VMs, everything. You know? All of this now will you can use the APM feature with the fixed pack five. With the APM feature enabled, OmekaMon AI for JVM automatically captures the detailed performance information for supported applications, interactions, including the response time, the CPU consumption, the execution context. Hopefully, this provides the deep visibility into how your applications are actually behaving, without any code changes in your JVM application. The solution, as you see in the slide, supports both Java EE and Jakarta EE environments, making it suitable for both traditional and, let's say, modern enterprise Java applications running on your zOS machines. All of this collected performance data is stored locally, in the SQLite database, within the DominiqueMon Collector or in the starter task as well. One thing to remember, very important, that APM is not enabled by default. There's couple of, lines how you can do that, and then you'll be able to get all of the great statistics and information, that, you know, you'll be able to then determine, why your JVM is slow or why it's not ex working as expected. Here's just the same screen, but within the web UI. You heard about web UI, how much we're invested. So we have the, of course, the dashboard for the web UI for the APM features as well, just more graphically represented. Of course, you can add, more, dashboards. You've seen how easily it is to do with the amazing case demonstration. So, yeah, it's there for you as well. From the server, request workspace, you can drill down into an individual request, right, to, investigate, the application behavior and the performance. As you know, if you're using Comigio Moneya for JVM for your zOS connect world, you can do every request out there for the particular APIs. We've basically done the similar stuff or even the same stuff now with your Java, WebSphere Liberty, and, you know, native WebSphere applications as well. So now I can select the specific server request. Omika man will open the cope, the detailed view that brings you all of the information provided for you to start troubleshooting in one in a single place. This includes the high level request overview, detailed execution, performance metrics, session information, network related data as well, everything for you to investigate if that particular request in my JVM, in my web server application was actually slow. Having all of this information, you know, you can view a single transaction, makes all single request, and then it will you you'll be able to basically understand exactly how that request was processed, where the time was spent, determine whether there were some issues originated from the application, infrastructure, or someone else as well. And, again, web UI. We want to highlight the web UI. All of the same statistics, same information, just like we've viewed in the e 30 d 74. The server request workspace is available on the web UI just with some more graphical, information as well as you can see in this amazing, slide. Continuing with the request analysis enhancement with the fixed pack five, to help you focus on the information that matters the most, you can now filter stuff. Right? You can filter capabilities across many of the key columns within the APM workspaces. Rather than manually scanning through the large numbers of application requests, if you have thousands, for example, your JVMs, thousands of JVMs, and etcetera, you can quickly filter just the data that makes sense and much easy identify the performance outliers, narrow down the scope of investigation as well, right, and then focus, where the intention, you you you know, is required the most. If you're just troubleshooting the slow request, investigating, performance issues, analyzing application behavior, hopefully, these filters filter capabilities will help you reduce the noise and help you accelerate the problem determination as well. Right? Because JVM, Java is so important and so great, running within the zOS, world as well. Situations. We've expanded our out of the box monitoring situations, as well with the latest fix packs. So you can automatically monitor your response times, your request, AGB methods, JCA calls, JDBC requests, server requests, and etcetera. All of this to make your life better, to make your alerting better as well, and even you can have some take action as well. Right? Like, take a heap dump, take a system dump, and etcetera, all within the powerful and great Amig Muni for GVM, fix pack five. And I think that's it, for the latest and greatest in Kicks d b two and GVM. I'm gonna pass over to Kevin for any key question and answers. Thank you, Alex. First of all, I'd like to thank everybody who, has been submitting questions in the q and a. Great. Thank you so much. There is a couple of questions that came up, that I'll go ahead and, read right now, which is one, does combined tracing for a IBM MegaMon CICS and DB two require specific traces on the CICS and or d b two side. And I think, Christoph, that might be yours. Yeah. I think I, talked about that. No specific traces in addition to those that you would, start anyway for, PIX or for DB and for DB two application tracing. So you can use them independently or use them together, but no specific action required, if you want to combine them. Does it answer the question? I hope so. Yes. Great. Thanks, Christoph. The other question is, can I track a specific program call path from the transaction down to the lowest level program? And I think that's on the Kicks side. And, Aleksandr, would that be yours? Yeah. Yeah. And I'm glad somebody asked about the program tracking because we're so proud of program tracking, in Amiga Money for Kicks. So, yes, definitely. You can you can do that with Amiga Money for Kicks. And as I mentioned, we call it a program tracking. It basically allows you to see all of the programs that were executed within a single transaction. Right? So for the individual task, Omega for Kicks will capture, the programs that run and provide the performance metrics for each of the program, such as CPU, time, count, how many how many times the program was actually invoked, the elapsed time, the dispatch time, and now we've also added the storage information as well. So these program tracking metrics will help you understand where the time is being spent within just a single task, just within a single transaction as well from the program level, type of analysis as well. So, yeah, please try program tracking. You have to enable it from the global as well, and let us know, what you think on it as well. But, yeah, it's very powerful, and it's, we're very proud of it. Thank you, Kevin. No. Thank you. There is one more question that came up, which is, does MegaMon AI for JVM provide visibility into ZIP and CPU usage? I think that's yours, Aleksandr. Yeah. I'll take this one as well. Right. Yeah. I think there was some sort of discussion around the, ZIP spillover and also the CPU. So definitely, yes, I mean, for JVM, can monitor how much CPU time is being consumed by your JVM, application. So that's US Connect. That's WebSphere. That's Liberty. That's Kicks JVMs. Anything. Everything is a JVM. Everything is a Java. Everything can be monitored. So you'll be able to view the CPU time, how much work is eligible to run on the ZIP processor, how much of that is eligible and actually should run on SIP versus the spillover on the general purpose CPs as well. So, that hopefully makes it easy to identify the workloads that are not achieving the expected ZIP offload benefits, and then you'll be able to understand the software licensing, the system costs. And, overall, all of these metrics correlate between each other with garbage collection, with CPU, and I can talk hours and hours about other capabilities and metrics. But, yes, you can monitor the ZIP, utilization, the CPU, the spillover, all within the Wikimedia for JVM. Thank you. Great, Aleksandr. Thank you. I think that's it for, this q and a segment. I appreciate, very much so, Christoph, Aleksandr, your your guys' segment. I'll go on to introduce the next segment, which is actually, going to be provided by Todd Lipp, who is a principal solution adviser for the z center of excellence. He is also part of the Omega Mons SWAT team. In regard to, this particular session, what he will be discussing is moving from the Tivoli enterprise portal to the new MegaMon web UI, and what are some of the best practices in doing so. So with that, Todd, thank you so much. Take it away. Okay. Thank you, Kevin. So we're gonna talk about, migrating from TEP to WebUI best practices. We're gonna focus mostly on workspace conversion as part of this conversation, primarily. Let's see here. Hi, everyone. Just give us one minute. We just had a slight technical difficulty. Todd is getting back on now. Todd, do you wanna test it out one more time? Yeah. Can you hear me now? Yes. I can. Go ahead, Todd. Thank you. Oh, okay. I don't know what happened there. I'm see. So we'll start over here a little bit and back up because I'm not sure where you lost me. So with when it when it comes to migrating from the TEP to the web UI, the Okay. I'm We lost we lost two again. Sorry, everybody. We're just having a slight bit of technical difficulty. Let let us have one second. We're coming we're coming back on. Hopefully, you can hear me okay. Give it one second while Todd determines his sound. I apologize, everybody. Alright. As you can tell, we're live. This is what happens live. So, Todd, do you wanna test it one more time? I know you took your headset off. Okay. I think he's he's still coming on, everybody. Thank you for your patience. Really appreciate it. Now luckily, he's on the first slide, so he knows exactly where to start. Let's see if we can toggle to the customer panel. Jen, could we toggle to the customer panel while Todd's getting his microphone set up? Is that possible? Alright. Perfect. So we're gonna go to the customer panel for now while we get Todd set up. I apologize for that, with Alex and Richard. So if we could, play the the panel, please, Jen. Hello, everyone again. So now we move into what is often one of the most valuable and insightful sessions of the event, our customer panel discussion. While today's presentations have showed the latest innovation, capabilities, direction of the AmicaMon portfolio, I think this session is where we hear directly from people who matter the most, our customers. After all, Omikamon is built to help customers solve their operational challenges, improve their visibility across their environments, and make decisions based, on actionable insights. So without further ado, I would like to introduce mister Richard Savage. So hello, Richard. Hello. Let's start simple. Could you just briefly introduce yourself, your background, and your current role at your comp company? Okay. My name again is, Richard Savage. I worked eighteen years for First Data Resources, which is now part of Pfizer. I worked in their posting area, which was called the suit date area, and, you know, posting monetaries and non mon's. I also worked four years at Beacon Insurance on their billing system, and I supported that. And for the last fifteen years at FIS, and I, currently worked the last nine years in CICS tech support. I also worked, four years on the B of A team, that is, at, TIS. And then, prior to that, I worked two years on the m MTA level one support. Oh, wow. That's really cool. I mean, I'm a Kicks guy as well, so it's so good, to speak, to another, kick Kicks guy. So, yeah, it's it's so cool to understand, the perspective and experience that you have. So I think, we're gonna have an amazing discussion, Richard. So yeah. The second question, that I have is about the AmigaMon for kicks because we're both kicks guys. Let's talk about kicks. So how does AmigaMon for Kicks help your organization and yourself? And can you share an example where it helped you identify, diagnose, or resolve a performance issue within your Kicks application or applications? Yes. A, recent example would be, we were getting several RLED events, resource limiting, due to exceeding the EDSA storage. Mhmm. And we could tell from, the fault analyzer that it was bombing in the TMM process, which is tables, memory manager, which loads the, DB2 tables into a data space. And so what we did, is we ran those transactions through and could tell, through the, high watermark, greater than high watermark storage that, indeed it was using quite a bit of the EDSA storage. So, from there, we were able to track down that, some processes were calling the, third party vendor, application tables memory manager that it was calling it incorrectly. Instead it reallocating, the same storage area. It was kept at every time, it was called, it was reallocating the EDSA storage, and there's a flag that should have been set prior to these, applications that would sit goes out to the third party vendor software. It says, okay. Reuse the storage that I just previously you used on the call. And after we made that change, then we used OmegaMon, to see if the change was effective. And, instead of using megabytes, we we went all the way down to kilobytes, and that solved our our LED bins. Oh, wow. That's that's cool that you're, like, using resource limiting, but at the same time, like, I you were able to determine where the issue is and save the storage for your kicks so you won't go short on storage anymore. Right? Right. Correct. Yeah. Yeah. That's that's really good to hear. Yeah. Especially, you know, these examples are are such, you know, good feedback for us as well, that the product is working as expected. So yeah. Thank you for sharing that, Richard. Let's talk about program tracking because I know that you're a big fan of program tracking. I myself a huge fan of program tracking. So, can you share how your team or yourself uses KIX program tracking, OmegaMon on KIX program tracking, and perhaps maybe an example where it help identify or solve, another performance issue that you potentially had? Well, for mainly, I use the program tracking, for our heavy hitting, applications such as our ACE system, which is, responsible for booking, new accounts. Mhmm. And, because a lot of the debugging tools that, are used, are very time consuming to set this application up with, and also, the application is so many layers deep that it's it's very, ineffective with the, debugging tools to isolate the issue. So by turning program, tracking on, able to see, quickly, what pro what programs it's calling. And then from there, we're able to, deduce, what kicks execute statements that it's executing. And from there, you can easily see, what commands are being processed and what isn't. So, if a transaction is not acting correctly, we're able to run this, and then the programmer looks at it, and we're able to track down exactly what the issue is. Yeah. And another recent example would be Mhmm. In our, one application for the Capital One, client. We were able to, return program tracking, on, and we could see where it was spending a lot of time, in a, inserting certain records. And, it was in trying to insert, KSDS records, and we were able to just, convert that by through the program tracking of OmegaMon. We were able, to see that, and from there, we went and converted the KSDS, VSAM to an ESDS, VSAM file because there was no reason for the file to really be allocated as KSDS. And they were able to greatly reduce the time spent, in that application, and, that that was very effective in solving that issue for the, high, CPU time being spent. Yeah. That's that's awesome. I mean, that you're using the program tracking and you're the fan of if they help you out, resolve some of the issues or track how the programs are behaving within the transactions just like, yeah, this is excellent. And we keep improving program tracking, you know, as as we go as well. So, yeah, this is just brilliant. So thank you thank you for that, for, for this feedback as well. Let's talk about a little bit about the, WebUI. So I know that you haven't fully explored the WebUI, but we had some conversations, you and me, about the Omnicomont WebUI, about the new UI, about the dashboarding. So I thought maybe I could ask you what are your initial impressions. Do you see any benefits in terms of ease of use, visibility, navigation, ability to identify or investigate, again, some performance issues more quickly, build your own dashboarding out of it as well. So, what are your thoughts, Richard? What I was really impressed with was the dashboarding ability. That is something that, I would wanna fully u utilize, from that product, and it would, give you a picture. You know, a picture's worth a thousand words. So it gives you a picture what exactly is going on and what the issue might be. So, I was very, very impressed with the dashboarding ability and how quickly you could add or change stuff for your dashboards. Yeah. Yeah. Well, we're excited with you, Richard, as well, and we're gonna help you the through the whole WebUI journey, you know, so you know where to find me. We're gonna keep going. But, yeah, that's very encouraging to hear those, thoughts that you have, your first impression. So, again, yeah, this is really great. Let's talk about a little bit AI maybe because, you know, it's the the world that we live in. It's all about AI. So you know about Omigamon AI as well, that, Omigamon AI for kicks, has introduced AI powered insights as well that automatically, identify the CPU and transaction response time anomalies. So how do you see these capabilities, fitting into your organization, if there is any? And, where do you think the AI driven insights could help you, your team, to detect, investigate, prevent, unexpected application behavior and maybe, server disruption as well more effectively, perhaps? What'd you think on that, Richard? I think it would greatly, reduce our time to find the root cause of issues. It's able to kind of, point us in the right direction, quickly, more so than, we were before. So that's where I see, the AI being of, really a benefit and a use in, just, the, speeding up the process of finding root causes for issues. Yeah. Yeah. Because, I mean, this is, why it's here for, you know, the AI help, the customers identify the the the performance issues. Yeah. So this is this is really good as well, your thinking and the focus that you're gonna have. Yeah. So we talk a little bit about kicks. We talk about AI, web UI. So, let's talk about maybe an overall feedback. So how would you describe your experience working with the Rocket Software, the center of excellence and the concierge teams so far? My experiences have been, very, very positive. The, the team, you know, composed of yourself and Samuel and Steven and Mike, you guys have been very accommodating when meeting with us and responding to all our questions and helping us to resolve our issues. So it's it's been really an awesome and great experience for us here at TIS. Oh, yeah. That's music to my ears, Richard. Yeah. So this is this is great. Yeah. And we're always here, you know, to help you out in the future as well, and I'm looking forward to to those interactions that we're gonna have. I know that you've participated in the Omegamon office hours, the great office hours that I think everyone loves. So, what do you think on the office hours, with your feedback on it? I I love the office hours, and the reason for that is because you get to, hear other companies questions and comments and concerns. And, it gives you an idea of how other people are using the product and, gives you some ideas of how you could use it for your organization. I just like to see it expanded to a full hour. Yeah. I know that. Yeah. I know that. Yeah. Maybe in the future, you never know. Yeah. But it yeah. This is and that's what office hours is all about. You, the customers, can interact, talk with each other, and think, okay. Maybe this is the way I should do this or the other way or just share your feedback, the good and bad, everything. So, yeah, this is this is exactly what you're what you're talking about as well. Yeah. I mean, I've enjoyed, as always, talking to you, Richard. I could probably talk for hours and hours, you and me, but I think, we need to finish, and hopefully finish on a high note. So to close, what is one or several key takeaways or your final message, that you would like to leave for this summit and for this whole audience that are currently listening to us? I just like to say that, the OmegaMon tool is a very, excellent tool, to use to diagnose and, to help you determine the root cause of issues. The measurements that are given for the transactions. There's a ton of measurements that that you can use to verify how your processes are performing. So to me, it's an invaluable tool, that we really can't do without. Great. And this is excellent. So thank you very much, Richard. Yeah. I guess I don't have any more questions. I mean, I really enjoyed, talking to Richard, and I think it's an excellent message to end on. So, Richard, on behalf of everyone at Rocket Software and here at IBM, thank you for joining us today, and sharing your experiences. I mean, the customer feedback, your feedback, and real world stories like yours are incredibly important because they help, us, to continue to innovate and ensure that OmegaMon evolves, to meet the challenges that you, the customers, feature face every day. We really greatly appreciate your partnership, with us and appreciate your continued support as well. So thank you, everyone, in the audience as well, and have a great day. Thank you. Thank you. Okay. I guess we're gonna try this again. Let's see if I fix my audio issues this time. We'll go through this a little quick quicker than I had planned because we're gonna we're we're gonna be hitting up the end of our time here soon. But Okay. Let's in terms of migrating from the TEP to the WebUI, as we mentioned earlier, there's not a lot that you actually have to do in terms of the migration. We're doing a lot of that for you in terms of giving you the admin functions and history configuration, and we're giving you the the situation editor and all that in the new web UI. There won't be any need to to port any of that type of stuff over. And so what we're really looking at as remaining to potentially have to migrate is your is your workspaces. And a lot of customers have have have told us that they have been working on workspaces and developing workspaces in the TEP specific to business needs, for decades. Right? The TEP is not a new is not a new tool by any means. And a lot of our customers are heavily invested in the workspaces and the and the application centric views that they have built and the navigation views that they have built within TEP. And so what's the easiest way, to get that all into the web UI? So we're gonna talk about a migration approach quickly, and then we'll we'll have a peek a sneak view or sneak peek at the conversion tool that that we'll be providing. So we're going to recommend that first and foremost to assess the workspaces you have, decide which ones need to be carried forward. You're gonna convert workspaces as you decide that you need to. You can have some validation of and effort, and then you're gonna do enhancements, and you're gonna deploy. Right? And we'll hit these points a little bit deeper here. First first off, maybe you don't need all your workspaces to carry forward. You have some specific workspaces you know you need. You wanna focus on ones you frequently use. You wanna eliminate any duplicate workspaces you may have and or any ones that you don't really wanna use before you go into the conversion process. Keeping in mind that, you know, you definitely wanna preserve that that history and the work and and time that's gone into building those workspaces, because they have value to you. But you're gonna find when you get to the the new web UI that you have, you know, features and functions and and some little little cool visualization tools that are above and beyond what the IBM TEP can do. Right? So don't don't pigeonhole yourself into what you have in the IBM TEP today. Convert the workspaces you need, but recognize that you're gonna be moving these to a more flexible environment and you might decide you want to enhance some or replace some from scratch. Right? You're gonna use the workspace converter tool to to accelerate the the workspaces that you do wanna migrate. Again, you wanna preserve your where your workspace investments. You got some time in there, and you're gonna just gonna build an an initial baseline understanding that we're also giving you a lot of sample starter dashboards as well. And so you you know, you might find there's some redundancy between the sample dashboards and your existing workspaces, etcetera. We got to have some kind of validation plan. Right? You you need to have the the affected end user community evaluate that they got the data they need. That the metrics are are the same as they were. You're getting the same metrics. Make sure that they're solving the same problem. That you're answering the same questions. And then these these last two points enhance and deploy, these are gonna be sort of of iterative iterative process. Right? You're gonna enhance it. You're gonna take advantage of some of the the the additional visualization capabilities of Grafana. You're gonna improve them. Maybe you'll decide to to retire a couple of workspaces even after you migrated them, and then you're gonna deploy them. And then the end users are gonna give you some feedback, and then maybe you're going to go through the enhanced cycle again. So this is not a one time, you know, cut it over and you're done. Understand these two WebViewIs can coexist. You don't have to do this in a hurry. What can the converter convert? It can convert your workspaces. It can move for it can convert your your navigator views and your little links. Right? If you have your if you're using the the little links that are built in the workspaces, those links will be also converted and carried forward. So keep that in mind as you as you as you take a look at what the converter will do for you. How does how does the converter work? Well, basically, if you're familiar with TACM and if you're a heavy user of of the TEP, you are probably familiar with TACM. You're gonna run a couple of export commands. It's really as simple as that. You're gonna run a couple of export commands. We're gonna create some XML output files, and you're gonna feed these into the conversion tool. Right? T converter is what we're calling these. There's some a simple configuration, step where you have to to do a little bit of prep work to do conversion. You will need to run this on a server that has Python installed. If you don't use Python, you will need to acquire Python because that's a dependency for the T converter. As you can see, it's just it's just a couple of, export workspaces and export navigator view, and that's all you're gonna issue. What's gonna happen is we're gonna we're gonna write this out to an XML file, then we're going to we're going to prep the T converter to read in the the the, the XML files that are created as this output, and we will convert these to to WebUI dashboards and and navigator views. And it's it's a very it's a very good one to one type of conversion. It's it's going to really create the view and very similar to the way it looks today. We're not just importing the queries, and the data. We're actually gonna make the view look an awful lot like it does today, with some minor variations based on what what the the two technologies look like. So there's just a few things you'll have to put in the config. Ini file. You'll have to give us the, URL for Grafana. You're gonna give us a token. So you're gonna go into Grafana, and you're gonna build a a service account, and that's gonna give you a unique certificate or a unique token. We're gonna need that token name. You're gonna give us the folder that you want to write the links out to and the workspaces out to within Grafana. So you'll need to go into Grafana and create two new folders for us to to run the converter as our output. And there it is also. It's another situation where you're gonna get a unique key for that folder, and you're gonna put that in the converter. And then the rest of this is basically just telling us what the XML files that you want me to import into the converter are. And then we're gonna go and we're gonna run. The next step is we're gonna run the converter itself. And you can see we've done we've been working with a customer. ABC Corp is not their real name, but we have we're working with a customer to kinda develop this tool. And you can see this particular customer, once we've populated the the the config big INI, we run the t converter. The file name is ABC Corp. That's the logical file name for it because it's the name of the of the of the customer. And you can see, hopefully, on this visual that we've imported 365 dashboards are converted. Right? So and this is really the target audience for for for for this conversion tool is the customers who have hundreds of dashboards and hundreds of workspaces. Right? If you just have a handful or a dozen or something, you're not a big user of customized dashboards, then you might just do manual conversion or just start from scratch and build some some views in the web UI as you as you as you choose. And so we're just gonna do, just kinda show you how realistic or how how we carry forward the the look. We're gonna go through and and just look at a few before and after pictures so we can point out that this is on the left hand side, what we have here is the, basically, the zOS workspaces that are in the a b c core folder in that navigator view on the tab. And you can see that we're pretty much one for one with the exception that somebody did add one to this folder after the fact, but pretty much one for one, same name, same view. It's gonna convert these in place. And so it's it's it's it's good to pretty close to one for one conversion. If you look at the well, just a few more of the before and afters, you can see, on this hopefully, you can see on this that you you know, top left, we have a line graph. Top left, we have a line graph over here on the WebUI. Then we have tables in the rest of the of the tables and the rest of the displays because that's what the visualization in the tap is. Right? We'll move to the next one. You can see we have some some table views at the top. In the middle, we have a horizontal bar chart. On the bottom, we have vertical bar charts. Again, we're not just importing, the data and the metrics. We're not just you're not just pulling in the query. We're actually gonna make these visualizations look very much like they do as much as possible like they do in the TEP today. So you'll be you'll be looking at the screen that's gonna look look like what you're used to looking at. Just a couple more to show, what I'm talking about here. We've got line graphs on the top, table displays on the bottom just like it was in the tab before we ran it, pie chart, bar chart, table views on the bottom. Again, this this just just another example of how we're taking the workspace, and we're gonna make it look exactly like it does in the temp to the degree that it the the visualization is supported in the in the new WebUI. So the key takeaway is what I wanna get to here. You do wanna preserve your operational knowledge. Right? You have a lot of workspaces built. You have a lot of of time, seasoned seasoned pro system programmers that have spent some time making workspaces that make sense for your business. You don't wanna lose that. Right? You wanna hold on to that. You wanna reduce the manual effort to recreate that. You wanna accelerate that dashboard development, but you want to use the converted dashboards as a baseline for modernizing. Right? You don't necessarily want to use everything exactly as it is because Gravana is going to provide you greater capabilities in terms of visualization, more dynamic capabilities in doing drill down and and and linking. And so absolutely take this opportunity to enhance some of these views once you get the the the the base set imported how you want it to look. Alright. And we're going to go straight to Guy Muller. Closing Thank you, Todd. Great presentation. remarks. Thank you all. Sorry. We are running a bit over. We had so much content to share. You know, we are passionate about this topic. Just give me a few more minutes, and, I just have some quite exciting news to share with you. So let me jump in. And, we are really customer centric. We really care about building trusted relation with selected user like you who are passionate about our product, who want to shape their future. So it's a relation that goes both way. Of course, you can ask in this exchange any question, raise any problems that you experience, but it also enable us to understand your environment, understand your challenges, and to capture your pain points. So and we're not talking about any big program. As Saghi said, we are easy to work with. So the idea, if you're interested, is just to have, from time to time, a quick discussion during which we can show you some development in progress and capture your feedback. This allows us to make adjustment in term of user experience, in term of testing, and make sure that we have the best product release each time. So, of course, in a dream world, you love this new feature so much that you cannot wait to implement it in your sandbox and to provide us, anonymous feedback. So don't hesitate to reach out. Don't hesitate to reach out to the z concierge team if you are interested in engaging more with the engineering team. We are passionate about, this product, and we will have to discuss with you. Five years ago, we defined this development strategy in collaboration with our customer, and it's great when customer tell us now, wow. You have delivered, and you really make our life easier. And I'm just going to go through it really quickly, but security. Security is more than ever a critical topic. We have what we have trained and we're training our team regularly. We have strict code review. We're doing stress testing, penetration testing, leveraging code scanning tools. Just stay as much as possible up to date with your product version, with your product update. It's really important, especially in today's AI world. Reducing the cost of ownership. You are probably already using config manager. And if you are not, please take it a look. But there is also the possibility to integrate with Ansible and to automate the update of your environment. And it's really important to minimize effort to have your environment be up to date. CPU consumption. We made huge progress on CPU consumption. Today, many customer, tell us that we consume up to 50% less than the competing monitor. For example, a customer recently told us that IBM OmegaMon for kicks has an overhead on the kick subsystem three times lower than a well known competitor. You heard it. This customer reduced his monitoring overhead in the kick subsystem by 70% when moving to OmegaMon. So please update the latest version. You are going to see that your CPU consumption will automatically decrease. We spoke about modernization of the user experience. We are investing in the enhanced thirty two seventy. We are investing in this wonderful graph on our web UI. You have seen it. And, we enable you to leverage the OmegaMon data in any analytical repositories that you have. And if you are not using OmegaMon data provider to stream your data today, look at it, and day one currency is a no brainer. Just to double click on the CPU consumption. As I told you, each time you upgrade, you are going to see that your CPU consumption decreases. Thanks to modernizing our code, leveraging the last compiler option, doing more in memory, thanks to 64 bit, doing performance and stress testing, and only at the end, leveraging ZIP for the remaining workload. To further reduce your CPU consumption, we offer you a quick assessment of your environment free of charge and provide you with customized recommendation that will enable you to further reduce your CPU consumption. And we are talking about low hanging fruits that are easy to implement, fine tuning your alerting, reviewing the data you are collecting, reviewing the settings of your mega man. So please reach out to the zCom search service, in order to leverage this, free offer. Sai mentioned this. OmegaMon turns 50. You have used OmegaMon for so long. For me, OmegaMon has never been so powerful, so modern, so strong. So if you are in Porto, Portugal next Monday, please join us. As part of iDog EMEA, we're going to have a celebration for Omega Moon. Just reach out. Likewise, if you are a tech exchange in Atlanta, please join us Monday, October 26. We are going to have the customer advisory council, and it's going to be a great opportunity to meet other user, to meet IBM expert, to have a preview of future development, and have the possibility to influence the future of the Omega Man. Again, we would love to have you join us. Don't hesitate to reach out. We spoke about the appetite to collaborate to support you, to provide you information, to make your life easier. The perfect example are the Omegaman officers. You are going to love the level of discussion, question between our users, the live answer of our expert, the sharing of tips and tricks, and best practices. You are all invited. And finally, I would like to talk about the z concierge program. Saghi and her team has put together this great offering that many other vendor are trying to duplicate without success. The reason is that it relies on a team of passionate experts. It's free of charge. All you have to do is to reach out, and you are going to be taken care of. I can tell you that I only had positive feedback from anybody who has a reference to the concierge program. So, of course, if you have a production issue or if you have product product dysfunction, open a customer support ticket. But in case you need help to upgrade, to deploy, or you have a question to better leverage our product feature, you have the possibility to directly access Saghi expert team, the z center of excellence, through the z concierge program. Don't hesitate to reach out. If you want to join us at one of the events that I just mentioned, just send a quick email to the z concierge. You are going to be taken care of. So thank you all for staying so long even if we run over. Thank you for your passion for this product. We're all excited to to work with you, and we're going to close this event for today. Thank you again.