EdWord Modernization Guide
EdWord is a content, books and documents product by Trax Softworks. Explore technical details, modernization strategies, and migration paths below.
Product Overview
EdWord is a word processing application specifically designed for mainframe environments such as z/OS, z/VM, and zVSE/VSEn.
EdWord integrates with mainframe security systems like RACF, ACF2, and Top Secret for authentication and access control.
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 EdWord do?
EdWord is a word processing application designed for mainframe environments. It allows users to create, edit, and manage documents directly on z/OS, z/VM, and zVSE/VSEn systems.
Is this a system, application, or tool?
EdWord is primarily an application, providing a user interface and functionality for word processing tasks. It leverages the resources of the underlying mainframe system to deliver its capabilities.
What types of organizations use this?
Organizations that rely on mainframe systems for core business operations and require word processing capabilities within that environment would benefit from EdWord. This includes industries like banking, finance, insurance, and government.
When should we consider EdWord?
A company should consider EdWord when they need a word processing solution tightly integrated with their mainframe systems, especially if they require direct access to mainframe data and resources during document creation and editing.
What are the alternatives to EdWord?
Alternatives to EdWord include other mainframe-based word processing solutions or using a separate word processing system and transferring files to/from the mainframe. However, these alternatives may lack the tight integration with mainframe resources that EdWord provides.
Technical
For mainframe products: Does this run in an LPAR?
EdWord runs directly on z/OS, z/VM, and zVSE/VSEn mainframe operating systems. It typically operates within an LPAR (Logical Partition) on the mainframe.
What infrastructure is required?
EdWord requires a compatible mainframe environment running z/OS, z/VM, or zVSE/VSEn. It may also require specific subsystems or libraries depending on its features and integration requirements.
Does EdWord have an API?
While specific API details are not available, EdWord likely provides interfaces for interacting with other mainframe systems and applications. These interfaces could be in the form of callable subroutines or data exchange mechanisms.
What are the main components of EdWord?
EdWord's architecture likely includes components for document editing, formatting, storage, and printing. These components communicate through internal interfaces and system calls within the mainframe environment.
Business Value
What is the business value of EdWord?
EdWord provides value by enabling users to create and manage documents directly within the mainframe environment, reducing the need for data transfer and improving workflow efficiency. This can lead to cost savings and improved productivity.
What happens if we do not use EdWord?
Without EdWord, organizations might rely on less integrated solutions, requiring data to be transferred between mainframe and non-mainframe systems for word processing. This can introduce delays, errors, and security risks.
How does EdWord integrate with other systems?
EdWord integrates with the mainframe environment, allowing users to access and incorporate data from mainframe databases and applications directly into their documents. This tight integration streamlines workflows and reduces the risk of errors.
Security
How does EdWord handle security?
EdWord leverages the security features of the mainframe environment, including authentication mechanisms like RACF, ACF2, or Top Secret. Access to documents and functions can be controlled through these security systems.
What access control model is used?
EdWord likely uses an access control model based on the mainframe's security system (RACF, ACF2, Top Secret), allowing administrators to define user permissions and restrict access to sensitive documents and functions.
How is data encrypted?
Data at rest within EdWord is protected by the mainframe's storage security features. Data in transit is secured using standard mainframe communication protocols.
What audit/logging capabilities exist?
EdWord's audit and logging capabilities are integrated with the mainframe's security and system logging facilities, providing a record of user activity and system events for security monitoring and compliance purposes.
Operations
How is EdWord deployed?
EdWord is typically deployed on-premise within the organization's mainframe environment. It requires technical expertise in mainframe systems administration and security to implement and maintain.
What ongoing operational requirements exist?
Ongoing operational requirements include monitoring system performance, managing user access, applying security patches, and performing regular backups. Mainframe systems programmers and administrators are typically responsible for these tasks.
What are common implementation challenges?
Common implementation challenges include integrating EdWord with existing mainframe security systems, configuring access controls, and ensuring compatibility with other mainframe applications.
Ready to Start Your Migration?
Download our comprehensive migration guide for EdWord or calculate your ROI.