Re: The SAGA or is it Soap Opera Continues

Hi Sam,

Yes this is exactly my problem. I think you mean 'unique definitions'.

Vern

I said different modules, I meant different procedures.

This is from IBM APAR site.

Frank

DESCRIPTION OF PROBLEM FIXED FOR APAR SE18964 :
-----------------------------------------------
Received call from customer saying that some compiles still
weren't working. Discussed with DEV's, they recommended two
more
PTF's SI16489 SI16420. Customer applied those two PTF's and
compiles are still failing with:
SQL0312 30 713 Position 24 Variable PROJREC not defined or not
usable.
SQL0314 35 1255 Position 42 Host variable PROJNO not unique.
Discussed with DEV's again and it appears that there is a change
at R530 that doesn't allow duplicate variable definitions
according to the following:
The programming with host languages book, chapter 6, section
Using host variables in ILE RPG for iSeries applications that
use SQL states that "The names of host variables must be unique
within the program, even if the host variables are in different
procedures." The precompiler did change the way it handles
duplicate names in v5r3. Previously, the type of a duplicate
name was not dependable and may even affect data
structures, but the precompiler never gave any warning/error.
Now the precompiler will issue an error.
Development will provide customer a work around so programs will
compile.

From: Samuel J Lennon <lennon_s_j@xxxxxxxxxxx>
As I recall, the SQL pre-compiler rules were tightened up in V5R4
and code that compiled previously may not now compile.
If you have a source member with multiple procedures,
identically named local variables now must have identical definitions.

That wasn't the case on V5R3.

(It has been a while since I ran into this, but I believe I have the facts

substantially correct.)

Sam