Currently, just a few options (they don't all appear when running proc options group= errorhandling allow to decide how message are displayed in the LOG (I am not too sure what the last 2 do...), like:
MERROR Issues a warning message for an unresolved macro reference.
SERROR Issues a warning message when a macro variable reference does not match a macro variable.
VALIDFMTNAME Specifies the maximum size that user-created formats and informat names can be before an error or warning is issued.
BYERR SAS issues an error message and stops processing if the SORT procedure attempts to sort a _NULL_ data set.
DKRICOND Specifies the error level to report when a variable is missing from an input data set during the processing of a DROP=, KEEP=, or RENAME= data set option.
DKROCOND Specifies the error level to report when a variable is missing from an output data set during the processing of a DROP=, KEEP=, or RENAME= data set option.
DSNFERR Issues an error message and stops processing when a SAS data set cannot be found.
MERGENOBY Specifies the type of message that is issued when MERGE processing occurs without an associated BY statement.
VARINITCHK Specifies the type of message to write to the SAS log when a variable is not initialized.
VARLENCHK Specifies the type of message to write to the SAS log when the length of the variable that is being read is longer than the length that is defined for the variable.
DS2SCOND Specifies the type of message that PROC DS2 generates.
RSASIOTRANSERROR Displays a transcoding error when illegal values are read from a remote application.
VNFERR SAS issues an error message when a BY variable exists in one data set but not another when the other data set is _NULL_.
We need more ways to customise how messages are displayed in the LOG when some events are flagged.
Some of the messages we consider worthy of a warning (some signal a fact that can't even be fixed!) include:
WARNING: The intervals on the axis labeled XXX are not evenly spaced WARNING: The enhanced date axis procedure has failed WARNING: Compression was disabled for data set WARNING: FOOTNOTE... WARNING: TITLE...
They give us a hard time for monitoring automated production jobs.
On the contrary notes like these are flagged as show-stoppers:
NOTE: MERGE statement has more than one data set NOTE: Library XXX does not exist. NOTE: SAS went to a new line NOTE: DATA STEP stopped due...
It would be nice to be able to raise valid alarms and avoid false alarms by setting the type of message for the various messages that SAS produces.