RE: ...along the embedded SQL path - Question and Comment

["Wilt, Charles" <CWilt@xxxxxxxxxxxx>]

> Now, this doesn't mean you can use a local procedure 
> variable.  That works.  But even though the variable is local 

That should have been "Now, this doesn't mean you CAN'T use a local procedure 
variable."

Sorry,

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
 

> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Wilt, Charles
> Sent: Tuesday, July 12, 2005 10:42 AM
> To: RPG programming on the AS400 / iSeries
> Subject: RE: ...along the embedded SQL path - Question and Comment
> 
> 
> Correct.
> 
> Now for what may be TMI at this point....but
> 
> The precompiler doesn't understand variable scope.  You'll 
> need to make sure that the variable names you use in embedded 
> SQL aren't defined multiple times with different attributes.
> 
> Now, this doesn't mean you can use a local procedure 
> variable.  That works.  But even though the variable is local 
> to the procedure, the precompiler will choke if the same 
> variable name is used someplace else in the source, another 
> procedure or global, and has different attributes.
> 
> 
> Additionally, at v5r2, you could pass a MODS but not a DS 
> array.  v5r3 added support for DS arrays.
> 
> for instance:
> 
> c/exec sql
> c+  fetch from myCursor for 30 rows into :hostDS
> c/end-exec
> 
> In v5r2, hostDS had to be a MODS.  In v5r3, hostDS could be a 
> MODS [OCCUR(30)] or an array [DIM(30)].
> 
> HTH,
> 
> Charles Wilt
> --
> iSeries Systems Administrator / Developer
> Mitsubishi Electric Automotive America
> ph: 513-573-4343
> fax: 513-398-1121
>  
>