Re: Parameter decimal-data error on submitted program

[booth@xxxxxxxxxxxx]

Because of this and similar problems I've made it a rule to only pass
alpha parms.  Its just so much easier in every way.

> I'm hitting a serious brain fade here.  FWIW, we're on v5r2.
>
> I have a CL program that has two numeric values.  The CL program then
> submits a job, calling an RPGLE program with those numeric fields as
> parameters.  The RPGLE program bombs with a decimal-data error.  The dump
> shows the two values as having hex zeros.
>
> When I change the CL program to call the RPGLE program directly using the
> same parameters, and not submit it, it works fine.  (See example code
> below.)
>
> Is SBMJOB doing something to those numeric parameter values?
>
> tia,
> db
>
>
> Pgm
>       Dcl   &p_Month    *Dec  (     2  0 ) Value( 01 )
>       Dcl   &p_Year     *Dec  (     4  0 ) Value( 2004 )
>
>       SbmJob     Cmd( Call ARR101CTSR +
>                    Parm( &p_Month &p_Year ))
>
>       Call ARR101CTSR   Parm( &p_Month &p_Year )
> Endpgm
>
> ARR101CTSR:
>
>   d Date            s              7  0
>    * Entry parameters
>   d p_Month         s              2  0
>   d p_Year          s              4  0
>
>   c     *Entry        Plist
>   c                   Parm                    p_Month
>   c                   Parm                    p_Year
>
>   c                   Eval      Date = ( p_year - 1900 ) * 10000 +
>   c                                           p_month * 100 + 01
>   c                   Eval      *inLR = *On
>   c                   Dump
>