class1, ...[/qualifiers]
Specifies the type of information that you want the manager to log. Similar types of information are grouped into an event class. The following table lists the event classes that the manager can write to the event log. You can also negate most of the event classes. If you do not specify a class, the command will restore the default event class list.
|
Event Class |
Description |
|
[NO]ABNORMAL_EVENT |
Logs abnormal scheduler events. |
|
ALL |
Logs all events. |
|
[NO]BROADCAST_MESSAGE |
Logs broadcast messages. |
|
[NO]DATABASE_CHECK |
Logs requested database checks. |
|
[NO]ERROR_TRAP |
Logs error trapping. |
|
[NO]INTERFACE EVENT |
Logs user commands. |
|
[NO]JOB_EVENT |
Logs job events. |
|
[NO]MAILBOX_MESSAGE |
Logs mailbox messages. |
|
NONE |
Does not log any events. |
|
[NO]NORMAL_EVENT |
Logs normal scheduler events. |
|
[NO]TERMINATION_EVENT |
Logs scheduler terminations. |
|
[NO]TIMER_SETTING |
Logs timer settings. |
|
[NO]STATE_CHANGE |
Logs job-state changes. |
To choose more than one event class with the SCHEDULE SET LOGGING command, separate the event classes with commas. For example:
SCHEDULE> SET LOGGING ABNORMAL,ERROR,TIMER SCHEDULE> SET LOGGING ALL SCHEDULE> SET LOGGING ALL,NOMAILBOX,NOBROADCAST SCHEDULE> SET LOGGING NONE
Important! We do not recommend that you log all event classes because this causes your event-log file to grow very quickly.
Each event class can contain several subclasses of events. For example, the JOB_EVENT class logs the following kinds of job events:
The default logging includes the following classes:
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |