1. Setting alerts or actions if an operation does not start or complete.
- Deadline and Action
If the operation does not complete within the deadline time an alert is issued and, optionally, an action taken.
- Not Started Alert
If, the day offset and time for the operation is passed an alert is issued and an action taken.
2. Filtering operations that are late.
From the SELECTING OPERATIONS (EQQSOPFP) panel, you can browse and modify the operations in the current plan that are late according to the following criteria:
- Their latest start time
- The day and time you specified in the Not Started Alert or Not Started Action field.
- Either their latest start time, or by the day and time that you specified in the Not Started Alert or Not Started Action field.
3. Optimizing the workload through a smooth submission of the operations
In the JTOPTS initialization statement, you can better balance the submission of operations by prioritizing the jobs that are urgent (with priority 9) or that belong to a critical path.
4. Integrating with IBM Common Data Provider for z Systems.
5. Specifying a return code for a completed operation in OPSTAT
The TSO command OPSTAT now supports the parameter COMPLCODE, to specify a return code for a completed operation.
6. NOPing operations after that time dependencies and special resources are resolved
In the JTOPTS statement, you can set the NOPWAIT parameter to specify that an operation that you are NOPing is actually NOPed after that time dependencies and special resources, if any, are resolved.
7. Deploying Dynamic Workload Console and IBM Z Workload Scheduler Agent with Docker containers.
Docker containers ensures standardization of your workload scheduling environment and provides an easy method to replicate environments quickly in development, build, test, and production environments, speeding up the time it takes to get from build to production significantly. Install your environment using Docker to improve scalability, portability, and efficiency
8. The Dynamic Workload Console has evolved
The Dynamic Workload Console has evolved with a new graphical layout, features, and improved functionality.
9. A brand new way to monitor your scheduling plan by using either a customized dashboard or the dashboard template provided
With the new infrastructure of the Dynamic Workload Console, the way you create the dashboard for your scheduling objects has completely changed and improved.
10. New reporting system
The reporting system is now organized in predefined reports and personalized reports. By using the predefined reports you can still perform the same actions as in the previous versions, but with an improved user experience that makes it easier and more intuitive.
With the Personalized Reports you can manage templates created with Business Intelligent Report Tool (BIRT) and use them to generate reports to retrieve data from the IBM Workload Scheduler database.
11. After migrating, old SSX writer queue is copied in the new SSX if the FMIDs are the same
When you specify BUILDSSX(REBUILD) in OPCOPTS to rebuild the SSX at a new level, the event-writer queue from the old SSX is copied to the new SSX, if the FMIDs are the same. In this way, all the events are kept.