Trax Softworks z/OS z/VM zVSE/VSEn

ESS Modernization Guide

Browse and EditContent, Books and Documents

ESS is a browse and edit product by Trax Softworks. Explore technical details, modernization strategies, and migration paths below.

Product Overview

ESS (Electronic Spreadsheet System) brings spreadsheet capabilities to mainframe environments, specifically z/OS, z/VM, and zVSE/VSEn.

You can then use ESS to create new spreadsheets, import data from existing mainframe datasets, and perform calculations and analysis.

Modernization Strategies

Rehost

Timeline:
6-12 months

Lift-and-shift to cloud infrastructure with minimal code changes. Fast migration with lower risk.

Refactor (Recommended)

Timeline:
18-24 months

Optimize application architecture for cloud while preserving business logic. Best ROI long-term.

Replatform

Timeline:
3-5 years

Complete rewrite to cloud-native architecture with microservices and modern tech stack.

Frequently Asked Questions

General

What does ESS do?

ESS is an electronic spreadsheet system designed for use in TSO, CMS, and CICS environments. It provides users with a tool to create, manipulate, and analyze data in a spreadsheet format. It essentially brings spreadsheet functionality to mainframe environments.

Is this a system, application, or tool?

ESS is an application, providing a user interface and functionality for spreadsheet creation and manipulation within the mainframe environment. It is not a system or a toolset, but a specific application designed for end-users.

What types of organizations use this?

Organizations that rely on mainframe systems for data processing and require spreadsheet functionality within those environments would benefit from ESS. This often includes larger enterprises in sectors like finance, insurance, and government.

When should we consider ESS?

A company should consider using ESS when they need spreadsheet capabilities directly on their mainframe systems, particularly when data resides primarily on the mainframe and needs to be analyzed or manipulated in place. This avoids the need to transfer data to other systems for spreadsheet processing.

What are the alternatives to ESS?

Alternatives to ESS include other mainframe-based spreadsheet applications or transferring data to desktop spreadsheet software like Microsoft Excel or Google Sheets. The choice depends on factors like data location, security requirements, and the need for real-time mainframe data access.

Technical

What infrastructure is required?

ESS requires a mainframe environment running z/OS, z/VM, or zVSE/VSEn. It operates within TSO, CMS, or CICS subsystems. No other specific products are explicitly required, but the appropriate operating system and subsystem infrastructure must be in place.

For mainframe products: Does this run in an LPAR?

ESS runs within an LPAR on a mainframe system. It is dependent on the z/OS, z/VM, or zVSE/VSEn operating system and requires the TSO, CMS, or CICS subsystems to be active and configured.

Is this a standalone product or does it extend/enhance another product?

ESS is a standalone application, although it integrates with the TSO, CMS, and CICS environments for data access and user interface. It does not extend or enhance another specific product but relies on the underlying mainframe infrastructure.

What types of APIs does this product expose?

While specific API details are not available, ESS likely provides interfaces for data import/export and integration with other mainframe applications. These interfaces would likely be based on standard mainframe protocols and data formats.

Business Value

What business problem does it solve?

ESS solves the business problem of providing spreadsheet functionality directly within the mainframe environment. Without it, organizations would need to extract data from the mainframe to use spreadsheet software on other platforms, which can be inefficient and pose security risks.

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

If an organization did not use ESS, they would need to rely on alternative methods for spreadsheet analysis of mainframe data. This could involve manual data extraction, custom programming, or using other less efficient or secure solutions.

What is the typical licensing model?

The licensing model for ESS is likely a perpetual license, but subscription or usage-based models are also possible. The total cost of ownership includes the initial license fee, maintenance fees, and the cost of mainframe resources used by the application.

Security

What specific authentication methods are supported?

ESS likely supports standard mainframe authentication methods, such as RACF, ACF2, or Top Secret. The access control model is probably based on user IDs and permissions defined within these security systems, controlling access to specific spreadsheets or data within them.

What access control model is used?

The access control model used by ESS is likely based on Role-Based Access Control (RBAC), where users are assigned roles with specific permissions to access and modify spreadsheets and data. This integrates with the mainframe's security system.

What encryption is used and where?

ESS likely uses encryption for data transmission and storage, especially for sensitive information. The specific encryption algorithms used would depend on the mainframe's security configuration and the requirements of the organization.

Operations

How is this product typically deployed?

ESS is typically deployed on-premise within the organization's mainframe environment. Implementing ESS requires expertise in mainframe systems, TSO, CMS, and CICS. Ongoing operational requirements include monitoring system performance, managing user access, and performing regular backups.

What administrative interfaces are available?

Administrative interfaces for ESS likely include a combination of command-line interfaces (CLIs) and potentially GUI-based interfaces accessible through TSO, CMS, or CICS. User management is typically handled through the mainframe's security system (RACF, ACF2, Top Secret).

What monitoring/logging capabilities exist?

Monitoring and logging capabilities in ESS likely integrate with the mainframe's system management tools, providing information on system performance, user activity, and potential errors. These logs can be used for auditing and troubleshooting.

Ready to Start Your Migration?

Download our comprehensive migration guide for ESS or calculate your ROI.

Calculate ROI