Integrate mainframe batch processing into enterprise workflows
Reduce mainframe operating costs by moving scheduling to Tidal
Apply advanced scheduling functionality to z/OS jobs
Formerly known as IBM Workload Scheduler for z/OS, IBM Z Workload Scheduler offers automation features to help simplify tasks for schedulers and system administrators when compared to your current plan. It includes ready-to-use packages like IBM Workload Automation Console and IBM Z Workload Automation Agent. It also:
Managing z/OS mainframe processes is a business-critical effort. As organizations incorporate a growing number of applications on a range of distributed devices, it’s important to manage them centrally and avoid islands of automation. When you offload scheduling from the mainframe, you can reduce your mainframe operating costs.
With Tidal’s z/OS integration, mainframe job scheduling in JES can be orchestrated within overall business processes for end-to-end management and automation. Once integrated, use the Tidal platform to:
Tidal, the IBM Z/OS Job Scheduler, manages job scheduling tasks within the z/OS environment with a wealth of customizations and integrations to enhance your capabilities.
WIth its extensive capabilities and customization, Tidal empowers organizations to streamline operations, ensure reliable job execution, and maximize productivity in the z/OS environment.
OUR CORE PLATFORM
A unified platform for centralized management and control of job scheduling across business, operations and IT processes. Tidal Automation Platform >
Even when you have integrated with Tidal, your teams will still be able to use the Dynamic Workload Console to monitor job submission, job runs, job tracking, operation status, started tasks, and more within IBM Z/OS Job Scheduler. The Tidal dashboard will allow you to do all these things for all workloads running across your enterprise.
While using Tidal to manage your workload automation will affect changes in IBM Workload Manager (WLM), the Tidal interface does not use JCL. If your teams wish to use JCL and JCL variables to define execution or allocation parameters, manage data sets with DDNAME, or use JCL error handling protocols, they can still do so.
Tidal incorporates automatic recovery mechanisms to address job failures. When a job ends in error, Tidal identifies the issue by examining the job log, message log, and return codes. It uses identifier information, such as the job name and job card, to pinpoint the error's source. Tidal then attempts to recover by applying predefined actions or executing error-handling procedures specified in the job definitions. This automatic recovery feature minimizes manual intervention and optimizes job execution within the z/OS system.
Troubleshooting Tidal involves several steps. First, check the message log for any error codes or messages that may indicate the source of the problem. Use Tidal's domain manager and programming interface to identify and address issues related to job scheduling. If necessary, specify parameters and options using Tidal's z-centric capabilities to fine-tune its behavior. Additionally, refer to IBM's Authorized Program Analysis Reports (APARs) for fixes to software defects.