IBM Tivoli Workload Scheduler for z/OS Best Practices: End-to-end and mainframe scheduling, 2nd Edition

Appendix A. Version 8.2 PTFs and a Version 8.3 preview 671

Workload Scheduler messages (AWS) to the server MLOG and to the

System Output Console (SYSLOG).

 End-to-end reduce network shutdown.

– APAR PK11811 improves the scheduling system by reducing the

“inactivity window” in the end-to-end environment.

 End-to-end server messages were not written to SYSLOG.

– APAR PK11314 End-to-end Server messages are not written to SYSLOG

to allow automatic detection of end-to-end server messages via system

automation tools.

 Tivoli Workload Scheduler for z/OS Workload Manager integration

requirement.

– APARs PK08998, PK08999, and PK09001 provide Tivoli Workload

Scheduler for z/OS Workload Manager integration based on scheduling

environments. This enables optimal use of available resources and to

ensure that you are getting the most from your existing resources and that

the Workload between resources is automatically balanced for optimal

throughput and performance.

Preview of Tivoli Workload Scheduler for z/OS V8.3

The following enhancements are planned for the next release of Tivoli Workload

Scheduler for z/OS Version 8.3, which is scheduled to be available in 4Q 2006.

 Enhance variables support in event-triggered jobs. This way there will be no

need to manually tailor event-triggered jobs.

 Increase capability to schedule unplanned workload, via Event Trigger

Tracking (ETT). This will provide additional flexibility during event-driven

planning.

 Improve special resources flexibility to simulate file dependencies. That way

there will be no need to manually change Special Resource availability status

in customer business process scenarios. This will reduce the Total Cost of

Ownership to implement common scenarios.

 Critical paths will be determined by Tivoli Workload Scheduler for z/OS to

user-defined critical jobs. Operations on critical path will be automatically

promoted (via operation internal priority and WLM high-performance service

classes), to reduce operator manual intervention.

 Introduce a delay between jobs to reduce Total Cost of Ownership in

implementing a solution to delay job submission respect to predecessor

completion.

672 IBM Tivoli Workload Scheduler for z/OS Best Practices

 Implement every option in application run cycle. This will help to reduce the

cost to create and maintain workflows, improve planning flexibility, and reduce

the cost to migrate from other scheduling products.

 Data storing capacity improvement will improve scalability for Restart and

Cleanup function in multiple environments.

 Enhanced end-to-end standard agent connected to master domain manager.

This will create centralized control of jobs running on standard agents.

 Integration with Tivoli Enterprise Portal. This will permit you to monitor Tivoli

Workload Scheduler for z/OS data through a common and consistent

interface.

 A new enhancement, the ability to simplify the pinpoint of loop conditions and

improve performance of loop detection. This will improve performance in

Tivoli Workload Scheduler for z/OS loop dependencies analysis and greatly

reduce Total Cost of Ownership for identifying the loop’s real cause.