Macro 4 z/OS

Automon Modernization Guide

Operating SystemAutomation

Automon is a operating system product by Macro 4. Explore technical details, modernization strategies, and migration paths below.

Product Overview

Automon is a platform designed for automating operations on z/OS systems.

For scheduling tasks, the `SCHD` command is employed.

Modernization Strategies

Rehost

Timeline:
6-12 months

Lift-and-shift to cloud infrastructure with minimal code changes. Fast migration with lower risk.

Refactor (Recommended)

Timeline:
18-24 months

Optimize application architecture for cloud while preserving business logic. Best ROI long-term.

Replatform

Timeline:
3-5 years

Complete rewrite to cloud-native architecture with microservices and modern tech stack.

Frequently Asked Questions

General

What is Automon?

Automon is a platform for developing automated operations solutions on z/OS. It provides a REXX programming environment and interfaces for console message trapping and scheduled processing.

What scripting language does Automon use?

Automon uses REXX as its primary scripting language. Users define rules and actions using REXX syntax to automate tasks.

What are some key capabilities of Automon?

Automon can trap and process console messages, allowing automated responses to system events. It can also schedule tasks to run at specific times or intervals.

How does Automon interact with z/OS and other systems?

Automon provides interfaces for interacting with z/OS consoles and system services. It also offers APIs for integration with other systems.

Technical

What are some common operations in Automon?

Common operations include defining message traps using the MSGTRAP command, scheduling tasks with the SCHD command, and writing REXX scripts to automate responses. Configuration is primarily done through REXX scripts and parameter files.

What types of APIs does Automon expose?

Automon exposes APIs for integration with other systems. These APIs may include methods for submitting commands, retrieving status information, and receiving event notifications. The specific API types and methods depend on the version and configuration.

What are the main system components of Automon?

The main system components include the Automon engine, the REXX interpreter, and the console interface. These components communicate through internal APIs and message queues.

How is Automon configured and how is user management handled?

Automon uses parameter files and REXX scripts for configuration. User management is typically handled through z/OS security mechanisms such as RACF or ACF2.

What monitoring and logging capabilities exist in Automon?

Automon provides monitoring and logging capabilities through its console interface and system logs. Users can define alerts and notifications based on specific events or conditions.

Business Value

What is the business value of Automon?

Automon automates routine tasks, reduces manual intervention, and improves system availability. By automating responses to system events, it minimizes downtime and ensures consistent operations.

How does Automon help organizations meet SLAs?

Automon helps organizations meet service level agreements (SLAs) by ensuring timely responses to system issues. Its automation capabilities enable faster problem resolution and improved service delivery.

How does Automon reduce operational costs?

By automating tasks and reducing manual effort, Automon lowers operational costs and improves efficiency. It frees up IT staff to focus on more strategic initiatives.

Security

What authentication methods are supported by Automon?

Automon supports authentication methods provided by z/OS, such as RACF, ACF2, and Top Secret. It integrates with these security systems to authenticate users and control access to resources.

What access control model is used in Automon?

Automon uses an access control model based on z/OS security features. Access to Automon functions and resources is controlled through RACF profiles and permissions.

What encryption is used and where?

Automon leverages z/OS security features for encryption. Data transmitted between Automon components can be encrypted using z/OS encryption facilities.

What audit/logging capabilities exist in Automon?

Automon provides audit logging capabilities to track user activity and system events. Audit logs can be used to monitor security and compliance.

Operations

What administrative interfaces are available for Automon?

Automon is administered through a combination of command-line interfaces (CLIs) and parameter files. The primary interface is the z/OS console.

How is user management handled in Automon?

User management is handled through z/OS security systems like RACF or ACF2. Automon leverages these systems for user authentication and authorization.

What are the main configuration parameters for Automon?

Key configuration parameters include message trap definitions, scheduling parameters, and REXX script locations. These parameters are typically stored in parameter files or REXX scripts.

What monitoring/logging capabilities exist in Automon?

Automon provides monitoring and logging capabilities through its console interface and system logs. Users can define alerts and notifications based on specific events or conditions.

Ready to Start Your Migration?

Download our comprehensive migration guide for Automon or calculate your ROI.

Calculate ROI