• Subject: Re: ILE RPG suggestions
  • From: "Eric N. Wilson" <doulos1@xxxxxxxx>
  • Date: Fri, 9 Jul 1999 16:28:51 -0700

I also agree with the suggestion that SQL precompiler be improved.

For example why can't we bind a cursor to the call of a stored procedure. I
do not want to have to program to the CLI (way too painful)

And why can we not declare an array of host variables and return them to the
caller as a recordset like you can in C. I DO NOT want to create temp tables
and return a cursor to them. (too much overhead)

If the above two things were not possible in other languages on the AS/400
then I would not complain so much. I just want there to be parity between
language implementations on the AS/400. Which has gotten LOADS better since
V3R2. Hans and folks I really appreciate all the work you are doing.

Thanks
Eric

______________________________________________
Eric N. Wilson
President
Doulos Software & Computer Services
2913 N Alder St
Tacoma WA 98407


----- Original Message -----
From: Dave Mahadevan <mahadevan@fuse.net>
To: <RPG400-L@midrange.com>
Sent: Friday, July 09, 1999 9:11 AM
Subject: Re: ILE RPG suggestions


> I love this DS implementation for External defined file formats.   Could
use it
> right now.
>
> Talking of SQL in RPG.  Can this be better implemented?.  For example
currently
> you have to use  all those SQLDA and Fetch and those incredible difficulty
in
> parsing for dynamic SQL.   The CRTSQLRPGI compiler is extremely non
descriptive
> on errors and trying to do debug is another problem altogether.  For
example,
> one field in the fetch ds not agreeing with the select can cause severe
> headaches on a debug.  I am sure others have similar issues with SQL
> implementation within RPG.
>
> Another suggestion, can library name be allowed in the EXTNAME keyword?
>
> Also, data area objects should have the ability of dynamic assignments.
> Currently, you have to explicitly specify the data area name in factor2.
The
> DEFINE  should accept  a field name in the traditional 20 character
> implementation used in API's.
>
> John Carr wrote:
>
> > Speaking of reading into a D/S with a subset of fields; .........
> >
> > I want to have a D/S   with (say)  5 fields from the file,   and then do
a
> > SQL  FETCH
> > and have the FETCH be smart enough to map FIELD NAME TO FIELD NAME !!!!
> > (from file fields  to D/S  fields with same name)
> > Is that so freaking hard ?????
> >
> > I just want to do a fetch into a host D/S without having to specify each
> > field on the fetch verb.
> > Oh Well,    Maybe we will get some MULTI-PASS compiler improvements.
> >
>
> --
> Thank You.
>
> Regards
>
> Dave Mahadevan.. mailto:mahadevan@fuse.net
>
>
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
> * This is the RPG/400 Discussion Mailing List!  To submit a new         *
> * message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
> * from this list send email to MAJORDOMO@midrange.com and specify       *
> * 'unsubscribe RPG400-L' in the body of your message.  Questions should *
> * be directed to the list owner / operator: david@midrange.com          *
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the RPG/400 Discussion Mailing List!  To submit a new         *
* message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
* from this list send email to MAJORDOMO@midrange.com and specify       *
* 'unsubscribe RPG400-L' in the body of your message.  Questions should *
* be directed to the list owner / operator: david@midrange.com          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *


This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].