CA TCPaccess Telnet Server Modernization Guide

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.

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.

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.

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.

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.

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.

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

The server used standard Telnet ports (typically port 23) for unencrypted communication and port 992 for encrypted communication using TLS/SSL. Configuration files defined the mapping between logical terminal names and physical devices.

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.

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.

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.

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.

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.

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.

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.

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

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.

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.

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.