This section contains the following statistics:
These statistics can be accessed online using the EXEC CICS® COLLECT STATISTICS RECOVERY command, and are mapped by the DFHRMGDS DSECT. For programming information about the EXEC CICS COLLECT STATISTICS command, see the CICS System Programming Reference manual.
DFHSTUP name | Field name | Description |
---|---|---|
Total number of syncpoints (forward) | RMGSYFWD | is the total number of syncpoint requests to commit forward.
Reset characteristic: reset to zero
|
Total number of syncpoints (backward) | RMGSYBWD | is the total number of syncpoint requests to commit backward
(for example, EXEC CICS SYNCPOINT ROLLBACK).
Reset characteristic: reset to zero
|
Total number of resynchronizations | RMGRESYN | is the total number of resynchronization requests.
Reset characteristic: reset to zero
|
Total shunted UOWs for indoubt failure | RMGTSHIN | is the total number of units of work that lost connection
to their recovery coordinator during syncpoint processing and had to be shunted
for indoubt failure, but have now completed.
Note that this value does not include those units of work that are currently shunted for indoubt failure. Reset characteristic: reset to zero
|
Total time shunted for indoubt failure | RMGTSHTI | is the total time (STCK) that the units of work shunted
for indoubt failure (RMGTSHIN) spent waiting in this condition, but have now
completed.
Note that this value does not include those units of work that are currently shunted for indoubt failure. Reset characteristic: reset to zero
|
Total shunted UOWs for commit/backout failure | RMGTSHRO | is the total number of units of work that had to be shunted
for commit/backout failure because a local resource manager could not perform
commit/backout processing at this time on behalf of the UOW during syncpoint,
but have now completed.
Note that this value does not include those units of work that are currently shunted for commit/backout failure. Reset characteristic: reset to zero
|
Total time shunted for commit/backout failure | RMGTSHTR | is the total time (STCK) that the units of work shunted
for commit/backout (RMGTSHRO) failures spent waiting in this condition, but
have now completed.
Note that this value does not include those units of work that are currently shunted for commit/backout failure. Reset characteristic: reset to zero
|
Current shunted UOWs for indoubt failure | RMGCSHIN | is the current number of units of work that lost the connection
to their recovery coordinator during syncpoint processing, and have been shunted
for indoubt failure.
Reset characteristic: reset to zero
|
Current time shunted for indoubt failure | RMGCSHTI | is the total time (STCK) that the units of work currently
shunted for indoubt failure (RMGCSHIN) have been waiting in this condition
so far.
Reset characteristic: reset to zero
|
Current shunted UOWs for resource failure | RMGCHSHR | is the current number of units of work that have been
shunted for commit/backout failure because a local resource manager was not
able to perform commit/backout processing at this time on behalf of the UOW
during syncpoint
Reset characteristic: reset to zero
|
Current time shunted for resource failure | RMGCSHTR | is the total time (STCK) that the units of work currently
shunted for commit/backout (RMGCHSHR) failures have been waiting in this condition
so far.
Reset characteristic: reset to zero
|
DFHSTUP name | Field name | Description |
---|---|---|
Total forces of indoubt action by trandef | RMGIAFTR | is the total number of UOWs that were forced to complete
syncpoint processing, despite losing the connection to the recovery coordinator,
because their transaction definition specified that they could not wait indoubt.
The UOWs would have committed or backed out according to the transaction definition indoubt action attribute, regardless of the actions specified or taken by any other participating region in this distributed UOW. Reset characteristic: reset to zero
|
Total forces of indoubt action by timeout | RMGIAFTI | is the total number of shunted indoubt UOWs that were
forced to complete syncpoint processing, although still unconnected to the
recovery coordinator, because their transaction definition wait for indoubt
timeout value was exceeded.
The UOWs would have committed or backed out according to the transaction definition indoubt action attribute, regardless of the actions specified or taken by any other participating region in this distributed UOW. Reset characteristic: reset to zero
|
Total forces of indoubt action by operator | RMGIAFOP | is the total number of shunted indoubt UOWs that were
forced to complete syncpoint processing, although still unconnected to the
recovery coordinator, through a CEMT, or EXEC CICS, SET UOW command forced a resolution.
The UOWs would have committed or backed out according to the command option, regardless of the actions specified or taken by any other participating region in this distributed UOW. Reset characteristic: reset to zero
|
Total forces of indoubt action by no wait | RMGIAFNW | is the total number of UOWs that were forced to complete
syncpoint processing, despite having the ability to wait indoubt, because
a local resource owner or connected resource manager used by the UOW was unable
to wait indoubt.
The UOWs would have committed or backed out according to the transaction definition indoubt action attribute, regardless of the actions specified or taken by any other participating region in this distributed UOW. See the following section on no support for indoubt waiting breakdown. Reset characteristic: reset to zero
|
Total forces of indoubt action by other | RMGIAFOT | is the total number of UOWs that were forced to complete
syncpoint processing, despite having the ability to wait indoubt, because
of reasons other than those described above (for example, a cold start of
the coordinator, level of RMI adapter modification, and resynchronization
errors).
The UOWs would have committed or backed out according to the transaction definition indoubt action attribute, regardless of the actions specified or taken by any other participating region in this distributed UOW. Reset characteristic: reset to zero
|
DFHSTUP name | Field name | Description |
---|---|---|
-Indoubt action forced by TD queues | RMGNWTD | is the number of UOW forces that occurred because the
UOW uses a recoverable transient data queue defined with an indoubt attribute
of WAIT=NO.
Reset characteristic: reset to zero
|
-Indoubt action forced by LU61 connections | RMGNW61 | is the number of UOW forces that occurred because the
UOW uses an LU6.1 intersystem link, which cannot support indoubt waiting.
Note that if an LU6.1 intersystem link can operate as last agent in syncpoint processing the lack of waiting ability is immaterial. For more details about last agent processing, see the CICS Intercommunication Guide. Reset characteristic: reset to zero
|
-Indoubt action forced by MRO connections | RMGNWMRO | is the number of UOW forces that occurred because the
UOW uses an MRO intersystem link to a downlevel CICS region, which cannot support indoubt
waiting.
Note that if an MRO intersystem link can operate as last agent in syncpoint processing the lack of waiting ability is immaterial. For more details about last agent processing, see the CICS Intercommunication Guide. Reset characteristic: reset to zero
|
-Indoubt action forced by RMI exits (TRUEs) | RMGNWRMI | is the number of UOW forces that occurred because the
UOW uses an RMI that declared an interest in syncpoint but could not support
indoubt waiting.
Note that if an RMI intersystem link can operate as last agent in syncpoint processing the lack of waiting ability is immaterial. For more details about last agent processing, see the CICS Intercommunication Guide. Reset characteristic: reset to zero
|
-Indoubt action forced by others | RMGNWOTH | is the number of UOW forces that occurred because the
UOW uses recoverable facilities other than above (for example, terminal RDO),
which invalidate the ability to support indoubt waiting.
Reset characteristic: reset to zero
|
-Total number of indoubt action mismatches | RMGIAMIS | is the total number of UOWs that were forced to resolve
using an indoubt action attribute, whether by definition, option or operator
override (as detailed in the above fields), and on so doing detected an indoubt
action attribute mismatch with a participating system or 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
|
Summary statistics are not available online.
DFHSTUP name | Description |
---|---|
Total number of syncpoints (forward) | is the total number of syncpoint requests to commit forward.
|
Total number of syncpoints (backward) | is the total number of syncpoint requests to commit backward.
For example, EXEC CICS SYNCPOINT ROLLBACK.
|
Total number of resynchronizations | is the total number of resynchronization requests.
|
Total shunted UOWs for indoubt failure | is the total number of UOWs that have lost connection
to their recovery coordinator during syncpoint processing, had to be shunted
for indoubt failure, but have now completed.
|
Total time shunted for indoubt failure | is the total time (STCK) that the UOWs shunted for indoubt
failure ('Total number of shunts for indoubt failure) spent waiting in this
condition.
|
Total shunted UOWs for commit/backout failure | is the total number of UOWs that had to be shunted for
commit/backout failure because a local resource manager was not able to perform
commit/backout processing at that time, but have now completed.
|
Total time shunted for commit/backout failure | is the total time (STCK) that the UOWs shunted for commit/
backout ('Total UOWs shunted for commit/backout failure) failures waited in
this condition, but have now completed.
|
Outstanding shunted UOWs for indoubt failure | is the current number of UOWs that have been shunted for
indoubt failure because the connection to their recovery coordinator during
syncpoint processing was lost.
|
Outstanding time shunted for indoubt failure | is the total time (STCK) that the UOWs currently shunted
for indoubt failure spent waiting in this condition so far.
|
Outstanding shunted UOWs for resource failure | is the current number of UOWs that have been shunted for
commit/ backout failure because a local resource manager was unable to perform
commit/backout processing at that time on behalf of the UOW.
|
Outstanding time shunted for resource failure | is the total time (STCK) that the UOWs currently shunted
for commit/backout failures have been waiting in this condition so far.
|
The following fields detail the reasons why UOWs may have introduced integrity exposures because they were forced to complete prematurely. The UOWs were not allowed to shunt, not capable of shunting, or forced to terminate a shunt, regardless of the outcome. | |
Total forces of indoubt action by trandef | is the total number of UOWs that were forced to complete
syncpoint processing, despite losing the connection to the recovery coordinator,
because their transaction definition specified that they could not wait indoubt.
|
Total forces of indoubt action by timeout | is the total number of shunted indoubt UOWs that were
forced to complete syncpoint processing, although still unconnected to the
recovery coordinator, because their transaction definition wait for indoubt
timeout value was exceeded.
|
Total forces of indoubt action by operator | is the total number of shunted indoubt UOWs that were
forced to complete syncpoint processing, although still unconnected to the
recovery coordinator because the operator (CEMT) forced a resolution.
|
Total forces of indoubt action by no wait | is the total number of UOWs that were forced to complete
syncpoint processing, despite having the ability to wait indoubt, because
a local resource owner or connected resource manager that the UOW used was
unable to wait indoubt. Further details are provided by the section below,
'No support for indoubt waiting breakdown'.
|
Total forces of indoubt action by other | is the total number of UOWs that were forced to complete
syncpoint processing, despite having the ability to wait indoubt, because
of reasons other than those described above (for example, a cold start of
the coordinator, level of RMI adapter modification, and resynchronization
errors).
|
No support for indoubt
waiting breakdown
|
|
The following fields further detail the
reasons why a UOW did not have the ability to wait indoubt (shunt) at the
time of indoubt failure (lost coordinator), and are breakdowns of the field
'Total forces of indoubt action by no wait'. This is because the UOW uses
either recoverable local resources, recoverable resources across intersystem
links, or external resource managers (RMI), which do not have the ability
to wait indoubt. As a result of a resolution of a UOW being forced for this
reason, integrity exposures may occur.
|
|
-Indoubt action forced by TD queues | is the number of UOW forces that occurred because the
UOW was using a recoverable transient data queue defined with an indoubt attribute
of WAIT=NO.
|
-Indoubt action forced by LU61 connections | is the number of UOW forces that occurred because the
UOW used an LU6.1 intersystem link, which cannot support indoubt waiting.
|
-Indoubt action forced by MRO connections | is the number of UOW forces that occurred because the
UOW used an MRO intersystem link to a downlevel CICS region, which cannot support indoubt
waiting.
|
-Indoubt action forced by RMI exits (TRUEs) | is the number of UOW forces that occurred because the
OUW used an RMI that declared an interest in syncpoint but could not support
indoubt waiting.
|
-Indoubt action forced by others | is the number of UOW forces that occurred because the
UOW used recoverable facilities other than above, for example, terminal RDO,
which invalidates the ability to support indoubt waiting.
|
Total number of indoubt action mismatches | is the total number of UOWs that were forced to resolve
using an indoubt action attribute, whether by definition, option, or operator
override (as detailed in the above fields), and detected an indoubt action
attribute mismatch with a participating system or RMI. For example, a participating
system in a distributed UOW resolves its work forward while other systems
back out theirs. The opposite also applies.
|