|
Douglas, It looks like you need to replace each double quote by a pair of single quotes: EVAL CMD = 'SBMJOB CMD(CALL PGM(INVMARGIN) ' + 'PARM("' + PARM1 + '" ' + '''' + %CHAR(DSTARTDATE) + ''' ' + '''' + %CHAR(DENDDATE) + '''))' Haven't tried this, but it should work. HTH, Peter Colpaert Application Developer Massive - Kontich, Belgium ----- Yoda of Borg are we. Futile is resistance, assimilated will you be. ----- "Douglas W. Palme" <dpalme@xxxxxxxxxxx> Sent by: rpg400-l-bounces@xxxxxxxxxxxx 18/07/2005 15:45 Please respond to RPG programming on the AS400 / iSeries To: RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> cc: Subject: RE: Error on compile I have and that part seems to work now, but apparently the way I have the CMD string structured it is not working correctly. In debug mode it tells me that I am not passing the correct number of parms to the called program. The called program has the following plist entry C *ENTRY PLIST C PARM ALPHPARM C PARM DSTARTDATE C PARM DENDDATE Which needs three parms and I am, or at least I thought I was passing three parms with the following code snippet: EVAL CMD = 'SBMJOB CMD(CALL PGM(INVMARGIN) ' + 'PARM("' + PARM1 + '" ' + '"' + %CHAR(DSTARTDATE) + '" ' + '"' + %CHAR(DENDDATE) + '"))' Do I need to separate the parms with commas? Interestingly enough, when I F11 on the CMD variable in debug mode it outputs the following: > EVAL CMD CMD = ....5...10...15...20...25...30...35...40...45...50...55...60 1 'SBMJOB CMD(CALL PGM(INVMARGIN) PARM("AA" "06/01/2005" "06/30' 61 '/2005")) ' 121 ' ' 181 ' ' For some reason it seems to be outputting more single quotes than I need or thought I was, however any change I make the the eval statement the compiler in seu balks. Should I change the double quotes to single? On Mon, 18 Jul 2005 09:28:07 -0400, Ali Ekinci wrote > use %char(parm2) > > -----Original Message----- > From: Douglas W. Palme [mailto:dpalme@xxxxxxxxxxx] > Sent: Monday, July 18, 2005 9:19 AM > To: RPG Group > Subject: Error on compile > > I have written a program that will submit another rpgle sql program > to batch mode.....however when I compile I am getting an error > saying that the operands are not compatible with the type of operator.... > > Here is the relevant code: > DPARM1 S 2A > DPARM2 S D DATFMT(*USA) > DPARM3 S D DATFMT(*USA) > DCMD S 200A > ********************************************************************** > * MAINLINE > ********************************************************************** > C EXFMT MAIN > C IF *IN12 = *ON > C EVAL *INLR = *ON > C RETURN > C ELSE > C MOVE DBRANCH PARM1 > C MOVE DSTARTDATE PARM2 > C MOVE DENDDATE PARM3 > C EVAL CMD = 'SBMJOB CMD(CALL > PGM(INVMARGIN) ' + C 'PARM("' + PARM1 + > '" ' + C '"' + PARM2 + '" > ' + C '"' + PARM3 + '"))' > > The errors refer to PARM2 and PARM3 specifically. Any suggestions > would be appreciated. I have tried everything from the ampersand ( > & ) to the plus I am now using and nothing seems to make a difference. > > If you bought, it was hauled by a truck - somewhere, sometime. > > -- > 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. > > -- > 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. If you bought, it was hauled by a truck - somewhere, sometime.
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.