Job Management Partner 1/Integrated Management - Manager Messages

2.7 Messages related to Central Scope Service (KAVB7001 to KAVB7999)

KAVB7001-I
The JP1/IM - Central Scope daemon has started. (Logical hostname: logical-host-name)

Central Scope Service started. If it is running on a physical host, logical-host-name is set to JP1_DEFAULT.

S:

Starts Central Scope Service.

KAVB7002-I
The JP1/IM - Central Scope daemon terminated normally. (Logical hostname: logical-host-name)

Central Scope Service stopped normally. If it is running on a physical host, logical-host-name is set to JP1_DEFAULT.

S:

Stops Central Scope Service normally.

KAVB7003-E
The JP1/IM - Central Scope daemon terminated abnormally. (Logical hostname: logical-host-name, End code: reason-code)

Central Scope Service stopped abnormally. If it is running on a physical host, logical-host-name is set to JP1_DEFAULT.

S:

Stops Central Scope Service abnormally.

O:

Check the system status based on the reason code. If the system does not recover normally, use the data collection tool to collect data, and then contact a system administrator.

Reason code: 4
Description: An attempt to initialize the JP1/Base communications base failed.
Action: Refer to the Job Management Partner 1/Base User's Guide to confirm that the communications base is set correctly.

Reason code: 7
Description: An ANSI exception occurred during startup processing.
Action: Make sure that memory or resources are sufficient.

Reason code: 8
Description: An HCCLib exception occurred during startup processing.
Action: Make sure that memory or resources are sufficient.

Reason code: 9
Description: An error occurred during Central Scope Service initialization.
Action: Take the corrective action given for the message that was output preceding this message.

Reason code: 10
Description: Startup notification could not be sent to the process management daemon.
Action: Determine whether the daemon was started from a start script (in Windows, a service) rather than directly.

Reason code: 255
Description: A problem occurred while Central Scope Service was running, and the service stopped abnormally.
Action: Take the corrective action given for the message that was output preceding this message.

KAVB7004-E
JP1/IM - Central Scope daemon will now stop because the logical hostname is invalid.

Central Scope Service will stop because the logical host name received from the process management daemon was invalid.

S:

Stops Central Scope Service.

O:

Check the logical host name definitions for errors.

KAVB7005-E
The JP1/IM - Central Scope daemon will now stop because the initialization of the JP1/Base common configuration failed.

Central Scope Service will stop because an attempt to initialize the JP1/Base common definitions failed.

S:

Stops Central Scope Service.

O:

Check the JP1/Base configuration for errors.

KAVB7006-E
The JP1/IM - Central Scope daemon will now stop because an attempt to initialize the internal trace log has failed.

Central Scope Service will stop because an attempt to initialize the internal log file failed.

S:

Stops Central Scope Service.

O:

Determine whether JP1/Base was uninstalled after installing JP1/IM - Manager. If it was not uninstalled, check the free space in system memory. Either increase available memory by stopping any unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

KAVB7007-E
The JP1/IM - Central Scope daemon will now stop because an attempt to initialize the message log file has failed.

Central Scope Service will stop because an attempt to initialize the log file for messages with IDs failed.

S:

Stops Central Scope Service.

O:

Check the free space in system memory. Either increase available memory by stopping any unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

KAVB7100-I
The initialization of the JP1/Base communication base has been completed.

The initialization of the JP1/Base communication base is complete.

S:

Completes initialization of the JP1/Base communication base.

KAVB7101-W
The jp1hosts cannot be validated, because the definition of jp1host is invalid.

jp1hosts cannot be validated because the definitions in jp1hosts are incorrect.

S:

Continues processing.

O:

Check the definitions in jp1hosts for errors.

KAVB7102-E
An attempt to initialize the JP1/BASE communication base failed. (Error code: reason-code)

Central Scope Service will stop because an attempt to initialize the JP1/BASE communication base failed.

S:

Stops Central Scope Service.

O:

Check the JP1/Base configuration for errors, and take action according to the error code.

Reason code: -1
Description: No logical host key exists in the common definitions.
Action: Refer to the Job Management Partner 1/Base User's Guide to determine whether logical host definitions exist for services started up with common definitions.

Reason code: -2
Description: JP1/Base communications base definition information is invalid.
Action: Refer to the Job Management Partner 1/Base User's Guide to determine whether there are errors in the JP1/Base communications base definition information.

Reason code: -4
Description: No logical host key exists in the common definitions, and the jp1hosts definition is incorrect.
Action: Refer to the Job Management Partner 1/Base User's Guide to determine whether logical host definitions exist for services started up with common definitions. Also check the jp1hosts definition for errors.

Reason code: -5
Description: JP1/Base communications base definition information is invalid, and the jp1hosts definition is incorrect.
Action: Refer to the Job Management Partner 1/Base User's Guide to determine whether there are errors in the JP1/Base communications base definition information and jp1hosts definition.

KAVB7103-W
The JP1/IM - Central Scope daemon will be started using the default port number (20305), because an attempt to acquire the port number has failed.

Central Scope Service will start using the default port number (20305) because an attempt to acquire a port number failed.

S:

Continues processing.

O:

Determine whether there are errors in the service file definitions.

KAVB7104-W
The JP1/IM - Central Scope daemon will be started using the default port number (20305), because OS reserves the defined port number (within 1023).

Central Scope Service will start using the default port number (20305) because the OS reserves the acquired port number (1023 or lower).

S:

Continues processing.

O:

Check the service file definitions for errors.

KAVB7105-I
The data in the JP1/IM - Central Scope daemon will be updated due to the reload request from the process management daemon.

The data in Central Scope Service is updated due to a reload request from the process management daemon.

S:

Updates the data in Central Scope Service.

KAVB7106-I
The updating of the data within the JP1/IM - Central Scope daemon succeeded.

Updating of the data in Central Scope Service was successful.

S:

Finishes updating the data in Central Scope Service normally.

KAVB7107-W
An attempt to update the data within JP1/IM - Central Scope has failed. The processing will continue using the old data.

An attempt to update the data in Central Scope Service failed. Processing continues using the previous data.

S:

Continues processing.

O:

Some data was not reloaded. Take the corrective action given for the message that was output preceding this message.

KAVB7108-I
The JP1/IM - Central Scope daemon will be stopped because a stop request was sent from the process management daemon.

Central Scope Service will stop because a stop request was sent from the process management daemon.

S:

Begins stop processing for Central Scope Service.

KAVB7109-E
The JP1/IM - Central daemon will be stopped because an invalid request was sent from the process management daemon.

Central Scope Service will stop because an invalid request was sent from the process management daemon.

S:

Begins stop processing for Central Scope Service.

O:

Process management daemon operation is abnormal. Take the corrective action given for the message that was output preceding this message.

KAVB7110-E
An attempt to report the startup to the process management daemon failed.

An attempt to report the startup to the process management daemon failed.

S:

Stops Central Scope Service.

O:

Process management daemon operation is abnormal. Take the corrective action given for the message that was output preceding this message.

KAVB7111-I
The creation of all the threads waiting for TCP/IP communication succeeded.

The creation of all threads waiting for TCP/IP communication was successful.

S:

The creation of all threads waiting for TCP/IP communication succeeded.

KAVB7112-W
The process continues even though a part of a thread waiting for TCP/IP communication has failed.

An attempt to create part of a thread waiting for TCP/IP communication failed, and processing continues.

S:

An attempt to create part of a thread waiting for TCP/IP communication failed. Continues processing.

O:

An attempt to create a TCP/IP socket failed for some IP addresses. Refer to the KAVB7115-E message that was output preceding this message, and then determine whether the problematic IP addresses can be used.

KAVB7113-E
The JP1/IM - Central Scope daemon will now stop because the creation of all the threads waiting TCP/IP communication has failed.

Central Scope Service will stop because an attempt to create all threads waiting for TCP/IP communication failed.

S:

Stops Central Scope Service.

O:

Refer to the KAVB7115-E message that was output preceding this message, and then determine whether the problematic IP addresses can be used.

KAVB7114-I
The creation of the threads waiting for the TCP/IP communication by IP address (IP-address) succeeded.

The creation of threads waiting for TCP/IP communication by IP address was successful.

S:

The creation of threads waiting for TCP/IP communication by IP address (IP-address) was successful.

KAVB7115-E
An attempt to create the thread for waiting for the TCP/IP communication by the IP address (IP-address) has failed.

An attempt to create a thread waiting for TCP/IP communication by IP address failed.

S:

Fails to create a thread waiting for TCP/IP communication by IP address.

O:

Make sure that you can use IP addresses on the server system that will run JP1/IM - Manager. Also make sure that the definitions of server names and IP addresses on the system and JP1/Base are correct.

KAVB7116-E
The JP1/IM - Central Scope daemon was stopped, because the database version is too old.

Service startup was canceled because the database version is not supported.

S:

Stops Central Scope Service.

O:

Convert the database by running the jp1csverup command (on a physical host) or the jp1cshaverup command (on a logical host).

KAVB7117-I
Startup will use the environment variable LANG (environment-variable-LANG) and the character encoding (character-code).

A server or command starts with an environment variable LANG (environment-variable-LANG) and character code (character-code). Windows normally does not output environment variable LANG.

S:

Continues processing.

KAVB7118-E
An attempt to set the message file has failed.

An attempt to set the message file failed.

S:

Suspends processing.

O:

Check the free space in system memory. Either increase available memory by stopping any unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

KAVB7119-E
An attempt to initialize the database has failed.

An attempt to initialize the database failed.

S:

Stops Central Scope Service.

O:

An attempt to build the database may have failed at installation. Check the installation log, execute the jcsdbsetup command to rebuild the database, and then restart JP1/IM - Manager. If the database was built correctly, there may be insufficient kernel parameters. Check the settings for kernel parameters, and then restart JP1/IM - Manager.

KAVB7120-E
An attempt to initialize the plugin service has failed. (err code: reason-code)

Central Scope Service will stop because an attempt to initialize the JP1/Base plug-in service failed.

S:

Stops Central Scope Service.

O:

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

KAVB7121-W
The database will be recovered from the backup because the database is corrupt.

The database will be recovered from backup because damage to the database was detected when Central Scope Service started.

S:

Continues processing.

O:

The latest changes may not have been saved. Make sure that the monitoring tree configuration is correct.

KAVB7122-E
The JP1/IM-Central Scope daemon will be stopped because an attempt to recover the database failed. (Cause: reason-code)

An attempt to recover the database failed because damage to the database was detected when Central Scope Service started. Central Scope Service stops.

S:

Stops Central Scope Service.

O:

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

KAVB7123-I
Startup will use the monitored object DB version CSV-version-of-monitored-object-DB.

Startup will use the monitored object DB version CSV-version-of-monitored-object-DB.

S:

Continues processing.

KAVB7124-W
Startup will use compatibility mode.

Startup will use compatibility mode. Only functionality predating the version upgrade can be used.

S:

Continues processing.

O:

To use all functionality from after the version upgrade, convert the database by executing the jp1csverup command (for a physical host) or the jp1cshaverup command (for a logical host).

KAVB7127-E
The event monitoring thread ended abnormally (Cause:reason-code)

The service stopped because an abnormality was detected in the event monitoring thread.

S:

Stops the service.

O:

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

KAVB7128-E
An attempt to initialize the event monitoring has failed because the memory was insufficient.

An attempt to initialize event monitoring while starting the service failed because the a memory shortage occurredwas insufficient.

S:

Stops Central Scope Service.

O:

Check the free space in system memory. Either increase available memory by stopping any unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

KAVB7129-E
An attempt to initialize the event monitoring has failed because the resources were insufficient.

An attempt to initialize event monitoring while starting the service failed because resources such as file descriptors were insufficient.

S:

Stops Central Scope Service.

O:

Make sure that system resources such as file descriptors are sufficient, and then restart JP1/IM - Manager.

KAVB7130-E
An attempt to initialize the event monitoring has failed because the IM-CC (event flow control) was not started.

An attempt to initialize event monitoring while starting the service failed because JP1/IM - Manager (event flow control) stopped or was not running.

S:

Stops the service.

O:

Make sure that JP1/IM - Manager (event flow control) is running, and then restart JP1/IM - Manager.

KAVB7131-E
An attempt to initialize the event monitoring has failed. (Cause: reason-code)

An attempt to initialize event monitoring while starting the service failed.

S:

Stops the service.

O:

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

KAVB7132-E
An attempt to monitor the event monitoring has failed because the memory was insufficient.

Memory became insufficient during event monitoring, preventing event monitoring. When the memory insufficiency is resolved, event monitoring will continue.

S:

Event monitoring continues.

O:

Check the free space in system memory. Either increase available memory by stopping any unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

KAVB7133-E
An attempt to monitor the event has failed. (Cause:reason-code)

An attempt to monitor an event failed.

S:

Event monitoring continues.

O:

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

KAVB7134-E
The event (event-ID) has failed to change the node condition because the memory was insufficient

The received event failed to change the node status condition because a memory shortage occurred.

S:

Cancels the status change of the monitoring node by the received event and continues event monitoring.

O:

Check the free space in system memory., Either increase available memory by stopping any unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

KAVB7135-E
The event (event-ID) has failed to change the node condition because the database was not accessible.

The event failed to change the node status condition because the database was not accessible.

S:

Cancels the status change of the monitoring node by the received event and continues event monitoring.

O:

Check access permissions for database files and directories.

KAVB7136-E
The event (event-ID) has failed to change the node condition. (Cause:reason-code).

The event could not change the node status condition.

S:

Cancels the status change of the monitoring node by the received event and continues event monitoring.

O:

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

KAVB7137-E
An attempt to create the condition change event message for the monitoring node (node name: node-ID) has failed because the memory was insufficient.

The status change of the monitoring node was successful, but the message for the status change event could not be created because a memory shortage occurred.

S:

Cancels issuing of the status change event set for the monitoring node by the received event and continues event monitoring.

O:

Check the free space in system memory. Either increase available memory by stopping any unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

KAVB7138-E
An attempt to create the condition change event message for the monitoring node (node name: node-ID) has failed. (Cause: reason-code)

The status change of the monitoring node was successful, but the message for the status change event could not be created.

S:

Cancels issuing of the status change event set for the monitoring node by the received event and continues event monitoring.

O:

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

KAVB7139-W
The extended information of the monitoring node (node-name) was dropped because the size of the received event is too large (event-ID).

The monitoring node whose status was changed could not be embedded in the status change event because the size of the extended information of the received event was too large. The part that exceeded the maximum size (10 kilobytes) was dropped.

S:

Continues event monitoring.

O:

If no attempt is made to access the extended information of the event that was dropped, no action is necessary. If you must access the extended information of the event that was dropped, access the directly received event instead.

KAVB7140-E
The status change event of the node (node-name) was not issued because the memory was insufficient.

The status change of the monitoring mode was successful, but the status change event was not issued because a memory shortage occurred.

S:

Cancels issuing of the status change event for the monitoring node by the received event and continues event monitoring.

O:

Check the free space in system memory. Either increase available memory by stopping any unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

KAVB7141-E
The status change event of the node (node-name) was not issued because the resource were insufficient

The status change of the monitoring mode was successful, but the status change event could not be issued because resources such as file descriptors were insufficient.

S:

Cancels issuing of the status change event for the monitoring node by the received event and continues event monitoring.

O:

Make sure that system resources such as file descriptors are sufficient, and then stop unnecessary processes.

KAVB7142-E
The status change event of the node (node-name) was not issued. (Cause:reason-code).

The status change of the monitoring mode was successful, but the status change event could not be issued.

S:

Cancels issuing of the status change event for the monitoring node by the received event and continues event monitoring.

O:

Check system conditions according to the error codes. If the system does not recover normally, use the data collection tool to collect data, and then contact a system administrator.

Reason code: 10 IMEV_S_PARAM_ERROR
Description: Parameter of Event Service API is invalid.
Action: System error. Use the data collection tool to collect data, and then contact a system administrator.

Reason code: 11 IMEV_S_SEQUENCE_ERROR
Description: Issue sequence of Event Service API is invalid.
Action: System error. Use the data collection tool to collect data, and then contact a system administrator.

Reason code: 40 IMEV_S_CONNECT_ERROR
Description: Cannot connect to Event Service.
Action: Make sure that JP1/Base (Event Service) is running.

Reason code: 43 IMEV_S_IO_ERR
Description: I/O error occurred in communication with Event Service.
Action: System error. Use the data collection tool to collect data, and then contact a system administrator.

Reason code: 51 IMEV_S_NOMEMORY
Description: Memory insufficient.
Action: Check system memory.

Reason code: 52 IMEV_S_MAXOPEN
Description: The system could not connect to Event Service because the number of open files reached its limit.
Action: Check the system's limit value for the number of open files.

Reason code: 60 IMEV_S_NOT_LOADING
Description: Communication with Event Service has not been initialized.
Action: Determine whether JP1/Base has been installed.

Reason code: 70 IMEV_S_SYSTEM_ERROR
Description: A system error occurred in Event Service API.
Action: System error. Use the data collection tool to collect data, and then contact a system administrator.

KAVB7144-E
An attempt to monitor the event has failed because the resources were insufficient.

An attempt to monitor the event failed because resources such as file descriptors were insufficient.

S:

Cancels reception of the event and continues event monitoring.

O:

Make sure that system resources such as file descriptors are sufficient, and stop unnecessary processes.

KAVB7145-E
An attempt to monitor the event has failed because it was not possible to connect with the event flow control.

An attempt to monitor the event failed because it was not possible to connect to JP1/IM - Manager (event flow control).

S:

Cancels reception of the event and continues event monitoring.

O:

Make sure that JP1/IM - Manager (event flow control) is running.

KAVB7148-E
Status change event for Node: node-name can't be launched. Because connection failed with Event service.

The status change of the monitoring mode was successful, but no status change event could be issued because the system could not connect to JP1/Base (Event Service control).

S:

Cancels issuing of the status change event for the monitoring node by the received event and continues event monitoring.

O:

Make sure that JP1/Base (Event Service control) is running.

KAVB7150-I
The TCP/IP communication waiting thread started.

The TCP/IP communication waiting thread has started.

S:

Starts the TCP/IP communication waiting thread.

KAVB7151-I
The TCP/IP communication waiting thread terminated normally.

The TCP/IP communication waiting thread ended normally.

S:

Terminates the TCP/IP communication waiting thread normally.

KAVB7152-E
The TCP/IP communication waiting thread terminated abnormally.

The TCP/IP communication waiting thread ended abnormally.

S:

Stops Central Scope Service.

O:

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

KAVB7153-W
The connection from JP1/IM - View will now be closed because the number of connection requests exceeds the maximum (64).

No further connections can be made because more than 64 JP1/IM - View units are connected.

S:

Closes the connection to JP1/IM - View.

O:

No new connections can be made. Close any unnecessary connections, and then reconnect to JP1/IM - View.

KAVB7154-W
An attempt too generate the communication request processing thread has failed, because there are not enough resources. The connection from JP1/IM - View will now be closed.

An attempt to generate the communication request processing thread failed because resources were insufficient.

S:

Closes the connection to JP1/IM - View.

O:

No new connections can be made. Exit unnecessary applications to resolve the resource insufficiency or close any unnecessary connections, and then re-connect to JP1/IM - View.

KAVB7155-E
The connection from JP1/IM - View will now be closed because the protocol was incorrect.

The connection to JP1/IM - View closed because the protocol was incorrect.

S:

Closes the connection to JP1/IM - View.

O:

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

KAVB7156-E
The request processing object cannot be created because an unsupported request has been sent from JP1/IM - View.

A request could not be processed because an unsupported request was sent from JP1/IM - View.

S:

Closes the connection to JP1/IM - View.

O:

Confirm that the version of JP1/IM - Manager is the version required by JP1/IM - View.

KAVB7157-E
The connection from JP1/IM - View will now be closed because an attempt to create the request processing object has failed.

The connection to JP1/IM - View closes because an attempt to create a request processing object failed.

S:

Closes the connection to JP1/IM - View.

O:

Confirm that the version of JP1/IM - Manager is the version required by JP1/IM - View.

KAVB7158-E
The connection from JP1/IM - View will now be closed because the login authentication has not been performed.

The connection to JP1/IM - View closes because the login authentication was not performed.

S:

Closes the connection to JP1/IM - View.

O:

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

KAVB7159-E
The connection from JP1/IM - View will now be closed because an error occurred during the request processing.

The connection to JP1/IM - View closes because an error occurred during request processing.

S:

Closes the connection to JP1/IM - View.

O:

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

KAVB7160-W
The communication process will now end because the closing of the connection to JP1/IM-View has been detected.

The communication process stopped because closing of the connection to JP1/IM - View was detected.

S:

Terminates the communication process with JP1/IM - View.

O:

Determine whether JP1/IM - View has generated a time-out or whether there is a problem in the communication environment.

KAVB7161-W
The communication process will now end because the waiting request from JP1/IM - View timed out.

The communication process stopped because a waiting request from JP1/IM - View timed out.

S:

Terminates the communication process with JP1/IM - View.

O:

Determine whether there is a problem in the communication environment.

KAVB7175-W
JP1/IM-CS (JP1/IM-Central-Scope-version) cannot process the request from JP1/IM-View (JP1/IM-View-version).

Requests from JP1/IM - View JP1/IM-View-version cannot be processed.

S:

Terminates the communication process with JP1/IM - View.

O:

Check the JP1/IM - View version.

KAVB7176-E
JP1/IM-CS (JP1/IM-Central-Scope-version) cannot process the request from JP1/IM-View (JP1/IM-View-version).

Requests from JP1/IM - View JP1/IM-View-version cannot be processed.

S:

Terminates the communication process with JP1/IM - View.

O:

Check the JP1/IM - View version.

KAVB7177-E
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The database could not be operated during backup, reason-code)

An operation request from JP1/IM - View failed because a database operation failed during backup.

S:

Cancels the requested operation.

O:

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

KAVB7178-E
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: Memory was insufficient during backup.)

An operation request from JP1/IM - View failed because memory became insufficient during backup.

S:

Cancels the requested operation.

O:

Stop the service, and check the free space in system memory. Either increase available memory by stopping any unnecessary processes or add memory based on a re-estimate of the required memory.

The database may have been corrupted. After restoring the database, restart the service.

KAVB7179-E
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The database file was not found during backup.)

An operation request from JP1/IM - View failed because a database file was not found during backup.

S:

Cancels the requested operation.

O:

Determine whether the database file and directory exist. Stop the service, create a new database, and then restart the service.

KAVB7180-E
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The disk space was insufficient during backup.)

An operation request from JP1/IM - View failed because disk space became insufficient during backup.

S:

Cancels the requested operation.

O:

Check the free space in the disk where the database is stored, and delete any unnecessary files.

The database may have been corrupted. Stop the service, restore the database, and then restart the service.

KAVB7182-E
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The database could not be accessed during backup.)

An operation request from JP1/IM - View failed because an access of the database failed during backup.

S:

Cancels the requested operation.

O:

Check access permissions for database files and directories.

KAVB7183-E
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: Resources were insufficient during backup.)

An operation request from JP1/IM - View failed because resources such as file descriptors were insufficient.

S:

Cancels the requested operation.

O:

Make sure that file descriptors are sufficient, and stop unnecessary processes.

The database may have been corrupted. Stop the service, restore the database, and then restart the service.

KAVB7184-E
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: Memory was insufficient.) Recovery also failed. (reason-code-for-recovery-failure)

An operation request from JP1/IM - View failed because of insufficient memory. Recovery processing also failed.

S:

Cancels the requested operation.

O:

Stop the service, and check the free space in system memory. Either increase available memory by stopping any unnecessary processes or add memory based on a re-estimate of the required memory.

The database may have been corrupted. After restoring the database, restart the service.

KAVB7185-E
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The disk space was insufficient to update the database.) Recovery also failed. (reason-code-for-recovery-failure)

An operation request from JP1/IM - View failed because of insufficient disk space. Recovery processing also failed.

S:

Cancels the requested operation.

O:

Check the free space in the disk where the database is stored, and delete any unnecessary files.

The database may have been corrupted. Stop the service, restore the database, and then restart the service.

KAVB7187-E
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The database could not be accessed.) Recovery also failed. (reason-code-for-recovery-failure)

An operation request from JP1/IM - View failed because an access of the database failed during backup. Recovery processing also failed.

S:

Cancels the requested operation.

O:

Check access permissions for database files and directories.

KAVB7188-E
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The database file was not found.) Recovery also failed. (reason-code-for-recovery-failure)

An operation request from JP1/IM - View failed because a database file was not found. Recovery processing also failed.

S:

Cancels the requested operation.

O:

Determine whether the database file and directory exist. Stop the service, create a new database, and then restart the service.

KAVB7189-E
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The database could not be operated. error-code-for-recovery-failure) Recovery also failed. (reason-code-for-recovery-failure)

An operation request from JP1/IM - View failed because an attempted operation using the database failed. Recovery processing also failed.

S:

Cancels the requested operation.

O:

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

KAVB7190-W
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: the memory is insufficient.), The database recovery operation succeeded.

An operation request from JP1/IM - View failed because of insufficient memory, but recovery processing was successful.

S:

Continues processing.

O:

The latest changes may not have been saved. Make sure that the monitoring tree configuration is correct.

KAVB7191-W
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The disk space was insufficient to update the database.), The database recovery operation succeeded.

An operation request from JP1/IM - View failed because of insufficient disk space, but recovery processing was successful.

S:

Continues processing.

O:

The latest changes may not have been saved. Make sure that the monitoring tree configuration is correct.

KAVB7192-W
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The database cannot be accessed.), The database recovery operation succeeded.

An operation request from JP1/IM - View failed because an access of the database failed, but recovery processing was successful.

S:

Continues processing.

O:

The latest changes may not have been saved. Make sure that the monitoring tree configuration is correct.

KAVB7193-W
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The database file was not found.), The database recovery operation succeeded.

An operation request from JP1/IM - View failed because a database file was not found, but recovery processing was successful.

S:

Continues processing.

O:

The latest changes may not have been saved. Make sure that the monitoring tree configuration is correct.

KAVB7194-W
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The database cannot be operated, reason-code), The database recovery operation succeeded.

An operation request from JP1/IM - View failed because an operation using the database failed, but recovery processing was successful.

S:

Continues processing.

O:

The latest changes may not have been saved. Make sure that the monitoring tree configuration is correct.

KAVB7196-W
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The requested operation is not authorized for the node ID (node-ID) )

The node ID (node-ID) is a virtual root node. Virtual root nodes cannot handle operation requests (request-name) from JP1/IM - View.

S:

Continues processing.

O:

Virtual root nodes cannot handle operation requests (request-name). Specify a child node of the virtual root node, and then perform the operation again.

KAVB7197-W
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The JP1/IM -View version (version-for-View) is not compatible with the JP1/IM-CS monitored object DB version (monitored-object-DB-version) )

JP1/IM - Central Scope could not execute the operation request from JP1/IM - View because the JP1/IM - View version is not compatible with the JP1/IM - Central Scope monitored object DB version.

S:

Continues processing.

O:

Recheck the JP1/IM - View version and JP1/IM - Central Scope monitored object DB version, and then perform the operation from a JP1/IM - View that is compatible with the monitored object DB version of the JP1/IM - Central Scope. See 9.2.2 Connectivity between JP1/IM products in the manual Job Management Partner 1/Integrated Management - Manager Overview and System Design Guide for combinations of JP1/IM - View and JP1/IM - Central Scope that can work together.

KAVB7198-W
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The status of the node ID (monitoring-node-ID) could not be changed to the monitored status because its group is in the unmonitored status)

The JP1/IM - View operation request failed because the monitoring group above the monitoring node on which the operation was attempted is in non-monitoring status. When the higher monitoring group is in non-monitoring status, the monitoring node cannot change from monitoring status to non-monitoring status. Operation permission for the higher monitoring group is necessary to change a monitoring node from monitoring status to non-monitoring status.

S:

Continues processing.

O:

Perform the operation as a JP1 user that has operation permission for the monitoring group above the monitoring node whose operation was attempted.

KAVB7201-E
A system error occurred while an operation request (login process) from JP1/IM-View was executing. (Detailed information: An error occurred during the login processing)

An error occurred during login processing.

S:

Waits for re-entry of information.

O:

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

KAVB7202-E
An attempt to authenticate the user has failed.

An attempt to authenticate the user failed.

S:

Waits for re-entry of information.

O:

Check the user name and password, and then retry the operation.

KAVB7204-E
JP1/IM-CS cannot connect to the authentication server.

Cannot connect to the authentication server.

S:

Waits for re-entry of information.

O:

Check the connection path to the authentication server (authentication server address, network, etc.). If the system does not recover normally, use the data collection tool to collect data, and then contact a system administrator.

KAVB7206-E
A system error occurred the operation request (logout processing) of JP1/IM-View was executing. (Detailed information: An error occurred during the logout processing)

An error occurred during logout processing.

S:

Waits for re-entry of information.

O:

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

KAVB7207-E
A system error occurred while the operation request (logout processing) of JP1/IM-View was executing. (Detailed information: A communication error occurred between the connecting host and the authentication server)

A communication error occurred between the connecting host and the authentication server.

S:

Waits for re-entry of information.

O:

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

KAVB7209-E
A system error occurred while the operation request (user list acquiring processing) of JP1/IM-View was executing. (Detailed information: An error occurred in user list acquiring processing)

An error occurred in user list acquisition processing.

S:

Waits for re-entry of information.

O:

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

KAVB7210-E
A system error occurred while the operation request (user list acquiring processing) of JP1/IM-View was executing. (Detailed information: An attempt to acquire the user list has failed)

A user list could not be acquired.

S:

Waits for re-entry of information.

O:

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

KAVB7212-E
A system error occurred while the operation request (user environment acquiring processing) of JP1/IM-View was executing. (Detailed information: An error occurred in user environment acquiring processing)

An error occurred in user environment settings acquisition processing.

S:

Waits for re-entry of information.

O:

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

KAVB7213-E
A system error occurred while the operation request (user environment acquiring processing) of JP1/IM-View was executing. (Detailed information: The user environment file does not exist)

A user environment settings file does not exist.

S:

Waits for re-entry of information.

O:

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

KAVB7232-E
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View.

An operation request from JP1/IM - View could not be executed due to an error.

S:

Cancels the requested operation and continues to accept requests.

O:

Check the log for the message that was output preceding this message, and take the corrective action given for that message.

KAVB7233-E
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (cause: the data format was invalid)

The format of the operation request data from JP1/IM - View is invalid.

S:

Cancels the requested operation and continues to accept requests.

O:

Determine whether there was an invalid access of the server system where JP1/IM - Manager is running. Also check the JP1/IM - View log to make sure that no problems have occurred. If the server system and log show no problems, a system error may have occurred. Use the data collection tool to collect data, and then contact a system administrator.

KAVB7234-E
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The tree ID (tree-ID) was not registered)

The operation request data from JP1/IM - View contained a tree ID that the service does not support.

S:

Cancels the requested operation and continues to accept requests.

O:

Make sure that the tree ID of the CSV file read by JP1/IM - View is correct.

KAVB7235-E
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The visual monitoring screen ID (Visual-Monitoring-window-ID) is not registered)

The operation request data from JP1/IM - View contained a Visual Monitoring window ID that the service does not support.

S:

Cancels the requested operation and continues to accept requests.

O:

Make sure that the Visual Monitoring window ID is within the supported range (1 to 64).

KAVB7236-E
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The common event monitoring condition ID (common-event-monitoring-condition-ID) is not registered)

The operation request data from JP1/IM - View contained a common event monitoring condition ID that the service does not support.

S:

Cancels the requested operation and continues to accept requests.

O:

Make sure that the common event monitoring condition ID is within the supported range (1 to 255).

KAVB7237-E
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The memory is insufficient)

The operation request from JP1/IM - View failed because a memory shortage occurred.

S:

Cancels the requested operation and continues to accept requests.

O:

Check the free space in system memory. Either increase available memory by stopping any unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

KAVB7238-E
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The resource was insufficient)

An operation request from JP1/IM - View failed because there were insufficient resources such as file descriptors.

S:

Cancels the requested operation and continues to accept requests.

O:

Make sure that system resources such as file descriptors are sufficient, and stop any unnecessary processes.

KAVB7239-E
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The disk space was insufficient to update the database)

An operation request from JP1/IM - View failed because there was not enough space on the disk where the database is stored.

S:

Cancels the requested operation and continues to accept requests.

O:

Check the free space on the disk where the database is stored, and delete any unnecessary files.

KAVB7240-W
JP1/IM-CS temporarily failed in executing the operation request (request-name) from JP1/IM-View. (Cause: The database is used)

An operation request from JP1/IM - View temporarily failed because the database was being used by another process.

S:

Cancels the requested operation.

O:

Wait awhile, and then retry the operation.

KAVB7241-E
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The database cannot be accessed)

An operation request from JP1/IM - View failed because a database access failed.

S:

Cancels the requested operation.

O:

Check access permissions for database files and directories.

KAVB7242-E
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The database file was not found)

An operation request from JP1/IM - View failed because a database file was not found.

S:

Cancels the requested operation.

O:

Determine whether the database file and directory exist. Stop the service, create a new database, and then restart the service.

KAVB7243-E
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The tree ID (tree-ID) is not registered)

The operation request data from JP1/IM - View contained a tree ID that is not defined in the database.

S:

Cancels the requested operation and continues to accept requests.

O:

Make sure that the tree ID of the CSV file read by JP1/IM - View is correct.

KAVB7244-E
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The node ID (node-ID) is not registered)

The operation request data from JP1/IM - View contained a node ID that is not defined in the database.

S:

Cancels the requested operation and continues to accept requests.

O:

Display the properties of the monitoring tree in JP1/IM - View, and confirm that the node ID exists.

KAVB7245-E
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The visual monitoring screen ID (Visual-Monitoring-window-ID) is not registered)

The operation request data from JP1/IM - View contained a Visual Monitoring window ID that is not defined in the database.

S:

Cancels the requested operation and continues to accept requests.

O:

In JP1/IM - View, close the Edit Visual Monitoring Window List window or the Open Visual Monitoring Window window, and then retry the operation.

KAVB7246-E
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The common event monitoring ID (common-event-monitoring-condition-ID) is not registered)

The operation request data from JP1/IM - View contained a common event monitoring condition ID that is not defined in the database.

S:

Cancels the requested operation and continues to accept requests.

O:

Close the Common Condition Settings window in JP1/IM - View, and then open it again.

KAVB7247-E
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The record in the database is invalid)

An operation request from JP1/IM - View failed because the record was not found in the database.

S:

Cancels the requested operation and continues to accept requests.

O:

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

KAVB7248-E
JP1/IM-CS could not execute the operation request (request-name) from JP1/IM-View. (Cause: The database cannot be operated, reason-code)

An operation request from JP1/IM - View failed because an operation using the database failed.

S:

Cancels the requested operation and continues to accept requests.

O:

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

KAVB7249-E
JP1/IM-CS could not create the result response data for the operation request (request-name) from JP1/IM-View. (Cause: Memory was insufficient)

The operation request from JP1/IM - View was executed correctly, but JP1/IM-Central Scope could not create the response data because a memory shortage occurred.

S:

Closes the connection to JP1/IM - View and continues to accept service requests.

O:

Check the free space in system memory. Either increase available memory by stopping any unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

KAVB7250-E
JP1/IM-CS could not create the result response data for the operation request (request-name) from JP1/IM-View. (Cause: reason-code)

The operation request from JP1/IM - View was executed correctly, but JP1/IM - Central Scope could not create the response data.

S:

Closes the connection to JP1/IM - View and continues to accept service requests.

O:

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

KAVB7252-W
A part of the tree cannot be created, because the definition information of a linked product could not be acquired. (host=host-name, product=product-name)

Part of the monitoring tree could not be created because definition information of a linked product could not be acquired by automatic generation of the monitoring tree.

S:

Cancels the requested operation and continues to accept requests.

O:

Check the following items. If the issue is not resolved, use the data collection tool to collect data, and then contact a system administrator.

Has the linked product's service been stopped?

Is the linked product running?

KAVB7253-W
A part of the tree cannot be created because the definition information of a linked product could not be acquired.

Part of the monitoring tree could not be created because definition information of a linked product could not be acquired by automatic generation of the monitoring tree.

S:

Cancels the requested operation and continues to accept requests.

O:

Check the following items. If the issue is not resolved, use the data collection tool to collect data, and then contact a system administrator.

Has the linked product's service been stopped?

Is the linked product running?

KAVB7254-E
A tree could not be created. (Cause number=reason-number)

A monitoring tree could not be created automatically.

S:

Cancels the requested operation and continues to accept requests.

O:

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

KAVB7255-E
An attempt to execute (request-name) from JP1/IM - View has failed. (Cause number=reason-number)

A request from JP1/IM - View failed.

S:

Cancels the requested operation and continues to accept requests.

O:

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

KAVB7256-E
(request-name) will now stop, because the tree was updated.

The requested operation was not performed because the monitoring tree has already been updated.

S:

Cancels the requested operation and continues to accept requests.

O:

Update the tree to the latest status using JP1/IM - View, and then retry the operation.

KAVB7257-I
(request-name) cannot be executed because no update has been done.

The requested operation was not performed because no update has been performed.

S:

Cancels the requested operation and continues to accept requests.

KAVB7258-E
An attempt to execute (request-name) from JP1/IM - View has failed because the number of visual monitoring windows exceeded the limit.

An attempt to execute the requested operation from JP1/IM - View failed because the number of visual monitoring windows reached its limit.

S:

Cancels the requested operation and continues to accept requests.

O:

Close unnecessary visual monitoring windows, and then retry the operation.

KAVB7259-E
An attempt to execute (request-name) from JP1/IM - View has failed because the number of nodes exceeded the limit.

An attempt to execute the requested operation from JP1/IM - View failed because the number of nodes reached its limit.

S:

Cancels the requested operation and continues to accept requests.

O:

Delete unnecessary nodes, and then retry the operation.

KAVB7260-E
An attempt to execute (request-name) from JP1/IM - View has failed because the number of common event monitoring conditions exceeded the limit.

An attempt to execute the requested operation from JP1/IM - View failed because the number of common event monitoring conditions reached its limit.

S:

Cancels the requested operation and continues to accept requests.

O:

Delete unnecessary common event monitoring conditions, and then retry the operation.

KAVB7261-E
An attempt to execute (request-name) from JP1/IM - View has failed because the system definition file could not be read.

An attempt to execute the requested operation from JP1/IM - View failed because the system definition file could not be read.

S:

Cancels the requested operation and continues to accept requests.

O:

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

KAVB7262-E
An attempt to execute (request-name) from JP1/IM - View has failed because the common event monitoring condition ID (common event monitoring condition ID =common-event-monitoring-condition-ID) is in use.

An attempt to execute the requested operation from JP1/IM - View failed because the common event monitoring condition ID is in use.

S:

Cancels the requested operation and continues to accept requests.

O:

Determine whether the common event monitoring condition you attempted to delete is in use as a user monitoring object in the tree, and then retry the operation.

KAVB7263-E
(request-name) will now stop because the visual monitoring window is updated.

The requested operation from JP1/IM - View was not performed because the Visual Monitoring window has been updated.

S:

Cancels the requested operation and continues to accept requests.

O:

Update the Visual Monitoring window to the latest status using JP1/IM - View, and then retry the operation.

KAVB7264-E
The same event monitoring condition name is already registered.

Duplicate common condition names cannot be registered.

S:

Suspends updating of the common event monitoring condition and continues to accept requests.

O:

Reconfigure the common condition names, and then retry the operation.

KAVB7265-E
Another user is making a tree.

Automatic generation cannot be executed because another user is running automatic generation.

S:

Suspends automatic generation and continues to accept requests.

O:

Wait until the other user has finished running automatic generation, and then retry the operation.

KAVB7266-W
An invalid common event monitoring condition is included in the node. (monitoring-node-ID)

A monitoring node of the tree includes an unregistered common event monitoring condition.

S:

Places the affected monitoring node in non-monitoring status.

O:

Check the status change condition settings of the monitoring node.

KAVB7267-W
JP1/IM - CS could not create the tree completely. (reason)

Part of a tree could not be created.

S:

Cancels the requested operation and continues to accept requests.

O:

Perform the check indicated by the reason, and then take corrective action.

KAVB7268-W
JP1/IM - CS could not completely execute the operation request (request-name) of JP1/IM - View completely.

Part of an operation request from JP1/IM - View could not be executed.

S:

Continues processing.

O:

Check the log for the message that was output preceding this message, and take the corrective action given for that message.

KAVB7269-W
Failed to resolve hostname. Tree generation may have gone wrong in part. (host: host-name).

Generation of part of a tree may have failed because the host name could not be resolved.

S:

Continues processing.

O:

Determine whether the host name is set in the jcs_hosts file or the hosts file.

KAVB7272-E
JP1/IM - CS could not execute the operation request (request-name) from command.

An operation request from a command was not executed because of an error.

S:

Cancels the requested operation.

O:

Check the log for the message that was output preceding this message, and take the corrective action given for that message.

KAVB7273-W
JP1/IM - CS could not completely execute the operation request (request-name) of command.

JP1/IM could not execute part of an operation request from a command.

S:

Continues processing.

O:

Check the log that indicates the cause of the immediately previous error, and then take corrective action.

KAVB7274-W
An attempt to acquire the name of the destination host, for acquiring the definition information of the linked product (product-name), has failed.

An attempt to acquire the name of the host at the destination for acquiring definition information failed.

S:

Uses the definition information acquisition destination host as its host and continues processing.

O:

If linked to another host, set up the information acquisition destination host.

KAVB7276-E
No linked product (product-name) has been installed or set up on the host (host-name).

Definition information could not be acquired because the linked product has not been installed or set up.

S:

Cancels processing.

O:

Install or set up the linked product.

KAVB7277-E
The service for the linked product (product-name) of the host (host-name) is not running.

The linked product could not be acquired because the service for the linked product is not running.

S:

Cancels processing.

O:

Start the linked product service.

KAVB7278-E
User (JP1-user-name) does not have permission to acquire the definition information of the linked product (product-name) of the host (host-name).

The definition information of the linked product could not be acquired because the user does not have permission to acquire the definition information of the linked product.

S:

Cancels processing.

O:

Log in as a user with permission to acquire the definition information of the linked product, and execute automatic generation. Alternatively, assign permission to the user.

KAVB7279-E
An attempt to acquire the definition information of the linked product (product-name) of the host (host-name) has failed. (details: detailed-information)

The definition information of a linked product could not be acquired because the linked product returned an error.

S:

Cancels processing.

O:

The message output by the linked product is displayed in the detailed information. Refer to the linked product documentation and take the corrective action indicated for that message.

KAVB7280-E
The host (host-name), which was specified as the destination host for acquiring the definition information of the linked product (product-name), does not exist.

The specified host name is invalid.

S:

Cancels processing.

O:

Make sure that the host name is correct. If an incorrect host was specified, specify the destination host for acquiring the definition information again.

KAVB7281-E
An attempt to acquire the definition information of the linked product (product-name) of the host (host-name) has failed. (cause number=reason-number)

The definition information of a linked product could not be acquired because JP1/Base returned an error.

S:

Cancels processing.

O:

Check the system status as directed by the reason number. If the system does not recover normally, use the data collection tool to collect data, and then contact a system administrator.

reason-number: 50
Description: The processing limit has been reached.
Action: Wait awhile, and then try the operation again.

reason-number: 101
Description: A parameter is invalid.
Action: System error. Use the data collection tool to collect data, and then contact a system administrator.

reason-number: 103
Description: The JP1/Base environment is invalid.
Action: Make sure that JP1/Base is installed correctly.

reason-number: 105
Description: An error occurred while acquiring linked product information.
Action: Use the data collection tool to collect data, and then contact a system administrator.

reason-number: 107
Description: A common definition value is invalid.
Action: Make sure that JP1/Base was set up correctly.

reason-number: 108
Description: A logical host name is invalid.
Action: Check the logical host name for errors.

reason-number: 114
Description: The network is unreachable, or a connection error occurred during communication.
Action: Check the network configuration and status. Also make sure that JP1/Base is running on the collection-target host.

reason-number: 115
Description: An error occurred during transmission processing.
Action: Check the network configuration and status. Also make sure that JP1/Base is running on the collection-target host.

reason-number: 116
Description: An error occurred during reception processing.
Action: Check the network configuration and status. Also make sure that JP1/Base is running on the collection-target host.

reason-number: 117
Description: A connection was ended.
Action: Check the network configuration and status. Also make sure that JP1/Base is running on the collection-target host.

reason-number: 118
Description: The protocol of the received transmission was incorrect.
Action: Temporarily invalid data may have been received. Retry the operation.

reason-number: 119
Description: Initialization was not performed.
Action: System error. Use the data collection tool to collect data, and then contact a system administrator.

reason-number: 199
Description: An error occurred.
Action: System error. Use the data collection tool to collect data, and then contact a system administrator.

Any other reason number
Action: System error. Use the data collection tool to collect data, and then contact a system administrator.

KAVB7282-E
A timeout occurred while acquiring the definition information of the linked product (product-name) of the host (host-name).

A time-out occurred while acquiring the definition information of a linked product.

S:

Cancels processing.

O:

Wait awhile, and then retry the operation.

KAVB7283-E
In (mid-sized-item-type:mid-sized-item-name), the (small-item-type) has exceeded the restricted value (byte-count byte), (large-item-name) updation is failed.

An attempt to update (large-item-name) failed because the (small-item-type) of (mid-sized-item-type:mid-sized-item-name) exceeded the limit value (byte-count bytes).

The following values are displayed as the message text variables.

mid-sized-item-type
Node ID, common condition name, or Visual Monitoring window

mid-sized-item-name
The actual name corresponding to the mid-sized-item-type item

small-item-type
Monitoring node name, attribute value of basic information, attribute value of common condition, condition name of status change condition, individual attribute value of individual condition, common condition name, attribute value of common condition, window title of the Visual Monitoring window, or comment of the Visual Monitoring window

byte-count
The maximum length (in bytes) of the small-item-type item

large-item-name
Monitoring tree, monitoring node, Visual Monitoring window, or common condition

S:

Suspends processing.

O:

Check the character string specified in small-item-type of mid-sized-item-name of mid-sized-item-type, shorten it so that it is within the limits for UTF-8 encoding, and then update large-item-name again.

KAVB7302-E
JP1/IM-CS could not execute the request from JP1/IM-View for acquiring the system environment. (Cause: An attempt to read the system environment setting file has failed)

Data cannot be acquired from the system environment settings file.

S:

Cancels the requested operation.

O:

The system environment settings file does not exist, or the user does not have access permission. Check the details of the message that was output preceding this message.

KAVB7303-E
JP1/IM-CS could not execute the request from JP1/IM-View for acquiring the system environment (Cause: The data format of the system environment setting file was invalid)

The description of the system environment settings information is incorrect.

S:

Cancels the requested operation.

O:

Check the system environment settings file for errors.

KAVB7304-E
JP1/IM-CS could not execute the request from JP1/IM-View for acquiring the system environment settings. (Cause: Memory was insufficient)

An attempt to acquire system environment settings information failed because a memory shortage occurred.

S:

Cancels the requested operation.

O:

Check the amount of free space in system memory. Either increase available memory by stopping unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

KAVB7305-E
JP1/IM-CS could not execute the request from JP1/IM-View for acquiring the system environment settings.

An attempt to acquire system environment settings information failed due to an internal error.

S:

Cancels the requested operation.

O:

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

KAVB7306-E
JP1/IM-CS could not create the result response data for the request from JP1/IM-View for acquiring the system environment settings. (Cause: Memory was insufficient)

Result response data for a request to acquire system environment settings information cannot be created due to insufficient memory.

S:

Cancels processing.

O:

Check the amount of free space in system memory. Either increase available memory by stopping unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

KAVB7307-E
JP1/IM-CS could not create the result response data for the request from JP1/IM-View for acquiring the system environment settings.

An attempt to create result response data for a request to acquire system environment settings information failed.

S:

Cancels processing.

O:

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

KAVB7350-I
The guide information cannot be acquired because the definition of the guide information does not exist.

Guide information cannot be acquired because the guide information definition does not exist.

S:

Cancels the requested operation.

O:

Determine whether the guide information file exists in the prescribed folder. If it exists, check the startup log of Central Scope Service to see if there are errors in the guide information file.

KAVB7351-I
The guide information cannot be acquired because the event history does not exist.

Guide information cannot be acquired because the specified monitoring node status has not changed.

S:

Cancels the requested operation.

O:

Execute the guide function targeting a monitoring node whose status has changed.

KAVB7352-I
The guide information cannot be acquired because the event does not exist.

Guide information cannot be acquired because no event whose monitoring node status has changed exists yet in the event database.

S:

Cancels the requested operation.

O:

Either delete the event database contents after the monitoring node status changes, or make sure that the event database has sufficient capacity.

KAVB7353-E
The guide information cannot be acquired because an attempt to acquire the event history has failed.

Guide information cannot be acquired because an attempt to acquire the event history failed.

S:

Cancels the requested operation.

O:

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

KAVB7354-E
The guide information cannot be acquired because an attempt to acquire the event has failed.

Guide information cannot be acquired because an attempt to acquire an event failed.

S:

Cancels the requested operation.

O:

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

KAVB7355-I
The corresponding guide information does not exist.

No guide information that matches the conditions was found.

S:

Cancels the requested operation.

O:

To output guide information, add a description to the guide information file.

KAVB7356-E
Guide information cannot be acquired because an attempt to acquire the guide message has failed.

Guide information cannot be acquired because an attempt to acquire a guide message failed.

S:

Cancels the requested operation.

O:

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

KAVB7357-E
Guide information cannot be acquired because a message development processing has failed.

Guide information cannot be acquired because an attempt to expand text beginning with $ in a guide message failed.

S:

Cancels the requested operation.

O:

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

KAVB7358-W
The guide message file name is not specified.

The guide message file name is not specified in EV_FILE.

S:

Ignores the specified guide message and continues processing.

O:

Carefully review the configuration of the guide message file.

KAVB7359-E
Guide information could not be acquired because acquisition of the guide title message has failed.

Guide information cannot be acquired because an attempt to acquire the guide title message failed.

S:

Cancels the requested operation.

O:

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

KAVB7360-W
The guide message file (file-name) does not exist.

The guide message file specified in EV_FILE or the default guide message file does not exist.

S:

Ignores the specified guide message and continues processing.

O:

Carefully review the contents of EV_FILE and the configuration of the guide message file.

KAVB7361-E
An error occurred during reading of the guide message file.

An error occurred while reading the guide message file.

S:

Cancels guide display processing.

O:

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

KAVB7362-W
The file name length of the guide message file (file-name) exceeds the limit of 1024 bytes.

The length of the guide message file name specified in the EV_FILE tag of the guide information file exceeds 1,024 bytes.

S:

Ignores the guide information definition that generated the error and continues processing.

O:

Carefully review the contents of the guide information file.

KAVB7363-E
The file size of the guide message file (file-name) exceeds the limit of size bytes.

The guide message file exceeds the maximum readable file size.

S:

Cancels guide display processing.

O:

Carefully review the amount of description in the guide message file.

KAVB7364-E
The user does not have permission to read the file file-name.

You do not have permission to read the guide message file.

S:

Cancels guide display processing.

O:

Carefully review read permissions in the guide message file for system accounts (in Windows) or superusers (in UNIX).

KAVB7365-E
Memory became insufficient during processing of the guide message file.

Processing cannot continue due to insufficient memory.

S:

Cancels guide display processing.

O:

Check the amount of free space in system memory. Use the following methods to ensure sufficient memory for execution, and then restart JP1/IM - Manager.

Increase available memory by stopping unnecessary processes.

Add memory based on a re-estimate of the required memory.

KAVB7366-E
The guide message file (file-name) is not a file.

A character string that is not a file (such as a directory) was specified in the guide message file specified by the EV_FILE tag of the guide information file.

S:

Cancels guide display processing.

O:

In the guide message file, specify a text file written in the language code of the Central Scope Service LANG environment.

KAVB7367-E
The version of the guide information definition file is invalid (DESC_VERSION = version).

The version of the specified guide information file is invalid. For DESC_VERSION, specify 1 or 2.

S:

Disables guide functionality.

O:

Specify 1 or 2 for DESC_VERSION in the guide information file.

KAVB7368-E
An invalid guide message file is specified.

An invalid guide message file was specified.

S:

Cancels guide display processing.

O:

In the guide message file, specify a text file written in the language code of the Central Scope Service LANG environment.

KAVB7377-W
The guide information definition could not be acquired because the guide information definition file does not exist.

The guide information file does not exist.

S:

Disables guide functionality and continues processing.

O:

To enable guide functionality, create a guide information file.

KAVB7378-W
The guide information definition could not be acquired because the user does not have access permission for the guide information definition file.

You do not have permission to access the guide information file.

S:

Disables guide functionality and continues processing.

O:

Check access permissions for the guide information definition file.

KAVB7379-W
The guide information definition could not be acquired because an attempt to read the guide information definition file has failed.

An attempt to read the guide information file failed.

S:

Disables guide functionality and continues processing.

O:

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

KAVB7380-W
The guide information definition could not be acquired because the guide information definition was not defined in the guide information definition file.

There are no guide information definitions in the guide information file.

S:

Disables guide functionality and continues processing.

O:

Carefully review the contents of the guide information definition file.

KAVB7381-W
The specified guide information definition was not validated because the number (number-of-conditional-expression-definitions) of conditional expression definitions specified by the guide information definition (guide-information-definition) is invalid.

An invalid value was specified in a conditional expression definition specified in the guide information definitions.

S:

Ignores the guide information definition that generated the error and continues processing.

O:

Carefully review the contents of the guide information definition file.

KAVB7382-W
The specified conditional expression (conditional-expression) was not validated because the attribute name (attribute-name) of the conditional expression definition (number-of-conditional-expression-definitions) specified by the guide information definition (guide-information-definition) is an invalid enhancement regular expression (detailed information: detailed-information).

Conditional expression

S:

Ignores the guide information definition that generated the error and continues processing.

O:

Refer to the following detailed information, and then carefully review the contents of the guide information definition file.

Detailed information
Invalid pattern.
A regular expression is invalid.
Corrective action
Make sure that the described regular expressions are correct.

Detailed information
Invalid contents within the {} pair.
The specified value for the number of iterations is invalid.
Corrective action
Make sure that the number of iterations specified within the curly brackets is correct.

Detailed information
Last character cannot be \.
The last character is an escape character (\).
Corrective action
Make sure that the expression does not end with \.

Detailed information
Invalid range within [] expression.
The end specified for a range is invalid.
Corrective action
Make sure that the range specified between square brackets is correct.

Detailed information
Invalid subexpression backreference number.
A specification indicating a number contains an invalid character.
Corrective action
Make sure that number statements are appropriate.

Detailed information
?, *, +, or {} is not preceded by a valid regular expression.
?, *, +, {, or } is not preceded by a valid regular expression.
Corrective action
Make sure that ?, *, +, {, and } are preceded by valid regular expressions.

Detailed information
() imbalance.
The numbers of open and close parentheses do not match.
Corrective action
Make sure that the numbers of open and close parentheses match.

Detailed information
{} imbalance.
The numbers of open and close curly brackets do not match.
Corrective action
Make sure that the number of open and close curly brackets match.

Detailed information
[] imbalance.
The numbers of open and close square brackets do not match.
Corrective action
Make sure that the numbers of open and close square brackets match.

Detailed information
Invalid character class type referenced.
An invalid character class was specified.
Corrective action
Make sure that character class specifications are appropriate.

Detailed information
Invalid collating element referenced.
An invalid collating element class was specified.
Corrective action
Determine whether an invalid collating element was specified.

Detailed information
The REG_EXTENDED flag is not specified.
The REG_EXTENDED flag for specifying extended regular expressions was not specified.
Corrective action
System error. Use the data collection tool to collect data, and then contact a system administrator.

Detailed information
Out of memory.
Memory has become insufficient.
Corrective action
Check the amount of free space in system memory. Either increase available memory by stopping unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

Detailed information
Internal error.
An internal error occurred.
Corrective action
System error. Use the data collection tool to collect data, and then contact a system administrator.

KAVB7383-W
The content of the guide information definition (guide-information-definition) was not validated because the guide information message is not defined.

No guide information message is defined in the guide information definitions.

S:

Ignores the guide information definition that generated the error and continues processing.

O:

Carefully review the contents of the guide information definition file.

KAVB7384-W
The content of the guide information definition (guide-information-definition) was not validated because the guide information message title is not defined.

No guide information message title is defined in the guide information definitions.

S:

Ignores the guide information definition that generated the error and continues processing.

O:

Carefully review the contents of the guide information definition file.

KAVB7385-W
The content of the guide information definition (guide-information-definition) was not validated because the number of conditional expression definitions is not defined.

The number of conditional expression definitions is not defined in the guide information definitions.

S:

Ignores the guide information definition that generated the error and continues processing.

O:

Carefully review the contents of the guide information definition file.

KAVB7386-W
The conditional expression definition was not validated because the conditional expression definition (conditional-expression-definition) of the guide information definition (guide-information-definition) is not defined.

No conditional expression definitions are defined in the guide information definitions.

S:

Ignores the guide information definition that generated the error and continues processing.

O:

Carefully review the contents of the guide information definition file.

KAVB7387-W
The conditional expression definition was not validated because the conditional contents (definition-content) of the expression definition (conditional-expression-definition) of the guide information definition (guide-information-definition) are invalid.

The definition contents of a conditional expression definition in the guide information definitions is invalid.

S:

Ignores the guide information definition that generated the error and continues processing.

O:

Carefully review the contents of the guide information definition file.

KAVB7388-W
The guide information definition could not be acquired because the format of the guide information definition file is invalid.

The format of the guide information definition file is invalid.

S:

Disables guide functionality and continues processing.

O:

Carefully review the contents of the guide information definition file.

KAVB7389-W
The guide information definition could not be acquired because an attempt to acquire the path of the guide information definition file has failed.

An attempt to acquire the path of the guide information file failed.

S:

Disables guide functionality and continues processing.

O:

Make sure that setup is correct.

KAVB7390-W
The tag name is invalid, so the content of the guide information definition (guide-information-definition) does not become effective.

An invalid tag was specified in the guide information file.

S:

Ignores the tag that generated the error and continues processing.

O:

Carefully review the contents of the guide information definition file.

KAVB7391-W
The content of the guide information definition (guide-information-definition) was not validated because the escape string (escape-character-string) of the guide information message is invalid.

An invalid escape character was specified in the guide information file.

S:

Ignores the guide information definition that generated the error and continues processing.

O:

Carefully review the contents of the guide information definition file.

KAVB7392-W
The content of the guide information definition (guide-information-definition) was not validated because the last character of the guide information message is an escape character.

An escape character was specified at the end of a guide information message.

S:

Ignores the guide information definition that generated the error and continues processing.

O:

Carefully review the contents of the guide information definition file.

KAVB7393-I
The guide information definition was initialized successfully.

Guide information definitions were initialized successfully.

S:

Continues processing.

KAVB7394-I
The guide information definition was reloaded successfully.

Guide information definitions were reloaded successfully.

S:

Continues processing.

KAVB7395-W
The length of the guide information message exceeds the limit of (guide-information-message-maximum-size) bytes.

The length of the guide information message exceeds the limit.

S:

Displays the message without the part that exceeds the limit.

O:

Carefully review the contents of the guide information definition file.

KAVB7396-W
An attempt to initialize the guide information definition has failed.

An attempt to initialize guide information definitions failed.

S:

Disables guide functionality and continues processing.

O:

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

KAVB7397-W
The old guide information definition will be used because an attempt to reload the guide information definition has failed.

An attempt to reload guide information definitions failed.

S:

Uses guide information definitions registered prior to reloading and continues processing.

O:

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

KAVB7398-W
The guide information definition cannot be used because an attempt to reload the guide information definition has failed.

An attempt to reload guide information definitions failed.

S:

Disables guide functionality and continues processing.

O:

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

KAVB7399-E
Guide information cannot be acquired because an attempt to acquire the maximum value of the guide message has failed.

An attempt to acquire the maximum length of the guide message failed.

S:

Cancels the requested operation.

O:

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

KAVB7400-E
A system error occurred. (function: function-name, errorcode: reason-code, reason: reason)

An error occurred during automatic generation processing.

S:

Cancels automatic generation processing.

O:

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

KAVB7401-E
A system error occurred. (function: function-name, errorcode: reason-code)

An error occurred during automatic generation processing.

S:

Cancels automatic generation processing.

O:

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

KAVB7402-W
A system error occurred. (function: function-name, errorcode: reason-code, reason: reason)

An error occurred during automatic generation processing.

S:

Continues automatic generation processing.

O:

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

KAVB7403-W
A system error occurred. (function: function-name, errorcode: reason-code)

An error occurred during automatic generation processing.

S:

Cancels automatic generation processing.

O:

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

KAVB7404-E
Memory became insufficient.

There is not enough memory for command execution.

S:

Cancels automatic generation processing.

O:

Check the amount of free space in system memory. Increase available memory by stopping unnecessary processes, and then re-execute the command.

KAVB7405-E
An argument is invalid.

An API argument contains an error.

S:

Cancels automatic generation processing.

O:

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

KAVB7406-E
An attempt to create the tree failed because a definition file (file-name) is invalid.

An invalid format was found in the contents of a definition file used by automatic generation.

S:

Cancels automatic generation processing.

O:

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

KAVB7407-E
Information from a linked product is invalid. (Host: host-name, identifier=ID)

An invalid format was found in information acquired by a JP1/Base plug-in service.

S:

Ignores the invalid information and continues automatic generation processing.

O:

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

KAVB7408-E
An attempt to collect information from a linked product failed. (function: function-name, errorcode: reason-code, reason: reason)

An attempt to acquire information from a JP1/Base plug-in service failed.

S:

Continues automatic generation processing for linked products other than the one for which acquisition failed.

O:

Make sure that the adapter command of the linked product is configured correctly.

KAVB7409-E
Failed to collect the information from cooperation products. (function: function-name, errorcode: reason-code)

An attempt to acquire information from a JP1/Base plug-in service failed.

S:

Continues automatic generation processing for linked products other than the one for which acquisition failed.

O:

Make sure that the adapter command of the linked product is configured correctly.

KAVB7410-W
An attempt to collect information from a linked product failed. (function: function-name, errorcode: reason-code, reason: reason)

An attempt to acquire information from a JP1/Base plug-in service failed.

S:

Continues automatic generation processing for linked products other than the one for which acquisition failed.

O:

Make sure that the adapter command of the linked product is configured correctly.

KAVB7411-W
An attempt to collect information from a linked product failed. (function: function-name, errorcode: reason-code)

An attempt to acquire information from a JP1/Base plug-in service failed.

S:

Continues automatic generation processing for linked products other than the one for which acquisition failed.

O:

Make sure that the adapter command of the linked product is configured correctly.

KAVB7412-E
An attempt to collect the configuration definition of JP1/IM failed. (function: function-name, errorcode: reason-code, reason: reason)

An attempt to acquire JP1/IM configuration definition information failed.

S:

Cancels automatic generation processing.

O:

Make sure that the JP1/IM system configuration (configuration definition) is configured correctly.

KAVB7413-E
An attempt to collect the configuration definition of JP1/IM failed. (function: function-name, errorcode: reason-code)

An attempt to acquire JP1/IM configuration definition information failed.

S:

Cancels automatic generation processing.

O:

Make sure that the JP1/IM system configuration (configuration definition) is configured correctly.

KAVB7414-W
An attempt to collect the configuration definition of JP1/IM failed. (function: function-name, errorcode: reason-code, reason: reason)

An attempt to acquire JP1/IM configuration definition information failed.

S:

Continues automatic generation processing only for the local host.

O:

Make sure that the JP1/IM system configuration (configuration definition) is configured correctly.

KAVB7416-E
An attempt to read the system definition file failed. (function: function-name, errorcode: reason-code, reason: reason)

An attempt to read a definition file required for automatic generation failed.

S:

Cancels automatic generation processing.

O:

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

KAVB7417-E
An attempt to read the system definition file failed. (function: function-name, errorcode: reason-code)

An attempt to read a definition file required for automatic generation failed.

S:

Cancels automatic generation processing.

O:

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

KAVB7418-W
An attempt to read the system definition file failed. (function: function-name, errorcode: reason-code, reason: reason)

An attempt to read a definition file required for automatic generation failed.

S:

Cancels automatic generation processing.

O:

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

KAVB7419-W
An attempt to read the system definition file failed. (function: function-name, errorcode: reason-code)

An attempt to read a definition file required for automatic generation failed.

S:

Cancels automatic generation processing.

O:

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

KAVB7420-W
An attempt to resolve the host name (host-name) failed.

An attempt to resolve the host name acquired from a linked product failed.

S:

Continues automatic generation processing for hosts other than the one whose host name was not resolved.

O:

Make sure that the host name is specified in the jcs_hosts file or hosts file.

KAVB7450-E
An attempt to convert the character code has failed because the memory was insufficient.

Processing cannot continue because there is not enough memory.

S:

Cancels character code conversion processing.

O:

Check the amount of free space in system memory. Either increase available memory by stopping unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

KAVB7451-E
A system error occurred. (Detailed information: An attempt to convert the character code has failed)

An attempt to convert character code failed.

S:

Cancels character code conversion processing.

O:

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

KAVB7452-E
A system error occurred. (Detailed information: The character code was invalid)

A character code conversion was attempted between unsupported character codes.

S:

Cancels character code conversion processing.

O:

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

KAVB7453-E
A system error occurred. (Detailed information: The buffer area for storing the converted character string was insufficient)

Insufficient buffer area was secured to store the converted character string.

S:

Cancels character code conversion processing.

O:

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

KAVB7455-E
The file operation processing has failed because the memory was insufficient.

Processing cannot continue because there is not enough memory.

S:

Cancels file operation processing.

O:

Check the amount of free space in system memory. Either increase available memory by stopping unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

KAVB7457-E
The default value (default-monitored-object-DB-version) will be used because the value specified for the monitored object DB version (monitored-object-DB-version) is invalid.

The monitored object database version is invalid. Assumes the default monitored object database version.

S:

Assumes the default monitored object database version and continues processing.

O:

The version may have been downgraded by an installation. Stop the service, and then set up the monitored object database again.

KAVB7458-E
The user does not have access permission for the definition file (file-name).

You do not have access permission for the specified file.

S:

Cancels file operation processing.

O:

Check access permissions for the specified file.

KAVB7459-E
The monitored object DB has not been set up.

An attempt to start Central Scope Service failed because the monitored object database was not set up.

S:

Stops Central Scope Service.

O:

Execute the jcsdbsetup command, and then set up the monitored object database.

KAVB7460-E
The definition file (file-name) cannot be opened.

The specified file cannot be opened.

S:

Cancels processing.

O:

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

KAVB7462-E
A system error occurred. (Detailed information: An attempt to initialize the lock has failed)

An attempt to initialize a lock failed.

S:

Cancels file operation processing.

O:

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

KAVB7463-W
English (Lang=C) is assumed as the language type because the language type could not be identified.

The setting for language type (LANG) cannot be acquired.

S:

Assumes English (LANG=C) as the language type and continues processing.

O:

Carefully review the language type (LANG) setting defined in JP1/Base.

KAVB7465-E
An attempt to acquire the size of the definition file (file-name) has failed.

An attempt to acquire the size of the specified file failed.

S:

Cancels processing to acquire the file size.

O:

Check the file status. Also refer to the message that was output for the preceding file operation.

KAVB7470-E
The contents of the definition information assigned to the file(file-name) is invalid (character string information: first-64-bytes-of-printable-characters)

An attempt to set definition information failed because the syntax of the specified character string data is incorrect. first-64-bytes-of-printable-characters is embedded text.

S:

Cancels processing to specify definition information.

O:

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

KAVB7471-E
An attempt to write the specified character string to the file (file-name) has failed (character string information: first-64-bytes-of-printable-characters)

An error occurred in processing to write the specified character string data in a file (only the first 64 bytes of printable characters is output). first-64-bytes-of-printable-characters is embedded text.

S:

Cancels processing to specify definition information.

O:

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

KAVB7473-E
An attempt to acquire the attribute value that corresponds to the section (section-name) and the attribute name (attribute-name) of the definition file (file-name) has failed.

An error occurred while searching for an attribute value that corresponds to the specified section and attribute name.

S:

Continues processing.

O:

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

KAVB7475-E
A system error has occurred. (Detailed information: An attempt to acquire the section name list has failed. Definition file: file-name, Section: section-name)

An error occurred in processing to acquire a list of section names under the specified section.

S:

Cancels processing.

O:

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

KAVB7479-E
The file size of the definition file (file-name) exceeds the limit ((size) bytes).

The definition file exceeds the readable file size limit.

S:

Terminates processing.

O:

Shorten the definition file size so that it is no greater than the upper limit.

KAVB7480-E
A format error of the definition file occurred. The invalid code is included in the tag name and the attribute name. (line number: line-number, file name: file-name)

Definition file format error. Use single-byte code rather than double-byte code for tag names and labels.

S:

Terminates command processing.

O:

Use single-byte code rather than double-byte code for tag names and labels.

KAVB7482-E
A syntax error exists in the definition file. The section does not start with the starting tag. (line number: line-number, file name: file-name)

A section in the definition file does not start with a starting tag.

S:

Cancels processing.

O:

Make sure that the starting tag in the definition file is described correctly.

KAVB7483-E
A syntax error exists in the definition file. An invalid character is in the starting tag. (line number: line-number, file name: file-name)

There is no tag name between the square brackets of the starting tag in the definition file, or an invalid character code was used.

S:

Cancels processing.

O:

Make sure that the starting tag in the definition file is described correctly.

KAVB7484-E
A format error exists in the definition file. The nesting of the section in the definition file exceeds the maximum value. (Detailed information: Maximum number of nests: maximum-number-of-nests, line number: line-number, file name: file-name)

The number of nesting levels in the definition file exceeds the maximum.

S:

Cancels processing.

O:

Make sure that the number of nesting levels in the section of the definition file does not exceed the maximum.

KAVB7485-E
A format error exists in the definition file. The characters in one line exceed the maximum value. (Detailed information: Maximum number of characters: maximum-number-of-characters, line number: line-number, file name: file-name)

The maximum number of characters that can be defined per line in the definition file was exceeded.

S:

Cancels processing.

O:

Check the number of characters defined per line in the definition file.

KAVB7487-E
A syntax error exists in definition file. The starting tag or the ending tag does not exist. (Line number: line-number, file name: file-name)

Definition file syntax error. The starting tag or the ending tag does not exist.

S:

Cancels processing.

O:

Make sure that the starting tag and ending tag are described correctly in the definition file.

KAVB7488-E
A syntax error exists in the definition file. An attribute name does not exist in front of equal (=). (Line number: line-number, file name: file-name)

An equal sign in the definition file is not preceded by an attribute name definition.

S:

Cancels processing.

O:

Make sure that attribute information is described correctly in the definition file.

KAVB7491-E
A syntax error exists in the definition file. The format is invalid. (Line number: line-number, file name: file-name)

The definition file format is invalid.

S:

Cancels processing.

O:

Make sure that the definition file is described using the correct format.

KAVB7492-E
A syntax error exists in the definition file. The definition tag does not correspond to the ending tag. (Line number: line-number, file name: file-name)

Definition file format error. The definition tag does not correspond to the ending tag.

S:

Cancels processing.

O:

Make sure that the number of definition tags and ending tags and the nesting are configured correctly in the definition file.

KAVB7493-E
A syntax error exists in the definition file. The definition cannot be updated. (Line number: line-number, file name: file-name)

Definitions could not be updated because the definition file format is incorrect.

S:

Cancels processing.

O:

Make sure that the definition file is described using the correct format.

KAVB7494-E
The definition file processing cannot be executed because the memory is insufficient.

Processing cannot continue because there is not enough memory.

S:

Cancels processing.

O:

Check the amount of free space in system memory. Either increase available memory by stopping unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

KAVB7496-E
A system error occurred. (Detailed information: An attempt to lock was executed even though the initialization of the lock has failed)

An attempt to lock was executed even though the initialization of the lock failed.

S:

Cancels processing.

O:

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

KAVB7497-E
A system error occurred. (Detailed information: An attempt to unlock was executed even though the initialization of a lock has failed)

An attempt to unlock was executed even though the initialization of the lock failed.

S:

Cancels processing.

O:

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

KAVB7498-E
A system error occurred. (Detailed information: The initialization of a lock has failed)

Initialization of a lock failed.

S:

Cancels processing.

O:

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

KAVB7550-E
An attempt to read the common definition associated with jcs_hosts has failed (Cause: reason-code).

An attempt to read common definition information associated with jcs_hosts failed.

S:

Terminates processing.

O:

Check the system status as directed by the reason code, and take corrective action. If the system does not recover normally, use the data collection tool to collect data, and then contact a system administrator.

Reason code: 2
Description: Key does not exist.
Action: Make sure that setup is correct.

Reason code: Other
Description: System error.
Action: Use the data collection tool to collect data, and then contact a system administrator.

KAVB7552-W
The value of the common definition (JCSHOSTS_TYPE) is out of range (value: value).

A value that is outside the specifiable range was specified for the common definition information (JCSHOSTS_TYPE) value.

S:

Continues processing using the default value (caching enabled).

O:

Check the value specified in the common definition information (JCSHOSTS_TYPE).

KAVB7555-W
jcs_hosts does not exist. The service will be continued with the jp1hosts or system hosts information.

jcs_hosts does not exist.

S:

Disables jcs_hosts and continues running the service using jp1hosts or /etc/hosts.

O:

If a jcs_hosts definition is required, create a jcs_hosts definition, and then reload jcs_hosts.

KAVB7556-I
jcs_hosts was reloaded successfully.

jcs_hosts was reloaded successfully.

S:

Central Scope Service runs with a new jcs_hosts definition.

KAVB7557-W
The old jcs_hosts will be used because an attempt to reload the jcs_hosts has failed.

An attempt to reload jcs_hosts failed due to a syntax error in the definition file.

S:

Uses the previously loaded jcs_hosts and continues processing.

O:

Determine whether jcs_hosts was excluded by the jcshostsimport command, and then reload jcs_hosts. If the same message is displayed, use the data collection tool to collect data, and then contact a system administrator.

KAVB7558-E
The jcs_hosts cannot be used because an attempt to reload the jcs_hosts has failed.

An attempt to reload jcs_hosts failed.

S:

Disables jcs_hosts and continues processing.

O:

Check the amount of free space in system memory. Either increase available memory by stopping unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

KAVB7559-E
An attempt to initialize jcs_hosts has failed.

An attempt to initialize jcs_hosts failed.

S:

Disables jcs_hosts and continues processing.

O:

Check the amount of free space in system memory. Either increase available memory by stopping unnecessary processes or add memory based on a re-estimate of the required memory, and then restart JP1/IM - Manager.

KAVB7560-I
jcs_hosts was initialized successfully.

jcs_hosts was initialized successfully.

KAVB7600-E
The logical hostname (logical-host-name) does not exist.

The specified logical host does not exist.

S:

Suspends command processing.

O:

Carefully review the specified logical host name to make sure that it is correct, and then re-execute the command.

KAVB7601-E
The user does not have execution permission.

You do not have execution permission.

S:

Suspends command processing.

O:

Log in as a user with Administrator permissions (in Windows) or superuser permission (in UNIX), and execute the command.

KAVB7602-E
Command execution will stop because memory is insufficient.

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 re-execute the command.

KAVB7603-E
Command execution will stop because disk capacity is insufficient.

There is not enough disk space to execute the command.

S:

Suspends command processing.

O:

Check the amount of free disk space, delete unnecessary files, and then re-execute the command.

KAVB7604-E
An error occurred during initialization of the database.

An error occurred during initialization of the database.

S:

Suspends command processing.

O:

Check the user's read and write permissions for files and directories in the database directory.

KAVB7605-E
An error occurred during database access.

An error occurred during database access.

S:

Suspends command processing.

O:

Check the user's read and write permissions for files and directories in the database directory.

KAVB7606-E
A connection could not be established with the JP1/IM - Central Scope daemon.

An attempt to connect to Central Scope Service failed.

S:

Suspends command processing.

O:

Make sure that Central Scope Service is running. If it is not running, start Central Scope Service, and then re-execute the command.

KAVB7607-E
The connection with the JP1/IM - Central Scope Service has been lost.

Communication with Central Scope Service ended.

An error occurred in the common definition API of JP1/Base.

An error occurred during definition file I/O.

S:

Suspends command processing.

O:

Make sure that Central Scope Service is running. If it is not running, start Central Scope Service, and then re-execute the command.

KAVB7608-E
The request could not be performed because a communication timeout error occurred.

A communication time-out occurred.

S:

Suspends command processing.

O:

Check the integrated trace log (HNTRLib2) to see if errors occurred in Central Scope Service.

KAVB7609-E
The response received from the JP1/IM - Central Scope Service is not valid.

The response data received from Central Scope Service is invalid.

S:

Suspends command processing.

O:

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

KAVB7610-E
The command (command-name) has been interrupted.

Processing was suspended by a user's suspension instruction.

S:

Suspends command processing.

O:

Processing was suspended by a user's suspension instruction. Execute the command again.

KAVB7611-E
An attempt to connect to the JP1/IM - Central Scope Service has failed because the jp1hosts definition for the specified logical host (logical-host-name) is invalid.

The definition of jp1hosts for the specified logical host is incorrect.

S:

Suspends command processing.

O:

Carefully review the definition of jp1hosts for the specified logical host.

KAVB7612-E
The command option is invalid. (option-name)

An incorrect command option was specified.

S:

Suspends command processing.

O:

Specify the correct command option, and then re-execute the command.

KAVB7613-E
The option-name option is specified more than once.

An option was specified more than once.

S:

Suspends command processing.

O:

Check the option specifications for the command.

KAVB7614-E
The value for the option-name option is not specified.

No value was specified for an option.

S:

Suspends command processing.

O:

Check the option specifications for the command.

KAVB7615-E
The option-name option is mandatory.

A required option was not specified.

S:

Suspends command processing.

O:

Check the option specifications for the command.

KAVB7616-E
The length of the value for the option-name option cannot be greater than numeric-value.

The character string length of the value specified in the option exceeds the maximum value.

S:

Suspends command processing.

O:

Check the option specifications for the command.

KAVB7617-E
Execute the command from the administrator console.

This command must be executed from the administrator console.

S:

Terminates command processing.

O:

Re-execute the command from the administrator console.

KAVB7618-E
An invalid value is specified for the option-name option.

An invalid value is specified for an option.

S:

Suspends command processing.

O:

Check the option specifications for the command.

KAVB7619-E
A system error occurred.

A system error occurred.

S:

Suspends command processing.

O:

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

KAVB7620-E
An error occurred during an attempt to set the locale.

A system error occurred during an attempt to set the locale.

S:

Suspends command processing.

O:

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

KAVB7621-W
Locale C is assumed because an attempt to set the locale has failed.

The default locale C was used because an attempt to set the locale failed. An invalid value may have been set for environment variable LANG or for a key that starts with LC_.

S:

Continues command processing.

O:

Carefully review the values set for environment variables, and correct invalid settings.

KAVB7622-E
An attempt to initialize the log has failed.

An attempt to initialize the log failed.

S:

Suspends command processing.

O:

Check the following items. If the issue cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

In UNIX, refer to the JP1/IM - Manager release notes, and make sure that file-related kernel parameters are set correctly.

Determine whether memory has become insufficient.

Determine whether disk space has become insufficient.

KAVB7623-E
An attempt to initialize the common definition has failed.

An attempt to initialize common definitions failed.

S:

Suspends command processing.

O:

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

KAVB7624-I
The command-name command finished successfully.

Command execution finished normally.

S:

The command finishes normally.

KAVB7625-E
A service or another command is already running.

Central Scope Service is running, or the version upgrade command is already running.

S:

Suspends command processing.

O:

If the service is running, the version upgrade is complete, so there is no need to execute the command.

If another version upgrade command is running, wait until that command finishes. If that command fails, retry the operation.

KAVB7626-E
An internal error occurred during execution of the command.

An internal error occurred during execution of a command.

S:

Suspends command processing.

O:

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

KAVB7627-E
Another command, command-name, is already running.

The command is already being executed.

S:

Suspends command processing.

O:

Wait for the command being executed to finish, and then retry the operation.

KAVB7628-E
The user does not have permission to read or write the file file-name.

You do not have read or write permission for the file.

S:

Suspends command processing.

O:

Check file access permissions.

KAVB7629-E
An attempt to execute has failed because another user is using the database.

Command execution failed because the database is being used by another function.

S:

Suspends command processing.

O:

Wait awhile, and then retry the operation.

KAVB7630-I
The status of the monitoring node (monitoring-node-ID) has been set to status.

Reports that the status of the monitoring node has changed.

S:

Terminates the command.

KAVB7631-E
The specified monitoring node (monitoring-node-ID) does not exist in the monitoring tree.

No monitoring node in the monitoring tree has the specified monitoring node ID.

S:

Suspends command processing.

O:

Make sure that the monitoring node with the specified monitoring node ID exists in the monitoring tree.

KAVB7632-E
The status of the specified monitoring node (monitoring-node-ID) cannot be changed because it is unmonitored.

The status of the monitoring node cannot be changed because the specified monitoring node is unmonitored.

S:

Suspends command processing.

O:

Start monitoring of the specified monitoring node, and then re-execute the command.

KAVB7633-E
The status of the specified monitoring node (monitoring-node-ID) cannot be changed to status, because the monitoring node is a group node. Group nodes can only be changed to "Initial" status.

The specified monitoring node can only be changed to initial status because it is a monitoring group.

S:

Suspends command processing.

O:

To change to a status other than initial, specify a monitored object.

KAVB7634-E
The jcschstat command ended abnormally.

The jcschstat command ended abnormally. This message is output following the message that was output during execution.

S:

Suspends command processing.

O:

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

KAVB7635-E
The maximum number of monitoring nodes that can be specified with the command is numeric-value.

The number of monitoring nodes exceeded the maximum that can be specified with the command.

S:

Suspends command processing.

O:

Check the option specifications for the command.

KAVB7636-E
The operation could not be executed because the central scope service or another command is already executing.

Central Scope Service is running, or another command is now executing.

S:

Suspends command processing.

O:

The jcsdbsetup command cannot be executed while the service is running. Stop the service. If another command is now executing, wait for it to finish.

KAVB7637-E
An attempt to create the lock file has failed.

An attempt to create the lock file failed.

S:

Suspends command processing.

O:

If the command was executed on a logical host, make sure that the shared disk is mounted, and then re-execute the command.

KAVB7638-W
An error occurred during initialization of the database, The database recovery operation succeeded.

An error occurred during database access processing on the server. Recovery was successful.

S:

Terminates command processing.

O:

The contents of the tree configuration information file were not saved on the server. Check the integrated trace log to find the source of the processing error on the server, and then re-execute the command.

KAVB7640-I
The database creation succeeded.

Creation of the monitored object database was successful.

S:

Creates a monitored object database.

KAVB7641-E
The parameter is invalid.

An argument is invalid.

S:

Terminates command processing.

O:

Carefully review the command arguments, and then retry the operation.

KAVB7642-E
The database creation could not be created. (return value : return-value)

The monitored object database could not be created.

S:

Terminates command processing.

O:

Check the system status according to the return value, and take corrective action. If the system does not recover normally, use the data collection tool to collect data, and then contact a system administrator.

Return value: 1
Description: Logical host name is invalid.
Action: Make sure that the logical host name specified by the argument is correct.

Return value: 4
Description: No permission to execute command.
Action: Make sure that the login account has Administrator permissions.

Return value: 10
Description: The JP1/IM - Manager definition information is not set up.
Action: Make sure that JP1/IM - Manager is installed correctly.

Return value: 12
Description: Not enough memory.
Action: Check the system memory.

Return value: 13
Description: Not enough disk space.
Action: Check the amount of free space on the disk.

Return value: 20
Description: Database already exists.
Action: If the existing database is not needed, delete it, and then re-execute the command.

Return value: 99
Description: Error with some other cause occurred.

KAVB7643-I
The processing to set up the JP1/IM-CS logical host will now start.

Processing to set up the Central Scope logical host will start.

S:

Starts processing to set up the Central Scope logical host.

KAVB7644-I
Processing to copy the definition file has started.

Processing to copy the logical host configuration file to the shared disk started.

S:

Starts processing to copy the logical host configuration file to the shared disk.

KAVB7645-I
JP1/IM Central Scope cluster environment setup completed successfully.

The logical host environment was set up successfully.

S:

Terminates command processing.

KAVB7646-E
Logical host of JP1/IM-CC is not setup.

The Central Console logical host environment is not set up.

S:

Terminates command processing.

O:

Set up the logical host of Central Console, and then re-execute the command.

KAVB7647-E
Specified shared directory does not exist

The specified shared directory does not exist.

S:

Terminates command processing.

O:

Carefully review the specified shared directory, and then re-execute the command.

KAVB7648-E
Failed to get default configuration data

An attempt to acquire the configuration information failed.

S:

Terminates command processing.

O:

Make sure that JP1/Base and JP1/IM - Manager are installed and set up correctly on the physical host.

KAVB7649-E
Failed to register configuration data

An attempt to register configuration information failed.

S:

Terminates command processing.

O:

Make sure that JP1/Base and JP1/IM - Manager are installed and set up correctly on the physical host.

KAVB7650-E
cannot create directory-name

An attempt to create a directory failed.

S:

Terminates command processing.

O:

Check the name of the specified shared directory and the access permissions, and then re-execute the command.

KAVB7651-E
cannot create database for logical host

An attempt to create a database failed.

S:

Terminates command processing.

O:

Make sure that the shared directory has enough disk space.

KAVB7652-E
Failed to update JP1/IM-CC conf files

An attempt to set up Central Console failed.

S:

Terminates command processing.

O:

Make sure that the shared disk of Central Console is mounted, and then execute setup again.

KAVB7653-E
Logical host of JP1/IM-CS is not setup

Setup of a standby server was attempted for a logical host for which the active server has not been set up.

S:

Terminates command processing.

O:

Set up the active server, and then set up the standby server.

KAVB7654-E
Failed to setup socket bind configuration

An attempt to set up the common definitions of the physical host failed.

S:

Terminates command processing.

O:

Make sure that JP1/Base and JP1/IM - Manager are installed and set up correctly on the physical host.

KAVB7655-I
The logical host database will now be created.

Processing to create the logical host database will start.

S:

Starts processing to create the logical host database.

KAVB7656-I
Update processing of the JP1/IM-CC definition file will now start.

Processing to update the Central Console definition file will start.

S:

Starts processing to update the Central Console definition file.

KAVB7657-I
Physical host communications will now be set up.

Setup of physical host communications will start.

S:

Starts setup of physical host communications.

KAVB7658-I
The JP1/IM-CS logical host will now be set up.

Central Scope logical host configuration processing will start.

S:

Starts Central Scope logical host configuration processing.

KAVB7660-I
Importing of the monitoring tree definition from the file file-name was successful.

Monitoring tree definitions were imported successfully.

S:

Terminates command processing.

KAVB7661-E
There is an error in the specified file. (file-name)

There is an error in the specified file.

S:

Suspends command processing.

O:

Use the jcsdbexport command to specify the file output.

KAVB7662-E
The specified input file (file-name) does not exist.

The specified file does not exist.

S:

Suspends command processing.

O:

Determine whether the specified file exists.

KAVB7663-E
A monitoring tree definition does not exist in the specified file.

A monitoring tree definition does not exist in the specified file.

S:

Suspends command processing.

O:

Use the jcsdbexport command to specify the file output.

KAVB7664-W
An invalid common event monitoring condition is included in the node.

An unregistered common event monitoring condition is included in the tree's monitoring node.

S:

Places the monitoring node in non-monitoring status and executes the command.

O:

Check the configuration of the status change conditions of the monitoring node.

KAVB7665-E
The specified definition file file-name is not a file.

The file specified as an argument is not a file.

S:

Suspends command processing.

O:

The specified file is not a file. Make sure that a file is specified, and then re-execute the command.

KAVB7666-E
The file (file-name) could not be imported because the file version is not compatible with the JP1/IM-CS monitored object DB version.

The file version of the file (file-name) is not compatible with JP1/IM - Central Scope. The specified file may have been created with a more recent version of JP1/IM - Central Scope.

S:

Suspends command processing.

O:

Check the file version, and then import monitoring tree definitions for JP1/IM - Central Scope that are compatible with that file version.

KAVB7667-E
In (mid-sized-item-type: mid-sized-item-name), the (small-item-type) has exceeded the restricted value (byte-count byte), import is failed.

An attempt to import failed because the (small-item-type) of (mid-sized-item-type: mid-sized-item-name) exceeds the limit (byte-count bytes).

The following values are displayed as the message text variables:

mid-sized-item-type
Node ID, common condition name, or Visual Monitoring window

mid-sized-item-name
The actual names corresponding to the items of mid-sized-item-type

small-item-type
Monitoring node name, attribute value of basic information, attribute value of common conditions, condition name of status change condition, individual attribute value of individual condition, common condition name, attribute value of common condition, window title of the Visual Monitoring window, or comment of the Visual Monitoring window

byte-count
The maximum length (in bytes) of the small-item-type item

S:

Suspends processing.

O:

Check the character string specified in small-item-type of mid-sized-item-name of mid-sized-item-type in the environment that exported the configuration file for monitoring tree, and shorten it so that it is within the limits for UTF-8 encoding. Then export the configuration file for monitoring tree again.

Move the exported configuration file for monitoring tree to the environment you want to import, and then import again.

KAVB7670-I
Exporting of the monitoring tree definition to the file file-name was successful.

Output of the monitoring tree definition to the file (file-name) was successful.

S:

Terminates command processing.

KAVB7671-E
There is no data in the database for the specified tree ID.

The specified tree ID cannot be found in the database.

S:

Suspends command processing.

O:

Make sure that the monitoring tree of the specified tree ID is in the database.

KAVB7680-E
An attempt to create jcs_hosts has failed (Cause: reason-code)

An attempt to create jcs_hosts failed.

S:

Terminates command processing.

O:

Check the system status as directed by the reason code, and take corrective action. If the system does not recover normally, use the data collection tool to collect data, and then contact a system administrator.

Reason code: 1024
Description: The number of files that can be opened has been exceeded.
Action: Check the status of the system's file resources.

Reason code: Other
Description: System error
Action: Use the data collection tool to collect data, and then contact a system administrator.

KAVB7681-E
A syntax error exists in the definition file. Specify the host name within 1-255 characters. (Line number: line-number, file name: file-name)

The host name described in the definition file exceeds 255 bytes.

S:

Terminates command processing.

O:

Correct the definition file syntax error, and then re-execute the command.

KAVB7682-E
A syntax error exists in the definition file. The maximum number of hosts that can be specified for one IP address is (number-of-hosts). (Line number: line-number, file name: file-name)

The number of hosts specified by the IP address described in the definition file exceeds the maximum.

S:

Terminates command processing.

O:

Correct the definition file syntax error, and then re-execute the command.

KAVB7683-E
A syntax error exists in the definition file. (character-string) is not an IP address. (Line number: line-number, file name: file-name)

A character string that is not recognized as an IP address is specified as an IP address in the definition file.

S:

Terminates command processing.

O:

Correct the definition file syntax error, and then re-execute the command.

KAVB7684-W
A syntax error exists in the definition file. Multiple hosts (host-name) are specified for an IP address (IP-address). (Line number: line-number, file name: file-name)

A host name is specified multiple times for a single IP address in the definition file.

S:

Continues processing.

O:

Check the contents of the definition file.

KAVB7685-W
A syntax error exists in the definition file. Only the first definition of IP address is validated because the IP address (IP-address) is specified several times. (Line number: line-number, file name: file-name)

An IP address is specified multiple times in the definition file.

S:

Continues processing.

O:

Check the contents of the definition file.

KAVB7686-E
A system error occurred while the command was executing.

A system error occurred while a command was being executed.

S:

Suspends command processing.

O:

Collect maintenance data while the command is being executed, and then contact a system administrator.

KAVB7687-E
The command option specification is invalid. You must specify the -o, -r, or -d option.

A required option is not specified.

S:

Suspends command processing.

O:

Specify the -o, -r, or -d option, and then re-execute the command.

KAVB7688-E
The command option specification is invalid. The -o, -r, and -d options cannot be specified simultaneously.

The -o, -r, or -d options have been specified simultaneously.

S:

Suspends command processing.

O:

The -o, -r, and -d options cannot be specified simultaneously. Review the specified options.

KAVB7689-E
An attempt to open jcs_hosts has failed. (Cause: reason-code).

An attempt to open jcs_hosts failed.

S:

Terminates command processing.

O:

Check the system status as directed by the reason code, and take corrective action. If the system does not recover normally, collect maintenance data while the command is being executed, and then contact a system administrator.

Reason code: 1024
Description: The number of files that can be opened has been exceeded.
Action: Check the status of the system's file resources.

Reason code: Other
Description: System error
Action: Use the data collection tool to collect data, and then contact a system administrator.

KAVB7690-E
An error occurred while jcs_host was being accessed. (cause: reason-code)

An error occurred while accessing jcs_hosts.

S:

Suspends command processing.

O:

Collect maintenance data while the command is being executed, and then contact a system administrator.

KAVB7691-E
The command execution will be stopped because the memory is insufficient.

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 re-execute the command.

KAVB7692-E
The user does not have the access permission for accessing the specified definition file (file-name) for jcs_hosts.

The user cannot access the file.

S:

Suspends command processing.

O:

Check the access permission for the specified file.

KAVB7693-E
The specified definition file (file-name) for jcs_hosts does not exist.

The file does not exist.

S:

Suspends command processing.

O:

The file name specified as an argument does not exist. Check the file name, and then re-execute the command.

KAVB7694-E
A system error occurred. (Detailed information: An error occurred in system call)

An error occurred in a system call.

S:

Suspends command processing.

O:

Check the amount of free space in system memory, increase available memory by stopping unnecessary processes, and then re-execute the command.

KAVB7695-E
The user does not have execution permission.

The user executing the command does not have Administrator permissions.

S:

Suspends command processing.

O:

Log in as a user with Administrator permissions, and then execute the jcshostsimport command.

KAVB7696-E
The jcs_hosts is invalid.

jcs_hosts is corrupted.

S:

Suspends command processing.

O:

jcs_hosts is corrupted. Set it up again. If the system does not recover normally, use the data collection tool to collect data, and then contact a system administrator.

KAVB7697-E
An attempt to initialize the log has failed (Cause: reason-code)

An attempt to initialize the log failed.

S:

Suspends command processing.

O:

Make sure that setup is correct, and, if necessary, perform setup again. If the system does not recover normally, use the data collection tool to collect data, and then contact a system administrator.

KAVB7698-E
The Jcs_hosts is busy.

jcs_hosts is being used by another process.

S:

Suspends command processing.

O:

Determine whether jcs_hosts is being used by another process.

KAVB7699-E
No entry is in the definition file (file name: file-name)

Processing will stop because no key is specified in the definition file.

S:

Suspends command processing.

O:

Specify the key in the definition file, and then re-execute the command.

KAVB7700-E
The process will be terminated because an attempt to read the definition file failed. (file name: file-name)

Command processing will stop because an attempt to read the definition file failed.

S:

Suspends command processing.

O:

This is a definition file syntax error. Correct the definition file error, and then re-execute the command.

KAVB7701-I
The jcshostsimport command successfully ended.

Command processing ended normally.

KAVB7702-E
A syntax error exists in the definition file. The host is not specified. (Line number: line-number file name: file-name).

The definition file contains a line that does not specify a host name.

S:

Suspends command processing.

O:

This is a definition file syntax error. Correct the definition file error, and then re-execute the command.

KAVB7703-E
An attempt to initialize the common definition has failed. (Cause: reason-code).

An attempt to initialize common definition information failed.

S:

Suspends command processing.

O:

Make sure that setup is correct.

Reason code: -2
Description: An attempt to initialize common definition information failed.
Action: Make sure that setup is correct.

KAVB7704-E
An attempt to set the locale has failed.

S:

Terminates command processing.

O:

Check the locale settings in the OS.

KAVB7705-W
C is assumed because an attempt to set the Local has failed.

S:

Continues processing using the default locale C.

O:

Check the locale settings in the OS.

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

The specified logical host does not exist.

S:

Suspends command processing.

O:

Check the specified logical host name to see if it contains errors.

KAVB7707-E
The number of IP addresses specified for one host exceeds the limit (maximum-number). (file name: file-name).

The number of IP addresses specified for one host name exceeds the maximum that can be specified.

S:

Terminates command processing.

O:

This is a definition file syntax error. Correct the definition file error, and then re-execute the command.

KAVB7708-E
An attempt to acquire the common definition has failed.

There is no key in the common definitions.

S:

Suspends command processing.

O:

Make sure that the key is specified.

KAVB7709-E
A system error occurred. (Cause: reason-code)

A fatal error occurred while analyzing arguments.

S:

Suspends command processing.

O:

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

KAVB7711-E
The command option specification is invalid.

A command argument is incorrect.

S:

Suspends command processing.

O:

A command argument is incorrect. Carefully review the arguments, and then re-execute the jcshostsexport command.

KAVB7712-E
The jcs_hosts does not exist.

jcs_hosts does not exist.

S:

Suspends command processing.

O:

Specify the correct database file name, and then execute jcshostsexport.

KAVB7713-E
JP1/IM-CS is not set up.

JP1/IM - Manager is not set up.

S:

Suspends command processing.

O:

Re-install JP1/IM - Manager.

KAVB7714-W
The command execution will be stopped because the disk space is insufficient.

There is not enough disk space to execute the command.

S:

Suspends command processing.

O:

Check the amount of free space on the disk.

KAVB7715-E
The specified definition file file-name is not a file.

The definition file for jcs_hosts that was specified as an argument is not a file.

S:

Suspends command processing.

O:

The definition file that was specified for jcs_hosts is not a file. Check the specification, and then re-execute the command.

KAVB7722-E
The logical host (logical-host-name) is not specified.

The logical host has not been specified, or the specified logical host information does not exist.

S:

Suspends command processing.

O:

Make sure that the specified logical host name is correct and that it has been specified correctly.

KAVB7723-E
The command option is invalid. The option (option-name) cannot be recognized.

The specified option is invalid.

S:

Suspends command processing.

O:

This is a definition file syntax error. Correct the definition file error, and then re-execute the command.

KAVB7724-E
The command option is invalid. The option (option-name) is specified redundantly.

An option has been specified more than once.

S:

Terminates command processing.

O:

Check the specified option, and then re-execute the command.

KAVB7725-E
The command option is invalid. The value of the option (option-name) is invalid.

A value required by the specified option has not been specified.

S:

Suspends command processing.

O:

Check the specified option, and then re-execute the command.

KAVB7726-E
A syntax error exists in the definition file. An IP address should be specified within 1-63 characters. (Line number: line-number, file name: file-name).

An IP address specified in the definition file is too long.

S:

Suspends command processing.

O:

This is a definition file syntax error. Correct the definition file error, and then re-execute the command.

KAVB7727-E
The command execution will be stopped because the memory is insufficient.

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 re-execute the command.

KAVB7730-I
The JP1/IM - Central Scope setup will now start.

The Central Scope setup command will start.

S:

Continues processing.

KAVB7731-I
The file file-name was relocated.

The file-name file was relocated.

S:

Continues processing.

KAVB7732-E
'/opt/jp1base/bin/jbssetcnf' could not be executed.

The /opt/jp1base/bin/jbssetcnf command could not be executed.

S:

Suspends command processing.

O:

Make sure that JP1/Base and JP1/IM - Manager are installed correctly.

KAVB7733-I
file-name was registered to the common definition.

Common definition information was registered successfully.

S:

Continues processing.

KAVB7734-E
file-name could not be registered to the common definition.

An attempt to register common definition information failed.

S:

Suspends command processing.

O:

Make sure that JP1/Base and JP1/IM - Manager are installed correctly.

KAVB7735-I
The registration of the common definition data has completed.

Registration of common definition information is complete.

S:

Continues processing.

KAVB7736-E
The system environment could not be set.

The system environment could not be set up.

S:

Suspends command processing.

O:

Make sure that JP1/IM - Manager is installed correctly.

KAVB7737-I
JP1/IM - Central Scope setup has completed.

The Central Scope setup command has ended.

S:

Terminates command processing.

KAVB7750-I
Upgrading of the database version has finished.

Upgrading of the database version is complete.

S:

Terminates command processing.

KAVB7751-I
The database version has already been upgraded.

The database version has already been upgraded.

S:

Suspends command processing.

KAVB7753-E
The specified work path (specified-path) does not exist.

The specified work path does not exist.

S:

Suspends command processing.

O:

Make sure that the specified work path exists.

KAVB7754-W
The database will now be recovered from the backup because the database is corrupted.

The database was recovered from the backup because it was corrupted when the jp1csverup and jp1cshaverup commands were executed.

S:

Continues command processing.

O:

The most recent changes may not have been saved. Check the monitoring tree configuration in JP1/IM - View, and make sure that the monitoring tree is correct.

KAVB7755-E
Command execution will now stop because the attempt to recover the database failed.

An attempt to recover the database failed because the database was corrupted when the jp1csverup and jp1cshaverup commands were executed.

S:

Suspends command processing.

O:

Monitoring tree information was lost when the database was corrupted. Execute the jcsdbsetup command to set up the database, and then rebuild the monitoring tree.

KAVB7765-E
An attempt to copy the definition file file-name has failed.

An attempt to copy a definition file (file-name) failed.

S:

Suspends command processing.

O:

Check the following items. If the issue cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

Determine whether the file-name file exists in the scope-path\conf\ directory.
If it does not, re-install JP1/IM - Manager.

Determine whether the \JP1Scope\conf\ folder exists in the shared folder of the specified logical host.
If it does not, execute the jp1cshasetup command to set up the Central Scope logical host again.

Make sure that there is sufficient memory.

Make sure that there is sufficient disk space.

KAVB7766-E
An attempt to add the common definition key has failed.

An attempt to add a key to the common definitions failed.

S:

Suspends command processing.

O:

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

KAVB7767-E
An attempt to delete the database has failed.

An attempt to delete the database failed.

S:

Suspends command processing.

O:

Determine whether the service is running. If it is running, stop the service, and then retry the operation. If the service is already stopped, use the data collection tool to collect data, and then contact a system administrator.

KAVB7770-I
The data was backed up successfully.

Reports that data was acquired successfully.

S:

Terminates the command.

KAVB7771-W
The logical host logical-host-name does not exist.

The specified logical host does not exist.

S:

Continues processing without acquiring the data of the specified logical host.

O:

Carefully review the specified logical host name to make sure that it is correct, and then re-execute the command.

KAVB7772-E
Command execution will stop because disk capacity is insufficient.

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 re-execute the command.

KAVB7773-E
The command option is invalid.

An incorrect command option was specified.

S:

Suspends command processing.

O:

Specify the correct command option, and then re-execute the command.

KAVB7774-E
Command execution will stop because memory is insufficient.

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 re-execute the command.

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

The shared directory of the specified logical host does not exist.

S:

Acquires only the data of the physical host and continues processing.

O:

Install the shared directory, and then re-execute the command.

KAVB7776-W
A part of the data was not correctly acquired.

Part 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.

KAVB7777-W
An attempt to acquire data for collection-directory-or-file did not finish successfully.

collection-directory-or-file data was not acquired normally.

S:

Continues command processing.

O:

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

KAVB7778-W
An attempt to acquire information from the registry for product-name-or-logical-host-name has failed.

product-name-or-logical-host-name data could not be acquired.

S:

Continues command processing.

O:

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

KAVB7779-E
An attempt to create the directory (specified-path) has failed.

The specified-path directory could not be created.

S:

Terminates command processing.

O:

Carefully review the executing user's read and write permissions for the directory above the specified directory, and then run the data collection tool again.

KAVB7780-W
The directory used by the physical host was not found. (directory-path)

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

S:

Continues processing without acquiring data in directory-path.

O:

Determine whether directory-path is temporarily unavailable.

KAVB7782-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.

KAVB7790-I
The pre-installation processing of JP1/IM-Central Scope will now start.

Pre-installation processing of JP1/IM - Manager will start.

S:

Starts pre-installation processing of JP1/IM - Manager.

KAVB7791-E
A prerequisite product has not been installed.

A prerequisite product has not been installed.

S:

Suspends installation.

O:

Install the prerequisite product(s), and then re-install Central Scope Service.

KAVB7792-I
The pre-installation processing of JP1/IM - Central Scope will now end.

Pre-installation processing of JP1/IM - Manager will end.

S:

Terminates pre-installation processing of JP1/IM - Manager.

KAVB7793-I
The post-installation processing of JP1/IM - Central Scope will now start.

Post-installation processing of JP1/IM - Manager will start.

S:

Starts post-installation processing of JP1/IM - Manager.

KAVB7794-I
The JP1/IM - the Central Scope service will now be registered.

The JP1/IM - Manager service will be registered.

S:

Adds a port number to the /etc/services file.

KAVB7795-I
The JP1/IM - the Central Scope service was registered.

JP1/IM - Manager service was registered.

S:

Adds a port number to the /etc/services file.

KAVB7796-E
The JP1/IM - the Central Scope service could not be registered.

The JP1/IM - Manager service could not be registered.

S:

Continues installation.

O:

Wait until installation finishes, and then add a port number to /etc/services.

KAVB7797-I
The post-processing of JP1/IM - Central Scope installation will now end.

Post-installation processing of JP1/IM - Manager will end.

S:

Terminates post-installation processing of JP1/IM - Manager.

KAVB7798-I
The uninstallation of JP1/IM - Central Scope will now start.

JP1/IM-Manager uninstallation will start.

S:

Starts uninstalling JP1/IM - Manager.

KAVB7799-E
An attempt to set the system environment has failed.

An attempt to set up the system environment failed because the /opt/jp1cons/bin/jcoimdef command could not be executed normally.

S:

Continues processing.

O:

After uninstallation is finished, execute the /opt/jp1cons/bin/jcoimdef command manually, specifying -s and OFF as arguments.

KAVB7800-E
'/opt/jp1scope/bin/jcsdbsetup' could be executed.

An attempt to create a Central Scope database failed because the jcsdbsetup command could not be executed normally.

S:

Continues processing.

O:

After installation is finished, execute the jcsdbsetup command manually.

KAVB7801-E
'/opt/jp1scope/bin/jp1cs_setup' could be executed.

Central Scope setup processing failed because the jp1cs_setup command could not be executed normally.

S:

Continues processing.

O:

After installation is finished, execute the jp1cs_setup command manually.

KAVB7802-E
The stop of services failed.

An attempt to stop services failed.

S:

Suspends installation or uninstallation.

O:

Stop JP1/IM - Manager manually, and then install or uninstall.

KAVB7900-I
Status of monitoring-node-name is changed status from status.

Reports that the status of a monitoring node has changed.

S:

The status of monitoring node monitoring-node-name has changed.

KAVB7901-W
The number of status change event for the monitored node monitoring-node-ID has reached the threshold.

The number of status change events for the monitoring node (monitoring-node-ID) exceeded the upper limit.

S:

Disables the linked functionality for which corrective action has already been taken for the monitoring node (monitoring-node-ID) and continues processing.

O:

Execute a status change event search, and then check the contents of the status change event. If it is not problematic to do so, manually change the status of the monitoring node, and then clear the history of the status change event.

[Contents][Back][Next]

[Trademarks]