Re: SQL precompiler does not support qualified variables

Andrew,

I like qualified variables because it allows me to have the same variable
name for different meanings.  Let's take trigger programs for an example.
Picture 3 data structures
     D NEW           E DS                  EXTNAME(LOGIN) QUALIFIED
     D OLD           E DS                  LIKEDS(NEW)
     D WORK          E DS                  LIKEDS(NEW)
Put the new buffer into new, the old buffer into old and use the work for
temporary values.  And if the file has a field called LibName then you will
have new.libname, old.libname, work.libname.

I use based on variables.  I have no problem with them, when applicable.
But if I have to do
     D WORK          E DS                  LIKEDS(NEW)
     D MyBasedVar      s                   like(work.libname)
based(pMyBasedVar)
     D pMyBasedVar     s                *
Then that won't work either because MyBasedVar is defined like a qualified
name
I would have to have
     D ThisVar         s               3a
Notice, no like allowed because my like would be like the 'sql intolerant'
qualified name

I suppose I could do:
     D LOGIN         E DS                  EXTNAME(LOGIN)
     D NEW           E DS                  LIKEDS(LOGIN)
     D OLD           E DS                  LIKEDS(LOGIN)
     D WORK          E DS                  LIKEDS(LOGIN)
And the variables in the login datastructure would not be qualified.  Me,
I'd rather they fix the problem versus me having to constantly work around.
Although violence would be temporarily satisfactory.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin