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 Killian-
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Greg Wilburn
Sent: Wednesday, November 16, 2016 4:13 PM
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
Just wait until your program fails to compile due to an error in the binding step... RDi does not report those anywhere.
When that happens, I have to go out to the green screen to compile so I can see the job log.
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Vernon Hamberg
Sent: Wednesday, November 16, 2016 4:08 PM
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
LOL George - man, sometimes I have just not been able to figure out the problem. I had one the other day that reported an out-of-sequence problem from the control specs on, when I'd used apparently an invalid keyword in a DCL-DS with LIKEREC or EXTFILE with INZ() - it just didn't make sense.
So yeah, even with the yellow triangles, the problem can be lurking in hidden byways!
Vern
On 11/16/2016 2:50 PM, George Smith wrote:
Egg on Face --
Thought about it a few seconds and wondered if somewhere in the code I had an unmatched ")". Yes I did and my problem went away by correcting that line. Of course the line that had the error was at least a dozen Page Downs into the code.
This new fangled tool is too smart for this old dog.
George R. Smith
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of
George Smith
Sent: Wednesday, November 16, 2016 2:42 PM
To: Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries
Subject: [WDSCI-L] H Control Specifications Shows Error
Hello All -
I attempted to adjust the existing H-Control Specifications and now I can't undo enough to get rid of the yellow triangle. And of course as I just learned today with the line error I don't get an Outline.
Here is the code:
H ACTGRP(*CALLER) DFTACTGRP(*NO)
H OPTION(*SRCSTMT:*NODEBUGIO:*SHOWCPY:*EXPDDS)
And hovering over the error shows: "(" expected instead of this input
George Smith
--
This is the Rational Developer for IBM i / Websphere Development
Studio Client for System i & iSeries (WDSCI-L) mailing list To post a
message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/wdsci-l.
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/wdsci-l.
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/wdsci-l.
midrange.com
