Hitachi

JP1 Version 12 JP1/Integrated Management 2 - Manager Messages


KAVB8102-E

The system file (file-name) will be created again because the file was corrupted. : data-content-of-corrupted-system-file

An attempt to read data failed because the contents of a system file managed by the system was were invalid.

S:

Deletes the existing system file and creates a new system file.

  • If file-name is ecsseq.inf

    Events are stored in the event buffer starting from the JP1 event registered in the event database after Event Console Service starts, even if -1 is specified for the event acquisition start position using the jcoimdef command.

  • If file-name is fcsseq.inf

    Action matching processing is performed starting from the JP1 event registered in the event database after Event Base Service starts, even if -1 is specified for the event acquisition start position using the jcoimdef command.

  • If file-name is fcssendseq.inf

    Whether the events are response-waiting events is determined, starting from the JP1 event registered in the event database after Event Base Service started. This occurs even if the response-waiting event management is enabled in the system settings by using the jcoimdef command.

O:
  • If file-name is ecsseq.inf

    Check the integrated trace log to see if an error message from Event Console Service (error messages KAVB0001 to KAVB2000) was output.

    If a message was output, take the corrective action given for that message.

  • If file-name is fcsseq.inf or fcssendseq.inf

    Check the integrated trace log to see if an error message from Event Base Service (error messages KAVB4001 to KAVB6000) was output.

    If a message was output, take the corrective action given for that message.

Also check the OS log to determine whether a resource shortage occurred.

If no resource shortage occurred, use the data collection tool to collect data, and then contact a system administrator.