Worried about how to summarize the stats of your historical jobs? Want to know the hassle-free solution for it?
Then Let’s Get Started!
If you are looking for statistics to detect success, error rates; minimum, maximum, and average duration; late and long duration statistics, then your choice could be “Job Run Statistics (JRS) Report”.
When a customer is approaching for the first time to schedule workloads on iSeries environments, a set of questions are usually raised. This blog is a collection of these questions and related answers, on a WA 94FP3 base.
How much does it cost? This is the key question asked by a buyer when evaluating a software purchase.
The answer is not always easy because the cost of a software solution is not just the price to be paid but it’s something more complex: it’s TCO.
As you probably know, TCO stands for “Total Cost of Ownership” and it’s a high importance parameter to evaluate the Return on Investment (ROI) which definitively defines if the software solution is worth the expense.
During the years, many features have been developed involving more and more complex analysis and actions in the Current Plan modifications due to ad hoc requests.
At the same time customer’s daily workload increased in size and complexity, becoming more dependent on ad hoc actions (ETT processing, Automatic recovery actions etc.)
Storage consuming also increased, so that we delivered via SPE (930 and 950) the possibility to use a Data Space dedicated to MCP actions.
Williams - a Workload Automation Administrator
“As an Administrator, I need to check the available load of workstations and also how many jobs or job streams are running on a particular workstation, on a particular day or period of time”.
A common need, coming from customers of Workload Scheduler for z/OS, is the possibility to list operation’s Successors in the Database, as it happens in the Current Plan (after the operation is loaded in the plan). At moment, through ISPF Dialog, it is possible to access only to Predecessor list for operations in the Database.
Spartan was born as a race competition in the gritty green mountains of Vermont, for those with something more to prove.
But it’s more than a competition, it’s a Way of Life, inspired by Spartans: Gritty. Resilient. Passionate. Spartans aren’t soft. Spartans overcome obstacles.
It’s also a community, a training program, a timed obstacle race and many other events.
The four fundamental areas that security tests on Workload Automation cover include: OpenSSL, GSKit, WAS Security and cURL
OpenSSL (Open Secure Sockets Layer) Overview
OpenSSL is a popular Open Source implementation of the SSL/TLS protocols. The project is managed by a worldwide community of volunteers. The core library, written in the C programming language, implements basic cryptographic functions and provides various utility functions. Wrappers allowing the use of the OpenSSL library in a variety of computer languages are available. Versions are available for most UNIX and UNIX-like operating systems (including Solaris, Linux, macOS, QNX, and the various open-source BSD operating systems), OpenVMS and Microsoft Windows. IBM provides a port for the System i (OS/400).
Workload Automation (WA) 9.5 Server, Console, and Agent components are available as Docker images that can be deployed easier and faster.
You may ask yourself whether there is a way to take advantage of the benefits even though you are not yet planning to deploy to the latest version. Is there a way to do this? yes, there is. You can still enjoy the benefits of Docker with the previous WA versions, in this blog post we will show you how.
This article will explain how to remove old records (tuples) from Workload Automation Event Log table.
If you configured your Workload Automation batch scheduling environment with event-based scheduling, defining actions in response to events that occur in your environment, then it’s recommended to clean up your Event Log table on a timely basis depending on your log retention requirement.