Explanation | The workspace could not be initialized. |
Action | Check the nested exception for additional information. |
Explanation | The saved context information could not be read. |
Action | Check the nested exception for additional information. |
Explanation | The specified string could not be parsed. |
Action | Check the string format. |
Explanation | The context could not be created because a context with the same name already exists. |
Action | Pick a context name that does not already exist. |
Explanation | The specified file could not be deleted. |
Action | Check the nested exception for additional information. |
Explanation | The specified context could not be released. |
Action | Check the nested exception for additional information. |
Explanation | The specified context could not be saved. |
Action | Check the nested exception for additional information. |
Explanation | The configuration repository could not be gotten. |
Action | Check the nested exception for additional information. |
Explanation | The state of the master repository could not be checked. |
Action | Check the nested exception for additional information. |
Explanation | The workspace session is not valid for one of the following reasons: - The same user ID has more than one session ID logged onto the workspace. The workspace for the first session ID became not valid. - The caller to the workspace has released the worskpace, but has continued to use it. |
Action | Have the caller to the workspace APIs: - Check why one user ID is logged on to the workspace with two session IDs. - Discontinue using the workspace after the workspace has been released. |
Explanation | The session ID could not be deleted. |
Action | Check the nested exception for additional information. |
Explanation | The session ID could not be created. |
Action | Check the nested exception for detail. |
Explanation | The specified file could not be extracted from the configuration repository. |
Action | Check the nested exception for additional information. |
Explanation | The specified context could not be found for a given name. |
Action | Check if the context exists. |
Explanation | The specified input stream could not be gotten. |
Action | Check the nested exception for additional information. |
Explanation | The specified ouput stream could not be gotten. |
Action | Check the nested exception for additional information. |
Explanation | The digest could not be gotten from the file system. |
Action | Check the nested exception for additional information. |
Explanation | The digest could not be saved to the file system. |
Action | Check the nested exception for additional information. |
Explanation | The file could not be read for synchronization. |
Action | Check the nested exception for additional information. |
Explanation | The repository adapter could not be gotten. |
Action | Check the nested exception for additional information. |
Explanation | The root for meta data definition is incorrect. |
Action | Check the value of user.install.root system property. |
Explanation | The contect type could not be gotten or cannot find the specified context type in the meta data definition. |
Action | Check the meta data information. |
Explanation | File validation for the master configuration repository update failed. |
Action | Refer to the trace output that accompanies this message for more information about the root cause. |
Explanation | The specified file could not be copied due to the specified exception. |
Action | Refer to the trace output that accompanies this message for more information about the root cause. |
Explanation | The context name contains a character that is not valid. |
Action | Do not use the specified character as it is not valid. |
Explanation | The user did not have the right authority to access the file. |
Action | Give proper authority to the user to access the file. |
Explanation | The resource object could not be gotten during validation on the z/OS operating system. |
Action | Refer to the trace output that accompanies this message for more information about the root cause. |
Explanation | The message indicates whether the workspace consistency check is enabled or disabled. |
Action | No user action is required. |
Explanation | The configuration change being made exceeds the license retrictions in effect, for example, the maximum number of clusters or members in a cluster. |
Action | Make configuration changes within the license restrictions. |
Explanation | The configuration change could not be checked against any licence restrictions. The license restriction data might be corrupted. |
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 | The extent could not be loaded. |
Action | Check the nested exception for additional information. |
Explanation | The specified resource could not be loaded from the specified context. |
Action | Check the nested exception for additional information. |
Explanation | The resource could not be saved. |
Action | Check the nested exception for additional information. |
Explanation | The specified resource could not be merged for the specified context. |
Action | Check the nested exception for additional information. |
Explanation | The specified server entry in the serverindex.xml file does not have a corresponding server in the configuration. This extra server entry will be removed from the serverindex.xml file. |
Action | Check the nested exception for additional information. |
Explanation | The specified deployed application in the serverindex.xml file does not have a corresponding deployment.xml file in the configuration. This extra deployed application will be removed from the serverindex.xml file. |
Action | Check the nested exception for additional information. |
Explanation | The source file is not available for copying due to a product internal error. |
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/ . |