Re: joining 2 files in datastructure assignment

I'm aware of the hazards of select *. In this case, it is required, as
its a comparison report between two files.





From: "Alan Campin" <alan0307d@xxxxxxxxx>
To: "RPG programming on the IBM i / System i" <rpg400-l@xxxxxxxxxxxx>
Date: 05/30/2018 02:20 PM
Subject: Re: joining 2 files in datastructure assignment
Sent by: "RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx>



You really need every field from two tables? Very bad form to use Select *
unless you really need every field.

On Wed, May 30, 2018 at 11:07 AM Carel <coteijgeler@xxxxxxxxx> wrote:

You define a DS as C1 but Fetch it in C3

Kind regards,

Carel Teijgeler


Op 30-5-2018 om 20:03 schreef Darren Strong:

I'm trying to figure out a better way to define a datastructure for a
cursor fetch when I have two files joined in an SQL. See the next as

an

example. I'd like to define the datastructure as two external

structures

combined, but the compiler doesn't like it much when I try. What i'm
doing now is specifying each field individually (77 fields in each

file),

so not only is that a lot of fields to define, but I'm currently off
somewhere (not in this example), so I'm having to slowly find where I

made

a mistake, and I'd rather let the compiler do the work.




dcl-ds IPIM_t extname('IPIM') qualified template end-ds;

// I know this doesn't work, but its an example of what

I'm

trying to specify
dcl-ds C1_t qualified template;
F1 likeds(IPIM_t);
F2 likeds(IPIM_t);
end-ds;

dcl-ds C1 likeds(C1_t) INZ;

// Parts in both systems with some kind of difference
exec sql declare C3 cursor for
select t2.*,IPIMX.*
from (select *
from QTEMP/IPIMP
except select *
from QTEMP/IPIMX) t2
join QTEMP/IPIMX
on IPIMX.PARTNUM=t2.PARTNUM;

exec sql open C3;
exec sql fetch C3 into :C3;


___________________________________
Darren Strong
Dekko

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD