|
How About Trying: CallP ExecuteCommand( cmd : %Len( %TrimR( %SubStr( cmd : 1 : CmdLen ) ) ) ) Create your own ExecuteCommand Procedure which takes the length. Then Substr the Command and pass it to IBM's QCMDEXC api... This is what we are using... PExcCmd B EXPORT DExcCmd PI 1 OPDESC D CmdStr 32767A CONST OPTIONS(*VARSIZE) D ExcMsgID 7A OPTIONS(*NOPASS: *OMIT) D ExcMsg 80A OPTIONS(*NOPASS: *VARSIZE) DPrmLen S 10I 0 STATIC DPrmPas S 10I 0 STATIC C CALLP CEEDOD(1: C DscTyp: C DtaTyp: C DscInf1: C DscInf2: C PrmLen: C *OMIT) C CALLP QCmdExc(CmdStr: C %LEN( C %TRIMR( C %SUBST(CmdStr:1:PrmLen)))) C* C IF %PARMS >= 2 C CALLP CEETSTA(PrmPas:2:*OMIT) C* C IF PrmPas = 1 C EVAL ExcMsgID = *BLANKS C END C* >>> BHopkins@xxxxxxxxxxxxxxxxxxx 11/06/03 12:09 PM >>> Got ask this off list. Someone was trying to test out PR of qcmdexc. Wants to do something like this to see how it works. But because parm is over 32A it has junk in the 3000A. Say he sends in SBMJOB command or something. Any way to get around this. I build my command strings in code so don't have this problem. Any comments on solution. He's learning I'm always learning. Thanks Bill Hopkins d ExecuteCommand PR ExtPgm('QCMDEXC') d cmdstr Like(Cmd) Const Options(*Varsize) d cmdLen 15P 5 Const d cmdOpts 3A Const Options(*NOPASS) D cmd S 3000A c *entry plist c parm cmd c CallP ExecuteCommand(cmd:%len(%trim(cmd)) c eval *inlr = *on c return _______________________________________________ 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.