RE: Parameter decimal-data error on submitted program

Hi Dan,

> So, in essence, the SBMJOB CMD(CALL PGM PARM(&A &B)) in the CL program would
> be replaced by SBMJOB CMD(MYCMD PARM(&A &B))?  And &A can be 2,0 and &B can
> be 4,0 defined in both the command and called program?

Errr... sort of.  OS/400 commands usually use keywords that describe
each parameter, so I'd say it'd be more like this:

SBMJOB CMD(LISTSALES TERRITORY(&MYTERR) DATE(&MYDATE))

rather than this:

SBMJOB CMD(CALL PGM(LISTSALES) PARM(&MYTERR &MYDATE))

And yes, the parameters can be packed 2,0, 8,0, whatever floats your boat,
because the CMD object will convert it to the right format before it calls
the program.

It also gives you a chance to make your code more self-documenting...