× 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.



(I'm just catching up on email. So sorry I'm a little late to the party
here.)

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.

Michael Quigley
Computer Services
The Way International

"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx> wrote on 02/16/2018 09:14:37 AM:
----- Message from Thomas Raddatz <thomas.raddatz@xxxxxx> on Fri, 16
Feb 2018 14:14:20 +0000 -----

To:

"Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries" <wdsci-l@xxxxxxxxxxxx>

Subject:

Re: [WDSCI-L] iSphere - problem calling QSYS.QCMDEXC - Need help

As far as I know, QSYS2.QCMDEXC has been introduced with 7.1. So
that is not option until I wanted to get rid of all user that are
still on 6.1. For sure I do not want that.

But I changed the Java code to use a CAST expression and I hope that
it will fix the problem. I wauit for feedback from Sune.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.