OC Systems

Home | Contact | Advanced Search 

Technology
RootCause for z/OS

What is RootCause for z/OS?
What is a Typical Engagement?
What can a subscriber get from RootCause for z/OS?
How can a consultant benefit from using RootCause for z/OS?
ROI
About Us
Become a Partner
Contact Us

What is RootCause for z/OS?

RootCause for z/OS is a monitoring tool for legacy applications. If you want to know what is happening in your legacy application, without changing the application source, we provide quality control support for legacy mainframe systems, through a combination of product and custom services provided by OC Systems. For example, we can help you capture internal legacy data before and after a planned maintenance cycle. In this example, you would run the before and after applications with RootCause for z/OS, plugging the same custom logger into both runs. Both runs would capture similar data. You would then compare the data from both runs. When satisfied that the maintenance cycle was good, you would run production, without RootCause for z/OS software. RootCause for z/OS is only needed in this instance for Quality Assurance.

Top

What is a Typical Engagement?

So you are probably asking yourself, how does this work? We make it simple for you.

Step # 1: Contact us and a senior technical staff member will be assigned to discuss your project with you

Step # 2: We'll outline a proof of concept, identifying data that is of interest to you, and OC Systems will write a plug-in for you to run on your application

Step # 3: Subscriptions start at $5K per year to include labor, support and software use

While each customer is different, we want to make the process useful to you. Managing and monitoring time and legacy environments can be complicated, so we do our best to give you the expertise that you need to get the most useful information back to your environment.

Top

What can subscribers get from RootCause for z/OS?

With plug-in support from RootCause for z/OS, legacy mainframe applications can be new assets instead of old burdens. For example, management may avoid extending a legacy application because of risk in changing old programs. The application can be extended by plug-ins, temporarily, without changing old programs. Plug-in extensions would make the application more useful. Plug-ins can be a new asset library for periodic temporary needs.

With legacy mainframe applications, many businesses preserve their legacy and adapt other technologies to work with it. With RootCause for z/OS, a preserved legacy application can give you new custom output without adapting other parts of your system. You can collect and monitor what you want to know, without changing the mainframe application source code. For example, a RootCause for z/OS plug-in can detect queued input which would surprise the legacy application. You don't need to analyze all places where data is sent to the legacy queue. You can analyze the data by plugging into the mainframe receiver. Your plug-in can analyze and log surprise data. Your plug-in can also adjust surprising data until your legacy maintenance processes it.

With mainframe legacy systems, maintaining integrity between applications is a continuing problem. RootCause for z/OS can save custom data streams for integrity tests. For example, RootCause for z/OS plug-ins can log what is processed from a queue, in the format of the queue send log. After application changes, you can compare send logs to processing logs, and confirm that what is now being sent is still being processed.

With application monitoring support from RootCause for z/OS, there is no need to rebuild stable legacy applications to monitor internal processing. There is also no need to rebuild them to see what else you might do with the data they already process. With RootCause for z/OS, you have an opportunity to monitor and observe IT dataflow. You make no application changes, so the application remains stable. You can see IT patterns, and you can be nimble with them. You can try experiments with the data you capture with plug-ins. For example, a RootCause for z/OS plug-in can log selected data in a format of your choice. You can then analyze the captured data with familiar tools and utilities. You can test a new use of old data as a plug-in. The new logic can later be inserted directly in the application. In this way, you can be nimble in the short term, before a long term official change is made.

Top

How can a consultant benefit from using RootCause for z/OS?

If you are a consultant – RootCause can help you in many ways. Learning our technology will not only give you a competitive advantage, but it will allow you to help your clients before and during an upgrade. Prior to an upgrade, the product's dynamic analysis complements your static analysis. Using plug-ins, you can watch a client's legacy application in motion, so we call these plug-ins "motion sensors". With a combination of motion sensors, you can:

confirm static analysis
detect extra cases
detect the absence of obsolete cases
detect performance paths
log data for proving correctness after you upgrade

Where do motion sensors come from? Most exist already in RootCause for z/OS, whose reusable motion sensors detect program flow and data change. OC Systems can write new motion sensors, and you can write custom sensors in the legacy language, which watch data relations and conditions.

During an upgrade, the client's legacy applications are a baseline for conversion. Experimenting inside baselines hasn't been common, because rebuilding a baseline while converting can be risky. Now you can experiment without changing your client's legacy source, with the technology plugging in temporary logic to run inside the baseline. You (or OC Systems) can write experiments and analysis you want, and RootCause for z/OS plugs what you want into the baseline for an experiment. The baseline remains in production, processing the client's business data, while you convert using what you learned inside the baseline.

Top

ROI

Working with OC Systems and learning to use RootCause for z/OS technology enables a subscriber to:

deep dive
reduce risk
reduce cost
increase quality

You will improve productivity and the value of your mainframe assets while reducing labor hours.

Using RootCause for z/OS technology as a consultant gives you both a competitive advantage and allows you to deliver faster, quality service within a reasonable budget.

Top

About OC Systems

OC Systems provides software instrumentation tools and consulting services that help organizations gain greater visibility into large, complex applications. Founded 1983, OCS is employee-owned, based in Fairfax, VA. We specialize in performance engineering, performance load testing, test automation, automated test execution and software audits – memory, tuning, diagnostics. We have a product line of other tools that include: Aprobe, RTI, and PowerAda, a leading compiler in the industry.

Top

Become a partner

If you are interested in becoming a technology partner, we would be interested in talking with you. Whether you become an expert with RootCause for z/OS technology or if you help contribute to the expansion of our sales channel, you will have a key role in the mainframe and legacy arena. Have a look at some of our other partners and contact us if you are interested in hearing more about our program.

Top

Contact Us

Give us a call or send us an email...

Contact us at 703-359-8160 or

System requirements
Contact us
RootCause for z/OS