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.
Securing communications in the Workload Automation environment is an essential step to meet your company’s security requirements. Does Workload Automation use a secure communication mechanism? The answer is yes! All communication is implemented over SSL protocol TLSv1.2. Read this blog to find out how to implement security correctly in a v9.5 environment by customizing default certificates.
“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 :
Delegate administrative tasks to other users in your Workload Automation on Cloud subscription folder
LET’S INTRODUCE what’s new
Get familiar with the new concepts introduced by Workload Automation on Cloud that leverage the 9.5 Fix Pack 1 on-premise version, released in July:
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.
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.