Re: SQL using subprocedure variables - v5r4

Hi,

 

in release V5R2 and before it was already documented, that variables used in
embedded SQL statements must be defined unique in the source, even if they
are defined locally. But it never was checked by the precompiler.

Under release V5R3 the precompiler checks for duplicated variables and
throws an error message with error level 30. 

The only way to get the sources recompiled under release V5R3 is to rename
the host variables.

 

With release V5R4 it is changed again:

Now you can define standalone variables and parameter fields (in procedure
interfaces) that are used in SQL-statement several times. 

If the variables have the same data type and length, they are accepted.

If the variables have the same data type but different length, the
precompiler throws a warning (error level 11).

If the variables are defined differently the precompiler throws an error
with error level 30 

 

Even in release V5R4 data structures and subfields in unqualified data
structures must be unique in the source. If you use always the same data
structure name, to hold the result of a fetch statement in different
procedures, you have to rename the data structures.  

 

... we also have to fight with these "enhancements". 

IMHO all sources that could be compiled in a previous release must be
compilable in a higher release.

 

Birgitta