KAMN533-W
There is an error in the monitoring definition file for the disk. Type: aa....aa. Server: bb....bb. Cause code: cc....cc. Monitored file: dd....dd.
Monitoring of the disk indicated by the type is specified incorrectly.
aa....aa: Type
Type |
Meaning |
---|---|
SYSTEM |
Indicates monitoring of the system disk. |
SERVER |
Indicates monitoring of the disk for business use of the server indicated by the server alias name. |
bb....bb: Server alias name (displayed as ---- if the type is SYSTEM).
cc....cc: Cause code
Cause code |
Meaning |
---|---|
DEFINITION NOT READ |
The disk monitoring definition file could not be read because it does not exist or nothing is specified in it. If this cause code is output, disk monitoring is not performed. |
PATH NOT FOUND |
The file to be monitored (specified in the disk monitoring definition file) does not exist. If this cause code is output, the specified file will not be monitored. |
TYPE NOT FILE |
The file to be monitored (specified in the disk monitoring definition file) is not an ordinary file. A path to one of the following might be specified as the monitoring target:
If this cause code is output, the specified file will not be monitored. |
DUPLICATE PATH |
The same file path to be monitored is specified multiple times in the monitoring definition file for one disk. Alternatively, the same file path to be monitored is specified in monitoring definition files for multiple disks. |
PATH TOO LONG |
The file path to be monitored (specified in the disk monitoring definition file) exceeds 247 bytes. If this cause code is output, the specified file will not be monitored. |
TOO MUCH FILES |
The file path to be monitored (specified in the disk monitoring definition file) exceeds 128 lines. The number of lines does not include the line that contains only the end of the file. If this cause code is output, the system operation varies depending on the type.
|
SYNTAX ERR |
The disk monitoring definition file contains tabs or spaces. |
INTERNAL ERR |
An error occurred in internal processing. |
dd....dd: Path specified in the disk monitoring definition file (displayed as ---- if the cause code is DEFINITION NOT READ or TOO MUCH FILES).
- S:
-
Continues processing.
- O:
-
Take one of the following actions according to the cause code:
Cause code
Meaning
DEFINITION NOT READ
Create a disk monitoring definition file, and then specify at least one absolute path of the file to be monitored.
PATH NOT FOUND
Specify the path of an existing file to be monitored.
TYPE NOT FILE
Specify the path of an ordinary file to be monitored.
DUPLICATE PATH
Make sure that the same file path to be monitored is not specified more than once in the monitoring definition file for one disk. Also make sure that the same file path to be monitored is not specified more than once in monitoring definition files for multiple disks.
PATH TOO LONG
In the disk monitoring definition file, specify the file path to be monitored, using no more than 247 bytes.
TOO MUCH FILES
In the disk monitoring definition file, specify the file path to be monitored, using no more than 128 lines.
SYNTAX ERR
Remove the tabs and spaces from the disk monitoring definition file.
INTERNAL ERR
See the message output before this message, and then eliminate the cause of the error.