|
Charles,
I think you were lucky that it worked. In the caller you have field P@ERR defined as 1 byte. When you call CADATE you are passing a pointer to this field. Now when CADATE puts '123' in the memory that the pointer points at, the '1' ends up in field P@ERR, but '23' ends up in whatever variable happens to sit next to P@ERR. It is quite possible that in the memory layout that the RPG III compiler generated this did no harm, while in the RPG IV layout it did.
Joep Beckeringh
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.