What was the command structure and configuration process for AON/MVS?

While specific command syntax is not available, AON/MVS likely used NetView command syntax extended with AON-specific parameters. Configuration files would have defined automation rules and network parameters.

What types of APIs and integration capabilities did AON/MVS offer?

Details on specific APIs are unavailable, but AON/MVS likely integrated with NetView through its existing API or command interface. Communication protocols would have included SNA and TCP/IP.

What were the main system components of AON/MVS and how did they communicate?

The main components likely included a rule engine, event processor, and communication modules for interacting with different network types. These components would communicate through internal APIs or message queues.

What administrative interfaces were available in AON/MVS?

Administrative interfaces likely included a command-line interface (CLI) and potentially a GUI integrated within NetView. User management would have been handled through NetView's security mechanisms.

What business value did AON/MVS provide?

AON/MVS provided business value by automating routine network operations, reducing manual intervention, and improving overall network availability. This led to cost savings and increased efficiency.

How did AON/MVS contribute to improved service levels?

By automating responses to network events, AON/MVS helped to minimize downtime and ensure consistent service levels. This proactive approach improved the overall user experience.

How did AON/MVS simplify network management?

AON/MVS enabled centralized control over diverse network environments, simplifying management and reducing the complexity of network operations. This centralized approach improved visibility and control.

What authentication methods were supported by AON/MVS?

AON/MVS likely integrated with NetView's security features, leveraging authentication methods such as RACF or ACF2. Access control would have been managed through NetView's user profiles and permissions.

What audit and logging capabilities existed in AON/MVS?

AON/MVS would have used NetView's auditing and logging capabilities to track user activity and system events. This provided a record of actions taken and helped to identify potential security issues.

What encryption methods were used to secure data transmitted by AON/MVS?

Data transmitted between AON/MVS components and managed devices would have been secured using SNA or TCP/IP security protocols. Specific encryption methods would have depended on the underlying network protocols.

What were the key operational tasks associated with AON/MVS?

AON/MVS operations involved defining automation rules, monitoring network events, and responding to alerts. This required configuring the system and training operators on its use.

What monitoring capabilities were available in AON/MVS?

Monitoring capabilities included real-time displays of network status, event logs, and performance metrics. These tools helped operators to identify and resolve network issues quickly.

What type of logging capabilities were provided?

AON/MVS provided logging capabilities to track system events, user activity, and automation actions. These logs were essential for troubleshooting and auditing purposes.

Share Your Product Experience

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

Share Your Experience

AON/MVS

IBM Not Supported z/OS

Networks and Communication Automation

Vendor

IBM

Product Overview

AON/MVS was a network automation solution for z/OS, built on NetView. 25, and TCP/IP networks using a rule-based engine triggered by time, status, and error conditions. 25, and TCP/IP, and integration points with NetView.

These components communicated through internal APIs and message queues. Security was provided through integration with RACF/ACF2 for authentication and access control. Administrative interfaces likely included a command-line interface (CLI) and potentially a GUI integrated within NetView.

AON/MVS is no longer supported. Organizations should migrate to IBM Z System Automation or Broadcom Automation Suite for z/OS. These alternatives offer similar functionality with modern architectures and continued support.

AON/MVS competed with products offering similar network automation features, but its tight integration with NetView was a key differentiator.

Frequently Asked Questions

What was the primary purpose of AON/MVS?

AON/MVS was used to automate network operations based on predefined rules and events. It could automatically execute commands based on time, status, or error messages.

What were the software prerequisites for AON/MVS?

AON/MVS required NetView as a prerequisite. It extended NetView's capabilities to provide automated network management.

What types of networks could AON/MVS automate?

AON/MVS could automate SNA, X.25, and TCP/IP networks. This allowed for centralized automation across different network types.

What criteria could be used to trigger automated actions in AON/MVS?

AON/MVS allowed users to define rules based on time, network status, and specific error messages. These rules triggered automated actions.

Help Improve This Directory

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

Report Issue Suggest Product Share Event

Share Your Product Experience

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

Share Your Experience

Share Your Product Experience

AON/MVS

Product Overview

Frequently Asked Questions

What was the primary purpose of AON/MVS?

What were the software prerequisites for AON/MVS?

What types of networks could AON/MVS automate?

What criteria could be used to trigger automated actions in AON/MVS?

What was the command structure and configuration process for AON/MVS?

What types of APIs and integration capabilities did AON/MVS offer?

What were the main system components of AON/MVS and how did they communicate?

What administrative interfaces were available in AON/MVS?

What business value did AON/MVS provide?

How did AON/MVS contribute to improved service levels?

How did AON/MVS simplify network management?

What authentication methods were supported by AON/MVS?

What audit and logging capabilities existed in AON/MVS?

What encryption methods were used to secure data transmitted by AON/MVS?

What were the key operational tasks associated with AON/MVS?

What monitoring capabilities were available in AON/MVS?

What type of logging capabilities were provided?

Related Products

More from IBM

Access 1

ACF/NCP

ACF/SSP

ACO SolutionPac

Ada/370

ADF II

Similar Products

_beta access monitor

$avers

2cIP

2cSNA

3770Link

3780Link

Help Improve This Directory

Share Your Product Experience