|
midrange.com
Jim,
What usually changes is that a list entry gets a nifty new field added to
the end of each list entry. If
1) You do not need this new field(s)
2) You use the 'list entry size' as defined by the General Header,
comparing this to
3) Pay attention to your data structure size
Then generally you will not have a problem.
Golden rule number 1 is never, ever violate rule number 2 except to match
your data structure size.
Once all your supported machines are up to the newer release then update
your format, and recompile to use the new data structure, if you have the
inclination.
This would then act much like a CPYF *MAP *DROP would.
One advantage to using pointers instead of QUSRTVUS is that you change the
base of your datastructure, incrementing it by the 'list entry size'. And
it automatically ignores the new fields. Instead of using QUSRTVUS to try
to force the '50 pounds of mud into a 5 pound sack'. (As quoted by Dolly
Parton when her dress split on a live awards show.)
Rob Berendt
==================
A smart person learns from their mistakes,
but a wise person learns from OTHER peoples mistakes.
Jim Langston
<jimlangston@conexfr To: RPG400-L@midrange.com
eight.com> cc:
Sent by: Subject: Re: Resolution to
my MCH3601 problem
owner-rpg400-l@midra
nge.com
05/31/01 12:52 PM
Please respond to
RPG400-L
Bruce,
From what I understand of this tread, never coding it myself, even if it
was coded as suggested, wouldn't the program still have to be recompiled
to include the new structure as described in the header file?
So wouldn't the change to the API need to be in the APIs by release?
Or is there something I'm not understanding about the issue. I have
started
to use some API's myself and this topic is of interest to me.
Regards,
Jim Langston
Me transmitte sursum, Caledoni!
bvining@vnet.ibm.com wrote:
>
<SNIP>
> And yes, change flags (though no longer vertical lines in the margin)
> continue to exist in the online API docs. As for a summary booklet
> of what might affect existing programs, the manual for that is the
> Memo to Users. The Memo to Users however does not point out changes
> to APIs that can impact improperly coded programs (like inadvertently
> retrieving 1000 bytes of data to a structure sized for 500).
>
> Bruce
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---
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.
