Explanation | Part of the migration process is to create a service integration bus. This was unsuccessful. |
Action | Check the reason message given and FFDC logs for possible causes of the failure. |
Explanation | Part of the migration process is to add the named server to the service integration bus. This was unsuccessful. |
Action | Check the reason message given and FFDC logs for possible causes of the failure. |
Explanation | Part of the migration process is to create a WebSphere MQ client link. This was unsuccessful. |
Action | Check the reason message given and FFDC logs for possible causes of the failure. |
Explanation | One of the queues found in the configuration data being migrated could not be created in the new configuration. |
Action | Check the reason message given and FFDC logs for possible causes of the failure. |
Explanation | This exception is unexpected. The cause is not immediately known. |
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 result returned by the command indicates that it failed. |
Action | Check the reason message given for a possible cause of the failure. |
Explanation | When a server is a member of a bus, it should have one messaging engine defined for that bus. In this case, no messaging engines have been found. |
Action | Run configuration validation. |
Explanation | When a server is a member of a bus, it should have one messaging engine defined for that bus. In this case, more than one messaging engine has been found. |
Action | Run configuration validation. |
Explanation | An exception was created. |
Action | See the stack trace for details. |
Explanation | The server configuration is not valid. |
Action | Run configuration validation. |
Explanation | The supplied JMS server has no "was.shortName" property, or the "was.shortName" property defines a null short name. |
Action | Ensure that the JMS server identified above has a "was.shortName" property correctly defined. |