When running an action that doesn't use the *EVENTF, an error message shows in the log regarding *EVENTF being missing from command string.

[richardschoen]

Describe the bug
When running a Run action that doesn't use the *EVENTF, an error message shows in the log regarding *EVENTF being missing from command string.

This message is not useful and I find it distracting. Perhaps eliminate the false error message or let me turn that off as a setting ?

Example:
*EVENTF not found in command string. Not fetching errors for LIB/SRCMBR001.

To Reproduce
Steps to reproduce the behavior:

1. Create an action or run any CL command that doesn't use *EVENTF in it's CL command string,
2. Run the action.
3. See error: *EVENTF not found in command string. Not fetching errors for LIB/SRCMBR001.

Expected behavior
I would expect that if the *EVENTF is not used in my command line, I should not have to see this extraneous non-useful message. It's distracting.

Perhaps eliminate the false error message or let me turn that off as a setting ?

I know what it's like to over message users. I've been doing that my entire career until someone points out sometimes that it's sometimes TMI and distracting.

Thanks

Screenshots

Environment (please complete the following information):

• Extension version [e.g. 2.14.7]
• IBM i OS version [e.g. 7.5]

[wimjongman]

I suggest to only fire this when the command is a CRT* command.