RE: Best way for numeric parms

[Scott Mildenberger <Smildenber@xxxxxxxxxxxx>]

Bill,

You should only get an error where you indicated if passcompany has a value
that won't fit in a 2,0 field.  In your example where the value is 1 this
should work fine (I didn't test it).  The scenario could result in an error
but not if the original fields in the programs are the same size.  Why are
all your program to program calls changed to 15,5?  This would only be
necessary if the programs are being called directly from the command line.

Scott Mildenberger

> -----Original Message-----
> From: Hopkins, Bill [mailto:BHopkins@saurerinc.com]
> Sent: Friday, October 25, 2002 9:14 AM
> To: 'rpg400-l@midrange.com'
> Subject: Best way for numeric parms
>
>
> I have a client who just with through alot of code and change
> Plist to use
> 15 5 values in his calls to RPG IV programs.
>
> stop data decimals on calls but now of course getting target
> to smal when
> trying to move back to correct size.
>
> ruff example RPGII call to RPG IV he has done
>
> RPGII code
>
> z-add 1             company          2 0
> z-add company passcompany
> call 'pgm2'
> parm                passcompany  15 5
>
>
> RPG IV code
>
> *Entry plist
>           parm     passcompany   15 5
>
>
> z-add passcompany  keycompany 2 0    <<< error of course
>
> Can fix but was wanting to get
> suggestions for replacement code
> for all of these type calls.
>