Job Management Partner 1/Integrated Management - Manager Messages

[Contents][Index][Back][Next]

2.8 JP1/IM-related common messages (KAVB8000 to KAVB8999)

KAVB8000-W

Option (specified-option) appears twice or more.

An option was specified more than once.

S:
Ignores the specified option and continues processing.

O:
Reset the option value, and then retry the operation.

KAVB8001-W

Specify an argument (argument-value) after the option (option).

The command could not be executed because no argument value was specified after the displayed option.

S:
Terminates processing.

O:
Specify an argument value after the displayed option.

KAVB8002-W

No Logical Host Name is specified.

No logical host name was specified for environment variable JP1_HOSTNAME.

S:
Uses the default logical host name and continues processing.

O:
If a logical host name must be specified, specify the environment variable, and then retry the operation.

KAVB8003-W

An invalid logical host name (logical-host-name) is specified.

The logical host name specified as the argument is invalid.

S:
Terminates processing.

O:
Specify a valid logical host name, and then retry the operation.

KAVB8051-I

The health check will now start. (host name = host-name)

The health check will start.

S:
Starts the health check.

KAVB8052-I

The health check will now stop. (host name = host-name)

The health check will end.

S:
Stops the health check.

KAVB8053-E

The health check will now stop because an error occurred. (host name = host-name) : maintenance-information

The health check stopped due to an error.

S:
Terminates the health check.

O:
Collect data, and then contact a system administrator.

KAVB8054-E

The definition file of the health check (file-name) cannot be opened. : maintenance-information

Cannot open the health check definition file.

S:
If JP1/IM - Manager is running, ignores the health check. If the jco_spmd_reload command is being executed, re-uses the current definitions and continues processing.

O:
Make sure that the health check definition file exists and that access permission is assigned correctly, and then execute the jco_spmd_reload command.

KAVB8055-E

There is an error in the definition file of the health check (file-name). The default value will be used. (line line-number) : detailed-information

The health check will be performed using the default values because an invalid value was specified in the health check definition file.

The character string that contained the error is shown in the detailed information.

S:
If JP1/IM - Manager is running, operates using default values only for those definition items with errors. If the jco_spmd_reload command is being executed, re-uses the current definitions only for those definition items with errors and continues processing.

O:
Make sure that the definition file is specified correctly, and then execute the jco_spmd_reload command.

KAVB8060-E

An abnormality was detected in function-name. (host name = host-name, process name = process-name, process ID = process-ID) : maintenance-information

A function abnormality was detected. The possible causes are as follows.

  • A process ended abnormally.
  • A process stopped responding.
  • The server or network is in high load status.

S:
Continues processing.

O:
Determine whether the server or network is in high load status.
If the load is high, take the following corrective actions.

In Windows:
For the evtcon, evgen, and jcdmain processes, execute the jcogencore command to output a dump for any function for which an abnormality was detected.
After a dump is output, use the data collection tool to collect data, and then contact a system administrator.
After executing the jcogencore command, restart JP1/IM - Manager.
For the evflow and jcamain processes, no dump can be output. Use the data collection tool to collect data, and then restart JP1/IM - Manager.

In UNIX:
Execute the jcogencore command to output a dump for any function for which an abnormality was detected. Functions (processes) for which a dump was output will stop.
After a dump is output, use the data collection tool to collect data, and then contact a system administrator.
After executing the jcogencore command, restart JP1/IM - Manager.

KAVB8061-I

function-name has been recovered. (host name = host-name, process name = process-name, process ID = process-ID) : maintenance-information

The function was recovered.

S:
Continues processing.

KAVB8062-E

An abnormality was detected in function-name. (host name = host-name, process name = process-name) : maintenance-information

A function abnormality was detected. The possible causes are as follows.

  • A process ended abnormally.
  • A process stopped responding.
  • The server or network is in high load status.

S:
Continues processing.

O:
Determine whether the server or network is in high load status.
If the load is high, collect JP1/Base data, and then restart JP1/Base Event Service and JP1/IM - Manager.

KAVB8063-I

function-name has been recovered. (host name = host-name, process name = process-name) : maintenance-information

The function was recovered.

S:
Continues processing.

KAVB8064-W

The function function-name was detected not to be responding. (host name = host-name, process name = process-name)

The function indicated in the message is not responding.

S:
Continues the health check. If the function still does not respond, the system reports a health check function abnormality.

O:
The host may be in high load status. Check the load status. If it is high, reduce the load.

KAVB8070-E

The JP1 event event-ID could not be issued. : maintenance-information

A JP1 event could not be issued.

S:
Continues processing.

O:
Determine whether Event Service is running. If it is not running, start it.

KAVB8071-I

The JP1 event event-ID was issued.

A JP1 event was issued.

S:
Continues processing.

KAVB8072-E

The notification command command could not be executed. : maintenance-information

A notification command could not be executed.

S:
Continues processing.

O:
Make sure that the definition file is specified correctly, and then execute the jco_spmd_reload command.

KAVB8073-I

The notification command command was executed.

A notification command was executed.

S:
Continues processing.

KAVB8074-W

No notification command is specified. (file name = file-name)

No notification command was specified in the definition file.

S:
Suspends processing.

O:
If a notification command must be specified in the definition file, specify the notification command, and then retry the operation.

KAVB8101-E

An attempt to open the system file (file-name) has failed. : system-error-code

An attempt to open a system file managed by the system failed.

S:
  • If file-name is ecsseq.inf
    If the attempt to open a file fails while reading a system file, 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 the attempt to open a file fails while writing to a system file, the system deletes the system file and continues processing. After the system recovers from the error, the system file is created again. If the system does not recover from the error and the system file is not created again, events are stored in the event buffer starting from the JP1 event registered in the event database after Event Console Service starts when JP1/IM - Manager starts again.
  • If file-name is fcsseq.inf
    If the attempt to open a file fails while reading a system file, 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 the attempt to open a file fails while writing to a system file, the system deletes the system file and continues processing. After the system recovers from the error, the system file is created again. If the system does not recover from the error and the system file is not created again, action matching processing is performed starting from the JP1 event registered in the event database after Event Base Service starts when JP1/IM - Manager starts again.
This message is not output again until the system file indicated by file-name is successfully opened.

O:
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.

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.

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.

KAVB8103-E

An attempt to read data from the system file (file-name) has failed. : system-error-code

An attempt to read data from a system file being managed by the system failed.

S:
  • 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.

O:
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.

KAVB8104-E

An attempt to write data to the system file (file-name) has failed. : system-error-code

An attempt to write data to a system file being managed by the system failed.

S:
Deletes the system file to which data could not be written and continues processing.

O:
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.

KAVB8105-E

An attempt to delete the system file (file-name) has failed. : system-error-code

An attempt to delete a system file being managed by the system failed.

S:
Stops file deletion processing and continues processing.

O:
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.

KAVB8400-E

The option is invalid

An option was invalid.

S:
Terminates processing.

O:
Check the option, and then re-execute the command.

KAVB8402-E

Specify the process ID.

No process ID was specified.

S:
Terminates processing.

O:
Specify a process ID, and then re-execute the command.

KAVB8403-E

The process ID is specified more than once.

Multiple process IDs were specified.

S:
Terminates processing.

O:
Specify only one process ID, and then re-execute the command.

KAVB8404-E

Specify the process ID of control-name process.

The process ID of a JP1/IM - Manager or JP1/IM - View process was not specified.

S:
Terminates processing.

O:
Specify a process ID for the JP1/IM - Manager or JP1/IM - View process, and then re-execute the command.

KAVB8405-E

The process ID is invalid.

A process ID value is invalid.

S:
Terminates processing.

O:
Make sure that a process ID is specified, and then re-execute the command.

KAVB8406-I

The core dump file will be output.

A core dump file will be output.

S:
Continues processing.

KAVB8407-I

When the core dump is output, process-name will stop. Is this OK? (y/n)

Confirms that it is OK to execute a core dump output.

S:
Waits for a user response. If y is entered, continues processing. If n is entered, terminates the command.

O:
To continue command execution, enter y. To suspend command execution, enter n.

KAVB8408-E

The specified process is not running.

The specified process is not running.

S:
Terminates processing.

O:
Determine whether the process is running.

KAVB8409-E

An error occurred during command execution. (cause : reason)

An error occurred during command execution.

S:
Terminates processing.

O:
Eliminate the cause of the error, and then re-execute the command. If the command cannot be executed, use the data collection tool to collect data, and then contact a system administrator.

KAVB8410-E

The process management process of JP1/IM -View is not running.

The process management process of JP1/IM -View is not running.

S:
Terminates processing.

O:
Make sure that JP1/IM - View is running. Alternatively, make sure that the process management process (jcoview.exe) of JP1/IM - View is running.

KAVB8411-E

The user lacks execution permission.

The user does not have permission to execute the command.

S:
Terminates processing.

O:
Log in as a user with Administrator or similar permissions, and then re-execute the command.

KAVB8412-E

JP1/IM - Manager is not running.

JP1/IM - Manager is not running.

S:
Terminates processing.

O:
Make sure that JP1/IM - Manager is running.

KAVB8413-E

An attempt to send the thread dump output request has failed.

An attempt to send a thread dump output request failed.

S:
Terminates processing.

O:
  • In JP1/IM - View, make sure that JP1/IM - View process management (jcoview.exe) is running.
  • In JP1/IM - Manager, make sure that the process management process (jco_spmd.exe) is running.

KAVB8414-I

The thread dump output request has been sent.

A thread dump output request transmission was completed.

S:
Continues processing.

KAVB8415-E

An attempt to open the message file has failed.

An attempt to open a message file failed.

S:
Terminates processing.

O:
Use the data collection tool to collect data, and then contact a system administrator.

KAVB8416-I

The core dump file has been output.

The core dump file was output.

S:
Continues processing.

KAVB8417-I

Please enter a number for the process to output the core dump file [1-6]:

Enter the number for the process to output the core dump file.

S:
Waits for entry of information.

O:
Enter the number for the process to output the core dump file.

KAVB8418-E

The specified logical host name does not exist.

The specified logical host does not exist.

S:
Terminates processing.

O:
Check the specified logical host name, and then re-execute the command.

KAVB8419-E

An attempt to read a shared configuration definition has failed.

An attempt to read common definition information failed.

S:
Terminates processing.

O:
Use the data collection tool to collect data, and then contact a system administrator.

KAVB8420-E

Specify the process name of JP1/IM - Manager.

The JP1/IM - Manager process name was not specified.

S:
Terminates processing.

O:
Specify the JP1/IM - Manager process name, and then re-execute the command.

KAVB8421-E

The process management daemon is busy.

A command is being processed.

S:
Terminates processing.

O:
Wait until processing is finished, and then re-execute the command.

KAVB8422-E

The lock file in the conf directory cannot be opened.

An attempt to open a lock file failed.

S:
Terminates processing.

O:
Make sure that the conf directory exists and that the user has write permission. If operating in a cluster environment, make sure that the defined conf directory exists and that the user has write permission.

KAVB8423-I

The core dump file (file-name) will be overwritten. Is this OK? (y/n):

Confirms that it is OK to overwrite the core dump file.

O:
Enter y to overwrite the core dump file. Enter n to cancel overwriting of the core dump file.

KAVB8424-I

Please enter a number for the process to output the dump file [1-4]:

Enter a number for the process to output the dump file.

KAVB8425-E

The process information could not be obtained by the process management daemon. (cause: reason)

An attempt to acquire information for the process to output the core dump file failed.

S:
Terminates command execution.

O:
Execute the jco_spmd_status command to determine whether process management is operating normally.
If the jco_spmd_status command ends abnormally, check the integrated trace log to see if a process management error message was output.
If a message was output, take the corrective action given for that message.
If the problem cannot be resolved by the above method, use the data collection tool to collect data, and then contact a system administrator.

KAVB8426-I

The process to output the dump is not running.

A dump could not be output because JP1/IM - Manager processes that are able to output a dump were stopped.

S:
Terminates command execution.

KAVB8427-I

When outputting dumps for the three processes evflow, jcamain, and evtcon at the same time, output the dumps in order of evtcon, jcamain, and evflow.

When outputting dumps for the evflow, jcamain, and evtcon processes at the same time, output the dumps in the order evtcon, jcamain, evflow.

S:
Continues command processing.

KAVB8428-W

The core dump file was not found.

No core dump file was found due to one of the following reasons:

  • No core dump file was output.
  • The output directory for the core dump file or the file name was changed.

S:
Continues command processing.

O:
Check the following items:
  • Is there sufficient disk space?
    Core dump files are output to the default output directories shown below. If there is insufficient free space, no core dump file is output.
    - For a physical host: /var/opt/jp1cons/log/
    - For a logical host: shared-directory/jp1cons/log/
  • Is the size of the core dump file set to 0?
    Check the root user's file size setting for core dump files. If the size of the core dump file is set to 0, no core dump file is output.

If the core dump file's output directory or file name was changed from the default settings, the data collection tool may not be able to collect the core dump file when the tool is executed. The data collection tool collects the files whose names begin with core in the default output directories shown below.

  • For a physical host: /var/opt/jp1cons/log/
  • For a logical host: shared-directory/jp1cons/log/

To collect previously output core dump files using the data collection tool, you must take the following actions before executing the data collection tool.

  • If the core dump file's output directory was changed:
    Copy the core dump file that was output to the default output directory.
  • If the core dump file's name was changed:
    Rename the core dump file that was output to a file name that begins with core.

KAVB8430-E

The file cannot be saved because of an invalid file name. (file=file-name)

The file cannot be saved because the file name is invalid. Invalid file names as are follows.

  1. Names that include any of the following characters: :, ?, ", <, >, |
  2. Exact matches of any of the following characters strings (including lower case): CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, LPT9
  3. Any of the file names in 1 or 2 with a suffix of .xxx (xxx can be any characters).
    (Example)CON.txt, PRN.txt.conf

S:
Suspends processing.

O:
Correct the file and directory names, and then retry the operation.

KAVB8500-E

Execute the command from the administrator console.

This command must be executed from the administrator console.

S:
Terminates command processing.

O:
Execute the command from the administrator console.

KAVB8600-I

The service control-name confirmed that the IM database service started.

The control-name process confirmed that the IM database service is running.

S:
Continues processing.

KAVB8601-I

The service control-name is waiting for the IM database service to start.

The control-name process is waiting for completion of IM database service startup.

S:
Waits for the IM database service to start.

KAVB8602-E

The service control-name could not be started because the status of the IM database service could not be confirmed. (details = reason)

The control-name process could not start because completion of IM database service startup could not be confirmed.

S:
The control-name process stops.

O:
Take corrective action based on the reason:
  • Reason: Processing to start or stop the IM database service is being performed.
  • Reason: The IM database service stopped.
    Execute the jimdbstatus command, confirm that the IM database service is running, and then perform the next operation.

In Windows:
Start the IM database service, and then restart JP1/IM - Manager.

In UNIX:
Stop JP1/IM - Manager, and then re-execute the jco_start command.
If this error occurs when the OS is starting, specify the following common definition information, and then increase the number of retries so that it does not time out.
- [logical-host-name\JP1CONSOLEMANAGER\IMDB]
- DB_START_RETRY_COUNT
  • Reason: The restart of the IM database service was interrupted.
    Execute jimdbstop -f, forcibly stop the IM database service, and then perform the next operation.

In Windows:
Start the IM database service, and then restart JP1/IM - Manager.

In UNIX:
Re-execute the jco_start command.
  • Reason: The IM database service has not been set up.
    Set up the IM database service, and then start JP1/IM - Manager.
  • Reason: The status of the IM database service could not be confirmed.
  • Reason: A system error occurred.
    Collect JP1/IM data, and then contact a system administrator.

KAVB8603-E

A request cannot be executed because the service control-name is waiting for the IM database service to start.

Processing could not be performed because the control-name process is waiting for completion of IM database service startup.

S:
Terminates processing.

O:
Execute the jimdbstatus command, and then check the status of the IM database service on the manager host.
Make sure that the IM database service is running, and then retry the operation.
If a KAVB8602-E message was output to the integrated trace log on the manager host, take the corrective action given for the KAVB8602-E message.

KAVB8604-I

A connection to the Integrated Monitoring database has been established.

A connection to the integrated monitoring database was established.

S:
Connects to the integrated monitoring database.

KAVB8605-E

Initialization of the Integrated Monitoring database API has failed. (reason = reason)

An attempt to initialize the integrated monitoring database API failed.

S:
Suspends processing.

O:
Determine whether the port number assigned to the IM database service is being used by another product.
If another product is using the same port, specify a unique port number for the IM database service.
If another product is not using the same port, or the error cannot be resolved by reassigning the port number, collect JP1/IM data, and then contact a system administrator.

KAVB8606-E

An attempt to establish a connection when initializing the Integrated Monitoring database has failed. (reason = reason)

An attempt to establish a connection when initializing the integrated monitoring database failed.

S:
Suspends processing.

O:
Take corrective action based on the reason.
  • Reason: An error occurred because a service is not running.
    Make sure that the IM database service is running, and then restart JP1/IM - Manager.
  • Reason: A connection error occurred.
    The system may be temporarily unable to acquire a connection or to use a connection. If the error is not resolved by restarting JP1/IM - Manager, collect JP1/IM data, and then contact a system administrator.
  • Reason: A system error occurred.
    Determine whether the port number assigned to the IM database service is being used by another product.
    If another product is using the same port, specify a unique port number for the IM database service. If another product is not using the same port, or the error cannot be resolved by reassigning the port number, collect JP1/IM data, and then contact a system administrator.

KAVB8607-E

Initialization of an Integrated Monitoring database table has failed. (reason = reason)

An error occurred during initialization of the integrated monitoring database table.

S:
Suspends processing.

O:
Take corrective action based on the reason.
  • Reason: An error occurred because a service is not running.
    Make sure that the IM database service is running, and then restart JP1/IM - Manager.
  • Reason: A communication error occurred. or A resource shortage occurred.
    Make sure that there are sufficient OS resources such as memory and file descriptors, and then restart JP1/IM - Manager. If the error is not resolved by restarting JP1/IM - Manager, collect JP1/IM data, and then contact a system administrator.
  • Reason: A connection error occurred.
    The system may be temporarily unable to acquire a connection or to use a connection. If the error is not resolved by restarting JP1/IM - Manager, collect JP1/IM data, and then contact a system administrator.
  • Reason: A system error occurred.
    Determine whether the port number assigned to the IM database service is being used by another product.
    If another product is using the same port, specify a unique port number for the IM database service. If another product is not using the same port, or the error cannot be resolved by reassigning the port number, collect JP1/IM data, and then contact a system administrator.

KAVB8800-E

An attempt to stop the JP1/IM - Manager has failed.

JP1/IM - Manager did not stop after a retry was performed.

S:
Terminates the command.

O:
Execute the jco_spmd_status command, and then check the status of JP1/IM - Manager. If JP1/IM - Manager has not stopped, re-execute the jco_stop command.
If using the IM database service, execute the jimdbstatus command, and then check the status of the IM database service. If the IM database service has not stopped, re-execute the jco_stop command.

KAVB8801-E

An attempt to stop the IM Database service has failed.

The IM database did not stop after a retry was performed.

S:
Terminates the command.

O:
Execute the jimdbstatus command, and then check the status of the IM database service. If the IM database service has not stopped, re-execute the jco_stop command.

KAVB8900-E

The command option is invalid.

The specified command option is invalid.

S:
Suspends command processing.

O:
Specify a valid command option, and then run the data collection tool again.

KAVB8901-E

The command option (option) is duplicated.

The specified command option (option) was duplicated.

S:
Suspends command processing.

O:
Specify a valid command option, and then run the data collection tool again.

KAVB8902-E

The logical host (logical-host-name) does not exist.

The specified logical-host-name does not exist.

S:
Suspends command processing.

O:
Carefully review the specified logical host name to make sure that it is correct, and then run the data collection tool again.

KAVB8903-E

The host name is not specified in the -h option.

No host name is specified by the -h option.

S:
Suspends command processing.

O:
Specify a valid command option, and then run the data collection tool again.

KAVB8904-E

The shared directory (shared-directory-path) used by the specified logical host (logical-host-name) was not found.

The shared directory (shared-directory-path) used by the specified logical host (logical-host-name) was not found.

S:
Continues command processing.

O:
For active server hosts, install the shared directory, and then run the data collection tool again.
For standby server hosts, no shared directory is installed, so no corrective action is necessary.

KAVB8905-E

The specified directory (data-storage-directory-name) is invalid.

The specified directory (data-storage-directory-name) is invalid.

S:
Suspends command processing.

O:
Specify a valid data storage directory, and then execute the data collection command again.
In Windows, check the following items:
  • Was a reserved device name (AUX, CON, NUL, PRN, COM1 to COM9, or LPT1 to LPT9) or any of the symbols ,, ;, %, &, ^, or ! used?
  • Was the specified directory name longer than 128 bytes?

KAVB8906-E

The directory has the same name as an existing file (file-name).

A file (file-name) with the same name as the directory already exists.

S:
Suspends command processing.

O:
Delete the file with the same name, and then run the data collection tool again.

KAVB8907-E

The directory (directory-name) could not be written to.

There is insufficient write permission for the directory (directory-name).

S:
Suspends command processing.

O:
Carefully review the executing user's write permission for the directory, and then run the data collection tool again.

KAVB8908-W

The directory (directory-path) used by the physical host does not exist.

The directory being used by the physical host does not exist.

S:
Continues processing without acquiring data in the directory path.

O:
Determine whether the directory path was temporarily disconnected.

KAVB8909-E

command-name does not exist.

command-name does not exist.

S:
Suspends command processing.

O:
Determine whether the command was deleted. If it does not exist, re-install JP1/IM - Manager.

KAVB8910-E

There is not enough free disk space to execute the command.

There is not enough disk space to execute the command.

S:
Suspends command processing.

O:
Check the amount of available disk space, increase available disk space by deleting unnecessary files, and then run the data collection tool again.
Also delete the data that was acquired before processing was suspended.

KAVB8911-E

There is not enough memory to execute the command.

There is not enough memory to execute the command.

S:
Suspends command processing.

O:
Check the amount of free space in system memory, increase available memory by stopping unnecessary processes, and then run the data collection tool again.

KAVB8912-W

An attempt to acquire the Windows event log (event-log-type) has failed.

An attempt to acquire the Windows event log failed.

Event log type: System or Application

S:
Continues command processing.

O:
Use the event viewer to acquire the Windows event log manually.

KAVB8913-E

The specified file cannot be read (file-name).

The specified file name cannot be read.

S:
Suspends command processing.

O:
Check the read permission for the specified file, and then run the data collection tool again.

KAVB8914-E

The specified file does not exist (file-name).

The specified file does not exist.

S:
Suspends command processing.

O:
Specify an existing file, and then run the data collection tool again.

KAVB8915-E

The specified directory has the same name as an existing file (file-name).

A file (file-name) with the same name as the specified data storage directory already exists.

S:
Suspends command processing.

O:
Either specify a different directory or delete the file with the same name, and then run the data collection tool again.

KAVB8916-E

A write operation cannot be performed for the specified directory (directory-name).

A write operation cannot be performed in the specified data storage directory.

S:
Suspends command processing.

O:
Either specify a different directory or make sure that the executing user has write permission for the directory above the specified directory, and then run the data collection tool again.

KAVB8917-E

An attempt to create the directory (directory-name) has failed.

An attempt to create a directory failed.

S:
Suspends command processing.

O:
Either specify a different directory or make sure that the executing user has write permission for the directory above the specified directory, and then run the data collection tool again.

KAVB8918-I

The data was successfully acquired.

Reports that data was successfully acquired.

S:
Terminates the command.

KAVB8919-E

Some of the data could not be acquired.

Some of the data could not be acquired. This message is output following messages that are output during execution.

S:
Terminates command processing.

O:
Take the corrective action given for the message that was output during execution.

KAVB8920-I

Deletion of the core dump file (dump-file-name) has finished.

Deletion of the core dump file (dump-file-name) is complete.

S:
Continues command processing.

KAVB8921-I

information will be acquired.

Reports that the data of information will be acquired.

S:
Continues command processing.

KAVB8922-I

information has been acquired.

Reports that the data of information was acquired.

S:
Continues command processing.

KAVB8923-W

information could not be acquired.

Reports that the data of information could not be acquired.

S:
Continues command processing.

O:
Refer to jim_log_result.log to see if data exists at the collection source, and then manually acquire the data that could not be acquired.

KAVB8924-I

The directory already exists. (directory-name)
The directory will be re-created.

directory-name already exists. Re-creates the directory.

S:
In Windows: Waits for a user response, then deletes the directory and continues processing.
In UNIX: Continues processing.

O:
In Windows: To continue processing, press any key. To suspend processing, press Ctrl + C.
In UNIX: No corrective action is necessary.

KAVB8925-I

The directory does not exist. (directory-name) The directory will be created.

directory-name does not exist. Creates the directory.

S:
In Windows: Waits for a user response, then creates the directory and continues processing.
In UNIX: Continues processing.

O:
In Windows: To continue processing, press any key. To suspend processing, press Ctrl + C.
In UNIX: No corrective action is necessary.

KAVB8926-I

Data acquisition processing will start.

Starts data acquisition.

S:
Continues command processing.

KAVB8927-I

Execution of the command-name command will start.

Starts executing command-name.

S:
Continues command processing.

KAVB8928-I

command-name execution is ended. (ERRORLEVEL=error-level)

command execution ended.

ERRORLEVEL: Return code of the command

S:
Continues command processing.

KAVB8929-I

information will be acquired. Please wait.

Wait until information is acquired.

S:
Continues command processing.

KAVB8930-E

An attempt to delete the directory (directory-name) has failed.

An attempt to delete the directory failed.

S:
Suspends command processing.

O:
Determine whether the directory is being used by another process. Make sure that it is not being used by another process, or specify another directory, and then run the data collection tool again.

KAVB8931-W

command-name does not exist.

command-name does not exist.

S:
Continues command processing.

O:
Determine whether the command was deleted. If the command does not exist, re-install JP1/IM - Manager.

KAVB8932-E

command-name does not exist.

command-name does not exist.

S:
Suspends command processing.

O:
Determine whether the command was deleted. If the command does not exist, re-install JP1/Base and JP1/IM - Manager.

KAVB8933-E

An attempt to access the registry for (information) has failed. (detailed-information)

An attempt to access the registry for information failed.

detailed-information: The argument passed to the function RegOpenKeyEx/RegEnumKeyEx and the return code.

S:
Suspends command processing.

O:
Contact a system administrator.

KAVB8934-I

The following logical host(s) exist on this machine:
logical-host-name
To acquire information about a logical host, execute "command-name -f output-directory-name -h logical-hostname".

The following logical-host exists on this computer.

Execute command-name -h logical-host-name to collect the logical host information.

S:
Continues command processing.

O:
Execute command-name -h logical-host-name to collect the logical host information.

KAVB8935-I

The following logical host(s) exist on this machine:
logical-host-name
To acquire information about a logical host, execute "command-name -f output-directory-name -h logical-hostname".

The following logical-host exists on this computer.

Execute command-name -h logical-host-name to collect the logical host information.

S:
Continues command processing.

O:
Execute command-name -h logical-host-name to collect the logical host information.

KAVB8936-W

An attempt to create the directory (directory-name) has failed.

An attempt to create directory failed.

S:
Continues command processing.

O:
Make sure that the executing user has write permission for the directory above the specified directory, and then run the data collection tool again.

KAVB8937-W

An attempt to execute command has failed. (rc=detailed-information)

An attempt to execute command failed.

detailed-information: Return code of the command

S:
Continues command processing.

O:
Take the corrective action given for the message that was output preceding this message.

KAVB8938-I

Execution of command was successful.

command was successfully executed.

S:
Continues command processing.

KAVB8939-E

The user does not have execution permission for the command (command-name).

The user does not have permission to execute command.

S:
Suspends command processing.

O:
Check the access permission for the command.

KAVB8940-I

Deletion of the thread dump file has finished.

Deletion of the thread dump file is complete.

S:
Continues command processing.

KAVB8941-I

Do you want to delete all the core dump files below the directory directory-name? [yes/no]

Confirms that you want to delete the core dump files located in the directory indicated by directory-name.

S:
If yes or y is entered, deletes the core dump files and terminates command processing.
If no or n is entered, terminates command processing without deleting the core dump files.

O:
To delete the core dump files, enter yes or y.
To cancel deleting of the core dump files, enter no or n.

KAVB8942-I

Do you want to delete all the thread dump files below the directory directory-name? [yes/no]

Confirms that you want to delete the thread dump files located in the directory indicated by directory-name.

S:
If yes or y is entered, deletes the thread dump files and terminates command processing.
If no or n is entered, terminates command processing without deleting the thread dump files.

O:
To delete the thread dump files, enter yes or y.
To cancel deleting of the thread dump files, enter no or n.

KAVB8943-E

A write operation cannot be performed because a file with the same name (file-name) already exists.

A write operation cannot be performed because a file with the same name already exists.

S:
Continues processing without creating a file.

O:
Check the write permission for the file. If the file is not needed, delete it, and then run the data collection tool again.

KAVB8944-I

file-name already exists. Do you want to overwrite it? [yes/no]

The file already exists. Do you want to overwrite it?

S:
If yes or y is entered, overwrites the file and continues command processing.
If no or n is entered, continues command processing without overwriting the file.

O:
To overwrite the file, enter yes or y.
To cancel overwriting of the file, enter no or n.

KAVB8945-I

Is the device (device-name) ready? [yes/no]

Is the device ready?

S:
If yes or y is entered, acquires data for the device and continues command processing.
If no or n is entered, continues command processing without acquiring data for the device.

O:
To acquire data for the device, enter yes or y.
To cancel acquisition of data for the device, enter no or n.

KAVB8946-I

Do you want to delete all the thread dump files below the directory directory-name? [y/n]

Confirms that you want to delete thread dump files located in the directory indicated by directory-name.

S:
If y is entered, deletes the thread dump files and terminates command processing.
If n is entered, terminates command processing without deleting the thread dump files.

O:
To delete the thread dump files, enter y.
To cancel deleting of the thread dump files, enter n.

KAVB8947-W

An attempt to get the IM Database backup file failed.

An attempt to acquire the IM database backup file failed.

S:
Continues command processing.

O:
Check the following items:
  • Is the IM database running?
  • Is sufficient system memory allocated?
  • Is there sufficient disk space in the destination folder for the IM database backup?

[Contents][Back][Next]

[Trademarks]

All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.