× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



IOW (correct me if I'm wrong), one cannot define a parm in an RPG program as
type N and be able to call that RPG program from both CL and RPG. If you
want to call it from both CL and RPG, define the parm as 1A.

--
Jeff Crosby
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
www.dilgardfoods.com

The opinions expressed are my own and not necessarily the opinion of my
company.  Unless I say so.


-----Original Message-----
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
that
was made in V6R1. Prior to V6R1, aggregates were always returned in
storage
so declaring the return value the wrong size and grabbing the left-most
byte
worked because of that particular implementation detail. In
V6R1 and later releases, the translator changed how small aggregates are
returned. Aggregates 8 bytes or less are now returned in a register.
The
data is right justified in the register so when it is assigned into static
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
doc
has always been (since OS version 510) to define the return value in CL as
1
character and use the EXTPROC(*CL:'CALLED_PROC') in the procedure.

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
list
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 thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.