We don't currently have an option to do that.
Would making the Commands Log view visible if a command (that does not have
*EVENTF) fails be sufficient.
The message box might be obtrusive and annoying.
From: Tools/400 <thomas.raddatz@xxxxxxxxxxx>
To: Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries
<public-wdsci-l-Zwy7GipZuJhWk0Htik3J/w@xxxxxxxxxxxxxxx>
Date: 26/02/2016 11:36 AM
Subject: Re: [WDSCI-L] No *ESCAPE message on wrong compile command
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>
Hi Vern,
The problem has nothing to do with the *EVENTF option. There are lots of
commands that do not have that option and I wonder how to get noticed by
RDi when such a command fails.
Today, I had a problem with a command of our change management system
that sent an *ESCAPE message, which was silently ignored by RDi. Then I
did additional tests and tried to compile a RPGLE source member with
CRTFOODCMD (which does not exist) and CRTTBL (which should not
understand a RPGLE source).
Guess what? Nothing happened what I tried to compile the module from an
RSE source member filter. That is really bad, when you are in a hurry
and you think that it compiled just fine.
At least I would like to see an option to enable a popup message box when:
* a command, that does not have specified *EVENTF, failed
* there is a typo in a custom compile command
The popup is not really necessary (maybe even annoying) when the command
created *EVENTF information.
Thomas.
Am 26.02.2016 um 16:34 schrieb Vernon Hamberg:
*EVENTF option
--
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
