Re: SQL1003-Nested /COPY statements not allowed.

["David Morris" <dmorris@xxxxxxxxxxxxx>]

Rob,

The SQL compiler has historically been about 1 release behind the latest RPG 
compiler.  
Lately it has gotten even worse.  It was recommended to me that I send in the 
comment 
card at the back of the manual.  I didn't even get a response.  I haven't got a 
complete 
list for this release, but the /copy, as you have discovered is a limitation.  
What I ended 
up doing was creating an SQL select module that supported dynamic output.  I 
then call 
procedures that contain the SQL SELECT, FETCH, etc. statements.  This has 
reduced 
our reliance on SQL modules.

New features that have lagged in the past include long field names, nested 
/copy, allow null, 
CVTOPT for date, time and varchar conversion, local variable naming problems, 
and debug 
views.  I am sure I have left out quite a few.

David Morris

>>> Rob Berendt <rob@dekko.com> 03/17/99 08:32AM >>>
I am trying to create an RPG program with imbedded SQL.  I am getting the above 
error message.

If I take the following program, as RPGLE, it compiles successfully:
 /DEFINE HSpec                                                     
 /COPY ROUTINES/QRPGLESRC,HSPEC                                    
 /UNDEFINE HSpec                                                   
                                                                   
C                   seton                                        lr

As SQLRPGLE it generated the SQL1003.

The contents of HSPEC does another /COPY.

Any one else feel that this is a stupid crippling limitation?  I have a problem 
opened with IBM.  I am hoping I do not get the dreaded
'working as designed'.

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* 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          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *