Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The application placement controller could not be enabled due to an unexpected error. |
Action | Restart the cell. |
Explanation | The application placement controller proposed a new placement. |
Action | No action is required. |
Explanation | The application placement controller experiences an error while executing the control loop. |
Action | Contact IBM Support. |
Explanation | Placement Controller configuration has been changed by a user. |
Action | No action is required. |
Explanation | A configuration setting for the application placement controller has been changed. |
Action | No action is required. |
Explanation | A configuration setting for the application placement controller has been changed. |
Action | No action is required. |
Explanation | The application placement controller started an out-of-schedule placement cycle. |
Action | No action is required. |
Explanation | The application placement controller could not find the bulletin board. |
Action | If BBSON is enabled, verify that no TCP and UDP port conflicts exist. |
Explanation | The application placement controller could not find the bulletin board factory. |
Action | If BBSON is enabled, verify that no TCP and UDP port conflicts exist. |
Explanation | The application placement controller could not subscribe to the specified bulletin board topic. |
Action | If BBSON is enabled, verify that no TCP and UDP port conflicts exist. |
Explanation | This error message is generated when an exception or an unexpected parameter value occurs within the application placement controller. It is generated to aid in problem diagnosis. |
Action | Contact IBM Support. |
Explanation | The server has been placed into maintenance mode. Typical causes are the server fails to start within the server operation timeout value that is specified in the application placement controller configuration. |
Action | Investigate and resolve any problems relating to the server starting, and remove the server from maintenance mode when corrected. |
Explanation | The application placement controller has detected that the server was started in maintenance mode after it previously failed to start. |
Action | No action is required. |
Explanation | The server failed to start or timed out while starting. The application placement controller will not attempt to restart the server until confirmation of a successful start is received, but will attempt to start other instances if appropriate. |
Action | Investigate and resolve any problems relating to the failed start attempt. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | Another application placement controller is configured and the local controller has connected to the remote controller. |
Action | No action is required. |
Explanation | Another application placement controller is configured and the local controller was unable to connect to the remote controller. |
Action | Use parameter 0 as shown in the message, along with the FFDC log files, to debug the problem. |
Explanation | The application placement controller is unable to meet the minInstances policy for a dynamic cluster due to insufficient memory. |
Action | Increase the total memory in the node group or specify larger minInstances policy values. |
Explanation | The application placement controller is unable to find a placement that satisfies all memory and CPU speed requirements. |
Action | Increase the node group capacity. |
Explanation | The placement plan sent for approval was not approved on time. The approval was ignored. |
Action | No action is required. |
Explanation | The approved placement plan was successfully completed. |
Action | No action is required. |
Explanation | The approved placement plan cannot be completed. |
Action | No action is required. |
Explanation | The application placement controller was unable to communicate with the node agent on the specified node. |
Action | Ensure that the node agent process is started, and that there are no network connectivity issues. |
Explanation | The application placement controller was unable to communicate with the node agent on the specified node. |
Action | Ensure that the node agent process is started, and that there are no network connectivity issues. |
Explanation | The application placement controller was unable to communicate with the deployment manager. |
Action | Ensure that the deployment manager is started, and that there are no network connectivity issues. |
Explanation | The application placement controller was unable to communicate with the deployment manager. |
Action | Ensure that the deployment manager is started, and that there are no network connectivity issues. |
Explanation | A dynamic event that requires the application placement controller to review the event and potentially reconfigure the system has occurred. |
Action | No action is required. Additional messages will be logged if a change is required. |
Explanation | The application placement controller has determined that a server instance needs to be stopped or started. See message DCPC0121I for additional information. |
Action | If the dynamic cluster operating mode is set to supervised, accept or reject the recommendation on the Task Management panel in the administrative console. If the dynamic cluster operating mode is set to automatic, no user action is required. |
Explanation | The application placement controller has submitted a task to the task management subsystem. See message DCPC0120I for additional information. |
Action | If the dynamic cluster operating mode is set to supervised, accept the recommendation prior to the expiration time on the Task Management panel in the administrative console. If the dynamic cluster operating mode is set to automatic, no user action is required. |
Explanation | The application placement controller has submitted a task to the task management subsystem and the task was denied. If there is a reoccurrence of the conditions that originally caused the task to be generated, a new task will be generated. |
Action | No action is required. |
Explanation | The application placement controller has received user approval for a previously submitted task. The task will be completed. |
Action | No action is required. |
Explanation | The application placement controller has submitted a task to the task management subsystem and the task has expired. If there is a reoccurrence of the conditions that originally caused the task to be generated, a new task will be generated. |
Action | No action is required. |
Explanation | The application placement controller will submit tasks to the task management subsystem from the indicated cell/node/server. |
Action | No action is required. |
Explanation | The application placement controller has been notified that a change has completed. |
Action | No action is required. |
Explanation | application placement controller has been notified that a change has completed with errors. |
Action | No action is required. |
Explanation | A request to shut down or set the maintenance mode of a server or node has been submitted. |
Action | Use the administrative console to modify the placement of the dynamic cluster instances to maintain the desired service level performance. |
Explanation | A request to shut down or set the maintenance mode of a server or node has been submitted. |
Action | No action is required. |
Explanation | A request to shut down or set the maintenance mode of a server or node has been submitted. |
Action | Use the administrative console to modify the placement of the dynamic cluster instances to maintain the desired service level performance. |
Explanation | A request to change the configuration of the dynamic cluster has been submitted. |
Action | No action is required. |
Explanation | The application placement controller is attempting to start or stop a server instance. |
Action | No action is required. |
Explanation | The application placement controller is attempting to start or stop a server instance. |
Action | No action is required. |
Explanation | Application Placement Controller has determined resources needs to be added or removed. See message DCPC0121I for additional information. |
Action | If custom property was set to supervised, use the Admin Console Task Management panel to accept or deny the recommendation. If the custom property was set to automatic, no user action is required. |
Explanation | Application Placement Controller is attempting to add or remove resources. |
Action | No user action is required at this time. |
Explanation | Application Placement Controller is attempting to add or remove resources. |
Action | No user action is required at this time |
Explanation | The application placement controller has attempted to start a server that did not start within the allotted time. The server logs or server node agent logs might contain the reason for the failure. |
Action | Check the server operation timeout value that is specified on the application placement controller configuration. This value might need to be increased. To change the value in the administrative console, click Operational Policies > Autonomic Managers > Application Placement Controller. |
Explanation | The application placement controller has removed a server that originally did not start within the allotted time. |
Action | Check the server operation timeout value that is specified in the application placement controller configuration. This value might need to be increased. To change the value in the administrative console, click Operational Policies > Autonomic Managers > Application Placement Controller. |
Explanation | A maintenance mode operation is in progress. |
Action | No action is required. |
Explanation | A maintenance mode operation is in progress. |
Action | No action is required. |
Explanation | A resource has been detected as maintenance, started, stopped, added, or removed. |
Action | No action is required. |
Explanation | The application placement controller has requested placement changes in order to maintain service levels for the specified service classes. |
Action | Review the action plan provided by the system and approve the proposed placement changes. |
Explanation | The application placement controller has determined that there is a more optimal placement of dynamic cluster instances and has requested a placement change. |
Action | Review the action plan provided by the system and approve the proposed placement changes. |
Explanation | The application placement controller has determined that there is a more optimal placement of dynamic cluster instances and has requested a placement change. |
Action | Review the action plan provided by the system and approve the proposed placement changes. |
Explanation | The minimum and maximum dynamic cluster instances is specified in the dynamic cluster configuration properties. The application placement controller compares the number of active instances against the configured values and requests placement changes if necessary. |
Action | Review the action plan provided by the system and approve the proposed placement changes. |
Explanation | Maximum CPU utilization is specified in the Autonomic Request Flow Manager configuration. The application placement controller monitors the CPU utilization per node and requests a placement change when the specified threshold is breached. |
Action | Review the action plan provided by the system and approve the proposed placement changes. |
Explanation | The application placement controller has requested placement changes in order to maintain service levels for the specified service classes. |
Action | No action is required. Placement changes have been initiated. |
Explanation | The application placement controller has determined that there is a more optimal placement of dynamic cluster instances and has requested a placement change. |
Action | No action is required. Placement changes have been initiated. |
Explanation | The application placement controller has determined that there is a more optimal placement of dynamic cluster instances and has requested a placement change. |
Action | No action is required. Placement changes have been initiated. |
Explanation | The minimum and maximum dynamic cluster instances is specified in the dynamic cluster configuration properties. The application placement controller compares the number of active instances against the configured values and requests placement changes if necessary. |
Action | No action is required. Placement changes have been initiated. |
Explanation | Maximum CPU utilization is specified in the Autonomic Request Flow Manager configuration. The application placement controller monitors the CPU utilization per node and requests a placement change when the specified threshold is breached. |
Action | No action is required. Placement changes have been initiated. |
Explanation | The application placement controller senses and monitors total memory utilization and memory capacity on a node. If the sum of memory consumed by all servers on a node exceeds the capacity of a node, application placement change is requested. |
Action | Review the action plan provided by the system and approve the proposed placement changes. |
Explanation | The application placement controller senses and monitors total memory utilization and memory capacity on a node. If the sum of memory consumed by all servers on a node exceeds the capacity of a node, application placement change is requested. |
Action | No action is required. Placement changes have been initiated. |
Explanation | The application placement controller receives dynamic cluster activity information from the On Demand Router. That information has changed such that activation / deactivation is required. |
Action | Review the action plan provided by the system and approve the proposed placement changes. |
Explanation | The application placement controller detected that the following dynamic cluster configured for lazy activation / deactivation needs to be acted upon because of recent activity or inactivity: "{0}". |
Action | No action is required. Placement changes have been initiated. |
Explanation | The application placement controller detected that these dynamic clusters are in violation of a configured isolation policy. Review the strategy for modifying the placement of dynamic cluster instances in the action plan. |
Action | Review the action plan provided by the system and approve the proposed placement changes. |
Explanation | The application placement controller detected that these dynamic clusters are in violation of a configured isolation policy. Review the strategy for automatically modifying the placement of dynamic cluster instances in the action plan. |
Action | No action is required. Placement changes have been initiated. |
Explanation | The application placement controller detected that instances of dynamic cluster are incorrectly running on a node. Review the strategy for modifying the placement of dynamic cluster instances in the action plan. |
Action | Review the action plan provided by the system and approve the proposed placement changes. |
Explanation | The application placement controller detected that instances of dynamic cluster are incorrectly running on a node. Review the strategy for automatically modifying the placement of dynamic cluster instances in the action plan. |
Action | No action is required. Placement changes have been initiated. |
Explanation | The application placement controller detected that the system performance can be improved by a reallocation of dynamic cluster instances. Review the strategy for modifying the placement of dynamic cluster instances in the action plan. |
Action | Review the action plan provided by the system and approve the proposed placement changes. |
Explanation | The application placement controller detected that the system performance can be improved by a reallocation of dynamic cluster instances. Review the strategy for automatically modifying the placement of dynamic cluster instances in the action plan. |
Action | No action is required. Placement changes have been initiated. |
Explanation | The application placement controller detected that these dynamic clusters "{0}" are violating restrictions associated with collocation of long running jobs and transactional workloads. Review the strategy for modifying the placement of dynamic cluster instances in the action plan. |
Action | Review the action plan provided by the system and approve the proposed placement changes. |
Explanation | The application placement controller detected that these dynamic clusters "{0}" are violating restrictions associated with collocation of long running jobs and transactional workloads. Review the strategy for automatically modifying the placement of dynamic cluster instances in the action plan. |
Action | No action is required. Placement changes have been initiated. |
Explanation | The application placement controller receives dynamic cluster activity information from the on demand router. That information has changed such that activation is required. |
Action | Since the dynamic cluster operating mode is set to supervised, accept or reject the recommendation on the Task Management panel in the administrative console. |
Explanation | The application placement controller receives dynamic cluster activity information from the on demand router. That information has changed such that activation is required. |
Action | Since the dynamic cluster operating mode is set to automatic, no action is required. |
Explanation | The application placement controller receives dynamic cluster activity information from the on demand router. That information has changed such that deactivation is required. |
Action | Since the dynamic cluster operating mode is set to supervised, accept or reject the recommendation on the Task Management panel in the administrative console. |
Explanation | The application placement controller receives dynamic cluster activity information from the on demand router. That information has changed such that deactivation is required. |
Action | Since the dynamic cluster operating mode is set to automatic, no action is required. |
Explanation | The application placement controller receives dynamic cluster activity information from the on demand router. That information has changed such that deactivation is required. |
Action | Since the dynamic cluster operating mode is set to supervised, accept or reject the recommendation on the Task Management panel in the administrative console. |
Explanation | The application placement controller receives dynamic cluster activity information from the on demand router. That information has changed such that deactivation is required. |
Action | Since the dynamic cluster operating mode is set to automatic, no action is required. |
Explanation | The application placement controller has run and information about the input and output has been logged. |
Action | No action is required. |
Explanation | The application placement controller cannot initiate or complete a recommended change. The change might be attempted during the next placement cycle. |
Action | Use the information in the "Resource" and "Reason" fields and correct the problem. |
Explanation | The Application Placement Controller determines if more resources are needed to minimize response time and meet service policy goals or resources can be removed and service policy goals will still be met. |
Action | No action is required, placement changes have been initiated. |
Explanation | The Application Placement Controller determines if more resources are needed to minimize response time and meet service policy goals or resources can be removed and service policy goals will still be met. |
Action | Since the custom property was set to supervised, use the Admin Console Task Management panel to accept or deny the recommendation. |
Explanation | The Application Placement Controller determined that a server needs to be started to meet the configured number of minimum instances. |
Action | Use the Admin Console Task Management panel to accept or deny the recommendation. |
Explanation | The Application Placement Controller detected a change in demand for the specified cluster. |
Action | No actions are necessary. |
Explanation | The Application Placement Controller detected that more resources are needed by the topology. |
Action | Use the Admin Console Task Management panel to accept or deny the recommendation. |
Explanation | The Application Placement Controller determined that a server needs to be started for performance reasons. |
Action | Use the Admin Console Task Management panel to accept or deny the recommendation. |
Explanation | The Application Placement Controller determined that a server needs to be stopped. |
Action | Use the Admin Console Task Management panel to accept or deny the recommendation. |
Explanation | The Application Placement Controller detected that fewer resources are needed by the topology. |
Action | Use the Admin Console Task Management panel to accept or deny the recommendation. |
Explanation | The Application Placement Controller determined that a server needs to be stopped because it has been idle longer than the configured threshold. The server is a member of a cluster with proactive idle stop enabled. |
Action | Use the Admin Console Task Management panel to accept or deny the recommendation. |
Explanation | The Application Placement Controller determined that a host does not have sufficient memory to run the specified server. |
Action | Use the Admin Console Task Management panel to accept or deny the recommendation. |
Explanation | The Application Placement Controller determined that a server needs to be started to meet requirements. |
Action | Use the Admin Console Task Management panel to accept or deny the recommendation. |
Explanation | The Application Placement Controller determined that a server needs to be stopped. |
Action | Use the Admin Console Task Management panel to accept or deny the recommendation. |
Explanation | This warning message is generated when an unexplainable condition caused a placement change. |
Action | No action is required. A placement change is pending or in progress. |
Explanation | The application lazy start controller detected incoming requests for the dynamic cluster and will start at least one server instance of this dynamic cluster. |
Action | No action is required. Placement changes have been initiated. |
Explanation | The application lazy start controller detected that this dynamic cluster has been idle for the specified wait period and will allow all its server instances to be stopped if resources consumed by them are needed by other dynamic clusters. |
Action | No action is required. |
Explanation | The application lazy start controller attempted to update the state of the dynamic cluster but had no prior representation of that dynamic cluster. |
Action | No action is required. |
Explanation | The application lazy start controller will permit deactivation of the dynamic cluster if its idle time exceeds the specified time. |
Action | No action is required. |
Explanation | The application lazy start controller is not permitted to deactivate this dynamic cluster in the future. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message provides a detailed list of all application placement controller states. |
Action | No action is required. |
Explanation | This message provides a detailed list of all application placement controller states. |
Action | Review the runtime tasks submitted by the application placement controller. In the administrative console, select System administration > Task Management > Runtime Tasks. |
Explanation | This message indicates which application placement controller predictor is being used. |
Action | No action is required. |