What infrastructure is required?

EDBC requires a mainframe environment running z/OS and the target databases (CA Datacom/DB, DB2, VSAM, IMS, CA IDMS/DB). It also requires a Windows or UNIX system to host the client-side components.

For mainframe products: Does this run in an LPAR?

EDBC runs on z/OS within an LPAR. It is dependent on the z/OS operating system and requires the presence of the target database subsystems.

What APIs does EDBC expose?

EDBC exposes APIs that allow client applications to connect and execute SQL queries against mainframe data sources. The specific API types and protocols used depend on the client-side implementation.

What are the main system components?

The main components of EDBC include the server-side component on the mainframe, the client-side driver on Windows/UNIX, and configuration files that define the data source mappings.

What business problem does it solve?

EDBC solves the business problem of providing access to valuable mainframe data for applications running on distributed platforms. Without it, organizations would face challenges integrating mainframe data with modern systems.

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

If an organization did not use EDBC, they would need to find alternative ways to access mainframe data, such as custom-built integration solutions, which can be costly and complex.

What access control model is used?

EDBC uses an access control model based on user roles and permissions to control access to mainframe datasets. This model may integrate with existing mainframe security systems.

What encryption is used and where?

EDBC uses encryption to protect data in transit between the client and the mainframe server. The specific encryption algorithms used depend on the configuration and supported protocols.

What audit/logging capabilities exist?

EDBC provides audit logging capabilities to track user access and data modifications. These logs can be used for security monitoring and compliance purposes.

What are common implementation challenges?

Implementing EDBC requires expertise in mainframe systems, networking, and security. Common challenges include configuring data source mappings, troubleshooting connectivity issues, and ensuring data security.

What ongoing operational requirements exist?

Ongoing operational requirements for EDBC include monitoring system performance, maintaining data source connections, and applying security patches. Staffing requirements include mainframe systems administrators and database administrators.

What administrative interfaces are available?

Administrative interfaces for EDBC may include a command-line interface (CLI) and potentially a web-based console. User management is typically handled through the mainframe security system.

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

EDBC

Name: EDBC
Availability: InStock

Actian Corporation Active z/OS

Legacy Application/Data Access Databases

Vendor

Actian Corporation

Product Overview

EDBC provides SQL access to mainframe legacy data from Windows and UNIX systems. It acts as middleware, bridging the gap between distributed applications and mainframe databases. This allows organizations to leverage their existing mainframe investments while modernizing their application landscape.

EDBC supports data sources such as CA Datacom/DB, DB2, VSAM, IMS, and CA IDMS/DB. The architecture of EDBC includes a server-side component running on z/OS within an LPAR, client-side drivers installed on Windows or UNIX systems, and configuration files that define the data source mappings. The client-side drivers communicate with the server-side component using network protocols.

EDBC supports authentication methods such as user ID/password and potentially integrates with mainframe security systems like RACF, ACF2, or Top Secret. It uses an access control model based on user roles and permissions to control access to mainframe datasets. Alternatives include IBM Data Server Client and other vendor-specific mainframe data access tools.

Frequently Asked Questions

What does EDBC do?

EDBC provides SQL access to mainframe legacy data from Windows and UNIX systems. It allows applications on these platforms to interact with mainframe databases using standard SQL queries.

Is this a system, application, or tool?

EDBC is middleware. It acts as a bridge between client applications and mainframe databases, translating SQL requests and handling data transfer.

What types of organizations use this?

Organizations that rely on mainframe systems for core business functions and need to integrate that data with distributed applications on Windows or UNIX platforms use EDBC.

When should we consider EDBC?

A company should consider using EDBC when it needs to provide real-time or near-real-time access to mainframe data for applications running on other platforms, or when modernizing applications while retaining mainframe data.

What are the alternatives to EDBC?

Alternatives to EDBC include other data access middleware products, data replication solutions, and custom-built integration solutions. Specific products include IBM Data Server Client, and other vendor-specific mainframe data access tools.

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

EDBC

Product Overview

Frequently Asked Questions

What does EDBC do?

Is this a system, application, or tool?

What types of organizations use this?

When should we consider EDBC?

What are the alternatives to EDBC?

What infrastructure is required?

For mainframe products: Does this run in an LPAR?

What APIs does EDBC expose?

What are the main system components?

What business problem does it solve?

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

How does EDBC provide business value?

What specific authentication methods are supported?

What access control model is used?

What encryption is used and where?

What audit/logging capabilities exist?

What are common implementation challenges?

What ongoing operational requirements exist?

What administrative interfaces are available?

Related Products

Similar Products

Access Manager for CICS

Access Manager for IMS

ADABAS

Adabas SQL Gateway

apX IMS Server

Artix

Help Improve This Directory

Share Your Product Experience