Explanation | The managesdk request requires a single task parameter. |
Action | Ensure your managesdk request contains a single task parameter and submit the request again. |
Explanation | The managesdk request requires a single task parameter. |
Action | Ensure your managesdk request contains a single task parameter and submit the request again. |
Explanation | No value was specified for paramerer on the managesdk request. |
Action | Provide a value for parameter and try the managesdk request again. |
Explanation | When used both parameters must both be specified. |
Action | Provide a value for both parameters and try the managesdk request again. |
Explanation | The sdk name specified on the managesdk request is not available. |
Action | Issue the managesdk -listAvailble command to get a list of the available sdk names. |
Explanation | The requested task requires the parameter that was not specified on the managesdk command. |
Action | Issue the managesdk request again and include the required parameter. |
Explanation | An unexpected exception was caught while performing the requested managesdk operation. |
Action | Resolve the cause of the exception and try the managesdk request again. |
Explanation | A parameter passed on the managesdk command is not one of the supported parameters. |
Action | Correct or remove the bad parameter and try the managesdk request again. |
Explanation | The -profileName parameter was specified with a value that is not a valid profile name. |
Action | Correct the -profileName parameter value and try the managesdk request again. |
Explanation | An attempt to locate a script failed. |
Action | Contact IBM service. |
Explanation | The task requested acts on a single profile but one was not specified. |
Action | Request the task again using the -profileName parameter along with a valid profile name. |
Explanation | The variable was not defined or had no value in the file. |
Action | Verify that script variable exists in file and that it has a valid value. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | The requested task does not accept the -profileName parameter and it will be ignored. |
Action | none. |
Explanation | The requested task does not accept the parameter and it will be ignored. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | none. |
Action | none. |
Explanation | The master configuration repository for a federated profile has been changed but not synchronized by the managesdk task. |
Action | You can initiate the synchronization operation explicitly or configure the node agent to synchronize nodes periodically. |