What infrastructure is required?

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: Does this run in an LPAR?

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).

Does this extend or enhance another product?

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.

What other products or components must be present for this to work?

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.

What business problem does it solve?

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.

What would happen if an organization did NOT use this product?

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.

How does SSR Server improve business value?

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.

What authentication methods are supported?

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.

What access control model is used?

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.

What encryption is used and where?

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.

What audit/logging capabilities exist?

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.

How is this product typically deployed?

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.

What level of technical expertise is required to implement it?

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.

What ongoing operational requirements exist?

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.

What are common implementation challenges?

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.

Share Your Product Experience

Help the community by sharing your experience with mainframe products. Your insights help others make informed decisions.

Share Your Experience

SSR Server

Applied Software Active z/OS

File Transfer

Vendor

Applied Software

Product Overview

SSR Server is a file transfer solution designed to replace or enhance IND$FILE functionality in mainframe environments. It facilitates file transfers between mainframe systems (TSO, VTAM, CICS) and user workstations, supporting both IND$FILE and HST protocols. The architecture comprises server components running on the mainframe (z/OS) and a client component (SSR Client) running on Windows workstations.

Communication between the client and server occurs over TCP/IP, utilizing standard file transfer protocols. SSR Server integrates with mainframe security systems (RACF, ACF2, Top Secret) for authentication and access control. The server components are configured through configuration files, specifying parameters such as network ports, security settings, and logging options.

Alternatives like Managed File Transfer Platform Server and Axway Transfer CFT offer more distributed architectures and API-driven integration capabilities. SSR Server is best suited for organizations seeking a direct replacement for IND$FILE with enhanced security and performance within a traditional mainframe environment.

Frequently Asked Questions

What does SSR Server do?

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.

Is this a system, application, or tool?

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.

What types of organizations use this?

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.

When should we consider SSR Server?

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.

What are the alternatives to SSR Server?

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.

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

SSR Server

Product Overview

Frequently Asked Questions

What does SSR Server do?

Is this a system, application, or tool?

What types of organizations use this?

When should we consider SSR Server?

What are the alternatives to SSR Server?

What infrastructure is required?

For mainframe products: Does this run in an LPAR?

Does this extend or enhance another product?

What other products or components must be present for this to work?

What business problem does it solve?

What would happen if an organization did NOT use this product?

How does SSR Server improve business value?

What authentication methods are supported?

What access control model is used?

What encryption is used and where?

What audit/logging capabilities exist?

How is this product typically deployed?

What level of technical expertise is required to implement it?

What ongoing operational requirements exist?

What are common implementation challenges?

Related Products

More from Applied Software

Similar Products

Help Improve This Directory

Share Your Product Experience