ETOM - Enhanced Telecommunications Operations Map

Enhanced Definition

ETOM, or Enhanced Telecommunications Operations Map, is a specialized component within IBM's `NetView` product on `z/OS` designed to automate the monitoring, control, and problem determination of telecommunications resources. It provides a structured framework for managing network events and initiating predefined actions to enhance the efficiency and reliability of mainframe network operations. Its primary goal is to reduce manual intervention in managing complex `z/OS` network environments. ETOM (Enhanced Telecommunications Operations Map) is a key component of IBM NetView for z/OS, providing a graphical, hierarchical representation of the telecommunications network and its resources within the mainframe environment. Its primary purpose is to enable operators and system administrators to visualize, monitor, and manage the operational status of network components, facilitating rapid problem identification and resolution.

Key Characteristics

- Event-Driven Automation: ETOM processes network events, messages, and alerts (e.g., SNA alerts, TCP/IP messages) and triggers automated responses based on predefined rules and policies.
- Integrated Network Management: It works in conjunction with NetView to offer a centralized point of control for managing VTAM, TCP/IP stacks, and other network resources connected to or running on z/OS.
- Problem Determination and Resolution: ETOM can automatically diagnose common network issues, gather diagnostic data, and initiate corrective actions, thereby reducing mean time to recovery (MTTR) and operational overhead.
- Customizable Automation: Operators can define and implement custom automation tables and procedures (often using REXX or CLIST) to tailor ETOM's behavior to specific operational requirements, network topologies, and service level agreements.
- Proactive Monitoring: Beyond reactive problem solving, ETOM supports proactive monitoring by detecting potential issues through threshold-based alerting and predictive analysis before they impact critical services.

Use Cases

- Automated VTAM Resource Management: Automatically activating or deactivating VTAM major nodes, managing LU sessions, and responding to VTAM error messages to maintain network availability.
- TCP/IP Stack Monitoring and Recovery: Monitoring the health and performance of TCP/IP stacks, automatically restarting unresponsive FTP or Telnet servers, or alerting operators to unusual network traffic patterns.
- Network Problem Isolation: When a network component fails, ETOM can automatically execute diagnostic commands, collect traces, and notify the appropriate support team with relevant information for quicker resolution.
- Scheduled Network Operations: Performing routine tasks such as cycling network connections, refreshing routing tables, or generating network configuration reports during off-peak hours without manual intervention.
- Integration with Enterprise Management Systems: Sending consolidated alerts and status updates to higher-level enterprise management consoles, providing a unified view of the z/OS network infrastructure health.

Related Concepts

ETOM is intrinsically linked with IBM NetView, often functioning as a core set of capabilities or a specialized module within it, leveraging NetView's robust automation engine and command processors. It directly manages resources defined within VTAM (Virtual Telecommunications Access Method) and TCP/IP stacks running on z/OS, ensuring the availability and performance of mainframe communication links. Its automation capabilities are frequently implemented using REXX or CLIST procedures, which are foundational scripting languages on z/OS for system automation and operational control.

Best Practices:

Thorough Testing of Automation: Rigorously test all ETOM automation scripts and rules in a controlled, non-production environment before deployment to prevent unintended disruptions to critical services.
Granular Event Filtering: Configure ETOM to filter out irrelevant messages and focus on critical events to avoid alert fatigue, improve processing efficiency, and ensure operators see only actionable information.
Regular Review and Updates: Periodically review and update automation scripts and rules to ensure they remain relevant to the evolving network topology, application requirements, and operational procedures.
Comprehensive Documentation: Maintain clear and detailed documentation for all ETOM automation, including triggers, actions, expected outcomes, and contact information for support, facilitating easier troubleshooting and maintenance.
Secure Access and Authorization: Implement strict