Re: Passing decimal data

["Francis Lapeyre" <flapeyre@xxxxxxxxx>]

FWIW, we pass packed parametes from CL to RPG all the time, even with SBMJOB
CMD(). I'm making a wild guess here, but if the OP is trying to "hard-code"
the packed decimal parameter in a SBMJOB command, the solution is:

DCL &PARM1 *DEC (2 0) VALUE(01) /* or whatever */

SBMJOB CMD(CALL PGM(MYPGM) PARM(&PARM1)

On Fri, Jun 6, 2008 at 10:28 AM, sjl <sjl_abc@xxxxxxxxxxx> wrote:

> Rob Berendt wrote:
>  Rule number 1:
>  Never use SBMJOB CMD(CALL MYPROGRAM) if the call has parameters.
>  Never.
>
> Rob -
>
> I don't disagree with using commands as a front-end for submitted jobs, but
> I'm going to have to disagree with this statement. It's just flat wrong,
> and
> in my opinion the lazy way out.
>
> The addition of the CMD() parm to the SBMJOB command was incredibly useful,
> and it eliminated the need to string together the program call and all of
> the parms into a variable for use in the RQSDTA parm.
>
> You just have to know how to pass and receive variables from/to jobs that
> cross subsystem boundaries.
>
> I'd also suggest that most vendor packages use SBMJOB CMD(CALL MYPROGRAM)
> extensively, so regardless of whether you use it or not in your own custom
> programs, you'll have to know the rules for parameter passing when
> modifying
> vendor-supplied code.
>
> And that's all I have to say about this topic.
>
> - sjl
>
>
>
>
>
> --
> This is the RPG programming on the AS400 / iSeries (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.