SSR Server Modernization Guide

SSR Server provides IND$FILE and HST file transfer capabilities between mainframe systems (TSO, VTAM, CICS) and workstations. It allows users to transfer files between a mainframe and 3270 emulation software or a Windows environment.

SSR Server is a software application designed to replace or enhance IND$FILE functionality. It provides a more robust and feature-rich solution for file transfers between mainframe and workstation environments.

Organizations that rely on mainframe systems for core business operations and need to transfer files between those systems and user workstations will find SSR Server useful. This includes companies in industries like banking, insurance, and government.

A company should consider SSR Server when they need a reliable and efficient way to transfer files between their mainframe systems and user workstations, especially if they are experiencing limitations with existing IND$FILE solutions or require HST transfer capabilities.

Alternatives to SSR Server include other IND$FILE replacement products, managed file transfer solutions, and custom-built file transfer utilities. Examples include Managed File Transfer Platform Server, Axway Transfer CFT, PC/Transfer, and SecureFTP.

SSR Server is deployed on-premise, typically on the mainframe system (z/OS) and on Windows workstations. It requires the appropriate mainframe subsystems (TSO, VTAM, CICS) to be installed and configured.

For mainframe products, SSR Server runs within an LPAR under z/OS. It is dependent on specific subsystems such as TSO, VTAM, or CICS, depending on the specific SSR Server product being used (e.g., SSR Server for TSO, SSR Server for CICS).

SSR Server enhances the capabilities of IND$FILE by providing a more robust and feature-rich file transfer solution. It can also provide HST transfer capabilities, which are not available in standard IND$FILE.

SSR Server requires a Windows client component (SSR Client) to be installed on user workstations. On the mainframe side, it requires the appropriate TSO, VTAM, or CICS subsystems to be active.

SSR Server solves the business problem of efficiently and reliably transferring files between mainframe systems and user workstations. Without it, organizations may face challenges with slow transfer speeds, limited functionality, and security risks associated with older file transfer methods.

If an organization did not use SSR Server, they would likely rely on older, less efficient file transfer methods, which could lead to increased transfer times, higher operational costs, and potential security vulnerabilities.

SSR Server can improve productivity by streamlining file transfer processes, reducing transfer times, and providing a more user-friendly interface for users. It can also enhance security by providing secure file transfer protocols and access controls.

SSR Server supports various authentication methods, including mainframe security systems (e.g., RACF, ACF2, Top Secret) and Windows authentication. The specific methods supported depend on the configuration of the mainframe and workstation environments.

SSR Server uses an access control model based on mainframe security systems (RACF, ACF2, Top Secret) to control access to mainframe datasets. It also provides access controls on the Windows client side to restrict access to files and directories.

SSR Server uses encryption during file transfer to protect data in transit. The specific encryption algorithms used depend on the configuration of the server and client components.

SSR Server provides audit logging capabilities to track file transfer activity, user access, and security events. These logs can be used for security monitoring and compliance purposes.

SSR Server is typically deployed on-premise, requiring technical expertise in both mainframe and Windows environments. Implementation involves configuring the server components on the mainframe and deploying the client software on user workstations.

Implementing SSR Server requires technical expertise in mainframe systems (z/OS, TSO, VTAM, CICS) and Windows environments. Familiarity with file transfer protocols and security concepts is also beneficial.

Ongoing operational requirements for SSR Server include monitoring file transfer activity, managing user access, and performing regular maintenance tasks. This may involve monitoring logs, applying security patches, and troubleshooting issues.

Common implementation challenges for SSR Server include configuring the server components to integrate with existing mainframe security systems, ensuring compatibility between the server and client components, and troubleshooting network connectivity issues.