Modernization Hub

Share Your Product Experience

Help the community by sharing your experience with mainframe products. Your insights help others make informed decisions.

Share Your Experience
Vendor
Categories
3
Recommended
Claim Your Listing
Verified Vendor Access
Request Access Now

Product Overview

Automation Control automated z/OS systems and System z processors using policy-based automation. It automated tasks such as system startup, shutdown, and resource management. Configuration files defined automation policies and system parameters.

The architecture likely included components for policy management, event monitoring, and action execution. It likely integrated with z/OS security features, such as RACF, for authentication and access control. While Automation Control did not expose standard APIs like REST or SOAP, it likely provided interfaces for interacting with z/OS system management facilities.

The access control model was likely based on z/OS security mechanisms, such as role-based access control (RBAC) or access control lists (ACLs). Audit logging capabilities were likely integrated with z/OS system logging facilities. The administrative interfaces likely included a command-line interface (CLI) and potentially a web-based console.

User management was likely handled through z/OS security administration tools, such as RACF or ACF2. Monitoring and logging capabilities were likely integrated with z/OS system monitoring tools. IBM Z System Automation is a replacement option.

Competing products include Broadcom Automation Suite for z/OS and BMC AMI Ops Automation. These alternatives offer similar automation capabilities for the z/OS environment.

Frequently Asked Questions

What is the primary function of Automation Control?

Automation Control provided policy-based automation for z/OS systems and System z processors. It allowed users to define policies that automated tasks such as system startup, shutdown, and resource management.

How were automation policies defined in Automation Control?

Automation Control used configuration files to define automation policies and system parameters. These files specified the actions to be taken in response to specific events or conditions.

How did Automation Control components communicate with each other?

Automation Control communicated between components using internal protocols specific to the z/OS environment. Details of these protocols are not publicly documented.

Related Products

More from IBM

Access 1

Not Supported
z/OS

Alternatives available

Access 1 was a system monitoring tool designed to provide a centralized view of system resources across multiple platforms, including z/OS. It collected data from...

View Details →

ACF/NCP

Not Supported
z/OSz/VMzVSE/VSEn

Alternatives available

ACF/NCP is a mainframe-based network operating system for communication controllers, initially developed in the 1970s. It supports protocols like SDLC, X.25, and SNA, enabling connectivity...

View Details →

ACF/SSP

Supported
z/OS

ACF/SSP is a suite of programs designed to support and manage ACF/NCP (Network Control Program) on z/OS systems. Key components include the NCPGEN utility for...

View Details →

ACO SolutionPac

Not Supported
z/OS

Alternatives available

ACO SolutionPac was an IBM solution for automating MVS operations on z/OS. It integrated with NetView to manage both system and network tasks. The core...

View Details →

Ada/370

Not Supported
z/OSz/VM

Alternatives available

Ada/370 was an IBM compiler for the Ada programming language, targeting z/OS and z/VM mainframe environments. It facilitated the development of robust and reliable applications....

View Details →

ADF II

Supported
z/OS

Alternatives available

ADF II was a mainframe-based 4GL application development system designed to create online applications for IMS and CICS environments. Its primary function was to accelerate...

View Details →

Similar Products

(E)JES

Active
z/OS

(E)JES is a z/OS tool designed to replace SDSF, offering enhanced job management capabilities. Key commands include `J` (Job Information), `ST` (Start Job), `C` (Cancel...

View Details →

$avers

Active
z/OS

$avers is an output management solution for z/OS, designed to manage, archive, and view JES output. Key components include the Output Manager, Archive Manager, and...

View Details →

4Tune

Not Supported
z/OS

Alternatives available

4Tune was a performance monitoring solution for z/OS systems, offering real-time and historical insights into system behavior. It collected data via SMF records and proprietary...

View Details →

ABARS/Assist

Active
z/OS

ABARS/Assist is designed to automate and monitor DFSMShsm ABARS backups. The core components include the Backup Manager, the Restore Manager, and the Monitoring Agent. These...

View Details →

ACC

Active
z/OS

ACC is a z/OS console automation solution designed to reduce manual intervention and improve operational efficiency. Key components include the Message Monitor, Rules Engine, and...

View Details →

Help Improve This Directory

Notice outdated information? Have insights about this product? Help the mainframe community stay informed with accurate, current data.

Are You a Vendor? Claim Your Listing

Take control of your product listings. Add verified information, showcase updates, and unlock a Claimed Vendor badge across the directory.

Claim Your Listing Now