Re: EVAL-CORR

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

Rory

I think EVAL-CORR is a good "all-the-time" option, since it devolves to 
EVAL when the structures are identical, according to the Reference. Best 
of both worlds!

Vern

On 1/3/2011 11:27 AM, Rory Hewitt wrote:
> David,
>
> As Dennis pointed out, doing a simple EVAL (RecordOut = RecordIn) will
> simply copy the bytes, starting at the left-most byte.
>
> However, if you either specifiy LIKEREC(*ALL) for both record formats or use
> EXTNAME rather than LIKEREC, then you could simply use EVAL. So a follow-up
> question would be why you're not using either of those methods - what
> exactly are the differences between RecordIn and RecordOut? In the vast
> majority of cases, they would be the same (for database files)...
>
> Rory
>
> p.s. There's nothing *wrong* with EVAL-CORR, but it's pretty rare that you'd
> need it.
>
> On Mon, Jan 3, 2011 at 6:02 AM, David FOXWELL<David.FOXWELL@xxxxxxxxx>wrote:
>
> > I was looking at the code I wrote last year. Well, last week actually, but
> > it seemed a long time ago. There I was, like the next developper called upon
> > todo the maintenance, and I said to myself, "Why has he put EVAL-CORR? -
> > that would suggest that the two DS were not the same". So, I went back to a
> > move, as in my OP but then asked myself if was safe, hence my question.