Re: Where to post ideas for RPG

On Mon, 2016-08-22 at 11:33 -0400, dlclark@xxxxxxxxxxxxxxxx wrote:

"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 08/22/2016 10:34:06
AM:

"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 08/19/2016 06:27:42
PM:

One possible downside to using SQL is that it doesn't support ...
complex qualified names. So temporary variables would occasionally
have to be set up ...

Yes, why doesn't the SQL precompiler support variable names
with more than one qualifier?

To give you an example, I have the following structures. The SQL
precompiler cannot resolve the TrgMgt_KeyData.Table.Name or
TrgMgt_KeyData.Table.Library variables and I have to use temporary
variables as substitutes.

dcl-ds TrgMgt_KeyData qualified;
Table likeds(TrgMgt_TableQual);
Process char(20);
Feature char(20);
Application char(30);
Company char(5);
end-ds;

dcl-ds TrgMgt_TableQual qualified template;
Name char(10);
Library char(10);
end-ds;

I'm not sure... I seem to recall once trying to use a multi-qualified
name as a reference and it failing. It may be a WDSC-7 issue or a
language issue that may have been changed (I can't test a compilation at
the moment, but having booted by virtual win box...)

In psudo-code, something along the lines of.

D Field like(nameds.anotherds.something)
Generates a "RNF0623E The simple name is not specified correctly."
within the editor.

Now obviously I could short cut to the "anotherds.something" in my
like(...), which I seem to recall did, but at the time I'm sure I had a
reason for wanting something more explicit or it was an issue with a
limitation somewhere else on the version of the OS (5R3?) I was using I
can't remember now.

So this problem isn't/wasn't restricted to SQL.

Sincerely,

Dave Clark
--
int.ext: 91078
direct: (937) 531-6378
home: (937) 751-3300

Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio 45439 USA
(937) 294-5331




*********************************************************************************************
This email message and any attachments is for use only by the named
addressee(s) and may contain confidential, privileged and/or proprietary
information. If you have received this message in error, please
immediately notify the sender and delete and destroy the message and all
copies. All unauthorized direct or indirect use or disclosure of this
message is strictly prohibited. No right to confidentiality or privilege
is waived or lost by any error in transmission.
*********************************************************************************************