RE: SQL finally "free'd"???

[Gina M Whitney <whitneyg@xxxxxxxxxx>]

> Does it support multiple SQL statements per  exec sql perchance???
> <drools>
No.

>Hopefully they've eliminated the need for /EXEC SQL and /END-EXEC that's
>the most irritating thing.  Having to code that for every line of SQL
>is just as bad as /free and /end-free
Each SQL statement must begin with EXEC SQL and end with a semicolon (;).
The EXEC SQL keywords must be on one line.
The remaining part of the SQL statement can be on more than one line.
Example: An UPDATE statement coded in free form might be coded in the
following way:
EXEC SQL UPDATE DEPARTMENT
                      SET MGRNO = :MGR_NUM
                      WHERE DEPTNO = :INT_DEP;


>Will it generate free format code?  Or will it generate code like the
>following?  I suppose I really shouldn't care about what it does under the

>covers.  My only concern is if this kind of stuff was what was limiting
>some variable types like dimensioned qualified data structures such as
>MyDivision(x).MyPlant(y).MyLocation(z)
>
>C*EXEC SQL
>C* Fetch C1 into :InliblTbl.InliblLib
>C*END-EXEC
>C                   Z-ADD     -4            SQLER6
>C                   CALL      SQLROUTE
>C                   PARM                    SQLCA
>C                   PARM                    SQL_00006
>C     SQL_00009     IFEQ      '1'
>C                   EVAL      INLIBLTBL.INLIBLLIB = SQL_00011
>C                   END
No, it writes out fixed form.  Reading and writing are two completely
different
processes.  Variable types like dimensioned qualified data structures are
not
supported in SQL syntax. It has nothing to do with the precompiler code.