× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx> wrote on 02/19/2018 03:34:20 PM:
We're on 7.1 and we do not have QSYS2.QCMDEXC. (Perhaps we haven't
installed something, but I'm doubtful of that.)

However, we get around the problem by defining a variable for the
command
string long enough to handle the longest string we anticipate needing to

process. Then we move the actual command string into it which leaves the

rest padded with blanks. after that, we simply call QCMDEXC with the
full
length of the field for the string passed as the second parameter.
QCMDEXC
doesn't care about the extra blanks on the end of the string.


A variable-length string is the best solution I came up with.
Works just like as in RPG except I don't think you can use the += operator
for complex concatenations. ;-)

Declare CmdStr VarChar(3000);
Declare CmdLen Decimal(15,5);

Set CmdStr = 'CALL UTSETLLCL (''' || CompNumb || ''' *FIRST)';
Set CmdLen = Length(CmdStr);
Call QCMDEXC (CmdStr, CmdLen);


Sincerely,

Dave Clark

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.