Re: No *ESCAPE message on wrong compile command

[Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>]

Hi Thomas

I think there's been another thread on this kind of thing here rather 
recently.

Does it do you any good to look at the Commands Log view? Admittedly, 
there is no popup from there that I know of.

Turnover DOES pop up a message when there is a compile failure - I think 
it depends on the kind of failure - it might still not do what you need. 
It probably depends on setting up a valid command for the object types.

Can't think of anything more, sorry!!

Vern

On 2/26/2016 10:35 AM, Tools/400 wrote:
> 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