| Explanation | The job scheduler may not have been configured. |
| Action | Verify that the job scheduler has been configured successfully. |
| Explanation | Internal error. |
| Action | Contact IBM Support. |
| Explanation | The grid endpoint sensor high availability component has successfully been activated. |
| Action | None |
| Explanation | The grid endpoint sensor high availability component has successfully been deactivated. |
| Action | None |
| Explanation | Internal error. |
| Action | Contact IBM Support. |
| Explanation | This is an internal problem. |
| Action | Contact IBM Support. |
| Explanation | This is an internal problem. |
| Action | Contact IBM Support. |
| Explanation | Errors detected during MBean lookup. |
| Action | Verify that the job scheduler is running. |
| Explanation | Errors detected during the specified MBean operation. |
| Action | Verify that the job scheduler is running. |
| Explanation | Internal error. |
| Action | Contact IBM Support. |
| Explanation | Internal error. |
| Action | Contact IBM Support. |
| Explanation | Indicates normal completion of Job scheduler message listener interface initialization. |
| Action | No user action required. |
| Explanation | Indicates normal listener initialization on indicated message queue. |
| Action | No user action required. |
| Explanation | Indicates Job scheduler is not listening on the indicated queue because it is not defined. |
| Action | No user action required. |
| Explanation | Indicates Job scheduler is not listening on the indicated queue due to the indicated initialization error. |
| Action | Ensure queue definition is correct. |
| Explanation | Indicates Job scheduler is unable to send outbound messages on indicated queue due to the indicated initialization error. |
| Action | Define required queue. |
| Explanation | Indicates Job scheduler is unable to send outbound messages on indicated queue due to the indicated initialization error. |
| Action | Ensure queue definition is correct. |
| Explanation | Indicates Job scheduler is unable to send outbound messages on indicated queue due to the indicated runtime error. |
| Action | Contact IBM service. |
| Explanation | Indicates Job scheduler received indicated exception. Job scheduler listener interface can continue normal operation. |
| Action | No user action required. |
| Explanation | Indicates Job scheduler received indicated exception. Job scheduler listener interface is disabled. |
| Action | Contact IBM Service. |
| Explanation | Indicates valid command syntax. |
| Action | No user action required. |
| Explanation | Indicates Job scheduler listener interface submitted indicated job. |
| Action | No user action required. |
| Explanation | Indicates Job scheduler listener interface failed to submit indicated job from either repository or file due to indicated error. |
| Action | Ensure correct job source information is specified. |
| Explanation | Indicates job submission request to Job Scheduler listener interface (e.g. via WSGrid command) was rejected because indicated required keyword was not specified. |
| Action | Specify required keyword. |
| Explanation | Indicates job submission request to Job Scheduler listener interface (e.g. via WSGrid command) was rejected because indicated mutually exclusive keywords were specified. |
| Action | Delete the unwanted keyword. |
| Explanation | Indicates job submission request to Job Scheduler listener interface (e.g. via WSGrid command) was rejected because of syntax error on indicated keyword. |
| Action | Correct syntax error. |
| Explanation | Indicates job submission request to Job Scheduler listener interface (e.g. via WSGrid command) encountered an unrecognized keyword. The keyword is ignored. The job submission continues. |
| Action | Remove unrecognized keyword. |
| Explanation | Indicates job submission request to Job Scheduler listener interface (e.g. via WSGrid command) failed due to indicated exception. |
| Action | Contact IBM Service. |
| Explanation | Indicates installation of unit test environment commencing for specified server in specified profile. |
| Action | No user action required. |
| Explanation | Indicates unit test environment successfully installed. |
| Action | No user action required. |
| Explanation | Indicates unit test environment failed to install correctly. |
| Action | Contact IBM Service. |
| Explanation | Indicates unrecognized option specified on action keyword. |
| Action | Specify valid action. |
| Explanation | Indicates unit test environment was not successfully installed because the required input file could not be found. |
| Action | Specify correct location of required input file. |
| Explanation | Indicates unit test environment was not successfully installed because the required input file is corrupted. |
| Action | Contact IBM Service. |
| Explanation | Indicates unit test environment was not successfully installed because specified profile was not found. |
| Action | Specify valid profile. |
| Explanation | Indicates unit test environment was not successfully installed because specified server was not found. |
| Action | Specify valid server. |
| Explanation | Indicates unit test environment was not successfully installed because specified server is not valid. The target server must be a standalone WebSphere Application Server. It cannot be part of a Network Deployment cell. |
| Action | Specify valid server. |
| Explanation | Indicates unit test environment was not successfully installed due to the specified error. |
| Action | Contact IBM Service. |
| Explanation | Indicates valid command syntax. |
| Action | No user action required. |
| Explanation | Indicates packaging started for specified application. |
| Action | No user action required. |
| Explanation | Indicates packaging completed successfully for specified application. |
| Action | No user action required. |
| Explanation | Indicates packaging did not complete successfully for specified application. |
| Action | Correct problems indicated by accompanying messages. |
| Explanation | Indicates packaging did not complete successfully due to specified error. |
| Action | Contact IBM Service. |
| Explanation | Indicates packaging did not complete successfully because application is name not valid. |
| Action | Specify valid application name. |
| Explanation | Indicates packaging did not complete successfully because output file name is name not valid. |
| Action | Specify valid output file name. |
| Explanation | Indicates packaging did not complete successfully due to missing required input parameter. |
| Action | Review syntax and specify all required parameters. |
| Explanation | Indicates packaging did not complete successfully due to syntax error on or around specified command text. |
| Action | Review syntax and specify valid syntax. |
| Explanation | Indicates packaging did not complete successfully due to specified syntax error. |
| Action | Review syntax and specify valid syntax. |
| Explanation | Indicates packaging did not complete successfully because same JNDI name was specified more than once. |
| Action | Ensure all JNDI names in package are unique. |
| Explanation | Indicates packaging did not complete successfully because specified class name is not valid. |
| Action | Specify valid class name. |
| Explanation | Indicates packaging did not complete successfully because specified class file is not found. |
| Action | Specify valid class file name. |
| Explanation | Indicates valid command syntax. |
| Action | No user action required. |
| Explanation | Indicates job scheduler environment successfully configured. |
| Action | No user action required. |
| Explanation | Indicates job scheduler environment failed to configure correctly. |
| Action | Contact IBM Service. |
| Explanation | Indicates grid endpoint environment successfully configured. |
| Action | No user action required. |
| Explanation | Indicates grid endpoint environment failed to configure correctly. |
| Action | Contact IBM Service. |
| Explanation | Indicates job scheduler environment was not successfully configured due to the specified error. |
| Action | Contact IBM Service. |
| Explanation | Indicates grid endpoint environment was not successfully configured due to the specified error. |
| Action | Contact IBM Service. |
| Explanation | Indicates unsupported configuration option specified. |
| Action | Specify valid configuration option. |