TPX Modernization Guide

TPX allows users to access multiple VTAM applications from a single 3270 session, improving productivity and reducing the need for multiple terminal emulators. It streamlines application access and simplifies user workflows.

Common operations include logging on to TPX, selecting applications from the menu, switching between active applications, and logging off. Users navigate using commands or function keys.

TPX uses configuration files to define users, applications, and access permissions. The primary interface is the 3270 terminal itself, along with administrative panels for configuration.

TPX enhances the 3270 experience by allowing users to manage multiple sessions within a single terminal window, reducing clutter and improving workflow efficiency. It also provides centralized access control and auditing.

TPX primarily communicates using VTAM protocols for connecting to mainframe applications. It does not expose standard APIs like REST or SOAP.

The main system components include the TPX address space, the VTAM interface, and the security manager interface (e.g., RACF). These components communicate through standard z/OS inter-process communication mechanisms.

TPX relies on VSAM datasets for storing configuration data, user profiles, and session information. It does not typically use relational databases.

User management is typically handled through the security manager (e.g., RACF) or through TPX's internal security features. Configuration parameters are set using TPX administration panels.

A typical logon sequence involves entering a user ID and password at the TPX logon screen. After authentication, a menu of available applications is displayed.

TPX improves productivity by allowing users to access multiple applications from a single terminal session, reducing the need to switch between different emulators. This streamlines workflows and saves time.

By centralizing access to multiple applications, TPX simplifies user management and reduces the administrative overhead associated with managing individual terminal sessions. This leads to cost savings and improved efficiency.

TPX provides a consistent user experience across different applications, making it easier for users to learn and use new systems. This reduces training costs and improves user satisfaction.

TPX can be integrated with existing security systems, such as RACF, to provide a secure and controlled environment for accessing sensitive applications. This helps organizations meet compliance requirements and protect their data.

TPX supports authentication methods such as user ID/password, integration with external security managers like RACF, ACF2, and Top Secret, and potentially multi-factor authentication solutions.

TPX uses an access control model based on user profiles and application definitions. Access to specific applications is controlled through permissions assigned to users or groups.

TPX can be configured to encrypt data in transit using SSL/TLS when communicating with certain applications. Encryption at rest is typically handled by the underlying z/OS security infrastructure.

TPX provides audit logging capabilities that track user logon/logoff activity, application access, and administrative changes. These logs can be used for security monitoring and compliance reporting.

TPX provides administrative interfaces through 3270 panels, allowing administrators to configure users, applications, and security settings. A command-line interface may also be available for certain tasks.

TPX monitoring capabilities include real-time session monitoring, performance statistics, and alerts for critical events. These metrics can be used to identify and resolve performance issues.

TPX generates logs that capture user activity, system events, and error messages. These logs can be analyzed to troubleshoot problems and identify security threats.

TPX can be integrated with z/OS system management tools for centralized monitoring and control. This allows administrators to manage TPX alongside other mainframe applications.