|
On 21/10/2005, at 8:23 AM, Mike Pantzopoulos - (H/O) wrote:
I have a colleague who has reported the following problem. Is there something going on with the compiler? I have a prototype file which contains a 5 signed numeric field. I have a CALLP to this procedure using a field which has the same external field reference as the prototype. The field I am using is defined in a physical file using DDS. The field name is RIGNOR. This database field appears as a signed field in the input area of a compiled listing as follows
<--- stuff deleted --->
This database fields appears as a signed field in the output area of a compiled listing as follows
<--- stuff deleted --->
However it appears in the Global reference of the compiled listing as a packed field
This is normal RPG behaviour. See the Reference regarding Internal vs. External data formats.
The end result is that I am getting a compilation error on the CALLP command" *RNF7535 30 "The type and attributes of the parameter do not match those of the prototype". Has anyone else come across this and if so what is the solution.
1) If the variable is input to the procedure specify CONST on the prototype and let the compiler sort it out
2) If the variable is output from the procedure use a work variable with the correct attributes
3) Specify an externally defined data structure using that file to force the compiler to use the external format as the internal format.
Regards, Simon Coulter. -------------------------------------------------------------------- FlyByNight Software AS/400 Technical Specialists http://www.flybynight.com.au/ Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 /"\ Fax: +61 3 9419 0175 \ / X ASCII Ribbon campaign against HTML E-Mail / \ --------------------------------------------------------------------
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.