|
It looks like you need to define the command string length as 15P 5. You might also consider prototyping the call to make it easier to work with. I think there is an example in the manual. Here is what ours looks like: DQCmdExc PR EXTPGM('QCMDEXC') Execute a command. D PR_CmdStr 4096A CONST OPTIONS(*VARSIZE) D PR_CmdStrLen 15P 5 CONST ... C CALLP QCmdExc(CmdStr: C %LEN(%TRIMR(CmdStr))) We built a this into a subprocedure so we can do something like: EVAL ErrFlg = ExcCmd('SndMsg Msg(''Bla Bla Bla'')': RtnMsgID: RtnMsgTxt) The return message is set from the program status data structure. David Morris >>> maena <maena@correo.com> 01/21 11:59 AM >>> I'm trying to use the QCMDEXC utility from an ILE RPG program, but I receive a runtime error which says that the syntax command passed to QCMDEXC is incorrect. The same sentence used from the command line is successful, so I suppose that the problem is related with the parameters definition. Here you have an example: *D specs: VCmd S 255 VLen S 15S 2 *C specs CmdParms PLIST PARM VCmd PARM VLen EVAL VCmd='SNDMSG(''TEXT'') TOUSR(QSYSOPR)' EVAL VLen=29 CALL 'QCMDEXC' CmdParms Could anyone point me to the error in my RPG code? ------------------------------------- Mª Elena Vázquez mailto:maena@correo.com ------------------------------------- * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This is the RPG/400 Discussion Mailing List! To submit a new * * message, send your mail to "RPG400-L@midrange.com". To unsubscribe * * from this list send email to MAJORDOMO@midrange.com and specify * * 'unsubscribe RPG400-L' in the body of your message. Questions should * * be directed to the list owner / operator: david@midrange.com * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
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.