How to orchestrate dynamic container instantiation and legacy applications with HCL Workload Automation
This article describes possible scenarios where HCL Workload Automation enables dynamic services creation. The need is to enable the prompt and dynamic provisioning of a service, triggered by external events such as: a new user subscribes to the service, a user logs in to the service, a user logs out of the service, a user signs off from the service.
Register for the Dynamic Workload Console Overview for z/OS Users webinar and discover high-level scenarios that are possible with the console, and see how an organization and z/OS users can benefit from its main features.
Strategic key performance indicators confirm greater efficiency and improved performance: VMWare-Linux case study
A year ago, we published Workload Scheduler V22.214.171.124 Performance Report to document how Workload Automation Performance Team have a constant focus on performance, scalability and reliability of the product, even if the systematic introduction of new product functional capabilities, release after release, makes this sustaining performance levels a constant challenge. The results published on that Performance Report were related to a product installation based on IBM Power7 + AIX 7.1 infrastructure.
The HCL business philosophy is based on a customer-centric approach. Thanks to our Client Advocacy Program, customers can have direct point of contact for Workload Automation products, enabling them to create a strategic relationship with our technical, management, and executive leaders.
When IT customers deal with scheduling on mainframe, often it can happen that their workload runs in more than one z/OS, sometimes with no interactions among these environments for many reasons. Anyway, in many cases there is the need of conditioning the start of a z/OS batch procedure if and only if another job or chain completed successfully in a totally different z/OS system.
The Agent for z/OS represents a lightweight solution to schedule jobs and monitor workload in the distributed Environment with z/OS system. You can use the agent for z/OS to schedule work from HCL Workload Automation on the JES2 or JES3 subsystem of z/OS. Register for the Workload Scheduler Distributed Agent for z/OS webinar to learn more!
In my previous post on innovation in workload automation, I talked about the challenges of job definitions and how end-to-end batch processing has helped over the last 50 years. IBM Workload Scheduler (IWS) can automate batch processing independent of the target platform to monitor and control workflow throughout the enterprise IT infrastructure. In this post, I want to continue talking about the evolution of IBM Workload Scheduler and how new innovations have helped with the challenges of job definition.
IBM Workload Scheduler V9.2 Fix Pack 3 was announced on June 19, 2018. Check out its new features, capabilities, and learn about the power of IBM workload scheduler V9.2 Fix Pack 3.
Ahead with innovation! I think workload automation is probably one of the biggest challenges we must engage if we want to move with the times in information technology. I strongly believe we are in front of a major innovation in our IBM Workload Automation solutions developed by our partner HCL.
A Customers Interaction Process to Influence and Cooperate with
Workload Automation Development Team
IBM + HCL WA Transparent Development Program is a solid process that for a number of years we have been proposing to customers during the development cycles to deliver new releases and various enhancements related to Workload Automation. This program is an agile way for customers to possibly influence and interact with the development process of new functionalities in the Workload Automation. Transparent Development is a concrete opportunity to share your priorities, feedback, requirements and strategic objectives, while a feature is being developed.