|
> -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx / Scott Klement > Sent: Tuesday, July 20, 2004 3:21 PM > > I don't know if anyone has suggested this yet or not (though, I'm pretty > sure it's in the FAQ) the way that I'd solve the problem is to create a > *CMD as a front-end to the program that you're submitting. > > When you submit the command, you don't have to do anything special with > the parameters -- you can supply them as normal. The command will take > care of making sure that they are converted properly for the program that > you're calling. Yes, the FAQ discusses it. I guess I need to weigh whether I want to add another object to the project, or just deal with the "klutz". 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? hmmmmmmmmmmmmmmm. Thanks Scott, one more thing to chew on! db
This mailing list archive is Copyright 1997-2026 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.