XACI Command Reference Manual

RESOLVE XATRANS obj-name[,action {commit|rollback}][,only {prepared|active}], reason tex[,after{now/idle}]t;
The obj-name can be:
[[\system-name.]XAID_HANDLE|*]
action
is the option to commit or rollback a transaction.
only
is the option to resolve prepared or active transaction
REASON text
text is a nonempty string literal up to 70 characters explaining why the transaction is being resolved . This
will be written to the EMS collector if the command is accepted. Strings longer than 70 characters will be
truncated with a warning. Single quoting is required.
XAID_HANDLE
is the unique handle for each global transaction. The complexity of typing or formatting XID is eliminated by
this way.
AFTER
The two options for this argument are NOW and IDLE.
IDLE is not supported in XACI release Version 1.0.
Example:
The following commands will resolve the XA transaction by committing:
XACI>>RESOLVE XATrans \sys.20,action commit, reason ‘text’, after now;
-- Resolve XATrans \sys.20 Successful
XACI>>RESOLVE XATrans *, reason ‘text’;
-- Resolve XATrans \sys.20 Successful
Commands for the XASession Object
This object represents the XA session and is the connection between MXOSRVR (server) and XABroker. The session
with the XABroker is established when the server executes the file open on XABroker process name. The session id (file
handler) helps the XABroker to identify the server which sends a request and to keep related information. For every
session (connection), the XABroker creates the worker thread that executes request from the server. When the session is
closed, the thread exits and all associated transactions in the ACTIVE state are rolled back by the XABroker.
INFO XASESSION
This command will display the information about XA session and provides information about the total number of
prepared, active and heuristically completed transactions, server name, and start time of the session. This is not a sensitive
command and “*” wild card is supported.