|
"Hopkins, Bill" wrote: > ... > 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. > > Bill, in my opinion, the best way to handle this is not to touch the program at all. Especially since there are other existing calling program around. Instead, just deal with the SBMJOB problem by adding a command to the program. For P00002, use this source: cmd prompt('Call P00002') parm co type(*dec) len(2 0) prompt('whatever') parm plt type(*dec) len(2 0) prompt('whatever') parm iloc type(*dec) len(3 0) prompt('whatever') parm po type(*dec) len(6 0) prompt('whatever') parm item type(*char) len(15) prompt('whatever') parm lin type(*dec) len(2 0) prompt('whatever') ===> crtcmd mylib/p00002 pgm(p00002) prdlib(mylib) Now, you can still call the program the normal way from other programs, and for SBMJOB, instead of this: SMBJOB cmd(call p00002 parm(&co &plt &iloc &po &item &lin)) Do this: SMBJOB cmd(p00002 &co &plt &iloc &po &item &lin) or SMBJOB cmd(p00002 co(&co) plt(&plt) iloc(&iloc) po(&po) + item(&item) lin(&lin))
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.