Please change the behavior where Enterprise Guide interprets events in the SAS log as errors that are not ERRORs in the SAS log. "ERRORs in the SAS log" being an instance when SAS generates a log statement prefixed with the string "ERROR:".
Example of this behavior. The format "gobble_dee_guk" is not defined for the purpose of this example.
/*options FMTERR;*/
options noFMTERR;
data _Null_;
x= put (y,gobble_dee_guk.);
stop;
run;
Without FMTERR:
29 options NoFMTERR;
30
31 data _Null_;
32 x= put (y,gobble_dee_guk.);
_______________
484
NOTE 484-185: Format GOBBLE_DEE_GUK was not found or could not be loaded.
33 stop;
34 run;
NOTE: Variable y is uninitialized.
NOTE: DATA statement used (Total process time):
real time 1.11 seconds
cpu time 0.03 seconds
With FMTERR:
29 options FMTERR;
30
31 data _Null_;
32 x= put (y,gobble_dee_guk.);
_______________
48
ERROR 48-59: The format GOBBLE_DEE_GUK was not found or could not be loaded.
33 stop;
34 run;
NOTE: The SAS System stopped processing this step because of errors.
NOTE: DATA statement used (Total process time):
real time 1.01 seconds
cpu time 0.04 seconds
If this program is run in Enterprise Guide, with the format not defined, and with option NOFMTERR set, then Enterprise Guide still interprets the SAS log as having an error, despite the absence of an "ERROR" statement in the log.
Two problems this can cause:
1. This can result in submitted code being interrupted against the wishes of the programmer.
2. This is difficult to see or find this error in a log unless you have specific knowledge of this exception, since in the SAS log the item that clues the programmer as to what is causing the error is a "Note".
See this link, I have a more editorial rant here if you're interested: EG8, options NOFMTERR, and submission status error
... View more
