Workload Scheduler for z/OS SPE 18.104.22.168 (APAR PI79321) provides you with the DevOps support for deploying applications among different z/OS environments.
You can export and import applications so that they can be shared with other Workload Scheduler for z/OS environments.
To export an application from one environment to another, you can use either the ISPF panels or the Dynamic Workload Console V9.4, Fix Pack 1.
In addition to logging updates to the current plan and recording auditing information for the requested files, you can also choose to log updates to the databases and record information for the requested files. You activate this extended-auditing function by setting AMOUNT(EXTENDED) in the AUDIT initialization statement.
Are you curious about Workload Scheduler? Do you want to get to know it in an easy, immediate way? How about a detailed, comprehensive overview of its main features, both the latest ones and the ones which have decreed its success over the years?
A great way to get started and understand what the fuss is all about is our exhaustive channel on YouTube, which features over one hundred very popular videos, describing the most exciting new features and tips and tricks on how to use the product for best performance and results.
Once you have requested a Workload Automation Trial and completed the agent installation on a computer on the same network as your SAP system, you have to do few actions to enable the communication between the agent and your SAP system.
Here is a step by step guide to achieve this:
Did you know? The Workload Automation agent contains the R3Batch SAP certified module to connect to you SAP system. It communicates with your SAP system to start the jobs and return its status. You can orchestrate your R/3, process chains and infopackage jobs with Workload Automation.
Workload Scheduler 9.4 Fix Pack 1 was recently released, and among the numerous enhancements for the Dynamic Workload Console (DWC) - a web interface of the product and the main access point for the cloud solution to automate and orchestrate workloads through the cloud – the new Graphical Views are the most compelling with a new modern look!
Read more about the 9.4 Fix Pack 1 release!
Starting from the latest Workload Scheduler (TWS) version 9.4 fix pack 1, as we written in our previous post, you can deploy the dynamic agent using Docker. The product provides you a simple way to create, update and maintain your Docker image and container with Workload Automation (WA) Dynamic Agent.
Following the top five scenarios you can address using the new feature.
IBM and HCL just released new enhancements with Workload Scheduler (TWS) version 9.4 Fix Pack 1, that from one side push the product on the road of a transformation strategy for Cloud, Docker and DevOps, and on the other side address many “Requests for Enhancements” from existing customers.
These new features make TWS a complete product for both enterprise and business digital automation that is required from modern application development and deployment methodologies.
Workload Scheduler is a state-of-the-art production workload manager, designed to help customers meet their present and future data processing challenges. It enables systematic enterprise-wide workload processing for both calendar and event-based (real-time) workloads across applications and platforms.
Over the last year, the Workload Scheduler team put out a new release of the product, Version 22.214.171.124, which introduces several new features:
When a problem occurs in a critical business process, the main priority is to get it fixed ASAP to ensure business continuity. You want results, not excuses! The service desk operator must be alerted so that the problem can be resolved timely avoiding serious impact on the entire workload. This usually means dealing with disparate applications and systems running in heterogeneous environments.
Standard email notification could work, but what if you could expedite error detection and resolution of failures by automating the incident creation followed by the application of the right recovery action based on the error.