Transactions: Resource statistics - integrity information
The integrity information statistics show the potential integrity exposures that may have occurred during transaction execution as a result of inabilities to shunt UOWs, or forcing of shunted UOWs to complete regardless of the decisions made by participating systems.
| DFHSTUP name | Field name | Description |
|---|---|---|
| Trans ID | XMRTI | The transaction identifier associated with the transaction definition.
Reset characteristic: not reset |
| Indoubt Wait | XMRIWTOP | The indicator of whether the transaction has been defined to support Indoubt
Waiting in the event of an two-phase commit indoubt window failure. This means the failing UOW will
be shunted by the CICS® recovery manager awaiting resynchronisation with its coordinator. The indoubt wait option
can have the following settings:
Reset characteristic: not reset |
| Indoubt Wait timeout | XMRITOV | The indoubt wait timeout limit defined for this transaction, specified in
minutes. This value has meaning only if the transaction is also defined to be able to wait indoubt
(see XMRIWTOP). A value of zero, specifies that there is no timeout should this transaction be
shunted by the CICS
recovery manager. Reset characteristic: not reset |
| Indoubt Action | XMRIACTN | This is an indicator of which way this transaction will commit its UOWs in the
event of not being able to wait indoubt (shunted), when an indoubt wait failure occurs. Or if the
transaction had been waiting that, the timeout value specified has expired. Both of these events
will force a resolution of the UOW in the direction specified by this field. The values can be :
Reset characteristic: not reset |
| Indoubt Waits | XMRIWAIT | The number of indoubt waits (shunts) that have occurred for UOWs executing on
behalf of this transaction. Reset characteristic: not reset |
| Indoubt action forced: Trandefn | XMRFATXN | The number of times this transaction id had a UOW that could not be shunted when
an indoubt failure occurred, because the transaction definition for this transaction id specified
that it could not support indoubt waiting (ie. XMRIWTOP = XMTIWTN). The UOW would have been forced
to resolve in the direction specified by XMRIACTN, regardless of the actions taken by any other
participating region in this distributed UOW. Reset characteristic: not reset |
| Indoubt action forced: Timeout | XMRFAIT | The number of times this transaction id had a UOW that, although shunted because
of an indoubt failure, had the wait for resynchronization with its recovery coordinator terminated
prematurely, because the indoubt wait timeout value (XMRITOV) had been exceeded. The UOW would have
been forced to resolve in the direction specified by XMRIACTN, regardless of the actions taken by
any other participating region in this distributed UOW. Reset characteristic: not reset |
| Indoubt action forced: Operator | XMRFAOP | The number of times this transaction id had a UOW that although shunted because
of an indoubt failure, had the wait for resynchronization with its recovery coordinator terminated
prematurely, because an operator (CEMT) or system command forced a resolution. The UOW would have
been forced to resolve in the direction specified by XMRIACTN by default, or in the direction
specified by the operator, regardless of the actions taken by any other participating region in this
distributed UOW. Reset characteristic: reset to zero |
| Indoubt action forced: No waiting | XMRFANW | The number of times this transaction id had a UOW that could not be shunted when
an indoubt failure occurred, although the transaction definition specified that it could (XMRIWTOP =
XMRIWTY), because the resource managers (RMIs) or CICS resources or CICS connections used by the UOW could not support indoubt
waiting (shunting). The UOW would have been forced to resolve in the direction specified by
XMRIACTN, regardless of the actions taken by any other participating region in this distributed UOW.
Reset characteristic: reset to zero |
| Indoubt action forced: Other | XMRFAOT | The number of times this transaction id had a UOW that although shunted because
of an indoubt failure, had the wait for resynchronization with its recovery coordinator terminated
prematurely, for reasons other than those already referenced in this table. This could be, for
example, a recovery coordinator which has been cold started, a resynchronization protocol violation
or failure, or because the level of resource manager (RMI) adaptor has not yet been changed to
support indoubt resolution. The UOW would have been forced to resolve in the direction specified by
XMRIACTN, regardless of the actions taken by any other participating region in this distributed UOW.
Reset characteristic: reset to zero |
| Action mismatch | XMRAMISM | The number of times this transaction id had a UOW that was forced to resolve
using the indoubt action attribute, whether by definition, option or operator override (as detailed
in the fields already described in this table), and on doing so detected an indoubt action attribute
mismatch with a participating system or resource manager (RMI). For example, a participating system
in a distributed UOW resolves its work forward while other systems back out theirs. The opposite
also applies. Reset characteristic: reset to zero |