RE: Best way for numeric parms

Bill,

I would guess that the original error was caused by a parm being packed in
one program and zoned in the other, probably caused by it being in a data
structure in one of the programs.  If that is taken care of the programs
will work fine with the original parms.  Parameters of 15,5 are only
necessary when a program is called directly from the command line (or as the
CMD parm in a SBMJOB).  Otherwise you can use any size/type as parameters
between two programs as long as the definitions match exactly between the
programs.  The programmer who changed things caused more of a mess by not
understanding what was causing the error in the first place.  I also say
that you won't get the error you are having if the value in the larger field
will fit in the smaller field.  What is the value of the larger field when
this error occurs, check the dump don't assume it is what was passed.  You
may still have some mismatch between parameters.

Scott Mildenberger

> -----Original Message-----
> From: Hopkins, Bill [mailto:BHopkins@saurerinc.com]
> Sent: Friday, October 25, 2002 11:19 AM
> To: 'rpg400-l@midrange.com'
> Subject: RE: Best way for numeric parms
>
>

> z-add p2co#    p$co#    <<<< target to small error
> etc.
>
> I can fix but was looking for a "best way" to handle this.
> He has changed to this in multi programs. Now I'm stuck
> cleaning up. But would rather do it right than patch up.
>
> Asking for suggestions on how others would handle.
>
> Keeping in mind than PO0001 or PO0002 might be called from
> RPG III also.
>
>