What are some common commands or operations performed by users?

Common operations include adding a new terminal (ADD TERMINAL), modifying an existing terminal (MODIFY TERMINAL), deleting a terminal (DELETE TERMINAL), displaying terminal status (DISPLAY TERMINAL), and listing all defined terminals (LIST TERMINALS).

What configuration files are used?

The product uses configuration files, often defined in datasets, to store terminal definitions and configuration parameters. These files are read during initialization and when changes are applied.

What types of APIs does this product expose?

While specific APIs are not typically exposed for external integration, the product integrates directly with IMS through internal interfaces and control blocks. This allows seamless management of terminals without requiring external API calls.

What are the main system components?

The main system components include the Terminal Definition Manager, which handles terminal definitions; the Message Interceptor, which intercepts and modifies IMS messages; and the Configuration Repository, which stores terminal configurations.

How does the product handle security?

The product uses standard z/OS security mechanisms for authentication and authorization. It integrates with security systems like RACF, ACF2, and Top Secret to control access to terminal management functions.

How does the product simplify terminal management?

The elimination of IMS ETO exits simplifies terminal management and reduces the complexity of the IMS environment. This results in easier maintenance and fewer potential points of failure.

How does the product contribute to cost savings?

The product's ability to manage terminals without requiring IMS downtime translates to significant cost savings by avoiding disruptions to critical business processes.

What authentication methods are supported?

The product supports authentication methods provided by z/OS security systems, including RACF, ACF2, and Top Secret. It leverages these systems for user authentication and authorization.

What access control model is used?

The product uses an access control model based on the z/OS security system in place (RACF, ACF2, Top Secret). Access to terminal management functions is controlled through user profiles and permissions defined in these systems.

What audit/logging capabilities exist?

The product integrates with z/OS security systems for auditing and logging. Security events and administrative actions are logged by RACF, ACF2, or Top Secret, providing a comprehensive audit trail.

What encryption is used and where?

The product leverages the encryption capabilities provided by z/OS for data in transit and at rest. Sensitive data, such as passwords and configuration parameters, can be encrypted using z/OS encryption services.

What administrative interfaces are available?

The product provides administrative interfaces through ISPF panels and command-line interfaces. These interfaces allow administrators to manage terminal definitions, security settings, and system parameters.

How is user management handled?

User management is handled through the z/OS security system (RACF, ACF2, Top Secret). User profiles and permissions are defined and managed within these systems, controlling access to the product's functions.

What are the main configuration parameters?

The main configuration parameters include terminal IDs, LTERM names, security attributes, and device characteristics. These parameters are defined in configuration files and managed through the administrative interfaces.

What monitoring/logging capabilities exist?

The product provides monitoring and logging capabilities through integration with z/OS system logging facilities. System events, errors, and administrative actions are logged for auditing and troubleshooting purposes.

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

Mainframe Extended Terminal Manager for IMS

Broadcom Active z/OS

Tools and Utilities IMS Administration

Vendor

Broadcom

Product Overview

Mainframe Extended Terminal Manager for IMS provides a robust architecture for dynamic terminal management in IMS environments. The key components include: * **Terminal Definition Manager:** Handles the definition, modification, and deletion of terminal definitions. * **Message Interceptor:** Intercepts and modifies IMS messages to dynamically manage terminal characteristics.

* **Configuration Repository:** Stores terminal configurations and system parameters. These components communicate through internal interfaces and control blocks within the z/OS environment. The product integrates with z/OS security systems (RACF, ACF2, Top Secret) for authentication and authorization.

Configuration is managed through ISPF panels and configuration files. The system uses standard z/OS datasets for storing configuration data. Unlike some competing products, this solution allows terminal management without requiring IMS restarts, minimizing downtime and improving system availability.

The architecture is designed for high availability and scalability, ensuring reliable terminal management in demanding IMS environments.

Frequently Asked Questions

What is the primary function of Mainframe Extended Terminal Manager for IMS?

Mainframe Extended Terminal Manager for IMS allows dynamic addition, modification, and deletion of devices in an IMS environment without requiring IMS downtime. It eliminates the need for IMS ETO exits, simplifying terminal management.

How does Mainframe Extended Terminal Manager for IMS manage terminal definitions?

The product intercepts standard IMS control blocks to manage terminal definitions. It uses internal tables and control structures to maintain device configurations, avoiding modifications to the IMS catalog.

What are the key components of the system architecture?

The architecture includes components such as the Terminal Definition Manager, the Message Interceptor, and the Configuration Repository. These components work together to dynamically manage terminal definitions and message flow.

How is the product configured and managed?

Configuration is primarily managed through a set of ISPF panels and configuration files. These interfaces allow administrators to define and modify terminal characteristics and security settings.

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

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

Are You a Vendor? Claim Your Listing

Mainframe Extended Terminal Manager for IMS

Product Overview

Frequently Asked Questions

What is the primary function of Mainframe Extended Terminal Manager for IMS?

How does Mainframe Extended Terminal Manager for IMS manage terminal definitions?

What are the key components of the system architecture?

How is the product configured and managed?

What are some common commands or operations performed by users?

What configuration files are used?

What types of APIs does this product expose?

What are the main system components?

How does the product handle security?

How does this product provide business value?

How does the product simplify terminal management?

How does the product contribute to cost savings?

What authentication methods are supported?

What access control model is used?

What audit/logging capabilities exist?

What encryption is used and where?

What administrative interfaces are available?

How is user management handled?

What are the main configuration parameters?

What monitoring/logging capabilities exist?

Related Products

More from Broadcom

Similar Products

Help Improve This Directory

Are You a Vendor? Claim Your Listing