zAutomation - Choices, Choices
MacH 100000KQU0 Visits (5803)
Automation is used to handle activities that do not require expert judgment or analysis – DUHH !!! So where and how do we automate on z/OS ? There are a couple of guidelines – automate as close to the source/destination as possible, automate at the appropriate scope (sub-system, system, sysplex, enterprise), and integrate automation – sub-system automation feeds/supports system/sysplex automation, system/sysplex automation feeds supports sysplex/enterprise automation. In addition there are application centric and scheduling management needs where automation can help.
Sub-system specific monitoring and automation – based on monitored values or states (and changes in those) – the OMEGAMON suite - can identify states changes or thresholds or simple patterns of these that are of interest. If there is a well-known, “do it every time” response, you can “Take Action”. For creating situations and Taking Action see TEP User’s Guide – Situations for event monitoring – Overview http
For basic automation across a system or a sysplex NetView for s/OZ provides a very rich set of automation capabilities including a set of system and network management capabilities that can be leveraged as part of automation. The NetView automation table can process messages, EIF events, SNMP traps, etc. It can modify messages and can maintain state for more complex automation. For more information please see Introducing NetView Automation - http
For a more structured automation capability System Automation for z/OS provides policy based automation. This provides for the automation of complex responses to things like planned and unplanned outages where time is critical and manual processes are too slow and error prone. The policies for SA can cover a wide range of complexity in both the “trigger” and the “response”. For insight into policies try Users Guide – “Introduction and Concepts” http
Managing entire applications across distributed and host systems can be automated with the feeds and capabilities above and distributed equivalents using System Automation Application Manager. It provides a single point for control for managing/automating an application. For a better understanding of the range of the capabilities of this solution go to Product Overview - http
Another type of automation is scheduling. Very simple scheduling can be provided by NetView and at a higher level, SA. However for a cross system enterprise scheduling capability that is easy to use and maintain, Tivoli Workload Scheduler for z/OS is the product to use. It works with Tivoli Workload Scheduler to provide a combined host/distributed scheduling solution to all of your enterprise workload scheduling needs. For an overview of how this works take a look at http
There is a rich set of automation capabilities and solutions available for automation on the host. You can automate as close to the source/destination as possible, automate at the appropriate scope (sub-system, system, sysplex, enterprise), and you can integrate automation up through an enterprise level. In addition you can do automated application centric and scheduling management. Choices, choices.