|
-----Original Message-----that
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of David Gibbs
Sent: Thursday, March 12, 2009 2:48 PM
To: Midrange Systems Technical Discussion
Subject: Re: Odd CALLPRC behavior when using RPG indicator with RTNVAL
David Gibbs wrote:
I'll call IBM tomorrow and open a PMR.
IBM's response:
The difference in behavior in V6R1 and later releases is due to a change
was made in V6R1. Prior to V6R1, aggregates were always returned instorage
so declaring the return value the wrong size and grabbing the left-mostbyte
worked because of that particular implementation detail. InThe
V6R1 and later releases, the translator changed how small aggregates are
returned. Aggregates 8 bytes or less are now returned in a register.
data is right justified in the register so when it is assigned into staticdoc
storage for the variable it remains right justified.
At the time we recommended the coding technique you are currently using it
was a workaround that was valid, but due to unforseen (at the time we
provided the workaround) changes in the translator code at 610, the
workaround is no longer valid. The 'official' published method in our
has always been (since OS version 510) to define the return value in CL as1
character and use the EXTPROC(*CL:'CALLED_PROC') in the procedure.list
Therefore we are saying that this is working as designed.
--
IBM i on Power - For when you can't afford to be out of business
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.