Whitepaper

Cost Saving with Quality Assurance – Customer Report

With the help of SmartJCL, production planning came to the conclusion that nothing stood in the way of a complete test of the application package. SmartJCL had caught errors in advance, preventing additional costs.

Situation

Recently a HORIZONT customer required a quality assurance (QA) system check of all processes of a large new application package before going productive.

This meant:

  • Completely replicating the application (including all interfaces) in the QA system.

  • Testing the modified processes over eleven production days in the QA system. To be able to recognize and resolve possible issues before the trial run, a JCL check was performed for the entire time frame.

JCL Check

The test focused on running a check of the application programs. This meant that production control had to make available all the elements required for running the application programs properly. “Unnecessary” issues such as JCL errors, checking whether programs exist, files and cassettes, resolution of scheduling variables and so on had to be eliminated in advance:

The customer uses the scheduling system “TWS for z/OS” (OPC) to run more than 65,000 z/OS jobs and 15,000 decentralized processes each day. HORIZONT SmartJCL was used to check the JCL. SmartJCL’s integrated simulation system made it possible to completely simulate the eleven production days required and to identify all possible errors in advance (“DATA SET NOT FOUND”, “REQUESTED MODULE NOT FOUND”, “UNDEFINED VARIABLE XYZ LINE 00008 OF ORIG JCL”)

A total of 453,406 jobs containing approx. 3 million steps were checked in approx. 6 hours.

Complete Data Integration in the QA System

The QA system had to be populated with the most current data possible – and of course with all the required data. To do this, the productive system of approx. 22 million files was mirrored in the QA system at a predetermined point in time. But the archived files and the files on cassette were still missing.

This is where the SmartJCL catalog check feature was able to help out. This SmartJCL feature simulates data flow across multiple jobs and reports data processing errors such as whether a file is missing or a file already exists. Optionally, this feature can also output a list of input files that are on cassette (specific VOLSER). The customer used this list to generate copy and recall jobs for integrating cassettes and their attached tape robots into the QA system.

SmartJCL checked the 450,000 jobs in the correct job run sequence and simulated the data processing of all 22 million files. Approx. 28,000 missing files were identified, primarily archived files on cassette.

Result

With the help of Smart JCL, production planning came to the conclusion that nothing stood in the way of a complete test of the application package. SmartJCL had caught errors in advance, preventing additional costs.

Production planning has now started using the SmartJCL catalog check feature for other purposes, for example, checking an entire production month of approx. 870,000 jobs in advance.

Further Resources

Blog Article

The Road to Enterprise Orchestration

Enterprise IT has never been more complex, and automation, in particular, continues to evolve rapidly as we head toward the age of agentic AI. An effective organization must coordinate workloads across on-premises infrastructure, multiple cloud providers, SaaS applications, Kubernetes clusters, APIs, and AI-powered services. In today’s business climate, IT processes can no longer run optimally on a single platform; they must span the entire technology ecosystem. Traditional job scheduling, therefore, is no longer enough in this environment. Instead, IT teams need to look towards a future of Enterprise Orchestration. This new approach coordinates entire business processes across the digital enterprise instead of automating only single tasks. In this article, we explore the evolution of enterprise automation and the road to enterprise orchestration.
Blog Article

DevOps Workflow Automation Explained in 2026

What happens at your company when a deployment fails at 6 a.m., and the engineer who owns that pipeline is asleep? For most teams, the honest answer involves a Slack alert, a scramble, and a manual fix. DevOps workflow automation is the practice of removing that manual dependency by letting scheduled and event-driven triggers handle builds, tests, deployments, and recovery on their own. Below, we break down what it actually involves, why it matters more in 2026 than it did even two years ago, the tools teams use to implement it, and how to roll it out without breaking what already works.
Blog Article

5 Best Job Scheduling Software & Tools for IT Teams in 2026

It’s 6 a.m and the finance team is waiting on an overnight batch job that didn’t deliver at 2 a.m. The problem is nobody gets an alert until the report doesn’t show up. That single missed dependency can delay payroll, stall a data pipeline, or disrupt an SLA a regulator cares about. This is the daily reality for IT teams running dozens or hundreds of interdependent jobs across mainframes, cloud platforms, and everything in between. Job scheduling software solves this by automatically triggering, sequencing, and monitoring tasks across your IT environment so you are not relying on cron jobs, spreadsheets, or a handful of engineers who know where all the bodies are buried. Below, we compare the five job scheduling and workload automation platforms enterprise IT teams evaluate most often in 2026, covering features, pricing, and exactly who each tool is built for.