For mainframe products: Did this run in an LPAR?

CA TCPaccess Telnet Server ran on z/OS. It required a TCP/IP stack to be configured and active on the mainframe. It typically ran within an LPAR.

What infrastructure was required?

The server required a configured TCP/IP stack on z/OS. Client workstations needed a TN3270 client application to connect to the server.

What were the main components?

The main components included the TN3270 server process, configuration files, and potentially a security server for authentication. The server process listened for incoming connections and managed terminal sessions.

What was the business value?

The primary business value was enabling access to mainframe applications from a wider range of devices and networks. This allowed organizations to extend the life of their mainframe investments and improve user productivity.

What happened without it?

Without a TN3270 server, organizations would be limited to using dedicated 3270 terminals or specialized hardware to access mainframe applications. This could increase costs and limit flexibility.

How did it integrate with security systems?

The product integrated with existing mainframe security systems, such as RACF, ACF2, or Top Secret, to control access to applications and data. It also supported TLS/SSL encryption to protect data in transit.

What authentication methods were supported?

CA TCPaccess Telnet Server supported authentication methods such as basic username/password authentication and integration with mainframe security systems like RACF, ACF2, and Top Secret.

What access control model was used?

The access control model was based on user IDs and group memberships defined in the mainframe security system. Access to specific applications and data was controlled through RACF, ACF2, or Top Secret rules.

What encryption was used?

TLS/SSL encryption was used to protect data transmitted between the TN3270 client and the server. This ensured that sensitive information, such as passwords and application data, was not exposed during transmission.

What audit/logging capabilities existed?

The server provided audit logging capabilities to track user access and application usage. These logs could be used for security monitoring and compliance purposes.

What ongoing operational requirements existed?

Ongoing operational requirements included monitoring the server for availability and performance, managing user accounts, and applying security patches. Regular maintenance was required to ensure the server remained stable and secure.

What administrative interfaces were available?

Administrative interfaces typically included a command-line interface (CLI) and configuration files. The CLI was used to manage the server, while configuration files defined the server's behavior.

How was user management handled?

User management was typically handled through the mainframe security system (RACF, ACF2, or Top Secret). User accounts and permissions were defined and managed within these systems.

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 TCPaccess Telnet Server

Name: CA TCPaccess Telnet Server
Availability: InStock

CA Technologies Not Supported z/OS

3270 Networks and Communication

Vendor

CA Technologies

Product Overview

CA TCPaccess Telnet Server provided TN3270 terminal emulation, enabling users to access mainframe applications over a TCP/IP network. It allowed standard workstations to connect to z/OS systems and interact with 3270-based applications. The server ran on z/OS within an LPAR and required a configured TCP/IP stack.

It used standard Telnet ports (typically port 23) for unencrypted communication and port 992 for encrypted communication using TLS/SSL. The main components included the TN3270 server process, configuration files, and a security server for authentication. Key architectural considerations included integrating with existing mainframe security systems (RACF, ACF2, Top Secret) for authentication and access control.

The access control model was based on user IDs and group memberships defined in the mainframe security system. TLS/SSL encryption was used to protect data transmitted between the TN3270 client and the server. Alternatives include IBM Communications Server and Micro Focus Host Access Management and Security Server.

As CA TCPaccess Telnet Server is no longer supported, organizations should migrate to a supported TN3270 solution, involving a full review of the architecture and security implications.

Frequently Asked Questions

What did CA TCPaccess Telnet Server do?

Was this a system, application, or tool?

It was an application that provided connectivity. It acted as a bridge between TCP/IP networks and the 3270 terminal environment traditionally used with mainframes.

What types of organizations used this?

Organizations that relied on mainframe applications and needed to provide access to those applications from standard TCP/IP networks used CA TCPaccess Telnet Server. This included businesses in finance, insurance, and government.

When did companies consider CA TCPaccess Telnet Server?

Companies considered CA TCPaccess Telnet Server when they needed to extend mainframe application access to users on standard networks. This was particularly relevant when migrating from SNA to TCP/IP networks.

What are the alternatives to CA TCPaccess Telnet Server?

Alternatives include IBM Communications Server, NetManage RUMBA, and Micro Focus Host Access Management and Security Server. These products provide similar TN3270 emulation and mainframe connectivity features.

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 TCPaccess Telnet Server

Product Overview

Frequently Asked Questions

What did CA TCPaccess Telnet Server do?

Was this a system, application, or tool?

What types of organizations used this?

When did companies consider CA TCPaccess Telnet Server?

What are the alternatives to CA TCPaccess Telnet Server?

For mainframe products: Did this run in an LPAR?

What infrastructure was required?

What ports did it use?

What were the main components?

What was the business value?

What happened without it?

How did it integrate with security systems?

What authentication methods were supported?

What access control model was used?

What encryption was used?

What audit/logging capabilities existed?

What ongoing operational requirements existed?

What administrative interfaces were available?

How was user management handled?

Related Products

More from CA Technologies

ADC2

AutoMate

CA 90s

CA Alert/VM

CA APAS Insight

CA Automated Code Structuring for COBOL

Similar Products

2cIP

2cSNA

3270 SUPEROPTIMIZER/CICS

3270 SUPEROPTIMIZER/IMS

3770Link

3780Link

Help Improve This Directory

Share Your Product Experience