CA STX Modernization Guide

CA STX provided connectivity between SNA networks and X.25 networks, enabling 3270 terminal users to access X.25 services. It acted as a protocol converter, translating SNA protocols to X.25 and vice versa.

CA STX used configuration files to define the mapping between SNA logical units (LUs) and X.25 addresses. These files specified parameters for protocol conversion, addressing, and security. The administrative interface allowed modification of these configuration files.

CA STX supported authentication through user IDs and passwords, often integrated with the z/OS or z/VM security systems. Access control was typically managed through access control lists (ACLs) that defined which users or groups could access specific X.25 resources.

CA STX provided logging capabilities to track network activity, errors, and security events. Administrators could use these logs to monitor the performance and security of the SNA-to-X.25 connections. The logs could be configured to capture different levels of detail.

CA STX did not expose standard APIs like REST or SOAP. Integration was typically achieved through configuration and scripting, leveraging the existing SNA and X.25 infrastructure. There were no specific SDKs or programming languages supported for direct integration.

The main components of CA STX included the SNA interface module, the X.25 interface module, the protocol conversion engine, and the administration module. The SNA and X.25 interface modules handled communication with their respective networks, while the protocol conversion engine performed the necessary translation.

CA STX used configuration files stored on the z/OS or z/VM system to manage its settings. These files defined the mapping between SNA logical units and X.25 addresses, as well as security and logging parameters. No external databases were used.

CA STX required specific ports for SNA and X.25 communication. The exact ports depended on the configuration of the SNA and X.25 networks. Standard SNA ports and X.25 virtual circuit identifiers (VCIs) were used.

CA STX enabled organizations to extend the life of their existing 3270 terminal infrastructure by providing access to X.25 services. This allowed users to access applications and data on X.25 networks without requiring a complete overhaul of their terminal systems.

By connecting SNA networks to X.25 networks, CA STX facilitated communication between different systems and technologies. This interoperability allowed organizations to integrate their legacy systems with newer X.25-based applications.

CA STX helped organizations avoid the cost and disruption of replacing their existing 3270 terminals and SNA infrastructure. By providing a bridge to X.25 networks, it allowed them to leverage their existing investments.

CA STX supported authentication via user IDs and passwords, often integrated with the host system's security. Access control lists (ACLs) defined which users or groups could access specific X.25 resources. Encryption was not a primary feature; security relied on the underlying SNA and X.25 protocols.

CA STX used an access control list (ACL) model to manage access to X.25 resources. ACLs defined which users or groups were permitted to access specific resources, providing a granular level of control.

CA STX relied on the encryption provided by the underlying SNA and X.25 protocols. It did not implement its own encryption mechanisms. Security was primarily focused on authentication and access control.

CA STX provided audit logging capabilities to track user activity, system events, and security-related incidents. These logs could be used to monitor the system for unauthorized access or other security breaches.

CA STX provided a command-line interface (CLI) for administrative tasks. User management was handled through the host system's user management tools (e.g., RACF on z/OS). Configuration parameters were stored in configuration files.

User management in CA STX was typically handled through the host operating system's user management tools, such as RACF on z/OS or the user directory on z/VM. CA STX integrated with these systems to authenticate users and control access to resources.

The main configuration parameters for CA STX included the mapping between SNA logical units and X.25 addresses, security settings, and logging parameters. These parameters were defined in configuration files.

CA STX provided logging capabilities to track network activity, errors, and security events. These logs could be used to monitor the system for performance issues and security breaches. The logs could be configured to capture different levels of detail.