contains a description of the SAS session and lists the lines of source code that were executed. Depending on the setting of SAS system options, the method of running SAS, and the program statements that you specify, the log can include the following types of information:
Because the SAS log provides a journal of program processing, it is an essential debugging tool. However, certain system options must be in effect to make the log effective for debugging your SAS programs. Customizing the Log describes several SAS system options that you can use.
contain the results of most SAS procedures and some DATA step applications. Results can be routed to a file, and printed as a listing. If you use the Output Delivery System (ODS), you can produce results for a high resolution printer or create HTML output for use with a web browser. You can customize your output by modifying or creating your own table definitions, which are descriptions of how you want to format your output. For more information about the flexibility of ODS, see the SAS Output Delivery System: User's Guide.
When the SAS log is not active, it contains information, warning, and error messages. When the SAS log is active, the SAS console log is used only for fatal system initialization errors or late termination messages.
Operating Environment Information: See the SAS documentation for your operating environment for specific information on the destination of the SAS console log.
contain log messages that you create using the SAS logging facility. Logging facility messages can be created within SAS programs or they can be created by SAS for logging SAS server messages. The logging facility log messages are based on message categories such as authentication, administration, performance, or customized message categories in SAS programs. In SAS programs, you use logging facility functions, autocall macros, or DATA step component objects to create the logging facility environment.
The logging facility environment consists of loggers, appenders, and log events. A logger defines a message category, references one or more appenders, and specifies the logger's message level threshold. The message level threshold can be one of the following, from lowest to highest: trace, debug, info, warn, error, or fatal. An appender defines the physical location to write log messages and the format of the message. A log event consists of a log message, a message threshold, and a logger. Log events are initiated by SAS servers and SAS programs.
When SAS processes a logging facility log event, it compares the message level in the log event to the message threshold that is defined for the logger that is named in the log event. If the log event message threshold is the same or higher than the logger's message threshold, the message is written to the locations that are specified by the appenders that are referenced in the logger definition. If the log event is not accepted by the logger, the message is discarded.
Appenders are defined for the duration of a macro program or a DATA step. Loggers are defined for the duration of the SAS session.
For more information, see SAS Logging Facility in SAS Logging: Configuration and Programming Reference.