In our previous blog Why you should manage cloud resources as an integral part of your business workflow, we described the challenge that customers face every day to reduce cloud costs while ensuring the right amount of resources to their business applications. We announced that a new solution pack is available on top of Workload Automation, provided by HCL Products and Platforms, including a set of new plug-ins to manage the provisioning and deprovisioning of virtual machines in the cloud, on as-needed basis. By orchestrating the application workflow and the workflow that manages the entire lifecycle of the virtual machines needed by the applications (including the actions: start, stop, snapshot, etc. …), Workload Automation can increase both business and infrastructure agility.
Looking at the last 2017 State of the Cloud Report from RightScale, two survey’ outcomes capture the reader’s attention:
The schema of the Workload Scheduler is only changed by the product's installation and update but sometimes can be happen that automatic scripts or manually changes are voluntarily or involuntarily applied to the database.
This situation could reduce the Workload Scheduler performances and data consistency if, for example, an index is dropped or a foreign key is removed. If you have installed the Workload Scheduler on a DB2 or Oracle RDBMS, you can easily check the status of your database schema.
In today’s fast-changing IT world, companies across all industries base their ability to be agile and efficient on a successful collaboration between their developers and their operational teams. The trend has gone by the name of DevOps that clearly highlights how the two departments need to engage in a constant dialog.
On the developers’ side, IT workers are getting more and more involved on all aspects of IT operational activities with a growing focus on automation.
With the Version 9.4 fix pack 1 of Workload Automation we introduced a new intuitive graphical view of the Dynamic Workload Console. These enhancements are intended to help customers navigate easily in the Workload Automation.
Through the plan view of job streams and dependencies you will easily detect issues and you will have an overall picture of the plan and how it’s structured. We also added graphical representation of the object to give a better user experience and improve the usability.
Problems in your Workload Automation environment? Get notified and solve it! Combine Event Rules and New Graphical Views
Workload Scheduler version 220.127.116.11 recently released a new version of the Graphical Views
to enhance the operator’s monitoring experience when using the Dynamic Workload Console.
In the monitoring area, existing features can be empowered with new functionalities provided by the web console: it's not just a matter of monitoring workloads. With a little tweaking, you can improve your daily activities also in terms of troubleshooting and recovery.
Among the latest enhancements of Workload Scheduler product (also known as TWS – Tivoli Workload Scheduler) there is the new role-based security model to grant and revoke accesses and permissions to Workload Scheduler users.
Available from both Command Line Interface (composer) and web interface (Dynamic Workload Console) the new security model introduces some new concepts that simplifies the usage of the Security File.
In this post we will see how define accesses from the web console.
You can upgrade the IBM Workload Scheduler for z/OS controller in an automatic way, with only few manual steps, by using the IWSZSELFUPGRADE job stream that is provided with the product.
For job types with advanced options you have the possibility to let variables and passwords be defined and resolved locally on the IBM Workload Scheduler for z/OS agents.
This is particularly useful in the case of passwords because you are not required to specify them in the job definition. The advantage is that, if the password has to change, you do not modify the job definition, but you change it with the param command locally on the agents (or on the pool agents) that run or may run the job. This feature is not restricted to Windows workstations alone. You can use it also on UNIX, as long as you apply it on job types with advanced options.
Currently Workload Automation customers are moving increasingly to dynamic agent scheduling managed by Dynamic Broker component (ITDWB enterprise application). Dynamic agent scheduling introduces additional processing to the traditional one.
There are multiple processing steps between job execute notification, via mailman server, to Broker component and the final job dispatch to the remote JobManager. All these steps correspond to an internal job status in the JOB_BROKER_JOBS table in the DWB schema that map to WAIT status in the plan (which could be check using conman or the Dynamic Console). The WAIT status means, as documented, that the job is waiting to fulfill its dependencies. In this blog, it is explained how to retrieve a meaningful detailed status of Jobs.