DisplayWrite/370 for MVS/CICS Modernization Guide

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.