 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!
0 Comments
 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.
 If you want to avoid a potential business disruption in your Workload Automation environment, you should leverage the Master/Backup Master configuration. But, what happens if the RDBMS connected to Workload Automation crashes?
In this article, we will describe how to manage both Workload Automation components and DB2 HADR to allow business continuity during a disaster event.  What can be better than working while having fun? What’s more exciting than learning and experimenting creatively without limits?
Playing outside our primary domain, creates multiple possibilities that we couldn’t even imagine and opens the way to innovation.  IBM i workload has traditionally been handled by scheduling tools or solutions focusing on IBM i. What happens when your environment becomes complex and you need to integrate IBM i workload with the rest of the enterprise process flow?
Workload Automation provides you not only with scheduling capabilities but also with an advanced workload automation solution to manage cross-platform and cross-application workloads across heterogeneous environments, including IBM i.  When I joined the Workload Automation team, I began as a tester but soon after I also became the owner of the build automation process. How do you think we automate the thousands of builds required to produce every release of Workload Automation? With Workload Automation, of course!
 Quick one-off changes: Edit a job instance in the plan - If you look at the typical time line of a job, you've got a modelling phase where you create your job definition in the database, the submission of the job into the current plan, and then according to the schedule, the job execution until the job completes and reports its status.
|
RSS Feed