Explanation | An exception occurred when the command ran. The exception is usually caused by incorrect parameter entry. |
Action | Correct the input parameters and rerun the command. |
Explanation | The required parameter for a command was set to null or is of zero length. |
Action | Verify that all the required parameters are getting set and re-issue the command. |
Explanation | No managed node was found with given managed node name. |
Action | Verify that all the managed node names identify registered managed nodes. |
Explanation | A managed node with the same node name or UUID is already registered with this JobManager. |
Action | Retry the registration using an alias for new managed node. |
Explanation | Job manager profileKey returned null, this operation will fail. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | All group members must be of the same type. |
Action | Verify that all members are of the same type and the group supports that type. |
Explanation | The Number of devices to be deleted is more than the number available in the group. |
Action | Verify that number of devices to be deleted is less than or equal to the number available in the group. |
Explanation | An unknown group name was passed. The delete operation failed. |
Action | Verify that all the groups to be deleted are valid groups. |
Explanation | A group with similar name already exists on this job manager. |
Action | Use a unique group name to create a group on this job manager. |
Explanation | Only one parameter needs to be set for this command. |
Action | Verify that only one parameter is set for this command. |
Explanation | Only one target can be specified for job submission. |
Action | Verify that only one target is specified for job submission. |
Explanation | At least one of the target needs to be specified for the job to be submitted. |
Action | Verify that only one target is specified for job submission. |
Explanation | No group was found with the provided group name. |
Action | Verify that the name identifies a valid group. |
Explanation | No information is available for the managed node. |
Action | Verify that the name identifies a valid managed node. |
Explanation | The query has unknown keys. |
Action | Verify that the keys for the query are correct. |
Explanation | The backup location is not empty or not writeable. |
Action | Provide a new location to backup the job manager data or use the force option to overwrite the file. |
Explanation | The backup location is not readable. No valid backup file was provided to restore from. |
Action | Provide a valid backup file to restore the job manager from. |
Explanation | Backup file location is was empty. Backup file location is a required field. |
Action | Provide a valid backup file to restore from. |
Explanation | Maximum return size for the query is not valid. |
Action | Provide a valid maximum return size for the query. |
Explanation | Job manager has no information regarding the provided job type. |
Action | Provide a valid registered job type. |
Explanation | Value for the key are of incompatible type. |
Action | Provide valid value types of same key. |
Explanation | This error is usually received if the query is not valid or is not formatted correctly. |
Action | Inspect the query and make sure it is valid. |
Explanation | Internal exception was received while processing users request. |
Action | Make sure that a valid input is provided. |
Explanation | Message header sent in the email after the job completion. |
Action | None. |
Explanation | Message sent in the email after the job completion. |
Action | None. |
Explanation | maxResult for the query has been reached. |
Action | Make sure that a valid input is provided. |
Explanation | Managed Resource with the provider identifier was not found in the database. |
Action | Make sure that a valid input is provided. |
Explanation | Missing corresponding data for either user name or password |
Action | Make sure user name and password are both present during job submission. |
Explanation | The job is being rejected because security information is not valid. |
Action | Make sure correct security information is provided for this job. |
Explanation | Usage of restoreJobManager command. |
Action | Read the usage of this command since this ia a distructive command. |
Explanation | Message before starting the JobManager restore of the command. |
Action | No action is needed from user. |
Explanation | Message after successful restore of JobManager. |
Action | No action is needed from user. |
Explanation | Exception received during execution of restore command. |
Action | Read the root cause of the exception and follow follow the instruction. |
Explanation | The current user does not have the appropriate credential to run this command. |
Action | Supply appropriate user id and password to this command. |
Explanation | Not supported value provided for a valid query key. |
Action | Modify the query to support valid values only. |
Explanation | The system clocks for all the systems that communicate with each other and have WebSphere Application Server installed must be synchronized. Otherwise, you might experience errors, such as security tokens no longer being valid. |
Action | To change the system clock, first stop all the servers on the system. After you stop the servers, change the system clock, and then restart the servers. If you change the system clock on one system, ensure the clocks on all systems that communicate with each other and have WebSphere Application Server installed are synchronized. |
Explanation | There is a problem retreiving the job manager's RSA certificate. Job manager clients are unable to securely connect to the job manager without the RSA certificate. |
Action | Refer to the exception. Check FFDC for certificate related problems. Check the job manager's RSA certificate, and update if it has expired. |