https://communities.sas.com/t5/SAS-Enterprise-Guide/Change-Notes-Warnings-in-log-to-Error/m-p/18931#M3288 Hi<BR /> Is there a systems option that can change NOTES to ERRORS in the log that relate to unitialized variables? In fact, is there a systems option that escalates all notes and warnings to errors? I find the systems option DKRICOND and DKROCOND very useful for making sure that potentially serious errors in the drop, keep, rename statements are caught by classifying these as errors. <BR /> <BR /> Thanks very much, <BR /> Robin. Tue, 19 Oct 2010 13:49:58 GMT deleted_user 2010-10-19T13:49:58Z https://communities.sas.com/t5/SAS-Enterprise-Guide/Change-Notes-Warnings-in-log-to-Error/m-p/18931#M3288 Hi<BR /> Is there a systems option that can change NOTES to ERRORS in the log that relate to unitialized variables? In fact, is there a systems option that escalates all notes and warnings to errors? I find the systems option DKRICOND and DKROCOND very useful for making sure that potentially serious errors in the drop, keep, rename statements are caught by classifying these as errors. <BR /> <BR /> Thanks very much, <BR /> Robin. Tue, 19 Oct 2010 13:49:58 GMT https://communities.sas.com/t5/SAS-Enterprise-Guide/Change-Notes-Warnings-in-log-to-Error/m-p/18931#M3288 deleted_user 2010-10-19T13:49:58Z https://communities.sas.com/t5/SAS-Enterprise-Guide/Change-Notes-Warnings-in-log-to-Error/m-p/18932#M3289 Give us an idea what "condition" you are attempting to treat as an ERROR as opposed to a NOTE/WARNING, please? Share with a code example revealed in a SAS log, preferably (paste the content in a reply to your post).<BR /> <BR /> Scott Barry<BR /> SBBWorks, Inc. Tue, 19 Oct 2010 19:58:09 GMT https://communities.sas.com/t5/SAS-Enterprise-Guide/Change-Notes-Warnings-in-log-to-Error/m-p/18932#M3289 sbb 2010-10-19T19:58:09Z https://communities.sas.com/t5/SAS-Enterprise-Guide/Change-Notes-Warnings-in-log-to-Error/m-p/18933#M3290 Robin,<BR /> <BR /> My question is what are you trying to do with this? All SAS steps have notes, e.g.<BR /> NOTE: DATA statement used:<BR /> Do you want to STOP the program (as ERRORs generally do), or just get information about processing?<BR /> <BR /> There are programming approaches to each of those, but I am unaware of an option.<BR /> <BR /> Doc Muhlbaier<BR /> Duke Tue, 19 Oct 2010 22:31:40 GMT https://communities.sas.com/t5/SAS-Enterprise-Guide/Change-Notes-Warnings-in-log-to-Error/m-p/18933#M3290 Doc_Duke 2010-10-19T22:31:40Z https://communities.sas.com/t5/SAS-Enterprise-Guide/Change-Notes-Warnings-in-log-to-Error/m-p/18934#M3291 Hi, thanks for the replies. Specifically, I would like to change the following "NOTE: Variable WIEGHT is uninitialized" from a note to an error (i.e. stop the code). Sometimes, this is missed by other beginners to SAS and can lead to significant errors. I figured a systems option would do the trick, but I cannot find anything in relation to this. Any other ways to catch this error would be appreciated (apart from training on checking logs properly of course). Wed, 20 Oct 2010 06:54:20 GMT https://communities.sas.com/t5/SAS-Enterprise-Guide/Change-Notes-Warnings-in-log-to-Error/m-p/18934#M3291 deleted_user 2010-10-20T06:54:20Z https://communities.sas.com/t5/SAS-Enterprise-Guide/Change-Notes-Warnings-in-log-to-Error/m-p/727874#M38373 a future answer, use dsoptions=note2err Fri, 19 Mar 2021 22:40:02 GMT https://communities.sas.com/t5/SAS-Enterprise-Guide/Change-Notes-Warnings-in-log-to-Error/m-p/727874#M38373 himself 2021-03-19T22:40:02Z