Re: Overlay an External DS

[cozzi@xxxxxxxxx]

I was referring to the example I provided that solved your program.
In my example the field needed to be a stand-alone field. I wasn't
talking about your original example.

-Bob


> 
> I don't think so, SEU (yeah yeah, I know...) won't permit the
overlay
> keyword on the field if I mark it as stand alone.  Besides,
whenever
> I've used overlay before it has been inside a DS, I just never did
it
> with an External DS before. 
> 
> Is it maybe because the External DS fields already have names?  I
> wouldn't think that matters, but at this point I'd believe almost
> anything.
> 
> Joel
> http://www.rpgnext.com
> 
> 
> On Wed, 2003-08-06 at 16:02, cozzi@xxxxxxxxx wrote:
> > The EXTDSOVR field should be a stand-alone field "S". Sorry.
> > 
> > -Bob
> > 
> > 
> > > 
> > > I'm trying to overlay an external DS that gets populated by an
> SQL
> > > statement.  When I do NOT include the data, the DS is populated
> > > correctly: if I add the overlay, the DS is blank even though
the
> > SQL
> > > statement has no trouble finding the record.
> > > 
> > > <psuedo-code>
> > > 
> > > // this way extDS gets populated
> > > d extDS        e ds                            extname(EXTDS)
> > > ...
> > > c/exec SQL
> > > c+   Fetch next 
> > > c+    from myCursor 
> > > c+    into :extDS
> > > c/end-exec
> > > 
> > > // this way extDS (and hence extDSovr) does NOT get populated
> > > // elem is the correct number of fields in EXTDS
> > > // All fields in EXTDS are defined the same: 100a
> > > d extDS        e ds                            extname(EXTDS)
> > > d extDSovr                             100a    overlay(extDS)
> > > %dim(elem)
> > > ...
> > > c/exec SQL
> > > c+   Fetch next 
> > > c+    from myCursor 
> > > c+    into :extDS
> > > c/end-exec
> > > 
> > > </psuedo-code>
> > > 
> > > Any idea why this is happening or even better how to fix it?
> > > 
> > > Thanks!
> > > 
> > > Joel
> > > http://www.rpgnext.com
> > > 
> > > 
> > > _______________________________________________
> > > This is the RPG programming on the AS400 / iSeries (RPG400-L)
> > > mailing list
> > > To post a message email: RPG400-L@xxxxxxxxxxxx
> > > To subscribe, unsubscribe, or change list options,
> > > visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> > > or email: RPG400-L-request@xxxxxxxxxxxx
> > > Before posting, please take a moment to review the archives
> > > at http://archive.midrange.com/rpg400-l.
> > _______________________________________________
> > This is the RPG programming on the AS400 / iSeries (RPG400-L)
> mailing list
> > To post a message email: RPG400-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> > or email: RPG400-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/rpg400-l.
> 
> _______________________________________________
> This is the RPG programming on the AS400 / iSeries (RPG400-L)
> mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.