HOW TURBOTUNE WORKS
Mainframe performance issues?
Increasing transaction times?
Increasing MLC costs?
These issues are often caused by file settings and parameters utilized. Improving the file settings, adjusting parameters and ensuring files are working properly together will drastically improve performance and reduce costs in your mainframe environment.
TurboTune operates at the file level. The underlying premise of the TurboTune process is file behavior. This is a primary factor in system resource utilization and performance. If file attributes are altered, based on a “best practices” methodology, system utilization will be reduced and performance will improve. The incremental contribution of performance gain for each file, when viewed cumulatively, produces significant results for a mainframe workload. Reductions in resource demand and increase in performance is highly noticeable due to the scale of the improvements. Reductions in resource demand (5% – 30% and possibly higher) leads to reductions in MIPS, MSUs, CPU, I/O and EXCP activity. This translates into a reduced need for engines, footprint and DASD space/volumes. Any increase in performance will lead to improved online response times, shortened batch run times, and increased end user productivity. Within a relatively short period of time TurboTune can outline solutions to reduce your cost of operation upwards of 30% annually, every year moving forward.
Critical Path Software will identify the root issues, improve buffering, reduce contention between files (in the LSR buffer pools and/or in batch JCL) and improve a variety of additional conditions including program code. It all begins with our NO-COST MAINFRAME ASSESSMENT.
Our flagship software, TurboTune, is the only predictive monitor in the mainframe space. All mainframe monitors can identify issues and point to the current location of the issue. TurboTune is the only software running completely outside of your mainframe environment eliminating risk to your system.
Identify the problem
Offer you a solution to the problem
Project what the solution will achieve in terms of cost and performance.
Project how much CPU can be saved
Project many MIPS can be saved
Project how many MSUs can be saved
Project how much I/O can be saved
Project how many EXCPs can be saved
Project how much DASD can be saved
Project how much Response Times will be reduced
Allowing the client to calculate the MLC savings as a result
NO PROGRAM LOGIC IS EVER CHANGED OR ADJUSTED IN ANY WAY BY TURBOTUNE.
THERE ARE ZERO SECURITY IMPLICATIONS FROM USING TURBOTUNE.
THERE IS NEVER SOFTWARE INSTALLED ON THE CLIENT’S MAINFRAME.
ONLY IBM UTILITIES ARE USED DURING OUR PROCESS.