Re: RPG SQL precompiler plans from Roch.

Two of those items I've just submitted DCR's on this week.  And was ready
to submit a DCR on another.

What I think needs to happen is to beat the laziness out of the RPG
precompiler people.  If we force them to document every feature that is
supported in RPG itself but not currently supported in the precompiler than
unless it is in that list then it must be considered a bug.  Thus if it is
a bug then they cannot say that it may be fixed in a future release but
must PTF it back to any currently supported release of OS whose version of
RPG supports that.  This documentation must be stored in the SQL
programming for host languages reference.  The logic being here is that it
would be more work for these lazy buggers to document this in all the
different languages required by that document than to fix the bug in the
first place.  And, then, since it is not a documented limitation then they
have to fix it - post haste!

Also, I saw no mention about host languages being able to retrieve a result
set without the use of the SQL CLI api's.  (Gee, I've just strung 3
acronyms together and they are meaningful {and clean}.)

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



                    jpcarr@tredegar.c
                    om                      To:     rpg400-l@midrange.com
                    Sent by:                cc:
                    rpg400-l-admin@mi       Fax to:
                    drange.com              Subject:     RPG SQL precompiler  
plans from Roch.


                    03/05/2002 08:32
                    PM
                    Please respond to
                    rpg400-l







Just got this from a friend of the SQL design team from Roch.    He said I
could pass it along.

John Carr
--------------------------------


This is in response to the quote:
" The plan to redesign the RPG precompiler has been dropped "

This is only partially true.  Initially a design was being considered that
would have re-engineered the RPG precompiler so that RPG enhancements would
kind of "automatically" be available to the SQL precompoiler.  However,
upon closer examination of this design it was found that it would just
shift the dependency from the SQL development team to the RPG compiler
development team.  Example:  If a new SQL enhancement was added in the
future that required changes from the RPG compiler team, then that feature
would only be made available to RPG SQL programmers if the RPG compiler
team decided to fund that SQL enhancement change (not a guarantee).

The 9 RPG precompiler reqs (see below) gathered from a NEWS/400 web survey
last year were then closely examined.  It was found that the majority of
these enhancements could be delivered for less than the costs of
re-engineering the RPG precompiler.  Given this information along with the
dependency mentioned above. it was determined that the best investment at
this time would be for IBM to just enhance the current RPG precompiler.

The RPG precompiler enhancements that are currently in plan will address
all of the items in the list  below except #1, 6, & 9.   Of the remaining
items, #1 is considered the most important  and it will be considered when
the DB2 plan content is constructed for future OS/400 releases.

1.  Support for using a local variable in a subprocedure as a host variable
in an SQL statement.
2.  Support for host structure in Update statements.
3.  Full support for properly parsing RPG subprocedures.
4.  Full support for the V5 qualified subfield names based on the new RPG
IV D-spec QUALIFIED keyword.
5.  Conditional precompilation: /If, /Define, and other directives.
6.  Support for a structure of host indicator variables.
7.  A precompiler directive to generate an array (or structure) of
indicator variables from a data structure.
8.  Nested /Copy.
9.  Support for /Include.



_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.