|
c-treeACE for COBOL is a sophisticated file system designed as a replacement for the default COBOL file systems.
The COBOL & SQL Challenge
|
|
Do you need simultaneous access to data using COBOL standard file IO routines and SQL? The very nature of COBOL data and the record definitions (including redefines) do not fit into a traditional RDBMS (SQL based) paradigm of table and record definitions. FairCom engineers overcame this with a unique solution that provides robust SQL access without imposing limitations on the existing COBOL application.
The c-treeACE for COBOL Advantage
|
|
The advantages of using c-treeACE for COBOL compared with other non-SQL based file systems can be summarized as better performance, better stability, and enhanced features. But there is a big advantage that none of the other non-SQL based solutions have: efficient and complete SQL access for the COBOL files.
File system details
|
|
By design, a COBOL runtime will interface with any file system that stores and retrieves record buffers, taking advantage, when requested, of indexes over these record buffers. That's exactly what FairCom’s c-treeACE ISAM interface does. Therefore it was natural to implement the required COBOL-specific interfaces and give COBOL access to c-tree.
Simple Yet Sophisticated File System Replacement
The functionality provided by the standard COBOL file systems is in some cases unable to satisfy modern application needs. Often, developers are forced to migrate to complex and expensive relational systems. These systems have a heavy impact on the COBOL applications both in terms of performance and code modifications.
 The FairCom solution maintains the simplicity of the standard COBOL file system interface while offering COBOL developers high-end database technology with features such as transaction processing and the client/server model. Existing applications will work with c-treeACE for COBOL without the need to recompile. In fact, c-treeACE for COBOL has been designed to fit ACUCOBOL-GT’s file system and Micro Focus’ ExtFH architectures and can therefore act as a replacement for the default file system. Developers will have the flexibility to choose which file system to use on a file by file basis.
In addition c-treeACE for COBOL transparently allows access to data used by your COBOL application using SQL and other FairCom interfaces such as ODBC, JDBC, and ADO .Net drivers.
|
Features
- Supports ACUCOBOL-GT Version 6.1.0 or later.
- Supports Micro Focus COBOL and other COBOL dialects through the standard Callable File Handler interface (ExtFH).
- Developed according to the ACUCOBOL-GT specifications and has no limitations with respect to the Vision file system. The "I$IO" call is fully supported.
- No need to recompile your application.
- Integrated as an additional file system. The file and path management is transparent for both Vision and c-treeACE files. The details for handling c-treeACE files are specified in the c-treeACE configuration file.
- Both c-treeACE and other file handlers co-exist in the same application allowing the conversion of data on-the-fly from one file system to the other.
- Supports READ-ONLY file access for applications storing data on CD-ROM (demo, etc.)
- Provides "ctutil" that implements the same functionalities of the well-known vutil utility of Vision. The ctutil capabilities are directly accessible to the COBOL runtime without the need of a SYSTEM call.
- Native COBOL record support (no DCI related record buffer conversion that slows down COBOL applications).
- SQL support on native COBOL records even on tables with redefined records (multiple records format).
- The cross-platform nature of the c-treeACE Engine makes it easy to offer client/server support across multiple platforms including Windows, Linux, Solaris, Mac OS X, AIX, HP-UX and others.
- The c-treeACE Engine includes industrial quality, on-line transaction processing (OLTP) features that guarantee ACID (atomicity, consistency, isolation, durability) properties of transactions that can be activated on any table while being transparent to the application.
|
|
