×
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.
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
midrange.com
