XACI Command Reference Manual

For XABROKER:
[[\system-name.]$XABroker-name]
For XADEF:
[[\system-name.]XA-index]
For XATRANS:
[[\system-name.]XAID-handle]
For XASESSION:
[[\system-name.]session-ID]
\system-name is the name of the system where the target XABroker process is running. The default starts as the
system where XACI is executing. This component is a system name data type, so must begin with a backslash.
●
$XABroker-name is the name of the running XABroker process. $XABR is the default process name and no other
name is allowed for the process.
●
XA-index is the index of the XABroker definition list. This is a unique identifier for each entry in the list.●
XAID-handle is an unique number for each XA transaction. This will avoid typing the complete XID while trying
to administer a specific transaction.
●
session-ID is a connection between XABroker and MXOAS server.●
The syntax is case sensitive only when single or double quotes are used.6.
Empty quoted strings are reported as syntax errors.7.
Users should be careful of the use of “\” and “$” in commands when input is not from the command line or an obey
file. These characters have special meaning to the OSS shell. It is not anticipated that many users will put these
commands in shell scripts, but it is possible using shell “here-document” syntax.
8.
Output Report Syntax Notation and Conventions
The conventions apply to the notation on the output reports themselves. The syntax is defined through examples, and the
user cannot modify the output reports:
All output reports contain a line showing the command and full object name. This could be the only line output for
some commands. Other commands could output same one line for each object accessed.
1.
When a wild card is used in a command and no objects are found, a simple output of "None" is sufficient. When a
specific object is requested by name and not found an error will be output.
2.
Security Requirement
The sensitive commands must be validated and are noted in each command definition below. They change the states,
values, and ADD or delete objects. Users of XACI must use only INFO type commands unless they are
registered as the super ID.
Command Objects
The XABroker has four command objects: XABroker, XADef, XATrans, and XASession. Each command object
represents the process running on the system, represents the definition of XACONFIG table, represents XA transactions,
provides support to get the information, and resolves XA transactions, and represents XA session and is the connection
between MXOSRVR (server) and XABroker.
The commands provided by each command object are listed in the following topics: