An Idea Exchange for SAS software and services

Comments
by Regular Contributor
on ‎04-21-2017 10:17 AM

My counterarguments are:

    (1) that it's a warning. It won't do anything to execution, so can't you just ignore it?

    (2) isn't there a way to systematically suppress warnings?

    (3) I've used outobs= for testing purposes. For example, I don't want to process all of the thousands/millions of records in a given dataset. Having a warning is a way to flag that I'm still using outobs, even if what I actually want is to process everything (for example, if I moved my development code into production.

 

If it's still something you don't want to see, I would much prefer to an option instead of removing the warning altogether.

by Super Contributor
on ‎04-23-2017 08:57 PM

My counterarguments are:

    (1) that it's a warning. It won't do anything to execution, so can't you just ignore it?  SB:  No, many sites have coding standards that require no warnings in the SAS log.

    (2) isn't there a way to systematically suppress warnings?  SB:  Not that I'm aware of.

    (3) I've used outobs= for testing purposes. For example, I don't want to process all of the thousands/millions of records in a given dataset. Having a warning is a way to flag that I'm still using outobs, even if what I actually want is to process everything (for example, if I moved my development code into production.  SB:  Weak argument but fair enough.  What if you left the data set options firstobs= and obs= in your development code?  Why the special treatment for the SQL outobs= behaviour?  And at some point the developer has to be responsible for his/her own code, usually via unit testing.

 

If it's still something you don't want to see, I would much prefer to an option instead of removing the warning altogether.  SB:  Fair enough.  The undocumented NOWARN option is too all-encompassing.  But, what happens when you have outobs= and (say) the nowarnoutobs SQL option in your code that you promoted to production?  The warning is again suppressed.

 

I just don't see the use for the warning, and removing it would be more consistent with other areas of SAS.  My opinion only, YMMV.  It would be good to get others' opinions on this as well.

Idea Statuses
Top Liked Authors