|
With your example there are no differences in outcome. In the first case the request message "'CALL WPC8060" is placed into the submitted job's external message queue. In the 2nd case the request message "CALL PGM(WPC8060)" is placed into the submitted job's external message queue. The CMD parameter was introduced early in the history of the AS/400 and it's advantage is that it syntax checks CL commands before submitting them and it allows users to prompt commands. When passing parameters on CALL commands it can sometimes make incorrect assumptions as to the formatting of the data. The RQSDTA parameter goes all the way back to the early days of the System/38. There is no syntax checking or prompting what-so-ever, mostly because in those days I think the developers had visions of being able to support more that one control language. The only advantage of using it, is that it makes no assumptions about the formatting of the parameters on the CALL command because you have to build command string exactly as you want it to appear. ----- Original Message ----- From: Captain Jerry To: RPG programming on the AS400 / iSeries Sent: Tuesday, August 15, 2006 1:36 PM Subject: SBMJOB ~ RQSDTA *Can anyone explain (maybe in layman's terms!) what the difference in the two CL Statements below is? Is one better then the other? More functionality? Different System Impacts? Anything?* ** * SBMJOB JOB(WPC8060) RQSDTA('CALL WPC8060 ') SBMJOB CMD(CALL PGM(WPC8060)) JOB(WPC8060) * *Thanks,* *Captain Jerry* -- 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.