Name: TMON One Modernization - 1st Half 2026 Innovations and Future
Uploaded: 2026-04-14T16:30:57.823Z
Duration: 42 min 40 s
Description: TMON One Modernization - 1st Half 2026 Innovations and Future

Transcript for "TMON One Modernization - 1st Half 2026 Innovations and Future": Hello, everyone. My name is Ken Lam. I'm product marketing manager for t mon. I'd like to welcome you all to this t mon one modernization webinar. We recently released the latest version of t mon, twenty six zero one, and this webinar will be running through the the key features that are in there and looking at each of the individual monitors to see what has been incorporated into those and also what we're working on for, the remainder of 2026. Before diving into it, just give you a little bit of housekeeping, and also what to expect. As you can see, we have a large number of people that will be jumping in and out. These are the development experts, the engineers who have been leading the different individual monitors. Each one will be stepping in to talk about their monitor or their capability they've been working on individually, so you should seal off the the people jumping in and out. These are the experts in the area, so, feel free to enter questions into the q and a. We look forward to being able to answer anything you do put in there. One thing to note, and I'll just move on to the next slide to point it out a little bit more. I'll come back to that. Sorry. Yeah. For the housekeeping, you'll see that there's both a chat and a q and a. The q and a, if you look when you put all your questions, the chat is really for anything that's not totally related to the webinar itself. Maybe if you've got any issues or anything else you want to raise. So please try and put your questions in q and a. We will try to provide a written response as we go through, but we do have a q and a session planned at the end. So we'll be on verbally and answer things in a bit more depth there. Also, there will be a short post event survey. Please take the time to do that. There's only four questions, should take less than a minute, but, it's really important for us to get that feedback and understand exactly, what interests you and what areas you feel that you want to, investigate more in the future and hear more from us in the future. So, with that, there is the disclaimer. It's the usual thing. Obviously, anything we talk about is subject to change, without notice. So please don't plan anything based on what we present today without contact contacting us directly and getting more assurances as we work to meet your needs. So what we will be doing, quick overview, we'll be diving into Team on Stream and the Team on HealthAI. These are two new major capabilities that are now available. We've got a number of slides on those, we'll go through them in detail. After that, we'll be looking at the individual monitors and providing an update on what we've incorporated and also what we're looking to do with each of those. So with that, I will pass on to our first, speaker, Sentel, to, walk you through the team on stream capability. Thanks, Ken. Hey, everyone. Good morning. Good evening. I'm Sentel, principal engineer for, Timon stream. You know, last Timon webinar, we introduced Timon stream as an upcoming feature. So it's now available with the p s 26 o one package, which was GA ed in February. So and we are already seeing lots of traction among our customers, so I hope you'll be excited. So what is streaming, and why does it matter now, and what kind of problems it can solve for you? So, today, almost all our mainframe performance data is still spread across, our individual team on subsystems or in some cases, some form of LFS archives. So we have, relayed on tools like a report writer for ages now. So they served us well, but, the reality is, the environments are getting, much bigger, not just your, the volume of transactions we're dealing with today, but, the increasingly complex workload. So things like, mobile, workload spanning across platforms and ATM channels, so whatnot. So it's getting kind of, harder to analyze performance issues, and customers are looking beyond mainframes to get a kind of a holistic view of their enterprise performance. So that's the problem, that Timon's team could solve for you. You can now integrate your mainframe performance data from your Timon subsystems into platforms like Splunk, Elastic, or, Datadog to get kind of a greater insights into your data. So that's about the solution, and, so here's how it's going to work. So on the left sorry. I went almost I'll be cool. Okay. Yeah. That so on the left, you have, the daemon subsystem. So it's already sitting on your mainframes. So monitors like the ZOS, Kicks, d b two. So all your subsystem monitors being hosted on mainframe. So what Stream does is it takes that performance data and pushes it out through what we call it as a rocket data gateway, and it gives a few options how the data moves or leaves the mainframe. You can get it as a standard TCP, IP, JSON lines, or as a kind of a HTTP post request or through, kind of platforms like Kafka or endpoints to Prometheus, so it can be taken out. So the data comes out of the mainframe in a kind of a standard JSON format. So, it's not something proprietary format that in we need to decode into. So on the right, what you see is a kind of a commonly seen, endpoints like Elastic, Splunk, Kafka. And, something not on the screen, even if you have a Datadog, it can very well integrate into a Datadog as well. So it's it's a very flexible architecture. You can decide what you want to stream. You can decide where you want to stream and in what shape. So plus, the architecture also gives you a flexibility, on where you actually want to run your streaming workload. So for example, you can run it on mainframe, or you can run it on a a zip enabled code. Or if you think, like, burning your, or, expensive mix cost is going to be a concern for you, you can try you can opt to run the streaming load of platform of mainframe as well. So, I'm talking about the coverage today in p s twenty six zero one. Eventually, the solution is going to cover the, whole performance data that's being tracked by Timmons today, but we are kind of rolling out in phases. So this is what Timmons team covers in twenty six o one today. So across the three core pillars, ZOS, KIX, and d b two. So from, ZOS system health to KIX transactional behavior, or you are at d b two workloads or SQL query efficiency. So, you can quickly see, like, where the time is spent, where the CPU is burned, and how the resources are being used. So in twenty six o two, we are going to expand our coverage into t one for m q and the t one for TCPIP. So you should be able to track all your messages flowing through your queue, your channel health, and your network throughput. So, you should be able to catch where the, network traffic is being stalled or slowed down with, that support. So also to kai highlight, like, the pack, the feature also comes out with what we something what we call it as a starter dashboard bundle. So we ship a Grafana and Kibana sample dashboards. So if you are someone who is new to this dashboarding or or, you don't like how to get started, So this starter dashboard bundle can come handy for you to get started. So it's going to come out of the box. You just configure it. You should see the streamed data show, shown visually in a fancy dashboard. So, that's the solution all about, like, if it if you think, like, it's something that, you would like to adopt, please reach out to us. We'll be glad to partner with you and take your efforts forward. So with that, I will pass on to Aruna for walking us through the LTI feature. Thank you, Sentel. Hello, everyone. I'm Aruna. I'm a principal software engineer at Rocket, and I take care of Timon Health AI. Timon Health AI is a relatively new product with exciting features. So I'll start by, walking you through some of the key highlights of Timon Health AI and then talk about what is in store for, Timon Health AI for this year. Right? So, to set the context, in today's world, IT infrastructure and applications are built across different languages, different platforms, mainframes, non mainframes, cloud, on premise. With all these, a lot of complexities are added as we all know. And maintaining reliable systems and managing their performance is becoming a challenging task with such an environment. Traditional monitoring products like Timon are doing a great job in identifying the problems, as they occur and are always the best friend of IT administrators. With Timon Health AI, we are actually, trying to move one step ahead by identifying the problems as they happen or even before they happen as they are building up. Maybe you can see problems in, problems building up under social stages or application delays, and it enables you to fix the problem even before, it actually causes a business impact. So, having said that, let me move on to the, core capabilities of Timon Health AI. We use advanced AI powered algorithm designed specifically for mainstream environments. It is not just, threshold based alerting. It intelligently understands your environment, complexities of your workload, and adapts to your environment. The whole value proposition lies in early detection of the problem. So it and as as it understands your environment, it also identifies, any minor deviation in the performance of your applications, and it alerts you, very early at before it actually creates an impact in your environment. Right? It also provides, customer alerts, as I said. So, you can tune it to send, emails, and, it provides, actionable insights through intuitive dashboards. And other key feature that does that is patent recognition, where, it identifies the patterns of performance of your applications, and, it's there is something special to that. Maybe I will, talk a little bit more as we go along. Moving on to the next slide. Okay. Regarding the key technical features of Timon Health AI, So Timon Health AI pulls data from all of the Timon products, Timon CACS, Timon DB two, Timon Sauce, m q, IMS, and TCPIP. So with this, it actually provides a comprehensive, comprehensive look of your mainframe environment. We also have added end to end security for every for every, the way that we access the data performance data, we actually store the performance data as well as we either trade the performance data. We are also providing, intuitive web interface, which has some, beautiful dashboards that can provide you insights through which, some actions can be taken, and, it also has some alerting mechanism through emails. Okay. So how this all works? Right. It pulls the performance metrics from all of the team on seamlessly, integrating with them, so you don't have to do anything extra. The monitoring products are already set, so the collection for every everything is already set. So with that, they'd sit as a digital analyst in your IT infrastructure, understands your ideas, your thousands of applications, and understands their performance, understands their performance patterns, and it also takes care of how your applications perform during different seasons. See, how how an application performs during a picker or, how a transaction performance during a off picker. Considering all this, our advanced algorithms actually, create some baseline profile for each of your applications. It identifies the patterns and, identifies even the slightest variation. We use some advanced algorithms for this, and it can identify every single nuance which a human eye cannot detect. And, as I said, it identifies the issues early, even before the actual problem happens as they are building up. So you can see alerts in, usage spikes, your job delays, or whatever, is causing anomaly there. And, it also provides, actionable insights through, dashboards. That's about it, how it works. So let me move on to the next. Okay. So what you see here is an anomaly list view. This is our scope, the b y. So whatever, you are seeing is called a list view where it lists all the anomalies. You can filter the anomalies, sort the anomalies. You can view, real time, on what all anomalies are happening. You can also go historic, and understand what has happened over a period of time. And, could move on to the next. So here is a view of our KPA view. This provides a single pane view of your entire IT asset. So you can see anomalies happening for for your different applications once you start creating your application views. And, it also, shows anomalies by, different KPIs that we are evaluating. KPIs are, system health indicators or key performance indicators that we have identified, against which we evaluate each of your application. So it will, show you how a particular application has, has performed over a specific KPI over time. Right? So all these actually enable you to, identify problems quickly, and, solve them or put any resolution for that. Okay. So what is in store for Timon Health AI this year? The first one, transaction level KPI for d b two. So as I said, we actually evaluate, the performance of your applications using some system health indicators called key performance indicators. We have identified a finite number of key performance indicators across your systems, applications, different domains, CACS, d b two, IMS, MQ. So as part of it, we are adding transact for trial with respect to transaction level KPIs, we have identified few KPIs for, CACS, MQ, and, IMS. With this particular feature, we are trying to add transaction level KPIs for d b two. Rakitiva integration. Rakitiva is a a conversational assistant, which can, help IT administrators, and IT operators. They actually can query it, query the data and then trace any anal trace any, functionalities and, maybe even, ask for some recommendations. So with this feature, we are integrating with, Rocketiva. And what's in store for, the 2026? So we started off as a pure mainframe based product and, our evaluation engine lies on mainframe at this point. So with this feature, we are trying to, add an evaluation engine outside mainframes, Predictive analytics. So, traditionally, are, identify the problems as they occur. With team on health AI, we are trying to be proactive and, say that, these are the problems that are building up. With this, we are trying to go a little bit predictive, over near time. Maybe, understand, the current trends and then see what is up what is gonna happen in the near term. Right? And, like, regarding the last one, expansion of KPIs, I see we are having multiple conversations with our customers, and, with that, and we understand some of their problems for which, we think few more KPIs can help them. So with this particular feature, we are trying to add, some more KPIs to our, evaluation list. So that's about Timon Health AI. I will probably move on to the Demand announcements. Thank you, everyone. Hello. My name is Andrew Joyce, and I'm a developer on the Timon products. I'd like to highlight our new release of Timon for z o s four ten, which is available on our p s twenty six zero one package. This this will focus on non fast problem determination, deeper performance insight, and easier setup. The first highlight is the intelligent navigation, which has been added. It allows the user to switch from real time displays to historical views on one screen. All the monitors, activity monitor, blade monitor, exception monitor, system health, and workload monitor have all been updated to simplify this transition from the real data to the historical data. Support was also added to, the zOS to capture, the ratios. This is a key performance metric that has helped evaluate the performance of the LPAR in real time and historical data. The measurement is one of the first data points to be examined when performing system performance issues. It's the system capture ratio. We also added the jazz privilege resource reporting. It's a small percentage of a few critical jazz resources are reserved for a privileged user to assist assistance programmer in case resolution of a critical jazz resource source condition. So we've added that support. We also increase the granularity of the CPU times reported. Many CPU times recently was reported in hundredths of a second. We've increased this with the increased speed of the z processors and hundredths of a second, and it's not granular enough to show the interval. So now we've increased it to the full stick value, so it it ensures, accurate reporting. Couple more things we've done, we've added, tracking to USS shared memory usage now. Users can track, able to track, USS shared memory in real time as well as some historical perspective, set exceptions against this data, and have, data aggregates in Netoplex. We also added a new screen to display the UNIX file system utilization. So if you wanna look at the UNIX file system utilization screen, it's much easier now. And one of the big things we did is we added, we've reduced the number of steps by 90% to customize and install the products the Timon product. It's much easier to install. So that's the enhancements for Timon zOS. Let me move on to t mon TCP. Alright. This screen highlights the t mon TCP enhancements, which are focused on security, network visibility, and modern connectivity. We've introduced secure FTP monitoring now, giving teams better insight into secure file transfer. So that's secure file transfer as well as regular file transfer. We've updated our Zurich displays, inserted its encryption readiness technology. It's a way customers can see which TCPIP connections are encrypted, how they're encrypted, are they using TLS, SSH, IPSec, what's being used. It's an easy way to see all the connections. We also added the RoCE SMC shared memory, facility, the adapter minor capabilities. It enables invisibility over the IDMA over converged Ethernet, which is increasingly important to high performance networks. It's it's a new way IBM moves data between LPAR to LPAR using shared memory. Lastly, we're coming up within q two. We've added, an additional VIPA display. We now display the method, ZOS uses to distribute incoming network traffic connections across multiple ports to ensure efficient and reliable network communication. But it's a nice way to see, where the connections are coming from, work cloud managers using them, how how how they're being distributed. And that's it for me. Onto, go to the next screen. Okay. Thank you, Andrew. Hi, everyone. I'm Pavel. I'm gonna quickly introduce the the most recent updates in t m m for kicks. So in t m m for kicks, we have added toleration support for KIXTS 6.3, ensuring that TCE operates without errors in the latest Qix TS environment. A new informational message has been introduced to notify customers when additional Qix tracing is enabled beyond the traces required by TCE. Hopefully, this helps customers avoid unnecessary tracing overhead and better manage system performance. As shown in this screenshot, all required trace components are now automatically set when data collection is initialized. An accompanying informational message displayed in the top left corner confirms the trace configuration status. TMOM for Kicks is now fully supports data streaming, a capability that was already covered earlier in today's session. That's all for Timon for Kicks. Over to Aditi. Thank you, Pavel. Hello, everyone. I am Aditi, a software engineering specialist at Rocket Software, and I work on the team on four m q product. And the slide covers recently team on for m q enhancement and a brief look ahead at what's planned. So for the delivered enhancements for the first half of the year, we have streaming queues. We've added support for streaming queues through new attributes on local and model queues that are managed by our distributed queue manager. These attributes include the streaming queue name and quality of service, and this functionality is useful for scenarios where additional processing or analysis is required without impacting the original application. Secondly, this was a customer, enhancement request for enhanced exception monitoring. We've added a new flag on the exception monitor definition screen. When enabled, t mon will generate alerts for a boolean exceptions that occurred in the previous interval but have since cleared. And this addresses a common operational gap for short lived conditions such as transient depth or rate breaches, that have resolved on their own and do not need further action by technical teams. The next one again is a customer, requested enhancement for queue utilization visibility, wherein we have added a new column that displays queue depth utilization as a percentage of the maximum depth. This gives immediate context beyond absolute depth values and makes it easier to identify queues that are trending towards capacity limits, especially in environments where queue definitions vary widely. Last one, I think Sentil already talked about it. So MQ statistic record types, queue manager statistics, page set queue, and channel statistics have been added for team on stream support, and customers can now consume a broader set of m q operational metrics in near real time for support, supporting advanced analytics. For what's coming in the next half of the year, firstly, we have independent accounting time for SMF one one six. Currently, both SMF one one five starts and SMF one one six accounting are controlled by a start time attribute. And IBM m q four z o s nine dot two, introduce accounting time queue manager attribute, allowing these intervals to be set independently. And we're going to support this. This is important because SMF one one six is significantly, more volume in this data, and customers will now be able to collect stats more frequently without the unnecessary accounting overhead for long standing applications. We're adding new data definition record for Q data, which is a new subtype two sixteen for SMF one one five introduced in IBM version 9.3. And this will have detailed queue level performance data for most recent SMF interval. We'll expand the streaming support to application queue stats And last but not the least, toleration support for IBM, MQ version 10, inclusive of new attributes as they are, becoming available. That would be it for MQ, and I would invite Bob to talk about d v two. Thank you. Hi, everybody. My name is Bob Hamilton. I'm a principal software engineer on the t monforty v two team. We are introducing a new version of six two, for team on for d b two. I'm gonna quickly go over some of the highlights. We did have some, major infrastructure changes that improved performance. We increase our use of the ZIP. We use utilize 64 bits support and, shared storage. And we also, provide support for streaming. To go through the screens, we now provide, smart logging user defined collection profiles to allow filtering of d b two threads. This helps limit the volume of, thread data collected by LFS. It's very similar to SQL analyzer filtering. The filtering will include character ID type fields like, con ID, core ID, auth ID, and then time oriented, fields on the right, lapsed time, CPU time. We also support, the the DBT East, fast index traversal, added the logging and display of IPKIDS, three eighty nine and four seventy seven, with that field support for IT one twenty five. Fast index traversal using, FTB is a d b two process that improves the performance of random index access. D b two provides FTP support for eligible indexes that exceed, the defined levels, and we provide, access to that new information. For our SQL, statement incompatible changes, we added the logging and display of DB2 FKID three seventy six. This helps, user identify, sequence statements with incompatible changes when switching to a new application or altering SQL. We also flag, log packages with incompatible changes and have added a status flag to our package screen. We added the CPU percent column to the end of our thread summary displays, both current and collected. The new column displays as a colored graph and is movable and can be filtered and sorted by the user with a GRF profile. The colorization thresholds of yellow and red can also be customized. With mainframe organizations, sustaining data compromises, we added support, for DORA compliance. These are regulations, specifically for, financial institutions. And we added, two new d b two utility of kits, 02/2120, to support the DORA data compliance. And lastly, these are, some upcoming, changes. The first one and I've got a a screenshot, to to look at. We'll add, ex exception triggering for d b two IRM messages. We already have d b two, messages logging to, our DW records and LFS. But the new functionality allows you to actually set, profiles, exception profiles for selected d b two messages. And you can trigger exception events and perform available actions. We're also going to provide improvements for EDM pools to include, ex we're gonna externalize new IBM statistics that have been made available to help, tune EDM pools, provide a way to show maximum EDM pool usage during a period of time, provide additional drill downs from EDM pools to other related displays, include additional EDM pool data fields to our existing screens and and to our LFS records. We'll display historical health data. Logging of DB2 health data was introduced with, version 6.1, and we'll include summarized spread data in version six two. The d b two health summary display will be expanded to provide the same colorized health score visualization available for current data but over a user selected period of time. This will provide a visual perspective to our d v two health data, using color graphs so users can quickly and easily see health changes to their d v two subsystems over time. And that's all I got. Thanks. Thanks, Bob. I'd also like to thank all the other speakers who stepped up. We are going to move into a q and a session, in a second or two. If you do have any questions, please enter them into the q and a, and the speakers will be available to answer those directly and dive into more detail. Before we go into the Q and A, just want to give a little bit of an advertising plug for the community forum. This is something that was set up recently, just in January. We're still getting up and running, but it's a place for you to go to and register your interest in Timon. In the forum, you'll get, updates on what's happening on the product. You'll be able to ask questions, join in discussions, see any information that we're posting, and basically connect with other people who are TmOn users within the community. So definitely suggest that you go there and, register your interest and check-in regularly. Once you've registered, you will get proactive notifications of any updates that happen in there. Maybe a little bit tricky to find, but if you go into any Rocket software web page, scroll right down to the bottom, you will see a link for community. So just click on that. And once you register and go in, go to the team on forum, which is under mainframe performance, and then join in the discussion. One other thing before the the q and a session is I mentioned we do have the survey. It is a very short four question survey just to get your feedback and also to get your input on what you'd maybe like to see coming up in the future for any webinars which we plan to do once or twice, before the end of the year. So definitely please hang about for the survey, run through that quickly, and, let us know your thoughts on this and future webinars. So with that, I'm not seeing any Q and A being typed in there. But if, you have anything, please put it in there just now and, let us know your thoughts exactly on what you you want to understand more about on the, product itself. So I'm just trying to get the survey up so that you can answer any questions in there. So hopefully you should be able to see that now. But again, if you do have any questions, now is your opportunity to interact with the developers themselves for the individual team on products and get that feedback from the experts. So, just having a look. Anyone have anything? One comment I did add to the chat was, there was mention of Rocketiva. If that's a product you haven't heard of before, it is newly introduced, in Q1 this year. We have a bit more information on our website about it, so you can certainly go and have a look there. It has been integrated. It's AI capability being integrated into team on and will eventually be integrated into more of our, Rocket product. So, please have a look at that for any information. So, just checking again, see if any questions are coming in. This is your opportunity, as I say, to interact with engineering team. If you've got any questions, concerns about current or future direction in the product, please type them in now, and we'd be more than happy to provide answers. Okay. So not seeing anything coming in. Someone must have a question on something I would have thought. Everyone very happy, with team on performance, the direction it's going. Is anyone considering using the HealthAI or the team on stream capability? Wanted to understand that a little bit more. Although this question is in the survey, do you have any preference for what you'd like to see in future webinars? You can also add that into the q and a in the chat. Particularly if you put something in the q and a that you'd like to see in the future, there's an opportunity for others to vote on that so we could see which areas are of the most interest to you. So I'll give it another couple of minutes to see if anyone just finishing off the survey, wants to put something in. So there is first question, excellent. Is Health AI included with base base products? With that, I'll I'll pull in Reid Gerson, who's our product manager. He should be able to provide you, an answer to that question. So, Reid, if you could join us on stage to to help answer Paul's question. And let me see. Just move Reid on stage. Hopefully, he'll be with us in a second. There we go. I didn't see the the steps to get onto the stage. So no. The, Timon Health AI along with Timon Stream is now included into a a new product called TimonOne Advantage. So TeamonOne Advantage has these new value add AI and data streaming products that are very easy to add to the individual monitors. But we also have launched a new suite of tMon. It's called tMon one Enterprise that has, tMon for CoX, KIX, DB2, MQ, TCPIP, and also includes this new tMon one advantage as well in a very, efficient way. But that all said, if, you are very interested in HealthAI, you can also have the ability to join our early adopter program. And so where we would offer you a complimentary license as long as you're part of, the team. So there's a great offer for anyone interested in Healthy Eye. Just reach out to us, and, we will talk to you about getting onto that early adopter program. Great opportunity to get involved, see how health AI and also team on stream works, and get that Adly in in detailed interaction with the development team and product management. So, any other questions? Everyone must be incredibly happy with team on and the monitors and how it all works. Okay. So with no more questions coming in, I'll open up to the speakers. I don't know if anyone would like to just jump on stage and provide a last comment. You know, not a problem if you you don't have that, desire to to jump back on again. But, I want to make sure everyone's got the opportunity to provide last thoughts and ideas about t mon, what's being worked on, and where we're going with the product. So as mentioned, you know, there's a number of new things being worked on. We should see those starting to appear and, we try to have quarterly releases. As I said, twenty six zero one was what came out in Q1, got twenty six zero two, we hope to get out during Q2 and so on through the year. We do plan on having another webinar, which dives into the details of the the new releases and any other technology that we're working on. That will be later on in the year. If you go into the forum, you should be able to see, notice of that getting posted once we schedule the the new webinar. So that'll be one of the first places to look and see what is