Explicação | Reply to a previous message was not valid. The previous message is reissued. |
Ação | Issue a valid reply to the reissued message. |
Explicação | A global transaction in which OTS was involved has exceeded its maximum processing time. The transaction was marked for rollback only. Any further method dispatches in this transaction will cause a CORBA::TRANSACTION_ROLLEDBACK exception to be thrown. |
Ação | Examine the application for a possible coding error. The transaction timeout value may have been explicitly set by the application to any value less than or equal to the value of the transaction_maximumTimeout environment variable. If a timeout was not explicitly set, it will default to the value in the transaction_defaultTimeout environment variable. Additional information: If the URID is non-zero, additional information about the transaction and any involved resource managers can be obtained through the RRS panels. If the URID is zero, this server had not done any transactional work in this branch of the transaction. The XID, written in <gtrid:bqual:formatid> format, can also be used to determine additional information about the transaction in a distributed environment. |
Explicação | WebSphere Application Server for z/OS failed in the resource recovery service indicated and that service completed with a hexadecimal return code indicated. |
Ação | See return codes for resource recovery services in the MVS Programming: Resource Recovery book for additional information. |
Explicação | This message is issued after a UR goes in-Doubt with RRS. It is only issued after this debug aid has been explicitly enabled with a modify command |
Ação | This is an internal programming error. For further information on resolving this error, please consult the IBM WebSphere Application Server for z/OS Support website at: http:www-3.ibm.com/software/webservers/appserv/zos_os390/support.html This site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided. |
Explicação | WebSphere Application Server for z/OS has detected that one or more resource managers involved in the global transaction, whose ID is displayed in the message, has indicated that some resources were assigned an outcome that was different than the overall outcome of the global transaction. For example, if the overall outcome of the transaction was commit, some of the resources that were involved in the transaction have been rolled back. |
Ação | This message contains the transaction identifier for which the heuristic condition occurred. Review the RRS transaction logs via the ATRFPCMN dialog facility provided by zOS, to determine which resources are inconsistent, and follow the procedures for that particular resource manager to restore or correct the state of those resources. Ref: MVS Programming: Resource Recovery. Document Number: GC28-1739-0y |
Explicação | WebSphere Application Server for z/OS has detected that one or more resource managers involved in the global transaction, whose ID is displayed in the message, may have assigned an outcome that was different than the overall outcome of the global transaction. |
Ação | This message contains the transaction identifier for which the heuristic condition may have occurred. Review the RRS transaction logs via the ATRFPCMN dialog facility provided by zOS, to determine if any resources are inconsistent, and follow the procedures for that particular resource manager to restore or correct the state of those resources. In addition, because this condition may have occurred when transactional optimizations were used, RRS may be unaware of the transactional outcome, because of a delegation of commit responsibilites to the single resource manager. In this case, the outcome of the single resource manager is unknown and a hazard condition exists. To determine the outcome, follow documented procedures for the given resource manager to determine the outcome or to correct any resources involved in the global transaction as displayed in this message. Ref: MVS Programming: Resource Recovery. Document Number: GC28-1739-0y |
Explicação | The transaction services component has initiated transaction restart and recovery with RRS. |
Ação | None. |
Explicação | The transaction services component has received restart units of recovery from RRS. The counts indicate the number of units of work with states at a previous server termination such that some recovery action must be performed during this restart. The IN-BACKOUT count specifies the number that were in the process of backing out. These must undergo recovery to restore resources modified by them to their previous consistent state. The IN-DOUBT count specifies the number that were interrupted between phase 1 and phase 2 of the commit process. These must undergo recovery to ensure resources modified by them are unavailable until their indoubt status is resolved. The IN-COMMIT count specifies the number that had started but not completed phase 2 of the commit process. These must undergo recovery to complete the commit process. |
Ação | None. |
Explicação | The transaction services restart process has completed. All units of recovery have been resolved. |
Ação | None. |
Explicação | During the RRS log name exchange process, RRS indicated that no previous log name was set. When restart is initiated, no incomplete RRS units of recovery will be returned. |
Ação | None. |
Explicação | During the RRS log name exchange process, RRS indicated that a log name was previouly set. When restart is initiated, some incomplete RRS units of recovery may be returned. |
Ação | None. |
Explicação | The transaction services restart process has completed. All units of recovery have been resolved. |
Ação | None. |
Explicação | The transaction service restart processing for the given URID has completed. |
Ação | None. |
Explicação | The transaction services restart processing has not completed within the configured time. The operator has indicated (by reply) that the server should no longer attempt recovery. Some units of recovery have not been completed and forgotten. |
Ação | None. |
Explicação | The transaction services restart processing has not completed within the configured time. The operator has indicated (by reply) that the server should continue to attempt transaction completion for an additional duration time specified by the transaction_recoveryTimeout environment variable. |
Ação | None. |
Explicação | The transaction services restart processing is still trying to resolve some incomplete restart units of recovery in restart and recovery mode. This message is issued at regular intervals to update the installation on the progress of the transaction recovery process. |
Ação | None. |
Explicação | While in restart and recovery mode, WebSphere was not able to contact the recovery coordinator for the transaction branch with the XID provided. The host name and port were obtained from the IOR for the recovery coordinator. If the IOR points to a WebSphere/390 object, the server name was also written. |
Ação | Ensure that the server and host can be reached by this WebSphere server. If connectivity can not be restored, the transaction information in this message can be used to manually resolve the outcome of the transaction with the RRS ISPF panels or the ATRSRV macro. Note that manually resolving the transaction can lead to mixed transaction outcomes across resource managers and servers. |
Explicação | While in restart and recovery mode, WebSphere was not able to contact the recovery coordinator for the transaction branch with the XID provided. Since the outcome could not be determined, this server could not provide a transaction resolution to the resources registered with the transaction coordinator on this server for the transaction branch with the XID information in this message. |
Ação | None. |
Explicação | While in restart and recovery mode, WebSphere was not able to successfully commit or rollback the resource involved in the transaction branch described by the XID information in this message. The outcome of the transaction has been determined but can not be completed until all subordinate OTS resources have been told the outcome. |
Ação | Ensure that the server and host can be reached by this WebSphere server. If connectivity can not be restored, the transaction information in this message can be used to manually resolve the outcome of the transaction for the subordinate nodes. The OTS interests in the RRS UR with the provided URID can be removed with the RRS ISPF panels or the ATRSRV macro. |
Explicação | While in restart and recovery mode, WebSphere was not told to forget an heuristic outcome for a transaction it was involved in. A transaction that is not forgotten is not complete as the RRS UR with the provided URID is still active. |
Ação | Ensure that the server and host in this message can successfully connect this server. If connectivity can not be restored or the superior does not know of the heuristic outcome, the RRS ISPF panels or ATRSRV macro can be used to remove the OTS interests in the UR with the provided URID. |
Explicação | The transaction services restart processing is still trying to resolve some incomplete restart units of recovery in restart and recovery mode. This message is issued at regular intervals to update the installation on the progress of the transaction recovery process. Since each XA resource manager maintains its own logs, it is impossible to tell how many units of recovery need to be resolved until each resource manager is contacted. |
Ação | None. |
Explicação | Transactional recovery for this server is currently executing on a peer server using the HA recovery framework. This server must wait for the HA recovery process to terminate before it can take over the transactional logs for this server. |
Ação | None. The peer server has been notified that it must terminate recovery. |
Explicação | The transaction service recovery processing was unable to resolve all incomplete transactions in the configured amount of retries. This is generally due to a communications failure with a another server that was involved in the transaction. |
Ação | If the server should continue its attempts to resolve incomplete transactions for the duration specified by the transaction_heuristicRetryLimit environment variable, reply 'CONTINUE.' If the server should not continue its attempts to resolve incomplete transactions, a reply of 'TERMINATE' will stop the recovery process. Information about the unresolved transactions can be found in the server's job output. This information can be used to resolve transactions using the RRS panels. |
Explicação | The transaction services recovery processing has not completed within the configured amount of retries. The operator has indicated (by reply) that recovery process should continue to attempt transaction completion for an additional amount of times specified by the transaction_heuristicRetryLimit environment variable. |
Ação | None. |
Explicação | The transaction services recovery processing has been terminated because the operator has indicated (by reply) that recovery process should stop. Some Units of Recovery have not been completed. |
Ação | None. |
Explicação | The transaction services recovery processing has not completed within the configured amount of retries. The transaction's outcome has been heuristically set to commit according to configured environment variable: transaction_LPSHeuristicCompletion. |
Ação | None. |
Explicação | The transaction services recovery processing has not completed within the configured amount of retries. The transaction's outcome has been heuristically set to rollback according to configured environment variable: transaction_LPSHeuristicCompletion. |
Ação | None. |
Explicação | The transaction services recovery processing has not completed within the configured amount of retries. The transaction's outcome has been heuristically set to manual according to configured environment variable: transaction_LPSHeuristicCompletion. |
Ação | Access the RRS panels to view and resolve any pending transactions. |
Explicação | The transaction services recovery processing was terminated because recovery for the failed server is already taking place on another server. The transaction service could not obtain the resources needed because they are being held by another server attempting perform recovery on the same failed server. |
Ação | This is an internal programming error. For further information on resolving this error, please contact the WebSphere Support team. |
Explicação | The transaction services recovery processing will be terminated because server for which recovery is taking place has been restarted. If recovery was not completed on the peer server, it will continue during server restart. |
Ação | None. |
Explicação | The transaction service attempted to drive a transactional object residing on the server, host and port specified in the message. The security credentials supplied on the call were rejected by the remote server. |
Ação | The security policy of the remote server may have changed since the transaction was started. If this is the case, update the security policy on the remote server temporarily to allow this transaction to complete. The operation will retry automatically. |