KAVA3645-E

The log file cannot be monitored correctly because the status of this file is abnormal. This error message is output if the format of the log file is different from the log file format specified in the action definition file.

For details about the status of the log file, see the following error numbers.

• code = 01: The log file being monitored was deleted.

• code = 02: The log file being monitored was re-created.

• code = 03: The size of the log file being monitored was reduced.

(S)

Continues processing.

(O)

If the format of the output log file is different from the log file format specified in the action definition file, one of the error numbers shown in the table below might be output. Revise the specification of the FILETYPE parameter to the correct format, and then restart the log file trapping.

FILETYPE value	Format of the output log file
	SEQ	SEQ2	SEQ3	WRAP1	WRAP2	HTRACE
SEQ	Y#1	code = 01 code = 02	--	--	code = 03	--#2
SEQ2	--	Y#1	--	--	code = 03	--#2
SEQ3	--	--	Y#1	--	code = 03	--#2
WRAP1	--	code = 01 code = 02	--	Y#1	code = 03	--#2
WRAP2	--	code = 01 code = 02	--	--	Y#1	--#2
HTRACE	--#2	--#2	--#2	--#2	--#2	Y#1

Legend:

Y: The format of the log file matches the log file format specified in the action definition file.

--: The KAVA3645-E message is not output.

#1: If the log file formats match but this message is output, the probable causes are as follows:

• The size of the monitored file exceeds 2 GB. (WRAP1 format only)

  In this case, code = 01 or code = 03 might be output. Make sure that the size of the monitored file does not exceed 2 GB.

• When a file on the shared disk was being monitored, the shared disk was moved (unmounted) while the log file trapping was running.

  In this case, code = 01 might be output. Make sure that the log file trapping is stopped before you attempt to move the shared disk.

#2: A KAVA3646-E error message is output when the log file trapping starts monitoring.