| Explanation | Informational message |
| Action | No action required |
| Explanation | Informational message |
| Action | No action required |
| Explanation | Informational message |
| Action | No action required |
| Explanation | It was determined that it was necessary to stop the specified dynamic cluster in order to make room for a different one to start. |
| Action | No action required |
| Explanation | It was determined that there was a need to start an instance of the specified dynamic cluster to process a job in queue. |
| Action | No action required |
| Explanation | Service policy relationships failed to load |
| Action | Ensure cell connectivity |
| Explanation | A system or internal error has occurred |
| Action | Contact administrator |
| Explanation | A system or internal error has occurred |
| Action | Contact administrator |
| Explanation | The Job could not be dispatched. There was a database exception. Please see logs for details. |
| Action | Examine the system logs for the underlying failure. |
| Explanation | Informational message |
| Action | No action required |
| Explanation | The Business Grid Endpoint Selector has determined available resources will be better utilized by stopping the specified Dynamic Cluster Member. |
| Action | Approve or deny the change. |
| Explanation | The Business Grid Endpoint Selector has determined available resources will be better utilized by starting the specified Dynamic Cluster Member. |
| Action | Approve or deny the change. |
| Explanation | The total outstanding jobs belonging to this job class have exceeded the configured limit. New jobs belonging to the class cannot be dispatched until some of the outstanding jobs complete. |
| Action | No action required |
| Explanation | The job has been canceled as it has been running longer than the maximum execution time of its job class. |
| Action | Ensure that appropriate values are configured for this job class. |
| Explanation | The job classification rule can not contain a blank operand. |
| Action | Specify a valid value for the operand. |
| Explanation | Indicates that the apptype operand must be specified as "j2ee" or "GridUtility". |
| Action | Specify a valid value for the apptype operand. |
| Explanation | Indicates that the platform operand must be specified as "zOS", "distributed" or "mixed". |
| Action | Specify a valid value for the platform operand. |
| Explanation | Informational message |
| Action | No action required |
| Explanation | Informational message |
| Action | No action required |
| Explanation | Informational message |
| Action | No action required |
| Explanation | Informational message |
| Action | No action required |
| Explanation | Informational message |
| Action | No action required |
| Explanation | Informational message |
| Action | No action required |
| Explanation | Informational message |
| Action | No action required |
| Explanation | Informational message |
| Action | No action required |
| Explanation | Informational message |
| Action | No action required |
| Explanation | Informational message |
| Action | No action required |
| Explanation | Informational message |
| Action | No action required |
| Explanation | Informational message |
| Action | No action required |
| Explanation | Informational message |
| Action | No action required |
| Explanation | Informational message |
| Action | No action required |
| Explanation | Informational message. |
| Action | Start the job application. |
| Explanation | Informational message |
| Action | Make sure the HTTP ports are active. |
| Explanation | Informational message |
| Action | Start the endpoint where the job application is installed. |
| Explanation | Informational message |
| Action | Start the endpoint where the grid execution environment is configured. |
| Explanation | Informational message |
| Action | Configure the job scheduler and grid execution environment. |
| Explanation | Informational message |
| Action | No action required |
| Explanation | Informational message |
| Action | No action required |
| Explanation | Informational message |
| Action | No action required |
| Explanation | Informational message |
| Action | The specified goal type is not supported. Supported goal types are Completion Time and Discretionary. |
| Explanation | The total outstanding jobs belonging to this job class have exceeded the configured limit. New jobs belonging to the class cannot be dispatched until some of the outstanding jobs complete. |
| Action | No action required |
| Explanation | Informational message |
| Action | No action required |
| Explanation | The specified grid endpoint has been quiesced. |
| Action | No user action is required. |
| Explanation | The specified grid endpoint has been resumed. |
| Action | No user action is required. |
| Explanation | The specified node-metadata file failed to load. |
| Action | Examine the system logs and referenced exception for the underlying failure. |
| Explanation | No application managed beans are running on the specified endpoint. |
| Action | No user action is required. |
| Explanation | An exception was encountered trying to retrieve the list of Application MBeans from the specified endpoint. |
| Action | Examine the system logs and referenced exception for the underlying failure. |
| Explanation | The server weight value was not set for the specified endpoint because it is not registered in the serverindex.xml file. |
| Action | No user action is required. Default value will be used. |
| Explanation | The transport state for the specified transport was not set on the specified endpoint because the endpoint is not registered in the serverindex.xml file. |
| Action | No user action is required. |
| Explanation | The specified serverindex.xml file failed to load. |
| Action | Examine the system logs and referenced exception for the underlying failure. |
| Explanation | An exception was detected preparing the job for placement. |
| Action | Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error. |
| Explanation | The Grid Application Placement could not initialize Bulletin Board services. |
| Action | See the problem determination information on the WebSphere Application Server Support Web page: https://ibm.biz/BdztgV. |
| Explanation | The Grid Application Placement could not initialize Bulletin Board services. |
| Action | See the problem determination information on the WebSphere Application Server Support Web page: https://ibm.biz/BdztgV. |
| Explanation | An exception was detected determining list of permitted endpoints for job. |
| Action | Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error. |
| Explanation | The specified application edition is not permitted. |
| Action | Verify that the application edition for your application is correct. |
| Explanation | The transaction class stats object could not be initialized for the specified transaction class. |
| Action | Verify that your Job Scheduler configuration is correct. |
| Explanation | The application stats object could not be initialized for the specified application name. |
| Action | Verify that your Job Scheduler configuration is correct. |
| Explanation | The module stats object could not be initialized for the specified application name and module name. |
| Action | Examine the exception in this message for problem determination. Check the logs, trace, and the First Failure Data Capture (FFDC) to find the most relevant root cause for this error. |
| Explanation | The Grid Scheduler statistic id is invalid. |
| Action | Correct the invalid value. |
| Explanation | The configuration change listener cannot be added. |
| Action | Verify that the endpoint and scheduler servers are running. |
| Explanation | The admin service handle was not found. |
| Action | Verify that the endpoint and scheduler servers are running. |
| Explanation | Unable to read grid job classes from the cell path directory. |
| Action | Verify that the file gridclassrules.xml exists in the endpoint server""s configuration directory. |
| Explanation | The gridclassrules.xml file cannot be read from the classification directory |
| Action | Verify that the file gridclassrules.xml exists in the endpoint server""s configuration directory. |
| Explanation | The deployment targets are not valid. |
| Action | Verify that the deployments targets are setup correctly. |
| Explanation | The endpoint event is unable to quiesce and is not registered with Grid Application Placement. |
| Action | Verify that the endpoint is listed in the Grid Application Placement nodes table. |
| Explanation | The endpoint is not registered and therefore cannot be resumed. |
| Action | Verify that the endpoint is listed in the Grid Application Placement nodes table. |
| Explanation | This message is for informational purposes only. |
| Action | No user action is required. |
| Explanation | This message is for informational purposes only. |
| Action | No user action is required. |
| Explanation | This message is for informational purposes only. |
| Action | No user action is required. |