Custom errors don't appear in log summary

[PaulNeag]

I am using EG7.1

I sometimes conditionnaly throw custom errors in my programs by using:

%PUT ERROR: CUSTOM ERROR THROWN BY MACRO;

or alternatively:

DATA _NULL_;
ERROR "ERROR:CUSTOM ERROR THROWN BY DATASTEP";
RUN;

I would expect these errors to appear in the log summary just like normal errors do.

They will show up in the log and a red "X" will show in the program icon but they do not show up in the error list.

Is there anyway to enable them showing in the list ? Perhaps a macro flag that needs to be set ?

Thank you

[Quentin]

Odd.  It works they way you want in EG 6.1.  User-written error messages are highlighted and show up in the log summary.

[Quentin]

Sorry, I was wrong. I didn't actually run the OP posted. 

@CaseySmith is correct. When I run:

DATA _NULL_;
ERROR "ERROR:CUSTOM ERROR not found by Log Summary";
ERROR "ERROR: CUSTOM ERROR found by Log Summary";
RUN;

In EG 6.1, only the second error message with the space after the colon is caught in the log summary.

[CaseySmith · Accepted solution]

Prior to EG 7.11, the log summary view did not find errors in the log if there wasn't a space immediately after "ERROR:".  So, to workaround, make sure you put a space between "ERROR:" and your error message.  This was fixed in EG 7.11, which recognizes errors with or without a space after "ERROR:".

Casey

ps- Fortunately, almost all SAS-generated errors start with "ERROR: " (with a space), so really only an issue for user-written errors.

[PaulNeag]

Thank you very much !