What infrastructure was required?

DisplayWrite/370 required an IBM mainframe system running the MVS (Multiple Virtual Storage) operating system and the CICS (Customer Information Control System) transaction processing system. It also needed sufficient storage and memory resources to support the application and its associated data.

For mainframe products: Did this run in an LPAR?

Yes, DisplayWrite/370 ran within an LPAR (Logical Partition) on an IBM mainframe. It was dependent on the z/OS operating system and required the CICS subsystem to be active and configured correctly.

Was this a standalone product or did it extend/enhance another product?

DisplayWrite/370 was a standalone application, although it integrated with the CICS environment for transaction processing and data access. It did not directly extend or enhance another specific product but relied on the underlying mainframe infrastructure.

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

DisplayWrite/370 required the MVS operating system, the CICS transaction processing system, and sufficient storage and memory resources. It also needed appropriate terminal emulators or access methods for users to interact with the application.

What business problem did it solve?

DisplayWrite/370 provided value by enabling users to create and edit documents directly on the mainframe, reducing the need to transfer files to other systems for word processing. This improved efficiency and security for organizations that needed to manage sensitive information within the mainframe environment.

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

If an organization did not use DisplayWrite/370, they would need to rely on alternative methods for creating and editing documents, such as transferring data to personal computers or using other text editors available on the mainframe. This could introduce inefficiencies, security risks, and compatibility issues.

What was the typical licensing model?

The typical licensing model for DisplayWrite/370 was likely a perpetual license based on the number of users or processors. The total cost of ownership would include the initial license fee, ongoing maintenance costs, and the cost of hardware and system software required to run the application.

How was security handled?

DisplayWrite/370 leveraged the security features of the underlying MVS and CICS environments. Access control was managed through CICS transaction security, which allowed administrators to define which users could access specific functions and data within the application. Data was protected by the mainframe's security mechanisms.

What specific authentication methods were supported?

DisplayWrite/370 likely supported authentication methods provided by the CICS environment, such as user IDs and passwords. It integrated with the mainframe's security system, such as RACF (Resource Access Control Facility), to manage user authentication and authorization.

What access control model was used?

DisplayWrite/370 used an access control model based on CICS transaction security and the underlying mainframe security system (e.g., RACF). This allowed administrators to define which users could access specific transactions and resources within the application.

How was this product typically deployed?

DisplayWrite/370 was typically deployed on-premise within an organization's mainframe data center. It required technical expertise in MVS, CICS, and mainframe operations to implement and maintain.

What ongoing operational requirements existed?

Ongoing operational requirements for DisplayWrite/370 included monitoring system performance, managing user access, applying software updates, and ensuring the availability of the CICS environment. It required skilled mainframe operators and system programmers.

What were common implementation challenges?

Common implementation challenges for DisplayWrite/370 included ensuring compatibility with existing CICS applications, configuring security settings correctly, and providing adequate training for users accustomed to modern word processing software.

Share Your Product Experience

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

Share Your Experience

DisplayWrite/370 for MVS/CICS

IBM Not Supported z/OS

Browse and Edit Content Books and Documents CICS

Vendor

IBM

Product Overview

DisplayWrite/370 for MVS/CICS was a word processing application designed for IBM mainframe systems, operating within the CICS transaction processing environment. It provided WYSIWYG editing capabilities, enabling users to create, modify, and format documents directly on the mainframe. The architecture comprised components tightly integrated with CICS, leveraging its transaction management and security features.

Data was stored and managed within the mainframe's storage infrastructure. Given the end of support for DisplayWrite/370, organizations must migrate to alternative solutions. This includes modern word processing applications or enhanced terminal emulators for mainframe environments.

The migration architecture should consider data migration strategies, integration with existing systems, security requirements, and user experience. Key architectural components to evaluate include data storage, application servers, security infrastructure, and network configurations. Ensure that the new architecture aligns with business requirements and provides a scalable and secure platform for document creation and management.

Frequently Asked Questions

What does DisplayWrite/370 for MVS/CICS do?

DisplayWrite/370 for MVS/CICS was a word processing application that ran on IBM mainframe systems using the CICS transaction processing system. It provided WYSIWYG (What You See Is What You Get) editing capabilities for creating and modifying documents directly on the mainframe.

Is this a system, application, or tool?

DisplayWrite/370 was an application designed for word processing. It provided a user interface and functionality for creating, editing, and formatting documents.

What types of organizations used this?

Organizations that relied on IBM mainframe systems for their core business operations and required word processing capabilities within the CICS environment used DisplayWrite/370. These were typically large enterprises in industries such as banking, insurance, and government.

When should we have considered DisplayWrite/370?

Companies that had a significant investment in IBM mainframe infrastructure and needed a word processing solution tightly integrated with their CICS-based applications would consider using DisplayWrite/370. It was particularly useful when document creation and management needed to occur directly on the mainframe.

What are the alternatives to DisplayWrite/370 for MVS/CICS?

Alternatives to DisplayWrite/370 include modern word processing software such as Microsoft Word, Google Docs, or LibreOffice Writer. For mainframe environments, other text editors and document management systems could be used, although they might not offer the same WYSIWYG capabilities within CICS.

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

DisplayWrite/370 for MVS/CICS

Product Overview

Frequently Asked Questions

What does DisplayWrite/370 for MVS/CICS do?

Is this a system, application, or tool?

What types of organizations used this?

When should we have considered DisplayWrite/370?

What are the alternatives to DisplayWrite/370 for MVS/CICS?

What infrastructure was required?

For mainframe products: Did this run in an LPAR?

Was this a standalone product or did it extend/enhance another product?

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

What business problem did it solve?

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

What was the typical licensing model?

How was security handled?

What specific authentication methods were supported?

What access control model was used?

How was this product typically deployed?

What ongoing operational requirements existed?

What were common implementation challenges?

Related Products

More from IBM

Access 1

ACF/NCP

ACF/SSP

ACO SolutionPac

Ada/370

ADF II

Similar Products

(E)JES

3270 SUPEROPTIMIZER/CICS

Access Manager for CICS

ACCOLADE

ACI Host Link

ADS for CICS

Help Improve This Directory

Share Your Product Experience