|
On 2/26/2018 9:23 AM, Craig Richards wrote:
Since moving to V 9.6 when I use Scott Klement's BUILD command, I'm notspecifying
getting anything in the Error List tab ( for a failed compile )
I have to look in the Commands Log to see if compiles worked.
Is anyone else experiencing anything similar?
The BUILD command works fine in 9.5 and looking at the Commands Log tab I
can see that when it runs the CRTSQLRPGI command it is correctly
OPTION( *EVENTF ) the same as the default compile command in RDI so I'mnot
quite sure why I'm not getting anything in the Error List tab.
I don't use Scott's command, but in general there are a couple of things
that RDi needs:
1) An indication on the RDi compile command that an event file will be
created. If there's no OPTION(*EVENTF), put that in a comment at the
end of the command.
2) The *LDA needs to be populated with the library and member of the
source.
https://archive.midrange.com/wdsci-l/201406/msg00119.html
Of course, the actual compiler needs to create the event file :-) For
those interested in a DIY solution to /that/, see this DeveloperWorks
thread:
https://www.ibm.com/developerworks/community/
forums/html/topic?id=6a0b8711-e8ff-4e14-bd0c-d78e34d84372
--
--buck
http://wiki.midrange.com
Your updates make it better!
--
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: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/wdsci-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.