EDBC Modernization Guide

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

EDBC allows organizations to leverage their existing mainframe investments while modernizing their application landscape. It reduces the need for costly data migration projects.

EDBC supports authentication methods such as user ID/password and potentially integrates with mainframe security systems like RACF, ACF2, or Top Secret.

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.

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.

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

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

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.

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.