Home

 

Parameter descriptions

 

(connection-name)

1 through 8 character connection name.

• For a CICS connection it is the CICS applid.

• For an IMS™ adaptor connection, it is the IMS control region job name.

• For an IMS bridge connection, it is the WebSphere MQ queue manager name.

• For an RRS connection, it is RRSBATCH.

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 is executed when the queue manager is a member of a queue-sharing group.

‘ ’

The command is executed on the queue manager on which it was entered. This is the default value.

qmgr-name

The command is executed on the queue manager you specify, providing the queue manager is active within the queue-sharing group.

We 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.

(*)

Resolves all threads associated with the connection.

QMNAME

Specifies that if the designated queue manager is INACTIVE, WebSphere 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(*)

 

Parent topic:

RESOLVE INDOUBT

sc12920_

 

Home