Re: [SPAM 1]Parameter prototype question

Prototypes will prevent the error your are describing.

Either you've found an IBM bug or more likely, you're not doing what
you think you're doing.

My guess, you've got the differing prototypes hard coded in multiple
places, instead of having it in a single source member that gets
/INCLUDEd.

The other possibility, instead of using CALLP to call with a
prototype, the code is using CALL with the PARM opcodes.

Last but not least, do you have the CONST or VALUE keywords on the
prototype and procedure interface that you are not showing?

HTH,
Charles Wilt

On Tue, May 11, 2010 at 10:28 AM, David FOXWELL <David.FOXWELL@xxxxxxxxx> wrote:

Hi,

I thought that prototyping protected me from this type of error, but it seems i was wrong.

 * MyVar declared like data dictionary standard.
D gMyVar          S                   LIKE ( DEF_MyVar )

 MyProc ( gMyVar )


 * Prototype for MyProc.
D MyProc          PR              N
D IMyVar                         9   2

I declared gMyVar using our standard without closely looking at MyProc's prototype definition.
Unit tests went OK. As this was a calcul of customer subscription fees, I did a test on all customers, eventually I got a MCH1210 zone receptor too small.
Using STRSRVJOB and STRDBG, I was unable to step into MyProc, I know not why.
I found that the attributs of gMyVar were 9P0. I thought that the compiler would have picked this up? How should I avoid this kind of error ( without modifying the hard coded definition, of course )?

Thanks.
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.