What types of APIs did Graphical Display and Query Facility expose?

The product did not expose any APIs for external integration. Its functionality was primarily accessed through terminal-based commands and interactions within the z/VM environment. There was no support for REST, SOAP, or other modern API types.

What were the main system components and how did they communicate?

The architecture was centered around the z/VM operating system. Key components included the display interface for terminal interaction, the GDF file processing module, and the data conversion utilities for different input formats. Communication occurred through z/VM system calls and file I/O.

What databases or storage mechanisms were used?

The product utilized GDF files for storing graphical data. These files were created from various input formats. There were no external database dependencies. Data was stored and managed within the z/VM file system.

What administrative interfaces were available?

Administration was performed through the z/VM console and terminal commands. There was no GUI or web console. User management was handled through z/VM user profiles and access control lists. Configuration parameters were set via system configuration files and command-line options.

What business value did Graphical Display and Query Facility provide?

Graphical Display and Query Facility provided a way to visualize and interact with graphic data on mainframe terminals. It enabled users to convert and display graphic files from various sources, enhancing data accessibility and usability within the mainframe environment.

How did Graphical Display and Query Facility facilitate data integration?

By supporting the creation of GDF files from multiple sources, the product facilitated the integration of graphic data from different systems. This allowed users to consolidate and manage graphic information within a single platform.

How did Graphical Display and Query Facility improve user productivity?

The product's ability to display and query graphic documents improved user productivity by providing a direct way to access and manipulate graphic data. This streamlined workflows and reduced the need for manual data conversion or external tools.

What specific authentication methods were supported?

The product did not have built-in security features beyond the z/VM security model. Authentication relied on z/VM user IDs and passwords. Access control was managed through z/VM access control lists (ACLs) and user profiles. There was no specific encryption or audit logging within the product itself.

What access control model was used?

Access control was managed through z/VM's existing security mechanisms, including user profiles and access control lists (ACLs). This allowed administrators to control user access to specific files and resources within the z/VM environment.

What encryption was used and where?

The product itself did not provide encryption capabilities. Security relied on the underlying z/VM system's security features. Data security was dependent on the security configurations of the z/VM environment.

What audit/logging capabilities existed?

Audit and logging capabilities were provided by the z/VM system. The product did not have its own audit logging features. Administrators could leverage z/VM's logging to monitor user activity and system events.

What operational interfaces were available?

Operations were managed through z/VM console commands and terminal interactions. There was no dedicated operations console. Monitoring was performed using z/VM system monitoring tools. Logging relied on z/VM system logs.

How was user management handled?

User management was handled through z/VM user profiles and access control lists. Administrators used z/VM commands to create, modify, and manage user accounts and permissions. There were no specific tools for user management within the product.

What were the main configuration parameters?

Configuration parameters were set via z/VM system configuration files and command-line options. There was no dedicated configuration interface. Administrators modified system settings to customize the product's behavior.

What monitoring/logging capabilities existed?

Monitoring and logging relied on the z/VM system's capabilities. Administrators used z/VM monitoring tools to track system performance and resource usage. Logging was managed through z/VM system logs.

Share Your Product Experience

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

Share Your Experience

Graphical Display and Query Facility

IBM Not Supported z/VM

GUI/Graphics Browse and Edit

Vendor

IBM

Product Overview

The architecture of Graphical Display and Query Facility was centered around the z/VM operating system. Key components included the display interface, GDF file processing module, and data conversion utilities. The display interface handled terminal interactions, allowing users to view and query graphic documents.

The GDF file processing module managed the creation, storage, and retrieval of GDF files. Data conversion utilities facilitated the transformation of various input formats, such as CADAM and APT PUNCH, into GDF files. Communication between components occurred through z/VM system calls and file I/O operations.

The system utilized GDF files for storing graphical data, with no external database dependencies. Administration was performed through z/VM console and terminal commands. Security relied on z/VM user IDs, passwords, and access control lists (ACLs).

The product is not supported. Alternative solutions include IBM GDDM or other graphic viewing software.

Frequently Asked Questions

What was the primary function of Graphical Display and Query Facility?

Graphical Display and Query Facility (GDF) allowed users to view and manipulate graphic documents on mainframe terminals. It supported the creation of GDF files from various sources, including CADAM, APT PUNCH, and GDDM Composition Utility.

What file formats could be used to create GDF files?

Users could create GDF files from several input formats. These included CADAM, APT PUNCH, APT CLFILE, CBDS 2, CATIA, GDDM Composition Utility, and Interactive Chart Utility. This allowed for a wide range of graphic data to be converted and displayed.

What platform was Graphical Display and Query Facility designed for?

The product was designed for use on z/VM systems, enabling users to view and interact with graphical data within the mainframe environment. It provided a bridge between various graphic data sources and mainframe terminals.

What were the main capabilities of Graphical Display and Query Facility?

The product's capabilities included the ability to display and query graphic documents. It also facilitated the creation of GDF files, which could then be used for further processing or display. The product offered a way to manage and visualize graphic data on mainframes.

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

Graphical Display and Query Facility

Product Overview

Frequently Asked Questions

What was the primary function of Graphical Display and Query Facility?

What file formats could be used to create GDF files?

What platform was Graphical Display and Query Facility designed for?

What were the main capabilities of Graphical Display and Query Facility?

What types of APIs did Graphical Display and Query Facility expose?

What were the main system components and how did they communicate?

What databases or storage mechanisms were used?

What administrative interfaces were available?

What business value did Graphical Display and Query Facility provide?

How did Graphical Display and Query Facility facilitate data integration?

How did Graphical Display and Query Facility improve user productivity?

What specific authentication methods were supported?

What access control model was used?

What encryption was used and where?

What audit/logging capabilities existed?

What operational interfaces were available?

How was user management handled?

What were the main configuration parameters?

What monitoring/logging capabilities existed?

Related Products

More from IBM

Access 1

ACF/NCP

ACF/SSP

ACO SolutionPac

Ada/370

ADF II

Similar Products

(E)JES

BIM-EDIT

BrowseMaster

BUDDS

C2J-IDE

CA MasterCat

Help Improve This Directory

Share Your Product Experience