Job Management Partner 1/Integrated Management - Manager Messages

2.12 Messages related to IM Configuration Management (KNAN22000 to KNAN24999)

KNAN22000-I
The host "host-name" was successfully registered.

The host was successfully registered.

S:

Registers the host.

KNAN22001-I
An attribute for the host "host-name" was successfully changed.

An attribute for the specified host was changed.

S:

Changes the host attribute.

KNAN22002-I
Host information from the host "host-name" was successfully collected.

Host information from the agent host was collected successfully.

S:

Collects the host information.

KNAN22003-I
The host "host-name" was successfully deleted.

The specified host was successfully deleted.

S:

Deletes the host.

KNAN22004-E
Collection of host information from all hosts failed. (Cause: error-code)

A search of all hosts failed.

S:

Does not collect host information.

O:

Execute the jimdbstatus command, and then make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

KNAN22005-E
Host "host-name" cannot be registered because a host with the same name is already registered.

The host is already registered in the IM Configuration Management database.

S:

Does not register the host.

O:

Register a host name that is not already registered.

KNAN22006-E
Registration of the host "host-name" failed because the number of registered hosts exceeded the maximum limit maximum-number-of-registered-hosts.

Registration of the host failed because the number of registered hosts exceeds the maximum.

S:

Does not register the host.

O:

Delete any unneeded hosts, and then register the host.

KNAN22007-E
The host "host-name-1" cannot be registered because the host "host-name-2" specified in related-host is not registered.

The host specified as the active host, the standby host, or the VMM host was not registered.

S:

Does not register the host.

O:

Specify a host that is not registered in the host list as the host name for the active host, the standby host, or the VMM host.

KNAN22008-E
Registration of the host "host-name" failed. (Cause: error-code)

Registration of the host failed.

S:

Does not register the host.

O:

Execute the jimdbstatus command, and then make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

KNAN22009-E
Registration of the host "host-name" failed because the host type of the host "related-host-name" specified in related-host is incorrect.

Registration of the host failed because the specified host type is incorrect.

S:

Does not register the host.

O:

Revise the condition based on the host type:

For a VMM host, specify the physical host.

For an active host, specify the physical host or the virtual host.

For a standby host, specify the physical host or the virtual host.

KNAN22010-E
An attribute of the host "host-name" cannot be changed because the host "host-name" specified in related-host is not registered.

An attribute of the host cannot be changed because the specified host is not registered.

S:

Does not register the changed host attribute.

O:

Specify a host that is not registered in the host list as the host name for the VMM host, the active host, or the standby host.

KNAN22011-E
An attribute of the host "host-name" cannot be changed because the host type of the host "related-host-name" specified in related-host is incorrect.

An attribute of the host cannot be changed because the specified host type is incorrect.

S:

Does not register the changed host attribute.

O:

Revise the condition based on the host type:

For a VMM host, specify the physical host.

For an active host, specify the physical host or the virtual host.

For a standby host, specify the physical host or the virtual host.

KNAN22012-E
An attempt to change a host attribute for the host "host-name" failed. (Cause: error-code)

A host attribute of the specified host could not be changed.

S:

Does not register the changed host attribute.

O:

Execute the jimdbstatus command, and then make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

KNAN22013-E
The host attribute cannot be changed to host-type because host host-name is referenced as related-host from host-name-2.

The host attribute cannot be changed because the specified host is referenced from another host.

S:

Does not register the changed host attribute.

O:

Edit the host attribute of the referencing host so that it is not referenced, and then retry the operation.

KNAN22014-E
The host attribute cannot be changed because the host "host-name" is the local host.

A host attribute of the local host cannot be changed.

S:

Does not register the changed host attribute.

O:

Do not change the host type of the local host.

KNAN22015-E
Collection of host information from the host "host-name" failed. (Cause: error-code)

Collection of host information from the specified host failed.

S:

Does not collect host information.

O:

If the following detailed information is displayed, take the indicated corrective action.

The data that was acquired while connected to the host is invalid.
It is possible that invalid data was sent from JP1/Base of the acquired host.
Make sure that JP1/Base of the acquired host is operating normally.

IM Configuration Management database access error.
Execute the jimdbstatus command, and then make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

There are not enough resources.
Make sure that there is sufficient disk space, memory, or other OS resources.

The connection destination host is busy.
Wait awhile, and then retry the operation.

Failed to receive the data from the connection destination host.

Failed to send the data to the connection destination host.
Check the OS resources and memory status, and then check the network configuration and status with the connection destination.
Also make sure that IM Configuration Management Service of the connection destination is running.

A request was executed in an invalid operating environment.
It is possible that the IM configuration (system hierarchy) has been deleted.
Click Operation, and then Verify IM Configuration to confirm that the current configuration is correct.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22016-E
Collection of host information failed because the version of JP1/Base on the host host-name is not supported.

Collection of host information failed because the version of JP1/Base on the specified host is not supported.

S:

Does not collect host information.

O:

Upgrade JP1/Base to version 09-00 or later.

KNAN22017-E
Collection of host information failed because a connection could not be established with the host "host-name".

Collection of host information failed because a connection could not be established with the specified host.

S:

Does not collect host information.

O:

Check the following items, and then retry the operation.

Has the connection destination been started?

Can a connection be made to the host?

Is JP1/Base running?

Can name resolution be performed?

KNAN22019-E
An attempt to collect host information for the host "host-name" failed because the actual host type is different from the registered host type. (registered host type = registered-host-type, collected host type = actual-host-type)

An attempt to collect host information for the specified host failed because the actual host type is different from the registered host type.

S:

Does not collect host information.

O:

Edit the host attribute so that it is the proper type, and then retry the operation.

KNAN22020-E
The host "host-name" cannot be deleted because a local host cannot be deleted.

A local host cannot be deleted.

S:

Does not delete the host.

O:

Do not delete a local host.

KNAN22021-E
The host "host-name" cannot be deleted because hosts in an IM configuration cannot be deleted.

The specified host cannot be deleted because it is contained in an IM configuration (system hierarchy).

S:

Does not delete the host.

O:

Separate the host from the IM configuration (system hierarchy), and then retry the operation.

KNAN22022-E
The host "host-name-1" cannot be deleted because it is referenced as a related-host host for the host "host-name-2".

The specified host cannot be deleted because it is referenced from another host.

S:

Does not delete the host.

O:

Edit the host attribute of the referencing host so that it is not referenced, and then retry the operation.

KNAN22023-E
Deletion of the host "host-name" failed. (Cause: error-code)

Deletion of the specified host failed.

S:

Does not delete the host.

O:

If the following detailed information is displayed, take the indicated corrective action.

IM Configuration Management database access error
Execute the jimdbstatus command, and then make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22024-E
Acquisition of product information for the host "host-name" failed. (Cause: error-code)

Acquisition of product information for the specified host failed.

S:

Does not collect host information.

O:

Execute the jimdbstatus command, and then make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

KNAN22025-E
Acquisition of host information for the host "host-name" failed. (Cause: error-code)

Acquisition of host information for the specified host failed.

S:

Does not acquire host information.

O:

Execute the jimdbstatus command, and then make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

KNAN22026-E
An attribute of the host "host-name" could not be changed because the host name "new-host-name" is already registered.

An attribute of the host could not be changed because the entered host name is already registered.

S:

Does not register the changed host attribute.

O:

Enter a different host name, and then retry the operation.

KNAN22027-W
Host information cannot be collected because the user user-name:View-host-name is collecting information for the host "host-name".

Host information cannot be collected because another user is collecting information.

S:

Does not collect host information.

O:

Do one of the following:

In the Login User List window, determine whether the user has acquired exclusive permission.
If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and then click the Release Exclusive Editing button to release exclusive permission.

Wait awhile, and then retry the operation.

KNAN22028-E
Host Registration failed because the number of registered hosts exceeded the maximum limit maximum-number-of-registered-hosts.

Registration of the host failed because the number of registered hosts exceeds the maximum.

S:

Does not register the host.

O:

Delete any unneeded hosts, and then register the host.

KNAN22031-E
Batch collection for hosts failed because the user user-name:View-host-name is executing the profile batch collect/reflect.

Batch collection for hosts failed because another user is executing profile batch collection or batch application.

S:

Does not collect host information.

O:

Do one of the following:

In the Login User List window, determine whether the user has acquired exclusive permission. If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and then click the Release Exclusive Editing button to release exclusive permission.

Wait awhile, and then retry the operation.

KNAN22100-E
An argument is incorrect.

An argument is incorrect.

S:

Does not collect host information.

O:

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

KNAN22101-E
Common definition initialization failed.

Common definition initialization failed.

S:

Does not collect host information.

O:

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

KNAN22102-E
The command jp1agentinfo will now stop because the logical host "host-name" does not exist.

The specified logical host does not exist.

S:

Does not collect host information.

O:

Specify a logical host that has already been configured.

KNAN22103-E
An internal error occurred. (Command name: jp1agentinfo, error code: error-code)

An internal error occurred.

S:

Does not collect host information.

O:

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

KNAN22104-E
The command command-name terminated abnormally. (error code = error-code)

The command terminated abnormally.

S:

Does not collect host information.

O:

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

KNAN22200-I
An IM configuration does not exist.

IM configuration (system hierarchy) could not be acquired because the IM configuration (system hierarchy) does not exist.

S:

Stops acquiring the IM configuration (system hierarchy).

KNAN22201-E
Acquisition of the IM configuration failed because the acquired configuration is invalid.

The acquired IM configuration (system hierarchy) is invalid.

S:

Stops acquiring the IM configuration (system hierarchy).

O:

Execute the jbsrt_get command to check the IM configuration (system hierarchy).

KNAN22202-E
Registration of the IM configuration failed because the maximum number of hosts (maximum-number-of-registered-hosts) was exceeded.

Registration of the IM configuration (system hierarchy) failed because the number of registered hosts exceeds the maximum.

S:

Stops acquiring the IM configuration (system hierarchy).

O:

Delete any unneeded hosts, and then retry the operation.

KNAN22203-E
Registration of the IM configuration failed because registration of the host "host-name" failed. (Cause: error-code)

Registration of the IM configuration (system hierarchy) failed because registration of the host information failed.

S:

Stops acquiring the IM configuration (system hierarchy).

O:

If the following detailed information is displayed, take the indicated corrective action.

IM Configuration Management database access error
Execute the jimdbstatus command, and then make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

The host has already been registered.
Enter a different host name, and then retry the operation.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22204-E
Registration of the IM configuration failed because writing to the database failed.

Registration of the IM configuration failed because writing to the IM Configuration Management database failed.

S:

Stops acquiring the IM configuration (system hierarchy).

O:

Make sure that there is sufficient disk space, memory, or other OS resources. If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KNAN22205-E
Collection of the IM configuration failed because the local host name "host-name-1" is different from the registered host name "host-name-2".

The local host name in the IM configuration (system hierarchy) is different from the local host name registered in the host list.

S:

Stops acquiring the IM configuration (system hierarchy).

O:

Edit the local host name to match the name of the host used in the IM configuration (system hierarchy), and then retry the operation.

KNAN22206-E
Acquisition of the IM configuration failed. (Cause: detailed-information)

Acquisition of the IM configuration (system hierarchy) failed because of an internal error.

S:

Stops acquiring the IM configuration (system hierarchy).

O:

If the following detailed information is displayed, take the indicated corrective action.

The execution environment of JP1/Base is invalid.

The JP1/Base configuration file could not be accessed.
Check the following items:
Is the JP1/Base conf directory defined in the common definition?
Did the JP1/Base configuration end normally?

An internal error occurred in JP1/Base during processing.
Check the following items:
Is there sufficient memory?
Has Configuration Management been started?
Was JP1/Base restarted after JP1/IM was installed?
Is there sufficient write and read permission for the conf/route/ directory?

An I/O error occurred.

Failed to read the configuration file.
Make sure that there is sufficient disk space, memory, or other OS resources.

A common definition could not be acquired.
The JP1/Base common definition information is not configured. Make sure that it is configured correctly.
If operating in a cluster environment, make sure that the logical host name set in the JP1_HOSTNAME environment variable is correct.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22207-I
The collection of the IM compositions ended.

Acquisition of the IM configuration (system hierarchy) ended.

S:

Stops acquiring the IM configuration (system hierarchy).

KNAN22208-E
IM Configuration collection is failed. (Cause: Configuration includes incorrect host name (host-name).)

Acquisition of the IM configuration (system hierarchy) failed because the IM configuration contains an incorrect host name.

S:

Stops acquiring the IM configuration (system hierarchy).

O:

Execute the jbsrt_get command, and then make sure that the output host name satisfies the following conditions:

Does the host name begin and end with alphabetic or numeric characters?

Does the host name begin and end with a hyphen (-) or a period (.)?

If a host does not satisfy the above conditions, delete the host from the primary system configuration.

KNAN22209-I
The IM configuration does not exist. Do you want to apply the IM configuration stored on the server?

The IM configuration (system hierarchy) does not exist. This message confirms that you want to switch to the IM configuration (system hierarchy) maintained in the server.

S:

Continues acquiring the IM configuration (system hierarchy).

KNAN22220-E
The IM configuration for the host "host-name" is invalid.

The IM configuration (system hierarchy) of the host is invalid.

S:

Stops verification.

O:

Refresh the IM configuration (system hierarchy), and then retry the operation.

KNAN22221-E
IM configuration verification for the host "host-name" is not supported.

IM configuration (system hierarchy) verification is not supported for the version of JP1/Base on the host.

S:

Stops verification of the host and continues verification of the remaining hosts.

O:

Upgrade to JP1/Base version 09-00 or later.

KNAN22223-E
IM configuration information could not be acquired from the host "host-name". (Cause: detailed-information)

IM configuration information (system hierarchy) could not be acquired from the host.

S:

Stops verification of the host and continues verification of the remaining hosts.

O:

If the following detailed information is displayed, take the indicated corrective action.

There are not enough resources.
Make sure that there is sufficient disk space, memory, or other OS resources.

The connection destination host is busy.
Wait awhile, and then retry the operation.

The data that was acquired while connected to the host is invalid.
Invalid data may have been received temporarily. Retry the operation.
Also check the network configuration and status with the acquired target.

A connection could not be established with the host.
Connection with the acquired host failed.
Check the network configuration and status with the acquired host.
Also make sure that JP1/Base is running on the acquired host.

The version of JP1/Base on the connection destination is not supported.
Make sure that the JP1/Base version is 09-00 or later.

Failed to receive the data from the connection destination host.

Failed to send the data to the connection destination host.
Check the OS resources and memory status, and then check the network configuration and status with the connection destination.
Also make sure that IM Configuration Management Service of the connection destination is running.

Connection with the host has ended.

A host connection timeout occurred.
Check the network configuration and status with the acquired host.
Also make sure that JP1/Base is running on the acquired host.

The configuration did not exist.

There is an invalid definition in the configuration file.
Execute the jbsrt_get command, and then make sure that the IM configuration (system hierarchy) exists on the host.
If there is no IM configuration (system hierarchy), use the IM Configuration Management window to refresh it.

Operations cannot be performed on the file.
Check the following items, and then retry the operation:
Is there sufficient memory?
Does the file exist?
Has the file access permission been set correctly?
Has the file been opened (locked) by another application?

A request was executed in an invalid operating environment.
It is possible that the IM configuration (system hierarchy) has been deleted.
Click Operation, and then Verify IM Configuration to confirm that the current configuration is correct.

A common definition could not be acquired.
The JP1/Base common definition information is not configured. Make sure that it is configured correctly.
If operating in a cluster environment, make sure that the logical host name set in the JP1_HOSTNAME environment variable is correct.

KNAN22224-I
The IM configuration of the host "host-name" is normal.

The IM configuration (system hierarchy) on the host is normal.

S:

Continues verification of the remaining hosts.

KNAN22225-E
IM Configuration verification for the host (host-name) is failed. (Cause: DB Updation is failed.)

IM configuration verification failed because updating of the IM Configuration Management database failed.

S:

Continues verification of the remaining hosts.

O:

Confirm that the IM Configuration Management database is running, and then retry the operation.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KNAN22240-E
An attempt to apply the IM configuration failed because database registration failed. (details = error-code)

An attempt to register with the IM Configuration Management database failed.

S:

Stops applying the IM configuration.

O:

If the following detailed information is displayed, take the indicated corrective action.

Operations cannot be performed on the file.
Check the following items, and then retry the operation:
Is there sufficient memory?
Does the file exist?
Has the file access permission been set correctly?
Has the file been opened (locked) by another application?

IM Configuration Management database access error.
Execute the jimdbstatus command, and then make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

The host does not exist.
Make sure that the host is registered in the host list of the IM Configuration Management window.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22241-E
An attempt to apply changes to the JP1/Base definition file (jbsrt_route.conf) failed.

An attempt to apply changes to the JP1/Base definition file (jbsrt_route.conf) failed.

S:

Stops applying the changes.

O:

Make sure that the user has write permission to the JP1/Base definition file (jbsrt_route.conf), and then retry the operation.

KNAN22243-E
An attempt to apply the IM configuration failed. (Cause: error-code)

An attempt to apply the IM configuration (system hierarchy) failed because an internal error occurred.

S:

Stops applying the IM configuration.

O:

If the following detailed information is displayed, take the indicated corrective action.

Operations cannot be performed on the file.
Check the following items, and then retry the operation:
Is there sufficient memory?
Does the file exist?
Has the file access permission been set correctly?
Has the file been opened (locked) by another application?

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22244-E
Cannot delete configuration for the host and its lower-level hosts. Try again after deleting configuration of the host "host-name" each definition separately.

An attempt to delete the IM configuration (system hierarchy) of the host and lower-level hosts failed.

S:

Stops deleting the IM configuration.

O:

Execute the jbsrt_del command from the displayed host and lower-level hosts, delete the IM configuration (system hierarchy), and then retry the operation.

KNAN22245-E
Cannot set configuration information in the host "host-name".

An attempt to apply the IM configuration (system hierarchy) failed for some hosts.

S:

Stops applying the IM configuration.

O:

Check the following items on the host where the error occurred:

Is JP1/Base running?

Is the JP1/Base Configuration Management port number the same as the port for an higher-level host of the host that had the error?

Are lower-level hosts defined for JP1/Base?

Is the higher-level host of JP1/IM - Manager JP1/IM - Satellite Console?

On the site manager or the relay manager, are 6 or more hosts defined directly below the JP1/IM - Central Console 5 Node?

On the site manager or the relay manager, are 11 or more hosts defined directly below the JP1/IM - Central Console 10 Node?

Can the host name of the host that had the error be resolved from the higher-level hosts?

Was the host that had the error defined as the previous topmost host? If the IM configuration (system hierarchy) defined as the topmost host remains, use the jbsrt_distrib command from the host that had the error to delete the IM configuration (system hierarchy).

Was JP1/Base restarted after JP1/IM was installed?

Is there sufficient memory?

Is there read and write permission for the JP1/Base installation directory and for the logical host shared disk conf/route/ directory?

If the problem is other than the above, take the following actions on the host with the error:

Execute the jbsrt_get command.

Determine whether any of the following occurred:
Message KAVB3162-E was output.
The jbsrt_get command finished abnormally.
The local host name is displayed in Higher-level hosts or Lower-level hosts.
A host name other than a local host is displayed in Local hosts.
The host name is unintelligible.

If any of the above occurred, recover using the following method:

Use the jbsrt_del command to delete the IM configuration (system hierarchy).

Re-apply the IM configuration (system hierarchy) from the manager host.

KNAN22247-E
Application of the IM configuration failed because host host-name is not registered.

Application of the IM configuration failed because the host (host-name) is not registered.

S:

Stops applying the IM configuration.

O:

Make sure that the host is registered, and then retry the operation.

KNAN22248-I
Application of the IM configuration was successful.

The IM configuration (system hierarchy) was applied successfully.

S:

Stops applying the IM configuration.

KNAN22249-E
Application of the IM configuration failed. (Cause: "Detailed information")

Application of the IM configuration (system hierarchy) failed.

S:

Stops applying the IM configuration.

O:

If the following detailed information is displayed, take the indicated action.

A communication with JP1/Base failed.
Make sure that JP1/Base is running.

JP1/Base is busy.
Wait awhile, and then retry the operation.

A timeout occurred.
Check the following items:
Has an error occurred on a lower-level host?
If allocation of the definition takes too much time, the jbsrt_distrib command will time out. Revise the system configuration.

Failed to read the IM configuration definition file.
Check the following items:
Is the configuration definition file in the correct location?
Do you have write permission for the conf/route/ directory?

A communication error occurred with JP1/Base.
Check the following items:
Revise the common definition jp1hosts.
Make sure that the JP1/Base configuration ended normally.
If these actions do not resolve the problem, collect data, and then contact a system administrator.

The execution environment of JP1/Base is invalid.
Check the following items:
Is the JP1/Base conf directory defined in the common definition?
Did the JP1/Base configuration end normally?

An internal error occurred in JP1/Base during processing.
Check the following items:
Is there sufficient memory?
Has Configuration Management been started?
Was JP1/Base restarted after JP1/IM was installed?
Do you have write and read permission for the conf/route/ directory?

There is not the local host name in the IM configuration.
Define a local host in the configuration definition file.

KNAN22250-E
Synchronization of the IM configuration failed. (details = host-name)

Synchronization failed because an error occurred on the displayed host.

S:

Stops synchronization.

O:

Determine whether JP1/Base is running on the host with the error. If it is running, take the following actions:

Execute the jbsrt_get command.

Determine whether any of the following occurred:
Message KAVB3162-E was output.
The jbsrt_get command ended abnormally.
The local host name is displayed in Higher-level hosts or Lower-level hosts.
A host name other than a local host is displayed in Local hosts.
The host name is unintelligible.

If any of the above occurred, recover using the following methods:

Use the jbsrt_del command to delete the IM configuration (system hierarchy).

Re-apply the IM configuration (system hierarchy) from the manager host.

KNAN22251-E
Synchronization failed because the Base Manager is not defined.

Synchronization failed because the site manager is not defined.

S:

Stops synchronization.

O:

Define the site manager, and then retry the operation.

KNAN22252-I
Synchronization of the IM configuration ended successfully.

Synchronization ended successfully.

S:

Stops synchronization.

KNAN22253-E
Synchronization of the IM configuration failed because an error occurred during acquisition of the IM configuration. (error code = error-code)

An error occurred in the synchronized IM configuration (system hierarchy) during application to the IM Configuration Management database.

S:

Stops synchronization.

O:

If the following detailed information is displayed, take the indicated corrective action.

IM Configuration Management database access error.
Execute the jimdbstatus command, and then make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

The host does not exist.
Make sure that the host is registered in the host list of the IM Configuration Management window.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22254-E
Synchronization of the IM configuration failed. (Cause: error-code)

Synchronization failed.

S:

Stops synchronization.

O:

If the following detailed information is displayed, take the indicated corrective action.

Operations cannot be performed on the file.
Check the following items, and then retry the operation.
Is there sufficient memory?
Does the file exist?
Has the file access permission been set correctly?
Has the file been opened (locked) by another application?

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22255-E
IM Configuration synchronization is failed. (Cause: detailed-message)

Synchronization failed.

S:

Stops synchronization.

O:

If the following detailed information is displayed, take the indicated corrective action.

An internal error occurred in JP1/Base during processing.
Check the following items:
Is there sufficient memory?
Has Configuration Management been started?
Was JP1/Base restarted after JP1/IM was installed?
Do you have write and read permission for the conf/route/ directory?

A communication with JP1/Base failed.
Make sure that JP1/Base is running.

JP1/Base is busy.
Wait awhile, and then retry the operation.

The IM configuration does not exist.
Execute the jbsrt_get command, and then make sure that the IM configuration (system hierarchy) exists on the host.
If there is no IM configuration (system hierarchy), use the IM Configuration Management window to refresh it.

A timeout occurred.
Check the network configuration and status with the acquired host.
Also make sure that JP1/Base is running on the acquired host.

The execution environment of JP1/Base is invalid.
Check the following items:
Is the JP1/Base conf directory defined in the common definition?
Did the JP1/Base configuration end normally?

The JP1/Base configuration file could not be accessed.
Make sure that the access permission to the file has been set correctly. Also determine whether the file has been opened (locked) by another application.

A communication error occurred with JP1/Base.
Check the following items:
Revise the common definition jp1hosts value.
Make sure that the JP1/Base configuration ended normally.
If these actions do not resolve the problem, collect data, and then contact a system administrator.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22263-E
Acquisition of the IM configuration information failed because a database access error occurred. (Cause: error-code)

Acquisition of the IM configuration (system hierarchy) failed because an IM Configuration Management database access error occurred.

S:

Stops acquiring the IM configuration (system hierarchy).

O:

IM Configuration Management database access error.
Execute the jimdbstatus command, and then make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

The host does not exist.
Make sure that the host is registered in the host list of the IM Configuration Management window.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22400-I
The profile list was acquired successfully.

Acquisition of the manageable profile list ended successfully.

KNAN22401-E
Acquisition of the profile list failed because the host type is not selected.

Acquisition of the manageable profile list failed because the host type is not selected.

S:

Stops acquisition of the profile list.

O:

In the Edit Host Properties window, select the host type, and then retry the operation.

KNAN22402-E
Collection of the profile list failed because host information has not been acquired.

Acquisition of the manageable profile list failed because the host information is not valid.

S:

Stops acquisition of the profile list.

O:

Correct the host information acquisition in the Edit Host Properties window.

KNAN22403-E
Acquisition of the profile list failed. (Detail Information: detailed-information)

Acquisition of the manageable profile list failed because a connection could not be established with the host.

S:

Stops acquisition of the profile list.

O:

If the following detailed information is displayed, take the indicated corrective action.

There is no access permission.
Make sure that there is access permission to the host.

Another session has exclusive rights.
In the Login User List window, determine whether the user has acquired exclusive permission.
If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and then click the Release Exclusive Editing button to release exclusive permission.

A required service or process is not running.
Make sure that the relevant service or process is running. If it is not running, take the following actions, and then retry the operation.
Start the service or process.
In the Display/Edit Profiles window, click Operation, and then Rebuild Profile Tree.

A communication error occurred.
Check the network condition and status with the acquired target.
Also make sure that JP1/Base is running.
If JP1/Base is not running, take the following actions:
Start the service or process.
In the Display/Edit Profiles window, click Operation, and then Rebuild Profile Tree.

The processing is busy. Please try again.
Wait awhile, and then retry the operation.

A memory shortage occurred on the manager host.
Make sure that there is enough free memory on the manager host, and then retry the operation.

A memory shortage occurred on the agent host.
Make sure that there is enough free memory on the agent host, and then retry the operation.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22404-E
Acquisition of the profile list failed because the specified host is not registered.

Acquisition of the manageable profile list failed because the host is not registered in the host list.

S:

Stops acquisition of the profile list.

O:

Make sure that the host is correctly registered in the host list of the IM Configuration Management window.

KNAN22405-E
Acquisition of the profile list failed because a database access error occurred. (Cause: detailed-information)

Acquisition of the manageable profile list failed.

S:

Stops acquisition of the profile list.

O:

If the following detailed information is displayed, take the indicated corrective action.

The OS information does not exist.
In the IM Configuration Management window, make sure that the OS type is displayed in the host information.
If it is not displayed, click Operation, and then Collect Host Information to confirm that the OS type is displayed.

There are not enough resources.
Make sure that there is sufficient disk space, memory, or other OS resources.

IM Configuration Management database access error.
Execute the jimdbstatus command, and then make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

The profile has already been registered.

The profile name is already in use by a process or service. Use a different profile name.
It is possible that multiple log file traps have been started from the same configuration file.
Log in to the agent machine, and then start only one log file trap for each configuration file.
If you want to start multiple log file traps in the same definition, copy the contents to a file with a different name, and then retry the operation.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22406-E
Acquisition of the profile list failed. (Cause: error-code)

Acquisition of the manageable profile list failed because of an internal error.

S:

Stops acquisition of the profile list.

O:

If the following detailed information is displayed, take the indicated corrective action.

The product does not exist.
In the IM Configuration Management window, make sure that JP1/Base is displayed in the product information for the host.
If JP1/Base is not displayed, click Operation, and then Collect Host Information, and then retry the operation.

Operations cannot be performed on the file.
Check the following items, and then retry the operation.
Is there sufficient memory?
Does the file exist?
Has the file access permission been set correctly?
Has the file been opened (locked) by another application?

The data that was acquired while connected to the host is invalid.
Invalid data may have been received temporarily. Retry the operation.
Also check the network configuration and status with the acquired host.

A required service or process is not running.
Make sure that all of the JP1/Base processes started normally.

A request was executed in an invalid operating environment.
It is possible that the IM configuration (system hierarchy) has been deleted.
Click Operation, and then Verify IM Configuration to confirm that the current configuration is correct.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22407-E
Collection of the profile list failed because the specified host is not in the configuration.

Acquisition of the profile list failed because the host is not in the IM configuration (system hierarchy).

S:

Stops acquisition of the profile list.

O:

Place the host in the IM configuration (system hierarchy), and then retry the operation.

KNAN22408-E
Collection of the profile list failed because the product "product-name" does not exist on the specified host.

Acquisition of the profile list failed because the product could not be found on the host.

S:

Stops acquisition of the profile list.

O:

Make sure that JP1/Base is installed and running on the host, and then retry the operation.

KNAN22409-E
Collection of the profile list failed because the specified host is not a managed host.

Acquisition of the profile list cannot be performed because the specified host is not a managed host.

S:

Stops acquisition of the profile list.

O:

Add the specified host to the IM configuration (system hierarchy), and then retry the operation.

KNAN22410-E
Acquisition of the profile list failed because the profile "profile-type" is not usable.

Acquisition of the profile list failed because the profile is not usable.

S:

Stops acquisition of the profile list.

O:

Check the following items:

Is the network activated?

Is JP1/Base running?

KNAN22411-W
Collection of the profile list was interrupted because the maximum number profile-type that can be managed for product-name was exceeded.

Acquisition of the profile list was suspended because the maximum number of profiles that can be managed was exceeded.

S:

Stops acquisition of the profile list.

O:

Start a number of processes that does not exceed the maximum number of manageable configuration files that are defined on the server. Alternatively, change the maximum number of manageable configuration files, and then retry the operation.

KNAN22412-E
Profile management failed because the host name is defined with IP address. Please define real host name.

Profile management failed because the name of the specified host is defined by an IP address.

S:

Stops display of the Display/Edit Profiles window for the host.

Also skips batch collection and batch application processing for that host only (other hosts can undergo normal collection and application).

O:

Use the following procedure to change the IP address to the host name:

In the host list, select the host for which the host name is given as an IP address.

Edit the host attribute to change to the host name.

Open the Edit IM Configuration window and apply the settings.

KNAN22421-I
Operation definition information for profile-type was collected successfully.

Acquisition of operation definition information ended successfully.

S:

Acquires operation definition information.

KNAN22422-E
Collection of operation definition information for profile-type failed. (Detail Information: detailed-information)

Acquisition of operation definition information failed because a connection could not be established with the managed host.

S:

Stops acquisition of operation definition information.

O:

If the following detailed information is displayed, take the indicated corrective action.

There is no access permission.
Check the configuration of the agent's host access control definition file (jbsdfts_srv.conf).

Another session has exclusive rights.
In the Login User List window, determine whether the user has acquired exclusive permission.
If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and then click the Release Exclusive Editing button to release exclusive permission.

A required service or process is not running.
Make sure that the relevant service or process is running. If it is not running, take the following actions, and then retry the operation.
Start the service or process.
In the Display/Edit Profiles window, click Operation, and then Rebuild Profile Tree.

A communication error occurred.
Check the network condition and status with the acquired target.
Also make sure that JP1/Base is running.
If JP1/Base is not running, take the following actions:
Start the service or process.
In the Display/Edit Profiles window, click Operation, and then Rebuild Profile Tree.

The processing is busy. Please try again.
Wait awhile, and then retry the operation.

A memory shortage occurred on the manager host.
Make sure that there is enough free memory on the manager host, and then retry the operation.

A memory shortage occurred on the agent host.
Make sure that there is enough free memory on the agent host, and then retry the operation.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22423-E
Collection of operation definition information failed because the host is not registered.

Acquisition of operation definition information failed.

S:

Stops acquisition of operation definition information.

O:

In the host list of the IM Configuration Management window, make sure that the managed host is registered correctly.

KNAN22424-E
Collection of operation definition information for profile-type failed. (Cause: detailed-information)

Acquisition of operation definition information failed because of an error.

S:

Stops acquisition of operation definition information.

O:

If the following detailed information is displayed, take the indicated corrective action.

A required service or process is not running.
Make sure that the relevant service or process is running. If it is not running, take the following actions, and then retry the operation.
Start the service or process.
In the Display/Edit Profiles window, click Operation, and then Rebuild Profile Tree.

The product is not supported.
In the IM Configuration Management window, make sure that the version of JP1/Base displayed in the product information is 09-00 or later. If the JP1/Base version is 09-00 or later, click Edit IM Configuration, and then confirm again that the version of JP1/Base is 09-00 or later.

The data that was acquired while connected to the host is invalid.
Invalid data may have been received temporarily. Retry the operation.
Also check the network configuration and status with the acquired host.

A request was executed in an invalid operating environment.
It is possible that the IM configuration (system hierarchy) has been deleted.
Click Operation, and then Verify IM Configuration to confirm that the current configuration is correct.

No authentication servers have been set up.
Register an authentication server using the JP1/Base Environment Settings dialog box (in Windows) or the jbssetusrsrv command (in UNIX), and then re-execute the command.

User mapping has not been registered.
The user mapping information was not registered, or the mapping information file may be corrupted. Re-execute the user mapping configuration command.

The execution environment of JP1/Base is invalid.
Re-register an authentication server using the JP1/Base Environment Settings dialog box (in Windows) or the jbssetusrsrv command (in UNIX), and then re-execute the command.
If the error cannot be resolved, check the following items:
Is the JP1/Base conf directory defined in the common definition?
Did the JP1/Base configuration end normally?
In Windows: Is there a problem with access permission to the blockade file in the installation destination folder \jp1base\conf\user_acl\blockade?
In UNIX: Is there a problem with access permission to the blockade file in the /etc/opt/jp1base/conf/user_acl/blockade directory?

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22425-I
The contents of the configuration file "file-name" for profile-type was collected successfully.

Acquisition of the contents of the configuration file ended successfully.

S:

Acquires the contents of the configuration file.

KNAN22426-E
Collection of the contents of the configuration file "file-name" for profile-type failed. (Detail Information: detailed-information)

Acquisition of the contents of the configuration file failed because a connection could not be established with the managed host.

S:

Stops acquisition of the contents of the configuration file.

O:

If the following detailed information is displayed, take the indicated corrective action.

There is no access permission.
Check the configuration of the agent's host access control definition file (jbsdfts_srv.conf).

Another session has exclusive rights.
In the Login User List window, determine whether the user has acquired exclusive permission.
If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and then click the Release Exclusive Editing button to release exclusive permission.

The file does not exist.

The directory does not exist.
Make sure that the specified file or directory exists and that it is accessible.

A required service or process is not running.
Make sure that the relevant service or process is running. If it is not running, take the following actions, and then retry the operation.
Start the service or process.
In the Display/Edit Profiles window, click Operation, and then Rebuild Profile Tree.

A communication error occurred.
Check the network condition and status with the acquired target.
Also make sure that JP1/Base is running.
If JP1/Base is not running, take the following actions:
Start the service or process.
In the Display/Edit Profiles window, click Operation, and then Rebuild Profile Tree.

The processing is busy. Please try again.
Wait awhile, and then retry the operation.

A memory shortage occurred on the manager host.
Make sure that there is enough free memory on the manager host, and then retry the operation.

A memory shortage occurred on the agent host.
Make sure that there is enough free memory on the agent host, and then retry the operation.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22427-E
Collection of operation definition information failed because a database access error occurred. (Cause: error-code)

Acquisition of operation definition information failed because an IM Configuration Management database access error occurred.

S:

Stops acquisition of operation definition information.

O:

If the following detailed information is displayed, take the indicated corrective action.

IM Configuration Management database access error.
Execute the jimdbstatus command, and then make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

There are not enough resources.
Make sure that there is sufficient disk space, memory, or other OS resources.

The OS information does not exist.
In the IM Configuration Management window, make sure that the OS type is displayed in the host information.
If it is not displayed, click Operation, and then Collect Host Information to confirm that the OS type is displayed.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22428-E
Collection of the configuration file "file-name" for profile-type failed because an attempt to save the profile file failed.

Acquisition of the contents of the configuration file failed.

S:

Stops acquisition of the contents of the configuration file.

O:

Check the following items:

Do the file and directory exist, and are they accessible?

Has sufficient disk space been allocated?

KNAN22429-E
Collection of the configuration file "file-name" for profile-type failed. (Cause: error-code)

Acquisition of the contents of the configuration file failed because of an internal error.

S:

Stops acquisition of the contents of the configuration file.

O:

If the following detailed information is displayed, take the indicated corrective action.

A required service or process is not running.
Make sure that the relevant service or process is running. If it is not running, take the following actions, and then retry the operation.
Start the service or process.
In the Display/Edit Profiles window, click Operation, and then Rebuild Profile Tree.

There are not enough resources.
Make sure that there is sufficient disk space, memory, or other OS resources.

Operations cannot be performed on the file.
Check the following items, and then retry the operation.
Is there sufficient memory?
Does the file exist?
Has the file access permission been set correctly?
Has the file been opened (locked) by another application?

The data that was acquired while connected to the host is invalid.
Invalid data may have been received temporarily. Retry the operation.
Also check the network configuration and status with the acquired host.

A request was executed in an invalid operating environment.
It is possible that the IM configuration (system hierarchy) has been deleted.
Click Operation, and then Verify IM Configuration to confirm that the current configuration is correct.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22430-E
Batch collection of profiles failed because the user user-name:View-host-name is executing the batch operation "batch-collection/reflection".

Batch collection of profiles failed because another user is executing batch collection or application of profiles.

S:

Stops batch collection of profiles.

O:

Do one of the following:

In the Login User List window, determine whether the user has acquired exclusive permission.
If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and then click the Release Exclusive Editing button to release exclusive permission.

Retry the operation after the other user's batch collection or application finishes.

KNAN22432-E
Collection of product-name of the host "host-name" failed because the system is now performing batch collection of profiles. (Cause: error-code)

Profile collection on the host failed because the system is now performing batch collection of profiles.

S:

Stops batch collection of profiles.

O:

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

KNAN22433-E
Collection of the configuration file "file-name" for profile-type failed because another user is currently accessing the file.

Acquisition of the configuration file failed because another user is currently accessing the file.

S:

Stops acquisition of the contents of the configuration file.

O:

Wait awhile, and then retry the operation.

KNAN22434-E
Collection of operation definition information for profile-type failed because the host "host-name" is not the authentication server.

Acquisition of the JP1 user authorization level information or the operation definition information in the JP1 user registration failed because the host is not the authentication server.

S:

Stops acquisition of the operation definition information.

O:

Update the profile list.

KNAN22435-E
Batch collection of profiles failed because a database access error occurred. (Cause: error-code)

Batch collection of profiles failed because an IM Configuration Management database access error occurred.

S:

Stops batch collection of profiles.

O:

If the following detailed information is displayed, take the indicated corrective action.

The product does not exist.
In the IM Configuration Management window, make sure that JP1/Base is displayed in the product information for the host.
If JP1/Base is not displayed, click Operation, and then Collect Host Information, and then retry the operation.

The profile does not exist.
Check the profile collection status in the IM Configuration Management window, and then determine whether profile collection is completed or partially completed.

The OS information does not exist.
In the IM Configuration Management window, make sure that the OS type is displayed in the host information.
If it is not displayed, click Operation, and then Collect Host Information to confirm that the OS type is displayed.

There are not enough resources.
Make sure that there is sufficient disk space, memory, or other OS resources.

IM Configuration Management database access error.
Execute the jimdbstatus command, and then make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

KNAN22437-E
Batch collection of profiles failed because the host does not exist in the database.

Processing failed because the host could not be found in the IM Configuration Management database.

S:

Stops batch collection of profiles.

O:

In the host list in the IM Configuration Management window, make sure that the managed host is registered correctly.

KNAN22438-E
Collection of the configuration file failed because the host is not registered.

Acquisition of the configuration file failed because the host is not registered.

S:

Stops acquisition of the contents of the configuration file.

O:

In the host list in the IM Configuration Management window, make sure that the managed host is registered correctly.

KNAN22439-E
Collection of the configuration file failed because a database access error occurred. (Cause: error-code)

Acquisition of the configuration file failed because of an error in the IM Configuration Management database access.

S:

Stops acquisition of the contents of the configuration file.

O:

If the following detailed information is displayed, take the indicated corrective action.

The product does not exist.
In the IM Configuration Management window, make sure that JP1/Base is displayed in the product information for the host.
If JP1/Base is not displayed, click Operation, and then Collect Host Information, and then retry the operation.

IM Configuration Management database access error.
Execute the jimdbstatus command, and then make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

The profile does not exist.
Check the profile collection status in the IM Configuration Management window, and then determine whether profile collection is completed or partially completed.

There are not enough resources.
Make sure that there is sufficient disk space, memory, or other OS resources.

The OS information does not exist.
In the IM Configuration Management window, make sure that the OS type is displayed in the host information.
If it is not displayed, click Operation, and then Collect Host Information to confirm that the OS type is displayed.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22440-E
Collection of the configuration file "file-name" for profile-name failed because the specified profile type is not supported for logical hosts.

Acquisition of the configuration file failed because the specified profile type is not supported for logical hosts.

S:

Stops acquisition of profiles.

O:

The environment is invalid.

Re-install JP1/IM - Manager.

KNAN22441-E
Profile information for the host "host-name" cannot be collected using batch acquisition because the host information is locked by the user "user-name:View-host-name ".

Batch collection processing failed because another user has acquired exclusive permission to the host information.

S:

Stops batch collection of profiles.

O:

Do one of the following:

In the Login User List window, determine whether the user has acquired exclusive permission.
If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and then click the Release Exclusive Editing button to release exclusive permission.

Retry the operation after exclusive access is released.

KNAN22442-E
Profile information for the host "host-name" cannot be collected using batch acquisition because the host information is being updated.

Batch collection processing failed because the host information is being updated.

S:

Stops batch collection of profiles.

O:

Collect the most recent information, and then retry the operation.

KNAN22443-E
product-name of "host-name" cannot be collected using batch collection because the profile information is locked by the user "user-name:View-host-name".

Batch collection processing failed because another user has acquired exclusive permission to the profile information.

S:

Stops batch collection of profiles.

O:

Do one of the following:

In the Login User List window, determine whether the user has acquired exclusive permission.
If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and then click the Release Exclusive Editing button to release exclusive permission.

Retry the operation after exclusive access is released.

KNAN22444-E
product-name of "host-name" cannot be collected using batch collection because profile information is being updated.

Batch collection processing failed because the profile information is being updated.

S:

Stops batch collection of profiles.

O:

Acquire the most recent information, and then retry the operation.

KNAN22445-E
Batch collection cannot be performed because the IM configuration tree is being updated.

Batch collection cannot be performed because the IM configuration information (system hierarchy information) is being updated.

S:

Stops batch collection of profiles.

O:

Acquire the most recent information, and then retry the operation.

KNAN22446-E
Batch collection cannot be performed because the IM configuration is being locked by the user "user-name:View-host-name".

Batch collection cannot be performed because update permission is being acquired for the IM configuration information (system hierarchy information).

S:

Stops batch collection of profiles.

O:

Do one of the following:

In the Login User List window, determine whether the user has acquired exclusive permission.
If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and then click the Release Exclusive Editing button to release exclusive permission.

Retry the operation after update permission is released.

KNAN22447-E
Batch collection cannot be performed because IM configuration verification is being performed by the user user-name:View-host-name.

Batch collection cannot be performed because the user is performing verification of the IM configuration information (system hierarchy information).

S:

Stops batch collection of profiles.

O:

Do one of the following:

In the Login User List window, determine whether the user has acquired exclusive permission.
If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and then click the Release Exclusive Editing button to release exclusive permission.

Wait awhile, and then retry the operation.

KNAN22448-E
Batch collection terminated abnormally.

Batch collection ended abnormally.

S:

Stops batch collection of profiles.

O:

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

KNAN22449-I
Setup file "file-name" for profile-type does not exist in Agent host.

The configuration file could not be found in the agent host.

S:

Stops acquisition of the contents of the configuration file.

O:

Make sure that the configuration file exists in the agent host, and then retry the operation.

KNAN22455-I
Changes to the configuration file "file-name" of profile-type were successfully saved on the server.

Changes to the profile were successfully saved on the server.

S:

Saves the configuration file on the server.

KNAN22456-E
Application of the configuration file failed because a database access error occurred. (Cause: error-code)

Changes could not be made to the profile on the server.

S:

Stops saving the configuration file.

O:

If the following detailed information is displayed, take the indicated corrective action.

IM Configuration Management database access error.
Execute the jimdbstatus command, and then make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

There are not enough resources.
Make sure that there is sufficient disk space, memory, or other OS resources.

OS information does not exist.
In the IM Configuration Management window, make sure that the OS type is displayed in the host information.
If it is not displayed, click Operation, and then Collect Host Information to confirm that the OS type is displayed.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22457-E
The configuration file "file-name" for profile-type could not be saved. (Cause: error-code)

Changes could not be made to the profile on the server because of an internal error.

S:

Stops saving changes to the profile on the server.

O:

If the following detailed information is displayed, take the indicated corrective action.

Operations cannot be performed on the file.
Check the following items, and then retry the operation.
Is there sufficient memory?
Does the file exist?
Has the file access permission been set correctly?
Has the file been opened (locked) by another application?

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22458-I
Exclusive edit rights for product-name of the host "host-name" were successfully acquired.

Exclusive edit permission was successfully acquired.

S:

Acquires exclusive edit permission.

KNAN22459-E
An attempt to save the configuration file "file-name" for profile-type failed because another user is currently accessing the file.

An attempt to acquire exclusive access permission failed because another user has acquired exclusive access permission for the host or product.

S:

Stops saving the configuration file.

O:

Wait awhile, and then retry the operation.

KNAN22460-I
Editing changes were successfully applied to the configuration file "file-name" for profile-type.

Changes made to the profile on the server were applied to the agent host profile.

S:

Applies changes to the configuration file.

KNAN22461-E
Batch application of profiles failed because the user user-name:View-host-name is executing a batch "collection/reflection" operation.

Batch application of profiles failed because another user is performing batch profile collection or application.

S:

Stops batch application of profiles.

O:

Take one of the following corrective actions:

In the Login User List window, determine whether a user has acquired exclusive access permission. If it is not problematic to do so, select the check box next to the user that has acquired exclusive access permission, and click the Release Exclusive Editing button to release exclusive access permission.

Wait until batch collection or application by the other user has finished, and then retry the operation.

KNAN22463-E
During batch application of profiles, an attempt to apply the changes of product-name of the host "host-name" failed, because the profile list for the product does not exist in the database.

An attempt to apply the profile of a host failed during batch application of profiles.

S:

Stops batch application of profiles.

O:

Check the following items, and then retry the operation.

Is profile collection complete?

Can the contents of the profile be referenced from the Display/Edit Profiles window?

KNAN22466-E
Application of changes failed because an error occurred when moving the configuration file "file-name" for profile-type. (Detail Information: detailed-information)

An attempt to apply changes failed because a connection could not be established with the agent host.

S:

Stops application of changes to the agent host.

O:

If the following detailed information is displayed, take the indicated corrective action.

There is no access permission.
Check the configuration of the agent host's access control definition file (jbsdfts_srv.conf).

Another session has exclusive rights.
In the Login User List window, determine whether a user has acquired exclusive access permission. If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and click the Release Exclusive Editing button to release exclusive permission.

The directory does not exist.
Make sure that the specified directory exists and is accessible.

A required service or process is not running.
Make sure that the relevant service or process is running. If it is not running, take the following corrective actions, and then retry the operation.
Start the service or process.
In the Display/Edit Profiles window, click Rebuild Profile Tree.

A communication error occurred.
Check the condition and status of the network with the acquired managed host.
Also make sure that JP1/Base is running.
If JP1/Base is not running, take the following corrective actions:
Start the service or process.
In the Display/Edit Profiles window, click Rebuild Profile Tree.

The processing is busy. Please try again.
Wait awhile, and then retry the operation.

A service or process failed to reload.
Make sure that the relevant service or process is running and that the configuration file is correctly formatted.
If it is not running, take the following corrective actions, and then retry the operation.
Start the service or process.
In the Display/Edit Profiles window, click Rebuild Profile Tree.

A memory shortage occurred on the manager host.
Make sure that there is enough free memory on the manager host, and then retry the operation.

A memory shortage occurred on the agent host.
Make sure that there is enough free memory on the agent host, and then retry the operation.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22467-E
Application of the configuration file failed because the host is not registered.

Application of changes to the agent host failed.

S:

Stops application of changes to the agent host.

O:

In the IM Configuration Management window, open the host list and make sure that the managed host is registered correctly.

KNAN22468-E
Application of changes to the configuration file "file-name" for profile-type failed. (Cause: error-code)

Application of changes to the agent host failed due to an internal error.

S:

Stops application of changes to the agent host.

O:

If the following detailed information is displayed, take the indicated corrective action.

Operations cannot be performed on the file.
Check the following items, and then retry the operation.
Is there sufficient memory?
Does the file exist?
Is the file access permission configured correctly?
Has the file been opened (locked) by another application?

The file name is too long.
Specify the file name using a maximum of 259 characters in the absolute path.

A required service or process is not running.
Make sure that the relevant service or process is running. If it is not running, take the following corrective actions, and then retry the operation.
Start the service or process.
In the Display/Edit Profiles window, click Rebuild Profile Tree.

The configuration file for rollback failed to be created.
Make sure that there is sufficient disk space, memory, or other OS resources.

A request was executed in an invalid operating environment.
It is possible that the IM configuration (system hierarchy) was deleted.
Click Verify IM Configuration, and make sure that the current configuration is correct.

The data that was acquired while connected to the host is invalid.
Invalid data may have been received temporarily. Retry the operation.
Also check the network configuration and status of the target host.

An error occurred during execution of the re-load command: The configuration file might contain a mistake.
Revise the contents of the configuration file definition.
Make sure that the relevant service or process is running. If it is not running, take the following corrective actions, and then retry the operation.
Start the service or process.
In the Display/Edit Profiles window, click Rebuild Profile Tree.

There might be a mistake in a configuration file definition, or JP1/Base might not be running properly.
Make sure that the relevant service or process is running and that the configuration file is formatted correctly.
If it is not running, take the following corrective actions, and then retry the operation.
Start the service or process.
In the Display/Edit Profiles window, click Rebuild Profile Tree.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22469-W
The configuration file "file-name" for profile-type in the agent host might have been changed.

The configuration file in the agent host may have been overwritten.

S:

Continues processing.

O:

Check the contents of the configuration file in the agent host.

Note:

When acquiring information from the agent host, changes are overwritten.

KNAN22471-E
Batch application of a configuration failed because a database access error occurred. (Cause: error-code)

Batch application of a configuration failed because an IM Configuration Management database access error occurred.

S:

Stops application of the configuration.

O:

If the following detailed information is displayed, take the indicated corrective action.

IM Configuration Management database access error.
Execute the jimdbstatus command, and determine whether the IM database service is running. If the IM database service is not running, start the IM database service.

There are not enough resources.
Make sure that there is sufficient disk space, memory, or other OS resources.

The product does not exist.
In the IM Configuration Management window, make sure that JP1/Base is displayed in the product information for the host.
If no host information is displayed in the window, click Collect Host Information, and then retry the operation.

The OS information does not exist.
In the IM Configuration Management window, make sure that the OS type is displayed in the host information.
If it is not displayed, click Collect Host Information, and confirm that the OS type is displayed.

The profile does not exist.
Check the profile collection status in the IM Configuration Management window, and then determine whether profile collection is complete or partially complete.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22472-E
Batch application for a host failed because the host is not registered.

Batch collection of a configuration file failed because the host is not registered.

S:

Stops application of the configuration file.

O:

Acquire the most recent information, and then retry the operation.

KNAN22473-I
Exclusive edit rights for the product-name of the host "host-name" was released successfully.

Reports that exclusive permission was released successfully.

S:

Terminates processing.

KNAN22474-E
Batch application was not performed because product-name does not exist on the host "host-name".

Application was not performed because the relevant product does not exist in the host.

S:

Stops application of the configuration file.

O:

Make sure that JP1/Base is installed on the host, and then retry the operation.

KNAN22475-E
Application of the configuration file "file-name" for profile-type failed because another user is currently accessing the file.

Application of the configuration file failed because another user is currently accessing the file.

S:

Stops application of the configuration file.

O:

Wait awhile, and then retry the operation.

KNAN22476-E
During batch application, application of the host "host-name" failed. (Cause: error-code)

Application of the profile information failed during batch application processing.

S:

Stops application of the configuration file.

O:

Check the contents of the detailed information. Take the indicated action, and then retry the operation.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KNAN22477-E
An attempt to save the configuration file to the server failed because a database access error occurred. (Cause: error-code)

An attempt to save the configuration file on the server failed because an IM Configuration Management database access error occurred.

S:

Stops saving the configuration file.

O:

If the following detailed information is displayed, take the indicated corrective action.

IM Configuration Management database access error.
Execute the jimdbstatus command, and make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

There are not enough resources.
Make sure that there is sufficient disk space, memory, or other OS resources.

The OS information does not exist.
In the IM Configuration Management window, make sure that the OS type is displayed in the host information.
If it is not displayed, click Collect Host Information, and confirm that the OS type is displayed.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22478-E
An attempt to save the configuration file to the server failed because the host is not registered.

An attempt to save the configuration file on the server failed because the host is not registered.

S:

Stops saving the configuration file.

O:

In the IM Configuration Management window, open the host list and make sure that the managed host is registered correctly.

KNAN22479-E
Application of the configuration file "file-name" for profile-name failed because application of the specified profile type is not supported for logical hosts.

Application of the configuration file failed because application of the specified configuration file is not supported for logical hosts.

S:

Stops application of the configuration file.

O:

The environment is invalid.

Re-install JP1/IM - Manager.

KNAN22480-E
Batch application of the host "host-name" was not performed because the host is locked by the user user-name:View-host-name.

Batch application processing of the profile information cannot be performed because another user has acquired exclusive access permission for the host information.

S:

Stops application of the configuration file.

O:

Take one of the following corrective actions:

In the Login User List window, determine whether a user has acquired exclusive access permission. If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and click the Release Exclusive Editing button to release exclusive permission.

After exclusive access permission is released, retry the operation.

KNAN22481-E
Batch application of the host "host-name" was not performed because another user is currently updating the host information.

Batch application processing of the profile information cannot be performed because the host information is being updated.

S:

Stops application of the configuration file.

O:

Acquire the most recent information, and then retry the operation.

KNAN22482-E
Batch application of product-name of the host "host-name" was not performed because the profile information is locked by the user user-name:View-host-name.

Batch application processing of the profile information cannot be performed because a user has acquired exclusive access permission for the host information.

S:

Stops application of the configuration file.

O:

Take one of the following corrective actions:

In the Login User List window, determine whether a user has acquired exclusive access permission.
If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and click the Release Exclusive Editing button to release exclusive permission.

After exclusive access permission is released, retry the operation.

KNAN22483-E
Batch application of product-name of the host "host-name" was not performed because the profile information is being updated.

Batch application processing of the profile information cannot be performed because the profile information is being updated.

S:

Stops application of the configuration file.

O:

Acquire the most recent information, and then retry the operation.

KNAN22484-E
Batch application processing was not performed because another user is currently updating the IM configuration tree.

Batch application processing cannot be performed because the IM configuration (system hierarchy) is being updated.

S:

Stops application of the configuration file.

O:

Acquire the most recent information, and then retry the operation.

KNAN22485-E
Batch application processing was not performed because the IM configuration is locked by the user user-name:View-host-name.

Batch application processing cannot be performed because a user has acquired update permission for the IM configuration (system hierarchy).

S:

Stops application of the configuration file.

O:

Take one of the following corrective actions:

In the Login User List window, determine whether a user has acquired exclusive access permission.
If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and click the Release Exclusive Editing button to release exclusive permission.

After exclusive access permission is released, retry the operation.

KNAN22486-E
Batch application processing was not performed because IM configuration verification was being performed by the user user-name:View-host-name.

Batch application processing cannot be performed because a user is performing verification of the IM configuration (system hierarchy).

S:

Stops application of the configuration file.

O:

Take one of the following corrective actions:

In the Login User List window, determine whether a user has acquired exclusive access permission.
If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and click the Release Exclusive Editing button to release exclusive permission.

Wait awhile, and then retry the operation.

KNAN22487-E
Batch application processing of host-name was not performed because host information has not been collected.

Batch application processing cannot be performed on the host because the host information has not been collected.

S:

Stops application of the configuration file.

O:

Wait until the host information has been collected, and then retry the operation.

KNAN22488-E
Application of the configuration file "file-name" for profile-type failed because the configuration file does not exist in the server.

Application of the configuration file failed because the configuration file has not been saved on the server.

S:

Stops application of the configuration file.

O:

Check the following items, and then retry the operation.

Has the profile been acquired?

Can the contents of the profile be referenced from the Display/Edit Profiles window?

KNAN22491-E
Batch application terminated abnormally.

Batch application ended abnormally.

S:

Stops application of the configuration file.

O:

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

KNAN22493-E
Application of log file trap contents failed because an error occurred when the reload command was executed. (Error code: error code. For details, see the description of the jevlogreload command in the JP1/Base manual.)

Application of the log file trap failed because an error occurred during execution of the reload/start command.

S:

Stops application of the configuration file.

O:

Refer to the JP1/Base manuals (jevlogstart and jevlogreload commands), and take the corrective action indicated by the command execution time error.

KNAN22494-E
Acquisition of exclusive edit rights failed. (Cause: Host is not registered.)

Acquisition of exclusive editing permission failed because the specified host could not be found in the host list.

S:

Stops acquisition of exclusive editing permission.

O:

Acquire the most recent information, and make sure that the host exists.

KNAN22495-E
Rollback of configuration file "file-name" for profile-type failed.
Note: The configuration file "file-name" stored the host "host-name" is changed to the contents of after-editing.

Rollback of the configuration file failed.

S:

Stops rollback processing.

O:

Make sure that the configuration information is correct, edit the configuration file, and then retry the operation.

KNAN22496-W
Rollback of configuration file "file-name" for profile-type is not executed because the rollback is not supported for JP1/Base's version of host "host-name".
Note: The configuration file "file-name" stored the host "host-name" is changed to the contents of after-editing.

Rollback of the configuration file failed because rollback is not supported for the version of JP1/Base on the host.

S:

Stops rollback processing.

O:

Edit the configuration file, and then retry the operation.

KNAN22497-I
The profile type configuration file "file name" could not be applied because the configuration file does not exist on the server.

Application of profile-type failed because the configuration file does not exist on the server.

S:

Applies profiles other than profile-type.

KNAN22498-E
Application of the configuration file file-name for profile-type was not performed because the configuration file contains control characters.

Application failed because the configuration file includes control characters.

S:

Applies profiles other than profile-type and terminates processing,

KNAN22499-E
Error occured during reload command execution for profile-type with the old configuration file.

Reloading of the rolled-back configuration file failed.

S:

Stops application.

O:

Make sure that the configuration information is correct, edit the configuration file, and then retry the operation.

KNAN22600-I
Collection of service information from the host "host-name" ended successfully.

Collection of service activity information ended.

S:

Stops collection of service activity information.

KNAN22601-E
Collection of service information failed because the JP1/Base service of host "host-name" is not running.

Collection of service activity information failed because JP1/Base is not running.

S:

Stops collection of service activity information.

O:

Make sure that JP1/Base is running, and then retry the operation.

KNAN22602-E
Collection of service information failed because the connection with the host "host-name" was lost.

A connection cannot be established with the host.

S:

Stops collection of service activity information.

O:

Make sure that JP1/Base is running, and then retry the operation.

KNAN22603-E
Collection of service information failed because the connection with the host "host-name" timed out.

The connection timed out.

S:

Stops collection of service activity information.

O:

Check the status of JP1/Base, and then retry the operation.

KNAN22604-W
The JP1/Base version on the host "host-name" is not supported.

The JP1/Base version on the host is not supported.

S:

Stops collection of service activity information.

O:

Make sure that the JP1/Base version is 09-00 or later.

KNAN22605-E
Collection of service information failed because the version of JP1/Base of the host "host-name" and the database are not the same.

The version of JP1/Base on the host does not match the IM Configuration Management database.

S:

Stops collection of service activity information.

O:

Collect the host information again, and then retry the operation.

KNAN22606-E
Service operation information collection for the host "host-name" failed because a database access error occurred. (Cause: detailed-information)

Collection of service activity information on the host failed because an IM Configuration Management database access error occurred.

S:

Stops collection of service activity information.

O:

If the following detailed information is displayed, take the indicated corrective action.

The host does not exist.
In the IM Configuration Management window, open the host list and make sure that the managed host has been registered.

IM Configuration Management database access error.
Execute the jimdbstatus command, and make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

KNAN22607-E
Collection of service information failed. (Cause: error-code)

Collection of service activity information failed.

S:

Stops collection of service activity information.

O:

If the following detailed information is displayed, take the indicated corrective action.

There are not enough resources.
Make sure that there is sufficient disk space, memory, or other OS resources.

The connection destination host is busy.
Wait awhile, and then retry the operation.

Failed to send the data to the connection destination host.

Failed to receive the data from the connection destination host.
Check the OS resources and memory status, and then check the network configuration and status with the connection destination.
Also make sure that the IM Configuration Management Service instance of the connection destination is running.

The data that was acquired while connected to the host is invalid.
Invalid data may have been received temporarily. Retry the operation.
Also check the network configuration and status of the acquired host.

A request was executed in an invalid operating environment.
It is possible that the IM configuration (system hierarchy) was deleted.
Click Verify IM Configuration, and make sure that the current configuration is correct.

A common definition could not be acquired.
The JP1/Base common definition information is not configured. Make sure that it is configured correctly.
If operating in a cluster environment, make sure that the logical host name set in the JP1_HOSTNAME environment variable is correct.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22608-E
The service operation information collection for host-name host is failed. (Cause: The execution of collection command command-name is failed.)

Collection of service activity information failed because command execution failed.

S:

Stops collection of service activity information.

O:

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

KNAN22800-E
The logical host "logical-host-name" does not exist.

The specified logical host does not exist.

S:

Stops processing the command.

O:

Check the logical host name, and then retry the operation.

KNAN22801-E
The user does not have execution permission.

The user executing the command does not have execution permission.

S:

Stops processing the command.

O:

Log in as a user with the following execution permission, and then retry the operation.

In Windows: Administrator permissions

In UNIX: superuser permission

KNAN22802-E
Command execution will now stop because memory is insufficient.

Command execution is suspended because memory is insufficient.

S:

Stops processing the command.

O:

Allocate sufficient memory, and then re-execute the command.

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

Free disk space is insufficient. Processing is suspended.

S:

Stops processing the command.

O:

Allocate sufficient disk space, and then re-execute the command.

KNAN22804-E
Command execution failed because a database access error occurred. (Cause: error-code)

An error occurred in the IM Configuration Management database during command execution.

S:

Stops processing the command.

O:

If the following detailed information is displayed, take the indicated corrective action.

The host has already been registered.
Enter a different host name, and then retry the operation.

The number of registered hosts has reached the maximum value.
Reduce the number of registered hosts.

IM Configuration Management database access error.
Execute the jimdbstatus command, and make sure that the IM database service is running. If the IM database service is not running, start the IM database service.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.

KNAN22805-E
A connection could not be established with the server.

The command could not establish a connection with the server.

S:

Stops processing the command.

O:

Execute the jco_spmd_status command, and make sure that jcfmain is running. After confirming that jcfmain is running, retry the operation.

KNAN22806-E
The connection with the server was lost.

The command's connection with the server was lost.

S:

Stops processing the command.

O:

Make sure that IM Configuration Management Service is running, and then retry the operation.

KNAN22807-E
The connection with the server timed out.

The command's connection has timed out.

S:

Stops processing the command.

O:

Make sure that IM Configuration Management Service is running, and then retry the operation.

KNAN22808-E
The command was interrupted.

When you press the Ctrl + C keys, a message is displayed notifying you that the command was suspended.

S:

Suspends command processing.

KNAN22809-E
The command option "option" is invalid.

The option is invalid.

S:

Stops processing the command.

O:

Check the option, and then retry the operation.

KNAN22810-E
The command option "option" is specified more than once.

The option is specified more than once.

S:

Stops processing the command.

O:

Check the option, and then retry the operation.

KNAN22811-E
The option "option-value" is mandatory.

A required option is not specified.

S:

Stops processing the command.

O:

Check the option, and then retry the operation.

KNAN22812-E
The maximum length of the value for the option "option-value" is maximum-length.

The option is too long.

S:

Stops processing the command.

O:

Check the option, and then retry the operation.

KNAN22814-E
The value of the option "option-value" is invalid.

The value of the option is invalid.

S:

Stops processing the command.

O:

Check the option, and then retry the operation.

KNAN22816-E
No value is specified for the option "option-value".

No value is specified for a required option.

S:

Stops processing the command.

O:

Make sure that a value is specified for the option, and then retry the operation.

KNAN22817-E
Please execute the command from an administrator console.

The command must be executed from the administrator console.

S:

Stops processing the command.

O:

Execute the command from the administrator console.

KNAN22819-E
The following command options are mutually exclusive: option-value.

The specified command options cannot be specified together.

S:

Stops processing the command.

O:

Check the options, and then retry the operation.

KNAN22820-I
The command command-name will now start.

Reports that the command will now start.

S:

Starts the command.

KNAN22821-I
A connection with the JP1/IM-CF server was established.

The command successfully established a connection with the server.

S:

Continues executing the command.

KNAN22822-I
The command command-name ended successfully.

The command ended normally.

S:

Terminates command processing.

KNAN22823-E
A command failed because the file format is invalid. (file name = file-name, line number = line-number, details = detailed-information)

The command cannot be executed because the file definition is invalid.

S:

Stops processing the command.

O:

If the following detailed information is displayed, take the indicated corrective action.

There are control characters in "file-name".
Delete the control characters in the file displayed in the message.

The host name "host-name" has not been specified by using only alphanumeric characters.
Specify the host name using alphanumeric characters.

"host-name" exceeds the maximum length "maximum-length".
Specify a host name whose length does not exceed the maximum length specified in the message.

There is not a VMM host, an active host, or a standby host "host-name" in the file.
Make sure that the VMM host, primary host, or standby host displayed in the message is listed in the file.
If it is not listed in the file, add it.

Do not specify an active host name, a standby host name, or a VMM host name for the physical host "host-name".
Specify a host other than a primary host, standby host, or VMM host as the physical host.

Do not specify an active host name, a standby host name, or a VMM host name for an unknown host "host-name".
Specify a host other than a primary host, standby host, or VMM host as an unidentified host.

Do not specify an active host name, a standby host name, or a VMM host name for the virtual host "host-name".
Specify a host other than a primary host, standby host, or VMM host as a virtual host.

The active host "host-name" is not a physical or virtual host.
Specify a physical host or a virtual host as the primary host or standby host.

Specify a VMM host name for the virtual host "host-name".
Specify a VMM host name as a virtual host.

Specify a physical host for the VMM host "host-name".
Specify a physical host as a VMM host.

Do not specify a VMM host name for the logical host "host-name".
Specify a host other than a VMM host as a physical host.

The active host name and the standby host name are the same.
The same host cannot be specified as both the primary host and the standby host. Specify a different host for each.

The header information was not found./The header information is invalid./There is an error in the CSV format.
Make sure that the file header information or the CSV format is correct.

The product name is invalid.
Make sure that the product name is formatted correctly.

The number of "value" has exceeded the maximum./The column name "column-name" exceeds the maximum length./The length of "value" exceeds the maximum limit.
Specify the number of values and their lengths so that they do not exceed the maximum values listed in the manual.

There is an invalid character in the value "value".
Make sure that the value displayed in the message does not contain the following characters:
/, :, ?, \", <, >, |, \\, *

The number of hosts has reached the maximum value (max-number-hosts).
Specify a number of hosts that does not exceed the maximum value displayed in the message.

There is a blank line.
Make sure that there are no empty lines in the file.

The host name "host-name" has been duplicated.
Do not specify a host more than once.

The Host type value is invalid.
Specify physical, logical, virtual, or unknown for the host type.

KNAN22824-E
A command failed because the file format is invalid. (file name = file-name, details = detailed-information)

The command cannot be executed because the file definition is invalid.

S:

Stops processing the command.

O:

If the following detailed information is displayed, take the indicated corrective action.

The format of the header information is invalid./There is an error in the CSV format.
Make sure that the file header information or the CSV format is correct.

The physical host for the host "host-name" is not present.
There is no definition for the physical host specified in the VMM host, primary host, or standby host. Specify the definition for the host displayed in the message.

There are control characters in "file-name".
Make sure that the file does not contain the following characters:
/, :, ?, \", <, >, |, \\, *

The host name "host-name" has not been specified by using only alphanumeric characters.
Specify the host name using alphanumeric characters.

"host-name" exceeds the maximum length "maximum-length".
Specify a host name whose length does not exceed the maximum length specified in the message.

The number of hosts has reached the maximum value (max-number-hosts)./The number of hosts, which includes the local host, exceeds the maximum value.
Specify a number of hosts, including the local host, that does not exceed the maximum value.

The protocol_ver tag is invalid.
The format of the import file below the directory specified with the -o option is invalid. Check the protocol_ver of the import information.

The topmost host "host-name" is different.
Specify the local host as the highest-level host.

The Base Manager configuration for the host "host-name" is invalid.
Make sure that the IM configuration (system hierarchy) of the host specified as the site manager is correctly defined.

The host "host-name" has been specified multiple times.
Specify a host only once.

The host "host-name" is looping.
The IM configuration (system hierarchy) is looped. Revise the definition of the IM configuration (system hierarchy) so that it is not looped.

The file content is invalid.
The contents of the system_tree_information are invalid. Revise the contents of the system_tree_information.

The manager host host-name does not exist.
The host specified in the manager host does not exist. Make sure that the host information has been defined.

KNAN22825-E
The import operation failed because the profile information of the host "host-name" is locked by user-name:View-host-name.

The import operation failed because the profile is locked by another user.

S:

Stops processing the command.

O:

After exclusive access permission is released, retry the operation.

KNAN22826-E
The import operation failed because the IM configuration information is locked by user-name:View-host-name.

The import operation failed because the IM configuration (system configuration) is locked by another user.

S:

Stops processing the command.

O:

After exclusive access permission is released, retry the operation.

KNAN22827-E
The import operation failed because the host "host-name" is locked by user-name:View-host-name.

The import operation failed because the profile is locked by another user.

S:

Stops the command.

O:

After exclusive access permission is released, retry the operation.

KNAN22828-E
The import operation failed because the version of the file is not supported. (file = file-name)

The import operation failed because the version of the file is not supported.

S:

Stops processing the command.

O:

Specify an export file whose version is supported by the manager, and then retry the operation.

KNAN22829-W
The host will be automatically registered because the specified host name does not exist in host list file. (host = host-name)

The host will be registered automatically because the host name is not defined in the host list.

S:

Continues executing the command.

KNAN22830-E
The specified path does not exist. (path = path)

The command cannot be executed because the specified path does not exist.

S:

Stops processing the command.

O:

Make sure that the specified file exists, and then retry the operation.

KNAN22831-E
The file cannot be accessed. (file = path)

The command cannot be executed because the specified file cannot be accessed.

S:

Stops processing the command.

O:

Make sure that the specified directory path and file exist, and then retry the operation.

KNAN22832-E
The file reading operation failed. (Cause: detailed-information)

Reading of the specified file failed.

S:

Stops processing the command.

O:

Check the following items, and then retry the operation.

Is there sufficient memory?

Does the file exist?

Is the file access permission configured correctly?

Has the file been opened (locked) by another application?

KNAN22833-W
An attempt to acquire a message from the resource file failed.

The relevant message could not be found in the message file.

S:

Continues executing the command.

O:

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

KNAN22834-E
The command "command-name" cannot be executed because the command "command-name" is executing.

The specified command cannot be executed because another command is now executing.

S:

Stops processing the command.

O:

Wait until execution of the other command is complete, and then retry the operation.

KNAN22835-E
A file with the same name already exists.

A file with the same name as the specified file already exists.

S:

Stops processing the command.

O:

Check the specified file, and then retry the operation.

KNAN22836-E
Command operation failed because an I/O error occurred. (details = detailed-information)

An I/O error occurred during output.

S:

Stops processing the command.

O:

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

KNAN22837-W
The profile information of the host "host-name" is locked by user-name:View-host-name.

The profile is locked by another user.

S:

Continues executing the command.

O:

After exclusive access permission is released, retry the operation.

KNAN22838-W
The IM configuration information is locked by user-name:View-host-name.

The IM configuration (system hierarchy) is locked by another user.

S:

Continues executing the command.

O:

After exclusive access permission is released, retry the operation.

KNAN22839-W
The host "host-name" is locked by user-name:View-host-name.

The host is locked by another user.

S:

Continues executing the command.

O:

After exclusive access permission is released, retry the operation.

KNAN22840-E
The number of command arguments is invalid.

The number of command arguments is invalid.

S:

Stops processing the command.

O:

Check the command arguments, and then retry the operation.

KNAN22841-I
The profile information does not exists.The import operation is carried out without the profile information.

The profile could not be found at the specified location. Information other than the profile is imported.

S:

Continues executing the command.

KNAN22842-E
Creation of a CSV file failed. (file name = file-name, details = detailed-information, error code = error-code)

Creation of a CSV file failed.

S:

Stops the command.

O:

If the following detailed information is displayed, take the indicated corrective action.

The file or directory path does not exist.
Make sure that the specified path is correct and that the file exists.

There is insufficient disk space.
Make sure that there is sufficient disk space, memory, or other OS resources.

There is no access permission.
Check the access permission for the specified path.

Too many files are open.
The file could not be opened due to insufficient resources.
Close any unnecessary files, and then retry the operation.

In addition, if the detailed information above is displayed, use the data collection tool to collect data, and then contact a system administrator.

KNAN22843-E
The file format is invalid. (file name = file-name, details = detailed-information, line number = line-number)

The file format is invalid.

S:

Stops the command.

O:

Check the contents of the detailed information. Take the indicated actions, and then retry the operation.

If the problem cannot be resolved, use the data collection tool to collect data, and then contact a system administrator.

KNAN22844-E
Creation of a temporary CSV file failed. (details = detailed-information)

Creation of a temporary CSV file failed.

S:

Stops the command.

O:

If the following detailed information is displayed, take the indicated corrective action.

There is no access permission.
Check the access permission for the specified path.

JP1CONFIG_TMPDIR cannot be obtained from the registry.
The common definition information is not configured. Make sure that the configuration is correct.
If operating in a cluster environment, and if the command is executed with the -h option, make sure that the logical host name is correct.
Also make sure that the logical host name set in the JP1_HOSTNAME environment variable is correct.

The path specified in JP1CONFIG_TMPDIR does not exist.
Make sure that the tmp directory exists. Also make sure that there is read and write permission for the specified path.
If operating in a cluster environment, check the following items:
Does the defined log directory exist?
Is the common disk mounted?
Is there read and write permission for the specified path?
If the command is executed with the -h option, was the command issued from the primary host?

The length of the Temp directory path exceeded the maximum value.
The file name specified by jcfmkcsdata exceeds the range allowed by the OS.
Shorten the file name, and then re-execute the command.

In addition, if the detailed information above is displayed, use the data collection tool to collect data, and then contact a system administrator.

KNAN22845-E
Log initialization failed.

Log initialization failed.

S:

Stops the command.

O:

Check the following items:

Make sure that the log directory exists, and that there is read and write permission for the log directory.

If operating in a cluster environment, check the following items:
Does the defined log directory exist?
Is the common disk mounted?
Is there read and write permission for the defined log directory?

If the command is executed with the -h option, make sure that the command was issued from the primary host.

KNAN22846-E
A command terminated abnormally. (Cause: detailed-information)

A command ended abnormally.

S:

Stops the command.

O:

If the following detailed information is displayed, take the indicated corrective action.

An error occurred while writing to a CSV file.

An error occurred while opening a CSV file.

Operations cannot be performed on the file.
Check the following items, and then retry the operation.
Is there sufficient memory?
Does the file exist?
Is the file access permission configured correctly?
Has the file been opened (locked) by another application?

An attempt to read the common definition parameter has failed.
The common definition information is not configured. Make sure that the configuration is correct.
If operating in a cluster environment, and if the command is executed with the -h option, make sure that the logical host name is correct.
Also make sure that the logical host name set in the JP1_HOSTNAME environment variable is correct.

An error occurred while opening a temporary CSV file.
Make sure that the tmp directory exists. Also make sure that there is read and write permission for the specified path.
If operating in a cluster environment, check the following items:
Does the defined log directory exist?
Is the common disk mounted?
Is there read and write permission?
If the command is executed with the -h option, was the host that issued the command the primary host?

An invalid node ID has been specified for a new node.
The node ID listed in the IMCS_ExportFile is incorrect.
Specify a node ID in the range from 00000001 to 7FFFFFFF.

If the problem cannot be resolved using the above methods, use the data collection tool to collect data, and then contact a system administrator.

KNAN22847-I
Conversion of an input file will now start.

Conversion of an input file will now start.

S:

Continues executing the command.

KNAN22848-I
Conversion of an input file was successful.

Conversion of an input file was successful.

S:

Continues executing the command.

KNAN22849-I
Conversion of an input file ended normally.

Conversion of an input file ended normally.

S:

Terminates command processing.

KNAN22850-E
The specified path "path" includes a reserved device name.

The specified path includes a reserved device name.

S:

Stops the command.

O:

Specify the path without a reserved device name, and then retry the operation.

KNAN23000-I
Login was successful. (user name = user-name, host = host-name)

Login was successful.

S:

Logs in successfully.

KNAN23001-E
Login cannot be performed because the number of users connected to the server exceeds the maximum limit of maximum-value.

Login cannot be performed because the number of users that are logged in exceeds the maximum.

S:

Stops login processing.

O:

Wait until another user logs out, and then log in again.

KNAN23002-E
User authentication failed. (user name = user-name, host = host-name)

User authentication failed.

S:

Stops login processing.

O:

Check the user ID and password, and then log in again.

KNAN23003-E
A connection to the authentication server could not be established.

Login failed because a connection to the authentication server could not be established.

S:

Stops login processing.

O:

Make sure that the authentication server is running and accessible, and then log in again.

KNAN23004-E
Login failed. (user name = user-name, host = host-name, details = detailed-information)

Login failed.

S:

Stops login processing.

O:

If the detailed information indicates that the common definition could not be acquired, take the following action:

A common definition could not be acquired.
If operating in a cluster system, make sure that the logical host name specified in the JP1_HOSTNAME environment variable is correct.

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

KNAN23005-E
Logout failed because a communication error occurred between the connecting host and the authentication server. (user name = user-name, host = host-name)

Logout failed because a communication error occurred with the authentication server.

S:

Stops logout processing.

O:

Make sure that the authentication server is running and accessible, and then log out again.

KNAN23006-E
Logout failed. (user name = user-name, host = host-name, details = detailed-information)

Logout failed.

S:

Stops logout processing.

O:

If the detailed information indicates that the common definition could not be acquired, take the following actions:

A common definition could not be acquired.
If operating in a cluster environment, make sure that the logical host name specified in the JP1_HOSTNAME environment variable is correct.

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

KNAN23008-E
Acquisition of the list of users failed. (details = detailed-information)

Acquisition of the user list failed.

S:

Stops processing.

O:

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

KNAN23009-E
The session timed out. (timeout = timeout-value)

The session timed out.

S:

Stops processing.

O:

Log in again.

KNAN23010-I
Logout was successful. (user name = user-name, host = host-name)

Logout was successful.

S:

Logs out successfully.

KNAN24000-E
A command option is invalid.

A command argument is invalid.

S:

Suspends command processing.

O:

Specify a valid argument, and then retry the operation.

KNAN24001-E
The specified file "file-name" is invalid.

The specified file is invalid.

S:

Suspends command processing.

O:

Specify a valid file, and then retry the operation.

KNAN24002-E
The file "file-name" does not exist.

The specified input file does not exist.

S:

Suspends command processing.

O:

Make sure that the specified input file exists.

KNAN24003-E
The output file "file-name" already exists.

The output file already exists.

S:

Suspends command processing.

O:

Specify the name of an output file that has not already been specified, and then re-execute the command.

KNAN24004-E
The user does not have access permission for the specified file "file-name".

There is no access permission for the specified file.

S:

Suspends command processing.

O:

Check the access permission for the specified file.

KNAN24005-E
No executing permission.

There is insufficient permission to execute the command.

S:

Suspends command processing.

O:

Check the permission required to execute the command.

KNAN24006-E
Memory allocation has failed.

A memory shortage occurred.

S:

Suspends command 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.

KNAN24007-E
An IO error occurred. (information = maintenance-information)

An I/O error occurred.

S:

Suspends command processing.

O:

Make sure that there is sufficient disk space, memory, or other OS resources.

KNAN24008-E
An attempt to start the Java VM failed.

An attempt to start Java VM failed.

S:

Suspends command processing.

O:

Make sure that there is sufficient disk space, memory, or other OS resources.

KNAN24009-E
Command execution failed. (information = maintenance-information)

Command execution failed.

S:

Suspends command processing.

O:

Make sure that there is sufficient disk space, memory, or other OS resources.

KNAN24010-E
Execute this command from the manager console.

The command was not executed from the administrator console.

S:

Suspends command processing.

O:

Execute the command from the administrator console.

KNAN24011-W
Acquisition of information from common definitions failed. (information = maintenance-information)

Acquisition of information from the common definition information failed. The default is to continue processing.

S:

Continues processing the command.

O:

Make sure that there is sufficient disk space, memory, or other OS resources.

KNAN24012-E
The option "option" is mandatory.

A required option is missing.

S:

Stops the command.

O:

Check the option, and then retry the operation.

KNAN24013-E
The command option "option" is invalid.

An option is invalid.

S:

Stops the command.

O:

Check the option, and then retry the operation.

KNAN24014-E
The command option "option" is specified more than once.

An option is specified more than once.

S:

Stops the command.

O:

Check the option, and then retry the operation.

KNAN24015-E
No value is specified for the option "option".

No value is specified for an option.

S:

Stops the command.

O:

Check the option, and then retry the operation.

KNAN24016-E
The value of the option "option" is invalid.

The value of an option is invalid.

S:

Stops the command.

O:

Check the option, and then retry the operation.

KNAN24017-W
An attempt to open the catalog file has failed. (information = maintenance-information)

An attempt to open the catalog file failed.

S:

Assumes that the value of the LANG environment variable is C and continues processing.

O:

Specify a valid value for the LANG environment variable.

KNAN24030-I
Acquisition of virtual machine configuration information will now start.

Acquisition of virtual machine configuration information will now start.

S:

Starts acquisition of virtual machine configuration information.

KNAN24031-I
Virtual machine configuration information was successfully output.

Virtual machine configuration information was output successfully.

S:

Outputs virtual machine configuration information.

KNAN24032-W
There is the Virtual OS of the host-name host that could not be taken the vm hostname. (VM name: VM-name)

The host-name virtual host name could not be acquired.

S:

Continues processing the command.

O:

Make sure that the virtual host can be acquired in the virtual OS of the specified host.

KNAN24033-W
Username or password for "host-name" host is wrong.

Authentication of the host (host-name) failed.

S:

Continues processing the command.

O:

Specify a valid user name and password.

KNAN24034-E
Acquisition of the virtual machine configuration information failed.

Acquisition of the virtual machine configuration information failed.

S:

Terminates command execution.

O:

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

KNAN24035-W
A communication error for the host "host-name" occurred.

A communication error for the host (host-name) occurred.

S:

Continues command execution.

O:

Check the following items:

Is the virtual machine software running on the specified host?

Is communication blocked by a firewall?

Is communication enabled for the communication type specified in the -m option?

KNAN24036-W
The host "host-name" is not VMware ESX Server or is not a supported version of VMware ESX Server.

The host (host-name) is not VMware ESX Server, or is not a supported version of VMware ESX Server.

S:

Continues command execution.

O:

Make sure that the connection destination is a supported version of VMware ESX Server.

KNAN24037-W
The host name of the host "host" is different from the SSL certification host name.

The host name of the host (host-name) is different from the SSL certification host name.

S:

Continues command execution.

O:

Specify an SSL certification host name as the host name.

KNAN24038-W
An SSL certification for the host "host-name" was not found.

An SSL certification for the host (host-name) was not found.

S:

Continues command execution.

O:

Use the keytool command to assign SSL certification to the host (host-name).

KNAN24039-E
The file vmware.keystore, which stores the certification information, is invalid.

The certification information stored in the file vmware.keystore is invalid.

S:

Terminates command execution.

O:

Delete the vmware.keystore file, and then use the keytool command to re-create the vmware.keystore file.

KNAN24040-I
A connection to the VMM host could be established. (host name = Host name, VMM name = VMM name, version = Version)

A connection to the VMM host could be established.

S:

Acquires the virtual machine configuration information.

KNAN24050-I
Conversion of the input file will now start.

Conversion of the input file will now start.

S:

Continues command processing.

KNAN24051-I
The input file was successfully converted.

The input file was successfully converted.

S:

Terminates command execution.

KNAN24052-I
Conversion of the input file ended normally.

Conversion of the input file ended normally.

S:

Terminates command execution.

KNAN24053-E
The maximum number of managable hosts was exceeded.

The maximum number of manageable hosts was exceeded.

S:

Terminates command execution.

O:

Revise the number of managed hosts.

KNAN24100-I
The JP1/IM - Configuration setup will now start.

The IM Configuration Management setup command will now start.

S:

Continues processing.

KNAN24101-I
The definition file file-name was relocated.

The file file-name was relocated.

S:

Continues processing.

KNAN24102-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 correctly installed.

KNAN24103-I
file-name was registered in the common definition.

Registration of the common definition information was successful.

S:

Continues processing.

KNAN24104-E
file-name could not be registered in the common definition.

Registration of the common definition information failed.

S:

Suspends command processing.

O:

Make sure that JP1/Base and JP1/IM - Manager are correctly installed.

KNAN24105-I
Registration of common definition information has finished.

Registration of common definition information is complete.

S:

Continues processing.

KNAN24106-E
An attempt to set the system environment has failed.

The system environment cannot be set.

S:

Continues processing.

O:

Make sure that JP1/Base and JP1/IM - Manager are correctly installed.

KNAN24107-I
JP1/IM-Configuration setup has finished.

The IM Configuration Management setup command has finished.

S:

Terminates command processing.

O:

Make sure that JP1/Base and JP1/IM - Manager are correctly installed.

[Contents][Back][Next]

[Trademarks]