What infrastructure was required?

CA Teleview Session Management ran on z/OS mainframe systems. It required VTAM (Virtual Telecommunications Access Method) to manage communication between the terminal sessions and the applications.

For mainframe products: Did this run in an LPAR?

Yes, it ran within an LPAR (Logical Partition) on the mainframe. It was dependent on the z/OS operating system and VTAM.

What configuration files or interfaces were used?

The product likely used configuration files to define the VTAM applications and their associated session parameters. These files would be edited by system administrators.

What was the business value of using this product?

The primary business value was increased user productivity. By allowing users to access multiple applications from a single session, it reduced the time and effort required to switch between tasks.

What would happen if an organization did not use this product?

Without CA Teleview Session Management, users would have to log on and off each application separately, which was time-consuming and inefficient. This could lead to reduced productivity and increased frustration.

What was the typical licensing model?

The licensing model was likely perpetual, with ongoing maintenance fees. The total cost of ownership included the initial license fee, maintenance, and the cost of system administration.

What specific authentication methods were supported?

Authentication methods likely included standard mainframe security mechanisms such as RACF, ACF2, or Top Secret. Access control was typically based on user IDs and group memberships defined in these security systems.

What access control model was used?

The access control model was likely based on ACLs (Access Control Lists) managed by the mainframe security system. These ACLs defined which users or groups had access to specific VTAM applications.

What audit/logging capabilities existed?

Audit logging capabilities existed within the mainframe security system. These logs tracked user access to applications and any security-related events.

What ongoing operational requirements existed?

Ongoing operational requirements included monitoring the system for performance issues, maintaining the configuration files, and ensuring compatibility with the z/OS and VTAM environments. System administrators were responsible for these tasks.

What were common implementation challenges?

Implementation challenges could include configuring VTAM correctly, ensuring compatibility with existing applications, and managing user access rights. Careful planning and testing were essential.

What administrative interfaces were available?

Administrative interfaces likely included a command-line interface (CLI) and potentially a GUI (Graphical User Interface) for managing the system. The CLI would be used for tasks such as configuring VTAM applications and managing user sessions.

Share Your Product Experience

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

Share Your Experience

CA Teleview Session Management

Broadcom Not Supported z/OS

Sharing 3270

Vendor

Broadcom

Product Overview

CA Teleview Session Management provided a centralized session management solution for mainframe environments. Its architecture centered around enabling users to access multiple VTAM applications from a single 3270 session. The main components included a session manager, VTAM interface, and configuration data storage.

The session manager handled user requests and managed connections to VTAM applications. Communication between components relied on VTAM protocols. The system ran on z/OS within an LPAR and required VTAM.

Security integration was achieved through mainframe security systems like RACF, ACF2, or Top Secret, which controlled access to applications. Alternatives include CL/Supersession, Multiterm/MVS, and InterSession. The product used configuration files to define VTAM applications and session parameters.

Deployment involved installing the software on the mainframe and configuring it to work with existing VTAM applications. Ongoing operations included monitoring performance and managing user access.

Frequently Asked Questions

What does CA Teleview Session Management do?

CA Teleview Session Management allowed a single 3270 terminal session to access multiple VTAM applications concurrently. This eliminated the need for users to log on and off different applications repeatedly, improving efficiency.

Is this a system, application, or tool?

It was an application that provided session management capabilities for IBM mainframe environments.

What types of organizations used this?

Organizations that relied on IBM mainframe systems and 3270 terminal access for their applications used CA Teleview Session Management. These were often large enterprises in industries like banking, insurance, and government.

When should we have considered CA Teleview Session Management?

Companies considered CA Teleview Session Management when they wanted to improve user productivity by simplifying access to multiple mainframe applications from a single terminal session.

What are the alternatives to CA Teleview Session Management?

Alternatives include CL/Supersession, Multiterm/MVS, and InterSession. These products offer similar session management capabilities for mainframe environments.

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

CA Teleview Session Management

Product Overview

Frequently Asked Questions

What does CA Teleview Session Management do?

Is this a system, application, or tool?

What types of organizations used this?

When should we have considered CA Teleview Session Management?

What are the alternatives to CA Teleview Session Management?

What infrastructure was required?

For mainframe products: Did this run in an LPAR?

What configuration files or interfaces were used?

What were the main system components?

What was the business value of using this product?

What would happen if an organization did not use this product?

What was the typical licensing model?

What specific authentication methods were supported?

What access control model was used?

What audit/logging capabilities existed?

What ongoing operational requirements existed?

What were common implementation challenges?

What administrative interfaces were available?

Related Products

More from Broadcom

AcceleREXX

ACF2

Allocate DASD Space and Placement

Auditor for z/OS

Automation Point

Bind Analyzer for Db2

Similar Products

3270 SUPEROPTIMIZER/CICS

3270 SUPEROPTIMIZER/IMS

Adabas Cluster Services

AUTOMON/VTAM

Aviva for Desktops

Aviva for Java

Help Improve This Directory

Share Your Product Experience