Re: EVAL-CORR

Thanks, Barbara

I had just given that information a rather cursory glance, enough to know I'd be OK with what I was doing, which does have the DS' related with LIKEDS.

In my case, things are rather deeply nested - file info that includes a key list, all also part of a larger state DS! But it all works beautifully with EVAL-CORR.

Happy New Year!
Vern

On 1/5/2011 10:14 AM, Barbara Morris wrote:

On 2011/1/3 8:30 AM, Vern Hamberg wrote:

I just had reason to look at eval-corr - turns out it is smart enough to
do a mass move if the DS' have all the same fields. Nice!

But it does the field-at-a-time if there is a difference, either in
order or name, I guess.

Vern, it only does a mass move if the two DS' are explicitly related
through LIKEDS or LIKEREC. If they are defined separately, and just
happen to have identical subfields, they will still be handled subfield
by subfield.

You can see exactly what will happen from the EVAL-CORR Summary in the
listing.

1 D ds1 ds qualified
2 D subf 1a
3 D ds2 ds qualified
4 D subf 1a
5 D ds2b ds likeds(ds2)
6 /free
7 eval-corr ds2 = ds1;
8 eval-corr ds2 = ds2b;

E V A L - C O R R S u m m a r y
EVAL-CORR summary 1 7
SUBF Assigned; exact match
EVAL-CORR summary 2 8
Both data structures defined with same LIKEDS or LIKEREC