Question 1

What does Displaywrite/370 for TSO do?

Accepted Answer

Displaywrite/370 for TSO was a word processing application that ran under IBM's Time Sharing Option (TSO) on mainframe systems. It allowed users to create, edit, format, and print documents directly from their TSO terminals. It provided features for text manipulation, formatting, and basic document management.

Question 2

Is this a system, application, or tool?

Accepted Answer

Displaywrite/370 for TSO was primarily an application. It provided a set of tools and functions for creating and managing documents within the TSO environment. It was not a system-level utility or a development framework.

Question 3

What types of organizations used this?

Accepted Answer

Organizations that relied on mainframe systems for their core business processes and required word processing capabilities directly within the TSO environment used Displaywrite/370. This often included large enterprises in industries such as finance, insurance, and government. These organizations typically had a significant investment in mainframe infrastructure and a need for centralized document creation and management.

Question 4

When should we consider Displaywrite/370 for TSO?

Accepted Answer

Companies should consider alternatives to Displaywrite/370 for TSO. The product is no longer supported, meaning no updates, security patches, or assistance is available. Modern word processing solutions offer enhanced features, better integration with other systems, and improved security.

Question 5

What are the alternatives to Displaywrite/370 for TSO?

Accepted Answer

Alternatives to Displaywrite/370 for TSO include modern word processing applications such as Microsoft Word, Google Docs, and LibreOffice Writer. These applications offer a wider range of features, better compatibility with different file formats, and support for cloud-based collaboration.

Question 6

What infrastructure is required?

Accepted Answer

Displaywrite/370 for TSO required an IBM mainframe system running the z/OS operating system and the TSO/ISPF environment. It also required sufficient storage space for document files and printer configurations for output. The system needed to be properly configured to allow TSO users to access and run the Displaywrite/370 application.

Question 7

For mainframe products: Does this run in an LPAR?

Accepted Answer

Displaywrite/370 for TSO ran within an LPAR (Logical Partition) on an IBM mainframe. It was dependent on the z/OS operating system and required the TSO/ISPF subsystem to be active. The application utilized standard z/OS services for file access, printing, and user authentication.

Question 8

What are the main system components?

Accepted Answer

The core system components of Displaywrite/370 for TSO included the main application executable, document storage files, printer definition files, and user profile data. These components interacted through standard z/OS system calls and TSO/ISPF services. The application accessed and managed document files stored on mainframe DASD (Direct Access Storage Devices).

Question 9

What types of APIs does this product expose?

Accepted Answer

Displaywrite/370 for TSO did not expose APIs in the modern sense. It was designed to be used interactively through the TSO/ISPF interface. Integration with other systems would typically involve custom-written programs that accessed Displaywrite/370 documents directly through mainframe file access methods.

Question 10

What is the business value of Displaywrite/370 for TSO?

Accepted Answer

The business value of Displaywrite/370 for TSO stemmed from its ability to provide word processing capabilities within the existing mainframe environment. It allowed organizations to create and manage documents in a centralized and controlled manner, leveraging their existing mainframe infrastructure and expertise. However, modern word processing solutions offer greater flexibility, collaboration features, and integration with other business applications.

Question 11

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

Accepted Answer

Using Displaywrite/370 for TSO allowed organizations to maintain a consistent document creation and management process within their mainframe environment. Without it, they would need to rely on alternative word processing solutions that may not integrate as seamlessly with their existing systems or provide the same level of centralized control. This could lead to inefficiencies, inconsistencies, and potential security risks.

Question 12

What is the typical total cost of ownership beyond licensing?

Accepted Answer

Displaywrite/370 for TSO was licensed on a per-machine or per-user basis. The total cost of ownership included the initial license fees, as well as the ongoing costs of mainframe hardware, software maintenance, and IT staff to support the system. Organizations should consider the cost of migrating to a modern word processing solution, including training and potential integration efforts.

Question 13

How is security handled?

Accepted Answer

Displaywrite/370 for TSO leveraged the security features of the z/OS operating system and the TSO/ISPF environment. It supported standard z/OS authentication methods, such as user IDs and passwords, and access control mechanisms, such as RACF (Resource Access Control Facility). Document access was controlled through z/OS dataset security settings.

Question 14

What access control model is used?

Accepted Answer

Displaywrite/370 for TSO utilized the access control model provided by the z/OS operating system. This typically involved using RACF to define user groups and permissions for accessing mainframe datasets containing Displaywrite/370 documents. Access control lists (ACLs) could be used to further refine access permissions at the individual document level.

Question 15

What audit/logging capabilities exist?

Accepted Answer

Displaywrite/370 for TSO relied on the auditing and logging capabilities of the z/OS operating system. Security events, such as failed login attempts and unauthorized access attempts, were logged to the z/OS system log. These logs could be analyzed to detect and investigate security incidents.

Question 16

What ongoing operational requirements exist?

Accepted Answer

Displaywrite/370 for TSO required ongoing operational support, including monitoring system performance, managing user accounts, and performing regular backups of document files. IT staff needed to be trained on the application and the underlying z/OS environment. Common operational challenges included ensuring sufficient storage space for documents, resolving printer issues, and addressing user support requests.

Question 17

What administrative interfaces are available?

Accepted Answer

Displaywrite/370 for TSO provided administrative interfaces through the TSO/ISPF environment. These interfaces allowed administrators to manage user profiles, configure printer settings, and perform other administrative tasks. User management was handled through standard z/OS user administration tools, such as RACF.

Question 18

What monitoring/logging capabilities exist?

Accepted Answer

Monitoring Displaywrite/370 for TSO involved tracking system performance metrics, such as CPU utilization, memory usage, and disk I/O. These metrics could be monitored using standard z/OS monitoring tools. Logging capabilities were provided by the z/OS operating system, which recorded system events and security-related activities.

Share Your Product Experience

Displaywrite/370 for TSO

Product Overview

Frequently Asked Questions

What does Displaywrite/370 for TSO do?

Is this a system, application, or tool?

What types of organizations used this?

When should we consider Displaywrite/370 for TSO?

What are the alternatives to Displaywrite/370 for TSO?

What infrastructure is required?

For mainframe products: Does this run in an LPAR?

What are the main system components?

What types of APIs does this product expose?

What is the business value of Displaywrite/370 for TSO?

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

What is the typical total cost of ownership beyond licensing?

How is security handled?

What access control model is used?

What audit/logging capabilities exist?

What ongoing operational requirements exist?

What administrative interfaces are available?

What monitoring/logging capabilities exist?

Related Products

More from IBM

Access 1

ACF/NCP

ACF/SSP

ACO SolutionPac

Ada/370

ADF II

Similar Products

(E)JES

Almost TSO

Application Support Facility

Application/Fax

BIM-EDIT

BookManager

Help Improve This Directory

Share Your Product Experience