 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.
0 Comments
Elevate the value of your mainframe investments: say hello to HCL Workload Automation for Z12/9/2019  “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.
 There are fundamentally 3 ways to define Standard SAP Batch Jobs in IWS :
 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:
 Nowadays, industries move towards microservice and cloud native architectures that makes use of containers to scale and deploy applications. But containers have its own challenges and adds complexity to the infrastructure to maintain especially in large dynamic environments (if you are not familiar with containers and Kubernetes don’t worry: catch up with our latest post, Containers and Workload Automation 101).
 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. All the questions you never dared ask about containers, Docker and Kubernetes  You have heard a lot about containers in the last years, but you still do not know how you can leverage them with Workload Automation? This is the right place to start then.
We collected the most frequent questions our users do when we talk about containers.  A new easy way to Create, Modify, Replace and Backup Variable Tables
The Workload Automation Programming Language (WAPL) interface allows to easily manage Variable Tables through batch jobs. In fact, it supplies a Batch Loader-like processor through which it is possible to CREATE and MANIPULATE variable tables inside IBM Workload Scheduler Database.  Drives application modernization with container-based deployments and support for batch resources and data analytics
IBM Z Workload Scheduler is the IBM Z offering that allow you to manage and automate batch execution across your enterprise, including applications running on mainframe, distributed platforms as well as on cloud and in containers. Dynamic Workload Console is a user-friendly Web UI available with the product (strongly improved in v 9.5), that provides end-to-end visibility and control on the batch plan and execution. Embedded predictive scheduling and what-if simulation are key feature of the product to keep under control SLA deadlines in despite of un-predictable workload and events. |
Archives
December 2019
Categories
All
|
RSS Feed