RESOLVE INDOUBT (resolve threads left in doubt) on z/OS

Use the MQSC command RESOLVE INDOUBT to resolve threads left in doubt because IBM® MQ or a transaction manager could not resolve them automatically.

Using MQSC commands

For information on how you use MQSC commands, see Performing local administration tasks using MQSC commands.

You can issue this command from sources 2CR. For an explanation of the source symbols, see Sources from which you can issue MQSC commands on z/OS®.

Syntax diagram
Usage notes
Parameter descriptions for RESOLVE INDOUBT

Synonym: RES IND

RESOLVE INDOUBT

Notes:

¹ Valid only when the queue manager is a member of a queue sharing group.

Usage notes

This command does not apply to units of recovery associated with batch or TSO applications, unless you are using the RRS adapter.

Parameter descriptions for RESOLVE INDOUBT

(connection-name)

1 through 8 character connection name.

For a CICS® connection it is the CICS applid.
For an IMS adapter connection, it is the IMS control region job name.
For an IMS bridge connection, it is the IBM MQ queue manager name.
For an RRS connection, it is RRSBATCH.
For a CHIN connection, it is the IBM MQ channel initiator name.

ACTION

Specifies whether to commit or back out the in-doubt threads:

COMMIT: Commits the threads
BACKOUT: Backs out the threads

CMDSCOPE

This parameter specifies how the command runs when the queue manager is a member of a queue sharing group.

' ': The command runs on the queue manager on which it was entered. This is the default value.
qmgr-name: The command runs on the queue manager you specify, providing the queue manager is active within the queue sharing group.
You can specify a queue manager name, other than the queue manager on which the command was entered, only if you are using a queue sharing group environment and if the command server is enabled.

NID

Origin identifier. Specifies the thread or threads to be resolved.

( origin-id )

This is as returned by the DISPLAY CONN command, and is of the form origin-node.origin-urid, where:

origin-node identifies the originator of the thread, except RRSBATCH where it is omitted.
origin-urid is the hexadecimal number assigned to the unit of recovery by the originating system for the specific thread to be resolved.

When origin-node is present there must be a period (.) between it and origin-urid.

You can specify multiple identifiers separated by a commas to resolve more than one thread.

(*)

Resolves all threads associated with the connection.

QMNAME

Specifies that if the designated queue manager is INACTIVE, IBM MQ should search information held in the coupling facility about units of work, performed by the indicated queue manager, that match the connection name and origin identifier.

Matching units of work are either committed or backed out according to the ACTION specified.

Only the shared portion of the unit of work are resolved by this command.

As the queue manager is necessarily inactive, local messages are unaffected and remain locked until the queue manager restarts, or after restarting, connects with the transaction manager.

Examples:


RESOLVE INDOUBT(CICSA) ACTION(COMMIT) NID(CICSA.ABCDEF0123456789)
RESOLVE INDOUBT(CICSA) ACTION(BACKOUT) NID(*)