Embedded SQL in COBOL (was: If you were inventing CoBOL...)

From: Lko Willms (lw-nospam_at_t-online.de)
Date: 09/22/04 

Date: Wed, 22 Sep 2004 10:35:15 +0200 (MES)

On Tue, 21 Sep 2004 21:52:11 GMT, Robert Wagner wrote:

>
>It's not clear what you mean by arbitrary. If the SQL is talking
>through an ODBC driver, it can access any brand of relational
>database, indexed file, sequential file or spread***.
>
>It's not possible to separate the pre-processor from the runtime
>because there's no standard for runtimes.

   When the compiler provides an ODBC client driver, i.e. a facility to send
SQL commands to an ODBC server, the compiler could do it by itself without an
preprocessor, isn't it? I would prefer that.

   I had worked with ESQL in COBOL using the UCOB, i.e. COBOL-85, compiler
for Unisys OS/1100 (Clearpath IX), and that did not require a preprocessor.
The compiler called the RDMS runtime system to check the validity of the
commands and table references.

   Since an ODBC client is initially detached from the database server, the
compiler could work the same way, don't you think so?

Yours,
L. Willms
------------------------------ all rights reserved ------------------------