KAVB1163-E

An error occurred during setting of the common exclusion-conditions.

S:

Terminates processing.

O:

If one of the following messages is displayed for cause, check the operation mode for the JP1/IM - Manager common exclusion-conditions, restart JP1/IM - View, and then retry the operation.

• JP1/IM - Manager is running in compatibility mode.

• The common exclusion conditions is operating in a basic mode.

If the message shown below is displayed for cause, the definition file might be corrupted. Stop JP1/IM - Manager, change the operation mode for the common exclusion-conditions to basic mode, and then change it back to extended mode to initialize the definition of the common exclusion-conditions (extended).

• The common exclusion extended definition file is invalid.

If the message shown below is displayed for cause, the IM database service is not running. Make sure that the KAVB4003-I message was output to the integrated trace log of the manager, and then retry the operation. If the KAVB4003-I message was not output and you are using the integrated monitoring database, execute the jimdbstatus command to check the status of the IM database service. When you have confirmed that the IM database service is running and the KAVB4003-I message is output to the integrated trace log, retry the operation.

• An attempt to switch the event acquisition filter has failed.

If the message shown below is displayed for cause, the definition includes a character that might cause character corruption when the definition is stored. Ensure that any environment-dependent character or other character that might cause character corruption is not used, and then apply the definition again.

• A character that cannot be stored successfully is included.

If a message other than the above is displayed for cause or if the problem cannot be resolved, check the following OS log items.

• In Windows: Windows event log

• In UNIX: System log (syslog)

After checking the OS log items, check whether a shortage has occurred in other OS resources such as file descriptors. If a resource shortage has not occurred, use the data collection tool to collect data, and then contact a system administrator.