RE: Same Local variable name using like( ) in multiple subprocedures gets SQL0312

Birgitta, we are on 6.1 as of April. The programs compiled under 5.4.0 with the PTF that fixed local scoping. Those objects tested successfully under 5.4.0 and 6.1. Just can't compile that original source now.
Michael

~~~~~~~~~~~~~~~~~

What release are you on?
IIRC local variable scope for the SQL precompiler was not introduced before
release 6.1. (may be with PTFs you can get in on release V5R4M0)

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"

-----Original Message-----

I know several similar issues are in the archives, but I suspect this
one could be solved with a PTF? Or else I need to know the rules...
I have an SQLRPGLE source that the compiler doesn't like (SQL0312 -
Variable not defined or not useable), but it was okay last December in
the v5r4 world. Here's the deal:
A global variable Account# is defined as 10 A.
inline subprocedure #1 defines a local variable "Account"
like(Account#).
Inline subprocedure #2 defines a local variable "Account"
like(Account#).
Precompiler appears to have a limited tolerance for defining Account
with "like(Account#)", because if I just change subprocedure #2 to
explicitly define "Account" as 10 A, it's okay with that.
I recall issues with locally defining variables of the same name in V5R4
until Gina told us about a PTF that made that all better. And when I
first wrote this code, and compiled in v5R4 (with the amazing PTF), it
was cool, even with all subprocedures using like(account). We went 6.1
and supposedly all pertinent PTFs last April. My project was installed
to production this morning, but two programs wouldn't compile
(CRTSQLRPGI) until the "like(Account#)" code was replaced with explicit
"10 A" definitions. (I tried compiling from both WDSC 7.0 and from PDM,
with the same result).

Is there a PTF for 6.1 that makes the Precompiler as smart as it used to
be? If not, do I understand correctly that we can only define a local
variable as "like" in one subprocedure when using the same local
variable name in multiple subprocedures?

Michael Koester