Category properties

Table 3-14 describes the category settings.

**Table 3-14: Logging category settings**
Tab name / Setting name	Specifies
General / Description	An optional description.
Options / Level	The logging level. Only messages of equal or greater severity are logged. Table 3-15 describes the severity codes.
Options / Use Parent Handlers	Whether to log to the parent category handlers as well as the handler associated with this category.
Options / Parent	The parent category.
Options / Resource Bundle	The name of a Java resource bundle containing localized messages that are logged from Java code. If this property is not set, the default resource bundle is the class ResourceBundle in the package with the same name as the category. For example, the default resource bundle for the category com.sybase.jaguar.server is com.sybase.jaguar.server.ResourceBundle.
Handler	One or more logging handler names. The handler properties specify how and where messages are logged. See “Handler properties” for more information.

Table 3-15 lists the severity level codes. You can set the logging level in the category to discard messages below a specified severity level.

**Table 3-15: EAS log subsystem error levels**
Level	To log
ALL	All messages.
CONFIG	Configuration errors. You should correct these problems.
ERROR	Errors that prevent completion of a requested action. For example, a component has thrown an uncaught exception and its transaction is being rolled back.
FATAL	Errors that indicate the server should terminate.
DEBUG	Debug messages.
FINE	Debug messages.
FINER	Has same effect as FINE.
FINEST	Has same effect as FINE.
INFO	Informational or status messages. For example, the name server has finished binding components.
OFF	No messages are logged.
WARN	Warning messages. For example, a warning might be that the server is in a cluster and other members are not found.