“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.
Once you have requested a Workload Automation Trial and completed the agent installation on a computer on the same network as your SAP system, you have to do few actions to enable the communication between the agent and your SAP system.
Here is a step by step guide to achieve this:
Did you know? The Workload Automation agent contains the R3Batch SAP certified module to connect to you SAP system. It communicates with your SAP system to start the jobs and return its status. You can orchestrate your R/3, process chains and infopackage jobs with Workload Automation.
Starting from the latest Workload Scheduler (TWS) version 9.4 fix pack 1, as we written in our previous post, you can deploy the dynamic agent using Docker. The product provides you a simple way to create, update and maintain your Docker image and container with Workload Automation (WA) Dynamic Agent.
Following the top five scenarios you can address using the new feature.
IBM and HCL just released new enhancements with Workload Scheduler (TWS) version 9.4 Fix Pack 1, that from one side push the product on the road of a transformation strategy for Cloud, Docker and DevOps, and on the other side address many “Requests for Enhancements” from existing customers.
These new features make TWS a complete product for both enterprise and business digital automation that is required from modern application development and deployment methodologies.
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.
Do you dream of a simple way to schedule and monitor your java batches? Are you looking for a way to orchestrate composite workloads and handle the workflow and the exceptions easily?
If your answer is yes, take a closer look at the new IBM Workload Automation plug-in for JSR 352 Java Batch. Here’s a brief description of the JSR 352 protocol and its integration into IBM Workload Automation.