× 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.



Yes, const or value would be the correct answer Barbara. When it is an
inquiry screen I don't need to change the passed value that was passed in
so using const allows me to use this with no problems.


Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777



Barbara Morris <bmorris@xxxxxxxxxx>
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
12/15/2011 12:25 PM
Please respond to
RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>


To
rpg400-l@xxxxxxxxxxxx
cc

Subject
Re: This compiler error doesn't make sense to me






On 2011/12/15 11:27 AM, Bryce Martin wrote:
Can we see the actual PI/PR for RunReport and the actual DDS defs for
the
8,0 date fields???? I'm doing this now and it works. I'll check it
against my code to see if something is different.


Bryce, when you're looking at your code, don't look at the DDS defs for
the passed parameters, look at the cross reference to see how the
internal fields are defined.

If you have zoned fields in your DDS, and zoned fields for your PR/PI,
then the most likely reasons your call is working are:

a. If the fields are zoned in the cross reference, you most likely
defined an externally-described DS to get the program fields defined
with the same type as the DDS fields.

or

b. If the fields are packed in the cross reference, you must have coded
CONST or VALUE on the prototype, which allows a packed field to be
passed to a zoned parameter.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.