|
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.
-----Message d'origine-----
De : rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] De la part de Vern Hamberg
Envoyé : lundi 3 janvier 2011 14:30
À : RPG programming on the IBM i / System i
Objet : Re: EVAL-CORR
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
On 1/3/2011 4:35 AM, Dennis Lovelady wrote:
Depending upon what the differences are, you probably needeval-corr.
Remember that an eval will do a left-to-right (or r-l)move. It does
not respect field names et al.enterprises
Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"Nothing is more humiliating than to see idiots succeed in
we have failed in."create a new one.
-- Flaubert
This is some code to read a file and copy the row to
( MyFormat :I notice that when compiling, the DS obtained from LIKEREC
--*INPUT ) is not the same as LIKEREC ( MyFormat : *OUTPUT ).
Therefore, in the example below, is it safe to use RecordOut =
RecordIn or is EVAL-CORR necessary?
Thanks.
This is the RPG programming on the IBM i / System i
(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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.