Automation scripts in REXX have been the standard on mainframes since the late 80s
NetView supports pipes for automation, there are many special pipe stages for entering commands, parsing and editing output, single and multiple lines (MLWTO).
Automation Policy can replace automation rules that trap messages and automation scripts for processing them.
Automation Policy not only describes the resources but also their dependencies, preferred systems, availability goals and whether they are a member of an application group that can represent a business application. The Tivoli System Automation family is policy-based.
Getting to the message you want to automate is also important. Automation can trap not only syslog messages, but also internal IMS messages, messages in joblogs, hardware events, and UNIX System Services messages.
Also important is integration, Automation uses and provides many interfaces from the subsystem interface (SSI) to the NetView program to program interface (PPI), EIF for events, SNMP traps, SOAP, and webserver with REST-based interfaces coming.