It is always good when issues are notified prior, to take precautionary steps. There are cases like technical issues where a ticket needs to be created immediately if something goes wrong and we cannot have waiting time to raise the ticket manually. At times, we need error logs to be retrieved automatically for trouble shooting.
IT environments are usually affected by routine maintenance activities on workstations and servers: it might happen due to a security patch to be installed, an environment to be upgraded, a middleware to be enhanced, etcetera.
IBM Workload Scheduler for z/OS V9.1 will go out of support on April 30, 2019.
More details are available here.
In the recent Dynamic Workload Console v9.4 FP2 release, a new powerful feature has been added: the possibility to handle the interaction with your z/OS workload through REST APIs!
Many times, our customers ask us how to call the Workload Automation functionality from their external programs.
Starting from version 9.3 FP2, Workload Automation provides a new set of REST APIs that give you programmatic access to Workload Automation services (we have already discussed this topic in a previous blog post: Driving Workload Scheduler with REST APIs is super simple with Swagger UI!).
Explore how in HCL we embraced Design Thinking to design a unique product experience for P&P products, always working with Customers and for Customers, and get some real-case examples on how we adopt it.
Starting from version 9.3 FP2, Workload Scheduler provides a set of fully functional APIs that are implemented based on Representational State Transfer (REST) services. The REST APIs are based on the same APIs used by the product user interface and provide full access to all the Workload Scheduler features, which is great!
A step by step guide to deploy your workflows with the Workload Automation plugin for IBM UrbanCode Deploy on z/OS Engines
In my previous article I provided a simple guide to implement the deployment of Workload Automation objects using Workload Automation plugin for IBM UrbanCode Deploy.
Attached to this article I provide a guide containing all the steps to implement a similar process for deployment of Workload Automation objects of z/OS Engines.
A step by step guide to deploy your workflows with the Workload Automation plugin for IBM UrbanCode Deploy on distributed Engines
As presented in the article “DevOps – Fast lifecycle management of workflow definitions” Workload Automation users can now use the Workload Automation plugin for IBM UrbanCode Deploy to automatically define workload automation objects on target environments.
This is the second part of the blog aimed at describing how the functionalities of the Dynamic Workload Console can improve your life also in Workload Scheduler for z/OS.