Glossary: Glossary

Glossary

additivity flag: a flag that is associated with a logger. An additivity flag controls whether ancestor loggers receive log events. By default, a log event is passed to the logger that is associated with the event as well as to any ancestor loggers. If a logger's additivity flag is set to false, then log events are not passed to ancestor loggers. For example, if the additivity flag for App.Meta is set to false, then App.Meta.IO events are passed to the App.Meta.IO and App.Meta loggers, but they are not passed to the App logger. See also appender additivity.
ancestor logger: a logger that is at a higher level in relation to other loggers in the logger hierarchy. For example, the Audit logger is an ancestor logger of Audit.Meta and Audit.Authentication.
appender: a named entity that represents a specific output destination for messages. Destinations include fixed files, rolling files, operating system facilities, and client applications.
appender additivity: a feature that causes each log event to be passed to the appenders that are associated with the logger as well as to appenders that are associated with the logger's ancestor loggers. For example, App.Meta.IO events are passed to appenders that are associated with App.Meta.IO as well as to appenders that are associated with App.Meta and App. See also additivity flag.
appender reference: an expression that identifies an appender whose destination receives messages for log events for a particular logger.
Application Response Measurement: the name of an application programming interface that was developed by an industry partnership and which is used to monitor the availability and performance of software applications. ARM monitors the application tasks that are important to a particular business. Short form: ARM.
ARM: See Application Response Measurement.
ARM agent: a software vendor's implementation of the ARM API. Each ARM agent is a set of executable routines that can be called by applications. The ARM agent runs concurrently with SAS. The SAS application passes transaction information to the agent, which collects the ARM transaction records and writes them to the ARM log.
autocall macro: a macro whose uncompiled source code and text are stored in an autocall macro library. Unlike a stored compiled macro, an autocall macro is compiled before execution the first time it is called.
conversion character: a single character that represents a data item that is generated in a log event. For example, d specifies the date of the event and t identifies the thread that generated the event. See also conversion specifier, format modifier, and pattern layout.
conversion pattern: an expression that specifies an appender definition's pattern layout. A conversion pattern consists of a combination of user-supplied literal text and conversion specifiers.
conversion specifier: an expression in a conversion pattern that consists of a percent sign (%), a conversion character, and optional format modifiers. See also conversion pattern.
descendant logger: a logger that is at a lower level in relation to other loggers in the logger hierarchy. For example, Audit.Meta and Audit.Authentication are descendant loggers of the Audit logger.
DTD: Document Type Definition. A file that specifies how the markup tags in a group of SGML or XML documents should be interpreted by an application that displays, prints, or otherwise processes the documents.
filter: in the logging facility, a set of character strings, thresholds, or a combination of strings and thresholds that you specify. Log events are compared to the filter to determine whether they should be processed.
format modifier: an optional set of characters in a conversion specifier that controls the field width, padding, and justification of the specified data item in log output.
Integrated Object Model: the set of distributed object interfaces that make SAS software features available to client applications when SAS is executed as an object server. Short form: IOM.
Integrated Object Model server: a SAS object server that is launched in order to fulfill client requests for IOM services. Short form: IOM server.
IOM: See Integrated Object Model.
IOM server: See Integrated Object Model server.
level: the diagnostic level that is associated with a log event. Examples of levels are TRACE, DEBUG, INFO, WARN, ERROR, and FATAL.
log event: an occurrence that is reported by a program for possible inclusion in a log.
logger: a named entity that identifies a message category. Logger names have a hierarchical format that enables you to configure logging at a broad or a fine-grained level.
logging configuration: an XML file or a set of SAS program statements that determines how log events are processed. You use the logging configuration to assign thresholds to loggers, to configure appenders, and to specify which categories and levels of log events are written to each appender.
pattern layout: a template that you create to format log messages. The pattern layout identifies the type, order, and format of the data that is generated in a log event and delivered as output.
planned deployment: a method of installing and configuring a SAS business intelligence system. This method requires a deployment plan that contains information about the different hosts that are included in the system and the software and SAS servers that are to be deployed on each host. The deployment plan then serves as input to an installation and configuration tool called the SAS Deployment Wizard.
root logger: the highest-level logger in the logger hierarchy. In a logging configuration, all other loggers inherit the root logger's attributes.
SAS console log: a file that contains information, warning, and error messages if the SAS log is not active. The SAS console log is normally used only for fatal system initialization errors or for late-termination messages. See also SAS log.
SAS Deployment Wizard: a cross-platform utility that installs and initially configures many SAS products. Using a SAS installation data file and, when appropriate, a deployment plan for its initial input, the wizard is designed to prompt the customer for all the remaining input at the start of the session so that the customer does not have to monitor an entire deployment.
SAS log: a file that contains a record of the SAS statements that you enter, as well as messages about the execution of your program. In some cases, the SAS log can also contain output from the DATA step and from certain procedures. See also SAS console log.
threshold: the lowest event level that is processed. Log events whose levels are below the threshold are ignored.

Top of Page