Explanation | A request was made to obtain the UserTransaction service, but no UserTransaction service has been wired to this bundle. |
Action | If access to the UserTransaction is required, use the OSGi console to investigate why no UserTransaction service has been wired to this bundle. |
Explanation | A request was made to fetch the Transaction object but an unexpected error occurred. |
Action | Check the logs for previous errors or FFDCs. |
Explanation | The current global transaction has timed out and therefore has been rolled-back. |
Action | Ensure the global transaction finishes within the allowed time frame or increase the timeout. |
Explanation | The invocation of the indicated service failed. The return code is a hexadecimal integer. |
Action | For additional information on the return code see the MVS Programming: Resource Recovery book. If the problem persists, contact your next level of support. |
Explanation | There were outstanding transactions at the time the resource manager was unregistered. All outstanding resources will go through recovery processing the next time the server is restarted. |
Action | Make sure all required settings for performing transactional work with RRS capable resources is in place. Review the server logs for more information. If the problem persists, contact your next level of support. |
Explanation | The specified resource manager has restarted with RRS. All reported unresolved units of recovery will undergo recovery. |
Action | No action is required. |
Explanation | Recovery processing for the specified resource manager has completed. All reported unresolved units of recovery have been recovered. |
Action | No action is required. |
Explanation | The RRS native context manager is shutting down. The context manager is waiting for all units of work with an associated native context to complete. |
Action | No action is required. The RRS native context manager will continue termination after all units of work have completed. |
Explanation | The RRS native context manager is shutting down. The context manager is waiting for all units of work with an associated native context to complete. |
Action | No action is required. The RRS native context manager will continue termination after all units of work have completed. |
Explanation | The RRS native context manager is shutting down, after waiting for active work to quiesce. The context manager is terminating the context identified in this message. The context is associated with a unit of work, and the unit of work will be backed out. |
Action | No action is required. One or more of your resource managers might report an error if they were processing work at the time the context ended. |
Explanation | The RRS native resource manager is shutting down. There are still active transactions that are using native RRS resources, such as type 2 database connections. The native resource manager will wait for these transactions to complete before shutting down. |
Action | No action is required. The resource manager will resume shutdown after the transactions have completed, or after the specified wait time has elapsed. If the maximum wait time has elapsed, message CWLIB0102W will indicate which transactions were still active. |
Explanation | The RRS native transaction manager service has stopped and is no longer connected to RRS. The transaction branch cannot be completed because RRS cannot be notified of the outcome. The server must be restarted to allow the transaction manger to resync with RRS and resolve the transaction. |
Action | Restart the server. |
Explanation | A RRS unit of recovery was found to have outstanding resource interests at the end of the unit of work. |
Action | Verify that the RRS capable resources being used are not operating outside of a transaction scope. If the problem persists, contact your next level of support. |
Explanation | The configured resource manager prefix must be 1 to 8 characters long, and it can only contain alphanumeric (a-z,A-Z,0-9) and national (@,$,#) characters. |
Action | Verify that the configured resource manager prefix follows the length and character requirements. If the problem persists, contact your next level of support. |
Explanation | The configuration update to set the resource manager prefix at run time is ignored. |
Action | Configure the resource manager prefix prior to server startup or prior to configuring the zosTransaction-1.0 feature. If the problem persists, contact your next level of support. |
Explanation | The authorization check that validates the user privileges against the configured resource manager prefix name has failed with the mentioned return codes. |
Action | Verify that the configured resource manager prefix follows the name, length, and character requirements. Verify that the prefix name was not configured in error. Verify that the user has been granted the appropriate privileges to utilize the prefix name. If the problem persists, contact your next level of support. |
Explanation | The specified thread is terminating and the RRS unit of recovery associated with the context has unresolved interests. Attempts to roll back the RRS unit of recovery have failed. |
Action | Verify that the RRS capable resource managers being used are not operating outside of a transaction scope. One or more of your resource managers may report an error if they were processing work at the time the context ended. If the problem persists, contact your next level of support. |
Explanation | The specified thread is ending and the RRS unit of recovery was found to have outstanding resource interests. |
Action | Verify that the RRS capable resource managers being used are not operating outside of a transaction scope. One or more of your resource managers may report an error if they were processing work at the time the unit of recovery was rolled back. If the problem persists, contact your next level of support. |
Explanation | An active WS-AT transaction matching the requested global transaction id cannot be found. |
Action | Refer to logs for error details. |
Explanation | A transaction participant matching the requested id cannot be found as part of the global transaction. |
Action | Refer to logs for error details. |
Explanation | The transaction timeout expired and the transaction was rolled-back. |
Action | Refer to logs for error details. |
Explanation | An error occurred when invoking the system web services. |
Action | Refer to logs for error details. |
Explanation | An error was received when processing the transaction function. |
Action | Refer to logs for error details. |
Explanation | WS-AT uses an SSL connection to secure the internal communication. |
Action | none. |
Explanation | WS-AT uses a proxy for the internal communication. |
Action | none. |
Explanation | An error occurred when processing a transaction manager resource. |
Action | Refer to logs for error details. |
Explanation | An error occurred when trying to obtain the endpoint for the system web services. |
Action | Refer to logs for error details. |
Explanation | Proxy address for WS-AT must start with http(s):// |
Action | Modify the externalURLPrefix address to start with http(s):// |
Explanation | Proxy address for WS-AT must start with https:// when SSL is enabled. |
Action | Modify the externalURLPrefix address to start with https:// when SSL is enabled. |