Customization considerations

Tivoli Workload Scheduler for z/OS is designed as a general-purpose workload automation subsystem. As such, it might not meet all the requirements for your specific installation. IBM® allows installations to implement installation exits and provides many callable services that can be used to supplement Tivoli Workload Scheduler for z/OS processing.

Carefully examine any customization that your site has installed. Determine whether the function is now provided in the product or if you need to modify the logic based on changes made to Tivoli Workload Scheduler for z/OS.

When new functions are added to Tivoli Workload Scheduler for z/OS, installation exits and macros used within installation exits can change. New installation exits or macros might also be introduced in a Tivoli Workload Scheduler for z/OS release. If a release provides a new installation exit, determine if your installation needs to implement the exit. A release can change an existing exit by modifying:

• What the installation exit expects on entry
• Return codes Tivoli Workload Scheduler for z/OS expects when the exit returns control to Tivoli Workload Scheduler for z/OS
• The function that the installation exit performs
• The processing that is performed before or after the exit.