Proof of Concept (POC)
Get Started with a No-Risk Proof of Concept
Curious how much your organization could save with smarter mainframe optimization? Our TurboTune® and TurboTuneSQL® Proof of Concept (PoC) is designed to deliver fast, measurable results—without disrupting your production environment.
The PoC process is designed to be light-touch, low-risk, and resource-efficient for the client. Critical Path SOftware handles all analysis and recommendation preparation, requiring only minimal execution support from the client team.
What You Can Expect:
Fast Setup – Most clients complete data collection in just a few hours.
Non-Invasive Process – We provide all scripts and support. No code changes required.
DEV-Only Testing – All activity is performed in your development environment to ensure zero risk.
Real Results – See measurable CPU, I/O, and performance improvements within weeks
Basic Requirements for PoC Setup:
Environment Access
- Access to the client’s development (DEV) LPAR whee data collection and performance validation will occur.
- No production changes are necessary during the PoC phase.
Data Collection:
- LISTCAT Metadata Collection (for VSAM datasets):
- Utilize CPS-provided JCL scripts.
- Non-invasive scripts collect dataset structure details for analysis.
- Db2 Cache Data Collection (for SQL workload analysis):
- Execute CPS-provided Db2 instrumentation utilities (REXX/INST).
- Capture dynamic SQL access patterns and high-consumption queries.
Upload Collected Data:
- Secure upload links will be provided for transfer.
Enhancement Implementation:
- VSAM Dataset Enhancements:
- Define improved VSAM datasets using provided CPS JCL, or create manually if preferred.
- Conduct performance testing using standard batch utilities to validate improvements in CPU and I/O efficiency.
- Db2 Index Optimization:
- Create or drop indexes based on CPS recommendations.
- Execute standard Db2 performance tests (DBA-led) to validate improvements in CPU and I/O efficiency.
Scope Control:
- All PoC activities are initially performed within the DEV environment to ensure complete isolation from production operations.
- Minimal client-side resource engagement is required beyond execution and validation activities.