What infrastructure was required?

DisplayWrite/370 ran on IBM's VM/CMS operating system, which typically ran on IBM mainframe systems. It required the CMS environment to be present and configured.

For mainframe products: Did this run in an LPAR?

As a mainframe product, DisplayWrite/370 would typically run within an LPAR (Logical Partition) on an IBM mainframe. It was not directly z/OS dependent but required the VM/CMS environment to function.

Was this a standalone product?

DisplayWrite/370 was a standalone application, although it likely integrated with other CMS utilities for printing and file management. It did not extend or enhance another specific word processing product.

What were the common commands?

Common commands in DisplayWrite/370 would have included commands for creating a document, editing text, formatting paragraphs, saving files, and printing. Specific command syntax would be detailed in the DisplayWrite/370 documentation.

What was the business value?

The business value of DisplayWrite/370 was in providing a word processing solution for organizations already invested in IBM's VM/CMS environment. It allowed them to create and manage documents using a familiar interface and feature set.

What vendor lock-in considerations existed?

Organizations using DisplayWrite/370 likely faced vendor lock-in due to their reliance on IBM's VM/CMS environment. Migrating to a different word processing solution could require significant effort and investment.

How did this product integrate with enterprise ecosystems?

DisplayWrite/370 likely integrated with other components of the VM/CMS environment, such as file management systems and printing services. Specific integration capabilities would be detailed in the product documentation.

How was security handled?

Security in DisplayWrite/370 would have been managed through the VM/CMS operating system's security features. This would include user authentication and access controls to protect documents and prevent unauthorized access.

What authentication methods were supported?

Authentication methods would have been those supported by the VM/CMS operating system, such as user IDs and passwords. Specific authentication protocols would depend on the CMS configuration.

What access control model was used?

The access control model would have been based on the capabilities provided by VM/CMS, likely involving access control lists (ACLs) to manage permissions for files and resources.

How was this product typically deployed?

Deployment of DisplayWrite/370 involved installing the software on a VM/CMS system. This typically required technical expertise in VM/CMS administration and mainframe operations.

What ongoing operational requirements existed?

Ongoing operational requirements would have included monitoring the VM/CMS environment, performing system maintenance, and providing user support for DisplayWrite/370. This required skilled mainframe operators and system administrators.

What administrative interfaces were available?

Administrative interfaces would have been those provided by the VM/CMS operating system, such as command-line interfaces and system administration tools. User management and configuration were handled through CMS commands and utilities.

Are You a Vendor? Claim Your Listing

Take control of your product listings. Add verified information, showcase updates, and unlock a Claimed Vendor badge across the directory.

Claim Your Listing Now

DisplayWrite/370 for VM/CMS

IBM Not Supported z/VM

Browse and Edit Content Books and Documents

Vendor

IBM

Product Overview

DisplayWrite/370 for VM/CMS was a word processing application designed for IBM's VM/CMS operating system, commonly deployed in mainframe environments. Its architecture was tightly integrated with VM/CMS, utilizing its file management and printing services. The application ran within an LPAR on an IBM mainframe, requiring the CMS environment to function.

Security was managed through VM/CMS's security features, including user authentication and access control lists (ACLs). Given its obsolete status, organizations should plan a migration to modern alternatives. A recommended architecture involves transitioning to cloud-based solutions like Google Docs or desktop applications like Microsoft Word or LibreOffice Writer.

This requires converting existing documents to compatible formats and integrating with modern identity management systems. The new architecture should prioritize security, scalability, and ease of integration with existing enterprise systems. Consider implementing a phased migration to minimize disruption and ensure data integrity.

Frequently Asked Questions

What does DisplayWrite/370 for VM/CMS do?

DisplayWrite/370 for VM/CMS was a word processing application that ran on IBM's VM/CMS operating system. It allowed users to create, edit, format, and print documents. It was primarily used for office and administrative tasks involving document creation and management.

Is this a system, application, or tool?

DisplayWrite/370 was an application. It provided a user interface and functionality specifically for word processing tasks, unlike a system or a tool set that offers broader capabilities.

What types of organizations used this?

Organizations that relied on IBM's VM/CMS operating system for their computing infrastructure were the primary users of DisplayWrite/370. These included large enterprises, government agencies, and academic institutions that had invested in IBM mainframe technology.

When should we have considered DisplayWrite/370 for VM/CMS?

A company might have considered DisplayWrite/370 if they were already using VM/CMS and needed a word processing solution tightly integrated with that environment. It provided a familiar interface and feature set for users accustomed to IBM's mainframe ecosystem.

What are the alternatives to DisplayWrite/370 for VM/CMS?

Alternatives to DisplayWrite/370 include modern word processing software such as Microsoft Word, Google Docs, and LibreOffice Writer. These applications offer broader platform support, cloud integration, and more advanced features.

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

Are You a Vendor? Claim Your Listing

DisplayWrite/370 for VM/CMS

Product Overview

Frequently Asked Questions

What does DisplayWrite/370 for VM/CMS do?

Is this a system, application, or tool?

What types of organizations used this?

When should we have considered DisplayWrite/370 for VM/CMS?

What are the alternatives to DisplayWrite/370 for VM/CMS?

What infrastructure was required?

For mainframe products: Did this run in an LPAR?

Was this a standalone product?

What were the common commands?

What was the business value?

What vendor lock-in considerations existed?

How did this product integrate with enterprise ecosystems?

How was security handled?

What authentication methods were supported?

What access control model was used?

How was this product typically deployed?

What ongoing operational requirements existed?

What administrative interfaces were available?

Related Products

More from IBM

Access 1

ACF/NCP

ACF/SSP

ACO SolutionPac

Ada/370

ADF II

Similar Products

(E)JES

Application Support Facility

Application/Fax

BIM-EDIT

BookManager

BookMaster

Help Improve This Directory

Share Your Product Experience