You can use the agent for z/OS - aka D-Driven - to schedule work using IBM Workload Scheduler. You install and configure the agent for z/OS in the z/OS system and this work as any other dynamic agent. As soon as it is configured, the agent automatically links with the dynamic domain manager component of IBM Workload Scheduler through the HTTP or HTTPS protocols. With the agent for z/OS you can define jobs and schedules on IBM Workload Scheduler and submit a subset of the jobs to a z/OS system and you run the planning tasks on IBM Workload Scheduler while the execution is demanded to the z/OS system.
“Mainframe essentially keeps the world running."
It may sound bold but it’s true. The quote above, which is from an IBM executive , Philip MacLochlainn, is indeed supported by stunning figures: “85% of all credit cards, 29 billion ATM transactions per year, 92 of the top 100 banks ... 12 billion passenger flights are booked” thanks to mainframe. And it makes no wonder to whom is familiar with mainframe’s history and the story of workload scheduling and management, which we contributed to write.
In the last few years there is a lot of focus around “Mainframe Modernization” … and there are multiple reasons for this focus and great benefit for the enterprises that will embrace this journey. In the journey to Cloud, the market is entering in a new chapter, while in the initial phase, that we call chapter 1, the focus and the plan was to migrate existing workload and application to Cloud, with a modernization of the IT and build new application as Cloud-ready, in the new chapter (Chapter 2) the focus on “migration “ was strongly reduced for multiple reasons.
Workload Automation and SAP: all you need to know about Dynamic SAP R/3 Jobs and Associated Return Codes
There are fundamentally 3 ways to define Standard SAP Batch Jobs in IWS :
IBM Z Workload Scheduler collects many information about its workload execution and data base definitions in different formats. You can obtain info from messages issued on SYSTEM and/or on IzWS product LOG, or you can obtain it from AUDIT function reports.
Starting from this info, an analysis can be done to better tuning workload, prevent problems and so on.
One of the top features of the IBM Workload Scheduler (aka TWS) is the What-If Analysis capability: an advanced simulation tool built to help IBM Workload Automation customers understand the possible impact of changes on their workload.
What-if Analysis is a predictive tool able to represent your workload using a Gantt View, to display scheduled activities faster and give you a visual representation of your workload that at a glance gives feedback about workload health.
Every day is a good day for enjoy a good coffee at the bar, before starting the morning work. But every IT administrator knows that a good day is a day where all that happens, it a predicted stuff. “If I have a plan, I can manage everything without pain” I say to myself.
When we started to have Workload Automation offered as a Service (Try it!), we have started to be customer of our product. And I was suffering of the same pains… What happens if I need to upgrade an agent? Can I deliver the build to the test before the start of the day? If I don’t my boss will blame me: the test team will declare to be late!
Have you ever dreamed of a real time, easy-to-use, global dashboard where you could easily understand in case of problems, what's going wrong in your environment and use the same dashboard to perform a fast response to those problems?
Well, now you have it!
Workload Automation – offered as both on-Cloud and on-premise solutions – is proud to announce the new Workload Dashboard 2.0!