× 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 11/16/2016 04:31:15 PM:
----- Message from Ken Killian <kkillian@xxxxxxxxxxxx> on Wed, 16
Nov 2016 21:19:34 +0000 -----

To:

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

Subject:

Re: [WDSCI-L] H Control Specifications Shows Error

Greg,

RDi communicates by a batch-job, so I do NOT submit my compile off
to brand new separate job to compile. I uncheck the box for compile
in batch...
Windows>preferences...>Remote System>IBM i>Command Execution -->
Unheck the "Compile in Batch"

So, when I do that, I can look at the "Command Log", a.k.a. the job
log for RDI. And I can find my binding step errors there!!!!

window>show view>Other --> filter by "log"
Open >Ibm I Commands Log

I do NOT have to leave my beloved RDI to see binding errors! I can
see it in the view "Command Log"!

PS. View that "command log" has taught me a lot what RDI does behind
the scenes, and has help me greatly understand how RDI works!

Ken,

Does the command log really show everything? I guess it should since
that's effectively the joblog for the compile. Do you see any problems
with the Command Log view getting too long/big through the day?

Thanks,
Michael Quigley
Computer Services
The Way International
www.TheWay.org

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.