SQLBridge

Stable, performant, for COBOL developers

Transfer your data to a relational data base with complete security. SQLBridge, which consists of a range of harmonized tools, allows you to securely transfer VSAM or ISAM data into a relational data base.

Advantages

Transparent data management in SQL

Extraction of data storage layers in COBOL

No alterations to development environments

Independent of specific platforms

Independent of specific data bases

Secure automatic execution

High level of flexibility

Doing so opens up a whole range of new possibilities for your data management:

    • Open up your previously COBOL proprietary ISAM data to other applications transparently. This includes, e.g., Java and .NET applications or data mining tools.
    • Support for transaction concepts.
    • Support for security mechanisms such as user functions and rights.
    • Simplified administration procedures relating to your data stock (back-ups, savepoints, TransactionLog etc.)
    • Ad-hoc SQL requests.
    • Deployment of reporting tools.

The basics

The basic concept behind SQLBridge consists of abstracting accesses to ISAM data in a first step and subsequently outsourcing these to a separate data access layer. This layer includes an I/O distributor module as well as access modules for each file or data base table. Such alterations do not affect the respective application logic nor COBOL programmes’ workflows. The only adjustment at this stage is that browse, read, write, update, and delete functions are now processed via SQLBridge interface functionalities. Any return codes used comply with ISAM standards. Access modules can be made available for both ISAM access and data base access. This allows you to choose between pure ISAM operation, pure data base operation, or a mixed operation mode for your data storage without additional changes to application programmes.

Implementation

The first step is an automated analysis and consolidation phase in which inconsistencies in the application are detected and master data structures are defined using support tools. This is followed by the fully automated implementation of all required programme alterations and the generation of access modules, load and unload programmes, and DDL scripts by our tools. Such a procedure guarantees a high level of security and avoids implementation errors. It is also possible, if desired, to normalise the data base in the 1st normal form as part of the data base I/O module generation. In addition, some optimisations to data base design can be undertaken while the definition of the master data structures takes place. Examples include combining related, structurally identical files in one table or distributing files with differing record types across tables. Depending on the client’s situation, applications can first be adapted to ISAM access modules and then transferred into the data base one file a ta a time on a step-by-step basis. After the initial implementation, our tools take over maintenance of access modules on the basis of previously defined master data structures. The chosen architecture and the flexibility of the tools used enable us to easily implement our customers’ specific requirements.

Who can benefit from SQLBridge?

SQLBridge strictly adheres to the SQL 92 standard. Therefore, SQLBridge can be used with all data bases which support at least this standard. The list includes Oracle, DB2/UDB, MySQL/MariaDB, and Microsoft SQL server. On a COBOL level, SQLBridge is independent of any specific platform. A Windows environment is only required for the maintenance of access modules.