Wednesday, August 19, 2015

A new name for Tivoli Workload Scheduler

In June we had released the new 9.3 version. The the new release, in addition to the new great features like the what-if, is also changing the name of the product, aligning the name of the product to IBM organization and strategy.

Starting with 9.3, IBM Tivoli Workload Scheduler is now just IBM Workload Scheduler


Actually there are more names to identify the product, based on the platform or the licencing, let's see all of them.

On-Premise version (the product you install on your machines) use these names:

IBM ServiceEngage / IBM MarketPlace (Cloud Software as a Service offering):

BlueMix (Cloud Platform as a Service offering):
  • Workload Scheduler for IBM Cloud, customers can easily use the service on the cloud to schedule their application running on IBM Cloud (a.k.a. Bluemix) or other clouds, control Workload Scheduler via APIs and optionally install on-premise agents to implement hybrid workflows. The price is based on the jobs actually run.

Since 9.3 Tivoli Workload Scheduler for Application does not exist anymore and all it's functionality are now included directly in all the above offerings.

Informally we will probably continue to call the product TWS for many years, as many are still using Maestro and OPC, but for the purpose of this blog I will use IBM Workload Scheduler (or just IWS) when I'll talk generically about the product and not about a specific offering.

If you like this article and you find it useful, please share it on social media so other people may take advantage of it.


  1. What is the reason dropping Tivoli name?

    1. This was an IBM marketing decision to stop using the Tivoli brand and focus on the IBM brand and product names, not just for TWS but for all products. It started few years ago and has been applied to new versions of products.

  2. I wanted to know if the SaaS offering includes workload automation for z/OS. I'm currently seeing agents for Windows, UNIX/Linux and IBM I (AS400?) systems? But nothing for z/OS. Would it be safe to say that I have to convert z/OS jobs to a distributed platform, then I could incorporate IWS for Cloud?

    1. Currently the SaaS offering is not supporting scheduling on z/OS. Adding the z/OS agent to the SaaS offering is one of the items in discussion for the future roadmap, I suggest to contact the offering managers (Flora Tramontano and Alexandra Thurel) or open an RFE if you are interested in this solution.