Name: DisplayWrite/370 for CICS/VSE
Availability: InStock

Question 1

What does DisplayWrite/370 for CICS/VSE do?

Accepted Answer

DisplayWrite/370 for CICS/VSE was a word processing application designed for use within the Customer Information Control System (CICS) and Virtual Storage Extended (VSE) environments. It provided users with a what-you-see-is-what-you-get (WYSIWYG) interface for creating and editing documents directly on mainframe systems. It allowed users to create, edit, format, and print documents.

Question 2

Is this a system, application, or tool?

Accepted Answer

DisplayWrite/370 was an application. It provided a user interface and functionality for creating and manipulating documents. It was not a system-level component or a set of development tools, but rather a self-contained application designed for end-user interaction.

Question 3

What types of organizations used this?

Accepted Answer

DisplayWrite/370 was suitable for organizations that relied on mainframe systems for their core business operations and required word processing capabilities within the CICS/VSE environment. These organizations typically included large enterprises in industries such as finance, insurance, and government. It was a good fit when organizations needed to create and manage documents directly on their mainframe systems without transferring data to other platforms.

Question 4

When might a company have considered DisplayWrite/370 for CICS/VSE?

Accepted Answer

A company might have considered using DisplayWrite/370 if they already had a significant investment in mainframe technology and needed a word processing solution that could integrate seamlessly with their existing CICS/VSE environment. It was also a viable option if the organization had strict security requirements that mandated keeping document creation and storage within the mainframe environment.

Question 5

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

Accepted Answer

Alternatives to DisplayWrite/370 include modern word processing software such as Microsoft Word, Google Docs, and LibreOffice Writer. These alternatives offer broader platform compatibility, more advanced features, and better integration with cloud-based services. OpenText Documentum and Alfresco are also alternatives.

Question 6

What infrastructure was required for DisplayWrite/370 for CICS/VSE?

Accepted Answer

DisplayWrite/370 required a mainframe environment running CICS and VSE. It needed sufficient memory and disk space to operate effectively. The system also required appropriate printer configurations to support document printing. It required the CICS and VSE subsystems to be properly configured and running.

Question 7

For mainframe products: Did this run in an LPAR?

Accepted Answer

DisplayWrite/370 operated within the CICS region of the VSE operating system. It did not run in a separate LPAR but rather as an application within the CICS environment. It was dependent on the services provided by CICS and VSE, such as transaction management, security, and data access.

Question 8

What types of APIs did DisplayWrite/370 for CICS/VSE expose?

Accepted Answer

DisplayWrite/370 did not expose APIs in the modern sense (e.g., REST or SOAP). Integration with other systems typically involved file transfer or data exchange using mainframe-specific protocols. It may have supported some level of integration through CICS transaction processing, but this would have been limited compared to modern API-driven integration.

Question 9

What were the main system components of DisplayWrite/370 for CICS/VSE?

Accepted Answer

The main system components of DisplayWrite/370 included the user interface, document processing engine, and print formatting module. These components communicated through internal program calls and data structures within the CICS/VSE environment. Data was typically stored in VSAM files or other mainframe-compatible storage mechanisms.

Question 10

What was the business value of DisplayWrite/370 for CICS/VSE?

Accepted Answer

The primary business value of DisplayWrite/370 was to provide word processing capabilities within the mainframe environment, allowing organizations to create and manage documents without moving data to other systems. This could improve security, reduce data transfer costs, and streamline workflows for organizations heavily invested in mainframe technology. It allowed users to create and manage documents directly on their mainframe systems.

Question 11

What was the typical licensing model for DisplayWrite/370 for CICS/VSE?

Accepted Answer

The licensing model for DisplayWrite/370 was typically a perpetual license based on the number of users or processors. The total cost of ownership included the initial license fee, ongoing maintenance costs, and the cost of mainframe resources required to run the software. Vendor lock-in was a consideration, as migrating documents and workflows to other systems could be complex and costly.

Question 12

How did DisplayWrite/370 for CICS/VSE integrate with enterprise ecosystems?

Accepted Answer

DisplayWrite/370 integrated with enterprise ecosystems primarily through file transfer and data exchange mechanisms common in mainframe environments. It could also integrate with other CICS applications through transaction processing. However, it did not offer the same level of integration with modern cloud-based services and applications as contemporary word processing software.

Question 13

What specific authentication methods were supported?

Accepted Answer

DisplayWrite/370 relied on the security features provided by the CICS and VSE environments. Authentication was typically handled through CICS user IDs and passwords. Access control was managed through CICS transaction security and resource access control facilities. Encryption was not a standard feature of DisplayWrite/370 itself, but could be implemented through underlying CICS or VSE security mechanisms.

Question 14

What access control model was used?

Accepted Answer

DisplayWrite/370 used the access control model provided by CICS, which was primarily based on transaction security and resource access control. This allowed administrators to control which users could access specific DisplayWrite/370 functions and data. The access control lists (ACLs) managed by CICS determined user permissions.

Question 15

What audit/logging capabilities existed?

Accepted Answer

Audit and logging capabilities in DisplayWrite/370 were typically provided by the underlying CICS and VSE environments. CICS could be configured to log transaction activity, including access to DisplayWrite/370 functions and data. These logs could be used to track user activity and identify potential security breaches.

Question 16

What ongoing operational requirements existed?

Accepted Answer

Ongoing operational requirements for DisplayWrite/370 included monitoring the CICS and VSE environments to ensure availability and performance. Regular maintenance was required to apply software updates and fix any issues. Staffing requirements included system administrators familiar with CICS and VSE, as well as end-users trained in the use of DisplayWrite/370.

Question 17

How was user management handled?

Accepted Answer

User management in DisplayWrite/370 was handled through the CICS environment. User IDs and passwords were created and managed within CICS. Access to DisplayWrite/370 functions and data was controlled through CICS transaction security and resource access control facilities. The CICS administrator was responsible for managing user accounts and permissions.

Question 18

What administrative interfaces were available?

Accepted Answer

Administrative interfaces for DisplayWrite/370 were primarily command-line interfaces (CLIs) provided by CICS and VSE. These interfaces allowed administrators to configure CICS parameters, manage user accounts, and monitor system performance. There was no dedicated GUI or web console for DisplayWrite/370 administration.

Are You a Vendor? Claim Your Listing

DisplayWrite/370 for CICS/VSE

Product Overview

Frequently Asked Questions

What does DisplayWrite/370 for CICS/VSE do?

Is this a system, application, or tool?

What types of organizations used this?

When might a company have considered DisplayWrite/370 for CICS/VSE?

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

What infrastructure was required for DisplayWrite/370 for CICS/VSE?

For mainframe products: Did this run in an LPAR?

What types of APIs did DisplayWrite/370 for CICS/VSE expose?

What were the main system components of DisplayWrite/370 for CICS/VSE?

What was the business value of DisplayWrite/370 for CICS/VSE?

What was the typical licensing model for DisplayWrite/370 for CICS/VSE?

How did DisplayWrite/370 for CICS/VSE integrate with enterprise ecosystems?

What specific authentication methods were supported?

What access control model was used?

What audit/logging capabilities existed?

What ongoing operational requirements existed?

How was user management handled?

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