Job Management Partner 1/Integrated Management - Manager Messages

2.13 IM Configuration Management messages common to all components (KNAN29000 to KNAN29927)

KNAN29000-I
The JP1/IM - Configuration daemon has started. (host = host-name)

IM Configuration Management Service started.

S:

Starts IM Configuration Management Service.

KNAN29001-I
The JP1/IM - Configuration daemon ended normally. (host = host-name)

IM Configuration Management Service stopped.

S:

Stops IM Configuration Management Service.

KNAN29002-E
The JP1/IM - Configuration daemon terminated abnormally. (host = host-name)

IM Configuration Management Service stopped abnormally.

S:

Stops IM Configuration Management Service.

O:

Take the following actions:

Make sure that the IM Configuration Management database is operating normally, and then restart IM Configuration Management Service.

Refer to the message that was output preceding this message, and take the corrective action given for that message.

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

KNAN29003-E
The JP1/IM - Configuration daemon cannot start because the host name is invalid. (host = host-name)

IM Configuration Management Service cannot start because the specified logical host name is invalid.

S:

Terminates IM Configuration Management Service.

O:

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

KNAN29004-E
The JP1/IM - Configuration daemon cannot start because initialization of JP1 common definitions failed.

IM Configuration Management Service could not be started because initialization of JP1 common definition access failed.

S:

Terminates IM Configuration Management Service.

O:

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

KNAN29005-E
The JP1/IM - Configuration daemon cannot start because initialization of the integrated trace log failed.

IM Configuration Management Service could not be started because initialization of the integrated trace log failed.

S:

Terminates IM Configuration Management Service.

O:

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

KNAN29006-E
The JP1/IM - Configuration daemon cannot start because initialization of the log of each process failed.

IM Configuration Management Service could not be started because initialization of the process-specific trace log failed.

S:

Terminates IM Configuration Management Service.

O:

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

KNAN29007-E
The JP1/IM - Configuration daemon cannot start because an initialization of the database failed.

IM Configuration Management Service could not be started because initialization of the IM Configuration Management database failed.

S:

Terminates IM Configuration Management Service.

O:

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

KNAN29008-I
Initialization of the JP1/Base communication finished successfully.

Initialization of the JP1/Base communication base finished successfully.

S:

Finishes initializing the JP1/Base communication base.

KNAN29009-E
Initialization of JP1/BASE communication is failed. (error code = error-code)

IM Configuration Management Service could not be started because initialization of the JP1/Base communication base failed.

S:

Terminates IM Configuration Management Service.

O:

The common definition information is not configured. Make sure that the configuration is correct.

If operating in a cluster environment, make sure that the logical host name set in the JP1_HOSTNAME environment variable is correct.

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

KNAN29010-W
A common definition value is invalid. The default value will be assigned. (key = key-name, default value = default-value)

A common definition value is invalid. The default value will be used.

S:

Continues processing.

KNAN29011-E
Acquisition of the common directory path name failed.

IM Configuration Management Service could not be started because acquisition of the conf directory from the common definition information failed.

S:

Terminates IM Configuration Management Service.

O:

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

KNAN29012-E
Acquisition of the log directory path name failed.

IM Configuration Management Service could not be started because acquisition of the log directory from the common definition information failed.

S:

Terminates IM Configuration Management Service.

O:

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

KNAN29013-W
The JP1/IM - CF daemon will be started using the default port number port-number because acquisition of the port number failed.

The default port will be used because IM Configuration Management Service could not acquire the port number.

S:

Continues processing.

KNAN29014-E
The JP1/IM - CF daemon cannot start because initialization of the service failed.

Initialization of the service failed.

S:

Terminates IM Configuration Management Service.

O:

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

KNAN29015-I
The JP1/IM - CF daemon will be reloaded.

Reloading of IM Configuration Management Service will start.

S:

Starts reloading of IM Configuration Management Service.

KNAN29016-I
The JP1/IM - CF daemon was reloaded successfully.

Reloading of IM Configuration Management Service has finished.

S:

Finishes reloading of IM Configuration Management Service.

KNAN29017-W
An attempt to reload the JP1/IM - CF daemon failed.

Reloading of IM Configuration Management Service failed.

S:

Continues operating using the data registered prior to reloading.

KNAN29018-I
The JP1/IM - CF daemon will stop because a stop request was received from the process management daemon.

IM Configuration Management Service will stop normally.

S:

IM Configuration Management Service stops normally.

KNAN29019-E
The JP1/IM - CF will stop because an invalid request was received from the process management daemon. (error code = error-code)

IM Configuration Management Service will stop abnormally.

S:

Terminates IM Configuration Management Service.

O:

Take the following actions:

Make sure that the IM Configuration Management database is running normally, and then restart IM Configuration Management Service.

Refer to the message that was output preceding this message, and take the corrective action given for that message.

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

KNAN29020-E
Startup completion could not be reported to the process management daemon.

Completion of startup could not be reported to SPMD.

S:

Terminates IM Configuration Management Service.

O:

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

KNAN29021-I
Creation of all the threads waiting for TCP/IP communication completed successfully.

Creation of all threads waiting for a TCP/IP connection finished successfully.

S:

Finishes creating all threads waiting for a TCP/IP connection.

KNAN29022-W
Creation of some threads waiting for TCP/IP communication failed, but processing will continue.

Creation of some threads waiting for a TCP/IP connection failed, but processing will continue.

S:

Continues processing.

KNAN29023-E
The JP1/IM - CF daemon will stop because the creation of all the threads waiting for TCP/IP communication did not succeed.

IM Configuration Management Service stops because creation of all threads waiting for a TCP/IP connection failed.

S:

Terminates IM Configuration Management Service.

O:

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

KNAN29024-I
Creation of threads waiting for the TCP/IP communication completed successfully. (IP address = IP-address)

Creation of threads waiting for a TCP/IP connection finished.

S:

Finishes creating threads waiting for a TCP/IP connection.

KNAN29025-E
An attempt to create a thread waiting for the TCP/IP communication failed. (IP address = IP-address)

Creation of threads waiting for a TCP/IP connection failed.

S:

Terminates IM Configuration Management Service.

O:

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

KNAN29026-I
The IM configuration management service will now start. (language = environment-variable and character encoding =character-code)

Reports that IM Configuration Management Service will now start.

S:

Starts IM Configuration Management Service.

KNAN29027-E
Initialization of the plugin service failed. (error code = error-code)

Startup of IM Configuration Management Service failed because initialization of the JP1 plug-in manager failed.

S:

Terminates IM Configuration Management Service.

O:

If the detailed information indicates that there are not enough resources, take the following corrective actions:

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

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

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

Reports that a thread waiting for a TCP/IP connection has started.

S:

Starts a thread waiting for a TCP/IP connection.

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

Reports that a thread waiting for a TCP/IP connection stopped normally.

S:

Stops a thread waiting for a TCP/IP connection.

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

A thread waiting for a TCP/IP connection stopped abnormally.

S:

Stops a thread waiting for a TCP/IP connection.

O:

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

KNAN29031-E
The connection with the client will be closed because an invalid protocol was received from the client.

The connection will be ended because an invalid protocol was received.

S:

Ends the connection with the IM Configuration Management - View.

O:

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

KNAN29032-E
The connection with the client will be closed because reception of a request failed.

The connection will be ended because reception of a request failed.

S:

Ends the connection with the IM Configuration Management - View.

O:

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

KNAN29033-E
The connection with the client will be closed because an error occurred during request processing.

The connection will be ended because an error occurred during request processing.

S:

Ends the connection with the IM Configuration Management - View.

O:

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

KNAN29034-E
Communication processing will now end because the connection with the client was closed.

Terminates connection processing because the connection was ended.

S:

Ends the connection with the IM Configuration Management - View.

O:

Log in again from the IM Configuration Management - View.

KNAN29036-E
The request "request-name" cannot be executed because of insufficient disk space to update the database.

Stops execution of the request due to insufficient disk space.

S:

Stops execution of the request.

O:

Make sure that sufficient free disk space has been allocated, and then retry the operation.

KNAN29037-E
request-name failed because the database could not be accessed.

Stops execution of the request because IM Configuration Management database access failed.

S:

Stops execution of the request.

O:

Make sure that the IM database service is running, and then retry the operation.

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

KNAN29038-E
The request "request-name" cannot be executed because the logged-in user "user-name" does not have update permission.

Stops execution of the request due to insufficient user permission.

S:

Stops execution of the request.

O:

Assign the required permission, and then retry the operation.

KNAN29041-E
A request could not be executed. (request = request-name, error code = detailed-information)

Execution of a request failed.

S:

Stops processing the request.

O:

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

KNAN29045-E
The format of a received request was was invalid. (request = request-name)

The format of a received request was invalid.

S:

Stops execution of the request.

O:

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

KNAN29046-E
A received request could not be executed. (request = request-name, error code = error-code)

A received request could not be executed.

S:

Stops execution of the request.

O:

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

The specified product is not supported
Make sure that the version of the installed product is 09-00 or later.

The IM configuration has not been applied
In the IM Configuration Management window, apply the IM configuration (system hierarchy), and then retry the operation.

KNAN29047-W
A request could not be executed because the database is busy. (request = request-name)

A request could not be executed because the IM Configuration Management database is busy.

S:

Stops execution of the request.

O:

Wait until another user finishes updating the database, and then acquire the most recent information.

KNAN29048-E
The JP1/IM - Configuration daemon will now stop because registration of an IM host failed.

IM Configuration Management Service will stop because registration of the local host failed.

S:

Stops IM Configuration Management Service.

O:

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

KNAN29049-W
The request "request-name" cannot be executed because another user is updating the IM configuration tree.

The request cannot be executed because the IM configuration (system hierarchy) is being updated.

S:

Stops execution of the request.

O:

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

KNAN29050-E
The request "request-name" cannot be executed because the profile is locked by another user.

The request cannot be executed because another user has acquired exclusive access permission for the profile information.

S:

Stops execution of the request.

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.

KNAN29051-E
The request "request-name" cannot be executed because the host is locked by another user.

The request cannot be executed because another user has acquired exclusive access permission for the host information.

S:

Stops execution of the request.

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.

KNAN29052-E
The request "request-name" cannot be executed because the IM configuration is locked by the user user-name:View-host-name.

The request cannot be executed because another user has acquired update permission for the IM configuration (system hierarchy).

S:

Stops execution of the request.

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.

KNAN29053-E
The request "request-name" cannot be executed because IM configuration verification is being performed by the user user-name:View-host-name.

The request could not be processed because IM configuration (system hierarchy) verification is being performed by another user.

S:

Stops execution of the request.

O:

Do one of the following:

In the Login User List window, determine the user that 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 then click the Release Exclusive Editing button to release exclusive permission.

Wait until processing is completed, and then retry the operation.

KNAN29054-E
The request "request-name" cannot be executed because the host "host-name" is locked by the user user-name:View-host-name.

The request could not be processed because another user has acquired exclusive access permission for the host information.

S:

Stops execution of the request.

O:

Do one of the following:

In the Login User List window, determine the user that 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 then click the Release Exclusive Editing button to release exclusive permission.

After exclusive access has been released, retry the operation.

KNAN29055-W
The request "request-name" cannot be executed because another user is updating the host.

The request could not be processed because the host information is being updated.

S:

Stops execution of the request.

O:

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

KNAN29056-E
The request "request-name" cannot be executed because the profile for the host "host-name" is locked by another user.

The request could not be processed because another user has acquired exclusive access permission for the profile information.

S:

Stops execution of the request.

O:

Do one of the following:

In the Login User List window, determine the user that 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 then click the Release Exclusive Editing button to release exclusive permission.

After exclusive access has been released, retry the operation.

KNAN29057-E
"request-name" was forcibly canceled by the user user-name:host-name

The current processing was canceled because exclusive access was forcibly released by the user.

S:

Stops execution of the request.

O:

Acquire exclusive access, and then retry the operation.

KNAN29058-E
The request "request-name" cannot be executed because the lock was forcibly cancelled by the user user-name:host-name.

Scheduled processing could not be executed because exclusive access was forcibly released by the user.

S:

Stops execution of the request.

O:

Acquire exclusive access, and then retry the operation.

KNAN29059-E
The request "request-name" cannot be executed because the lock was forcibly released.

The request could not be processed because exclusive access was forcibly released.

S:

Stops execution of the request.

O:

Acquire exclusive access, and then retry the operation.

KNAN29060-E
The request "request-name" cannot be executed because processing is in progress.

The request could not be processed because processing is in progress.

S:

Stops execution of the request.

O:

Wait until processing is completed, and then retry the operation.

KNAN29061-E
The request "request-name" cannot be executed because the IM Configuration is already locked. Release the lock and then try again.

IM Configuration (system hierarchy) update permission was already acquired. Release the update permission, and then retry the operation.

S:

Stops execution of the request.

O:

Wait until update permission has been released, and then retry the operation.

KNAN29062-E
The request "request-name" cannot be executed because the product "product-name" of the host "host-name" has been locked by the user user-name:View-host-name.

The request could not be processed because another user acquired exclusive access permission for the profile.

S:

Stops execution of the request.

O:

Do one of the following:

In the Login User List window, determine the user that 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 then click the Release Exclusive Editing button to release exclusive permission.

After exclusive access has been released, retry the operation.

KNAN29063-E
The request "request-name" cannot be executed because the product "product-name" of host "host-name" is being updated by another user.

The request could not be processed because the profile information is being updated.

S:

Stops execution of the request.

O:

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

KNAN29064-E
The request "request-name" cannot be executed because an error occurred while trying to acquire the lock.

The request could not be processed because an attempt to acquire exclusive access failed.

S:

Stops execution of the request.

O:

Acquire exclusive access, and then retry the operation.

KNAN29065-W
Initialization of a profile failed.

An attempt to initialize a profile failed.

S:

Stops execution of the request.

O:

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

KNAN29066-E
The request "request-name" cannot be executed because the database was updated.

The request could not be processed because the IM Configuration Management database was updated.

S:

Stops execution of the request.

O:

Acquire the most recent information.

KNAN29067-E
The connection from a client for which login authentication was not performed will now be closed.

The connection will be ended because the client has not logged in.

S:

Continues processing.

O:

Log in, and then retry the operation.

KNAN29069-E
The request cannot be processed because the database was updated.

The request could not be processed because the IM Configuration Management database was updated.

S:

Stops execution of the request.

O:

Acquire the most recent information.

KNAN29070-E
Since startup status of IM database service could not be confirmed, IM configuration management service cannot be started.(Status : status)

IM Configuration Management Service could not be started because the startup status of the IM Configuration Management database could not be confirmed.

S:

Stops execution of the request.

O:

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

KNAN29071-E
The JP1/IM - Configuration daemon is not started because the resource initialization is failed.

The IM Configuration Management daemon could not be started because an attempt to initialize resources failed.

S:

Stops execution of the request.

O:

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

KNAN29080-I
The IM Configuration Management service confirmed that the IM database service has started.

IM Configuration Management Service reports that IM database service startup is complete.

S:

Continues processing.

KNAN29081-I
The IM Configuration Management service is waiting for the IM database service to start.

IM Configuration Management Service is waiting for completion of IM database service startup.

S:

Waits for completion of IM database service startup.

KNAN29082-E
The IM Configuration Management service cannot start because it cannot confirm whether the IM database service has started. Cause: cause

IM Configuration Management Service could not be started because completion of IM database service startup could not be confirmed.

S:

Stops IM Configuration Management Service.

O:

Take corrective action based on the reason:

Reason: The IM database service is now performing start or stop processing.

Reason: The IM database service is stopping.
Execute the jimdbstatus command to determine whether the IM database service is running, and then perform the following operation.

In Windows:

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

In UNIX:

Stop JP1/IM - Manager, and then re-execute the jco_start command.

Reason: The IM database service was interrupted during a restart.
Execute the jimdbstop -f command to forcibly stop the IM database service, and the perform the following operation.

In Windows:

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

In UNIX:

Execute the jco_start command.

Reason: The IM database service is not set up.
Set up the IM database service, and then start JP1/IM - Manager.

Reason: Status confirmation error

Reason: System error
Collect JP1/IM data, and then contact a system administrator.

KNAN29083-E
Processing cannot be executed because the IM Configuration Management service is still starting up.

Processing could not be performed because IM Configuration Management Service is starting.

S:

Suspends processing.

O:

Execute the jco_spmd_status command to determine whether jcfmain is running. Make sure that jcfmain is running, and then retry the operation.

KNAN29084-E
Processing cannot be executed because the IM database service is waiting to start.

Processing could not be performed because IM Configuration Management Service is waiting for completion of IM database service startup.

S:

Suspends processing.

O:

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

KNAN29900-I
JP1/IM Configuration Management Cluster environment setup will start now.

Processing to set up the logical host for the IM configuration management will start.

S:

Starts processing to set up the logical host for the IM configuration management.

KNAN29901-I
Copying of the configuration files of logical host to the shared disk will start now.

Processing to copy the logical host settings file to the shared disk will start.

S:

Starts processing to copy the logical host settings file to the shared disk.

KNAN29902-I
JP1/IM Configuration Management cluster environment setup completed successfully.

The logical host environment was set up successfully.

S:

Terminates command processing.

KNAN29903-E
Logical host of JP1/IM-CC is not setup.

The logical host environment for the integrated console has not been set up.

S:

Terminates command processing.

O:

Set up the logical host for the integrated console, and then re-execute the command.

KNAN29904-E
Specified shared directory does not exist.

The specified shared directory does not exist.

S:

Terminates command processing.

O:

Check the specified shared directory, and then re-execute the command.

KNAN29905-E
Failed to get default configuration data.

An attempt to acquire the configuration information has failed.

S:

Terminates command processing.

O:

Make sure that JP1/Base and JP1/IM - Manager on the physical host have been installed and set up correctly.

KNAN29906-E
Failed to register configuration data.

An attempt to register the configuration information has failed.

S:

Terminates command processing.

O:

Make sure that JP1/Base and JP1/IM - Manager on the physical host have been installed and set up correctly.

KNAN29907-E
cannot create directory-name

An attempt to create a directory has failed.

S:

Terminates command processing.

O:

Check the name of the specified shared directory and its access permissions, and then re-execute the command.

KNAN29909-E
Logical host of JP1/IM-CF is not setup.

The logical host environment for the IM configuration management has not been set up.

S:

Terminates command processing.

O:

Set up the logical host for the IM configuration management, and then re-execute the command.

KNAN29910-E
Failed to setup socket bind configuration.

An attempt to set up the common definition for the physical host has failed.

S:

Terminates command processing.

O:

Make sure that JP1/Base and JP1/IM - Manager on the physical host have been installed and set up correctly.

KNAN29911-I
Updating of JP1/IM-CC configuration files will start now.

Updating of the integrated console definition file will start.

S:

Starts updating of the integrated console definition file.

KNAN29912-I
Setting up of socket bind configuration for default environment will start now.

Setup of the physical host communication will start.

S:

Starts setup of the physical host communication.

KNAN29913-I
The logical host setup processing of JP1/IM-CF will start now.

Setup of the logical host for the IM configuration management will start.

S:

Starts setup of the logical host for the IM configuration management.

KNAN29914-E
Failed to update JP1/IM-CC conf files.

An attempt to set up the integrated console has failed.

S:

Terminates command processing.

O:

Make sure that the shared disk for the integrated console has been mounted, and then retry the setup.

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

The IM configuration management setup command has started.

S:

Continues processing.

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

The file indicated by file-name is relocated.

S:

Continues processing.

KNAN29922-E
'/opt/jp1base/bin/jbssetcnf' could not be executed.

The /opt/jp1base/bin/jbssetcnf command cannot be executed.

S:

Cancels command processing.

O:

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

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

The common definition information was registered successfully.

S:

Continues processing.

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

An attempt to register the common definition information has failed.

S:

Cancels command processing.

O:

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

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

The IM configuration management setup command has terminated.

S:

Terminates command processing.

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

The IM configuration management setup command has terminated.

S:

Terminates command processing.

[Contents][Back][Next]

[Trademarks]