trnls {-t [-{a|c}]|-T transaction-global-identifier [-{a|c}] |-bc|-B system-node-ID [-{a|c}]|-rc |-R RM-name + RM-extension [-{a|c}]}

The trnls command displays information about transactions managed by the transaction manager or displays the number of transaction branches.

The following lists the display information for transactions:

1. Transaction global identifier
   An identifier combining a system node ID and a global transaction number (a unique number assigned by the system to manage a global transaction)
   
2. Transaction branch identifier
   An identifier combining a system node ID and a transaction branch number (a unique number assigned by the system to manage a transaction branch)
   
3. Transaction's first status
   Transaction branch processing status
   
4. Transaction's second status
   Status related to the transaction branch process
   
5. Transaction's third status
   Transaction branch communication status
   
6. Process ID
   ID of the process in which the transaction branch is operating
   
7. Server name
   Name of the server activating the transaction branch
   
8. Service name
   Name of the service activating the transaction branch
   
9. Transaction descriptor
   An index number used to identify each transaction branch with the same transaction global identifier
   
10. Branch descriptor
    An index number used to identify a transaction branch that branches out from another transaction branch
    
11. Parent transaction descriptor
    The transaction descriptor of a transaction that has generated the corresponding transaction branch
    The following lists the display information for the number of transaction branches:
    

    1. Transaction global identifier

    An identifier combining a system node ID and a global transaction number (a unique number assigned by the system to manage a global transaction)

    2. System node ID

    OpenTP1 system node ID

    3. Resource manager name

    Name of the resource manager in use under the transaction branch

    4. Number of transaction branches

    Number of transaction branches under processing

-t

Specifies that information about all transactions is to be displayed.

-T transaction-global-identifier~<16 alphanumeric characters>

Specifies the transaction global identifier whose information is to be displayed.

The transaction global identifier can be obtained by the trnls -t command.

-b

Specifies that information about branched transactions is to be displayed.

-B system-node-ID~<8 alphanumeric characters>

Specifies the ID of a system when information about transactions that have branched out to the computer with the specified system node ID is to be displayed.

-r

Specifies that information about transactions connected to resource managers is to be displayed.

-R RM-name + RM-extension~<1-33 alphanumeric characters>

Displays the information about a transaction connected to the resource manager with the specified name.

The resource manager names provided by OpenTP1 are:

OpenTP1_DAM

TP1/FS/Direct Access resource manager name

OpenTP1_TAM

TP1/FS/Table Access resource manager name

OpenTP1_MCF_A

TP1/Message Control resource manager name

To display the information about a transaction connected to a certain MCF, the MCF RM name + MCF RM extension (the manager process identifier for the MCF to be displayed) must be specified.

OpenTP1_MQA

TP1/Message Queue resource manager name

OpenTP1_ISM

ISAM/B resource manager name

The "RM-extension" must be appended when the -i option is specified in the definition command trnstring of the transaction service definition.

-a

Specifies that all the transaction information is to be displayed.

-c

Specifies that the number of transaction branches is to be displayed.

If the -a and -c options are omitted, the information in (1) through (8) above is displayed.

(1) "trnls -ta" specified

The 1. lines and the 2. lines are each displayed on a single line.

2. This information is displayed as many times as there are transactions.

aaaaaaaa

OpenTP1 system node ID (8 characters)

bbbbbbbb

Global transaction number (8 digits)

cccccccc

Transaction branch number (8 digits)

dd...dd

Transaction's first status (up to 20 characters):

BEGINNING

Transaction branch start processing is underway

ACTIVE

Executing

SUSPENDED

Suspended

IDLE

Changing to synchronous point processing

PREPARE

Under commit (phase 1) processing

READY

Waiting for commit (phase 2) processing

HEURISTIC_COMMIT

Heuristic decision commit processing is underway

HEURISTIC_ROLLBACK

Heuristic decision rollback processing is underway

COMMIT

Commit processing is underway

ROLLBACK_ACTIVE

Waiting for rollback processing

ROLLBACK

Rollback processing is underway

HEURISTIC_FORGETTING

Transaction branch termination processing after heuristic decision is underway

FORGETTING

Transaction branch termination processing is underway

e

Transaction's second status (1 character):

u

User server executing in a user server process

r

Transaction branch recovery processing in a transaction recovery process

p

Waiting for completion of other transaction branch recovery processing in a transaction recovery process

If the first status is READY and the root transaction branch is not on the same computer, the transaction will be placed on user instruction wait status. If you are using the XA resource service, the transaction will be placed in wait state for instructions from the XA resource service.

f

Transaction's third status (1 character):

s

Under sending

r

Under receiving

n

Not under sending/receiving

gg...gg

Process ID (decimal)

hh...hh

Server name (up to 8 characters)

ii...ii

Service name (up to 32 characters) (for SUP, this item is blank)

jjjjjjjjjj

Transaction descriptor (decimal)

kkkkkkkkkk

Branch descriptor (decimal) (for the root transaction branch, "**********" is displayed)

llllllllll

Parent transaction descriptor (decimal) (for the root transaction branch, "**********" is displayed)

Note

The term "under sending" or "under receiving" refers to synchronization between transaction branches.

(2) "trnls -tc" or "trnls -T transaction-global-identifier -c" specified

1. This information is displayed as many times as there are global transactions.

aaaaaaaa

OpenTP1 system node ID (8 characters)

bbbbbbbb

Global transaction number (8 digits)

ccccc

Number of transaction branches in the global transaction (decimal)

(3) "trnls -bc" or "trnls -B system-node-ID -c" specified

1. This information is displayed as many times as there are computers executing transactions.

aaaaaaaa

OpenTP1 system node ID (8 characters)

bbbbb

Number of transaction branches currently being executed on the corresponding computer (decimal)

(4) "trnls -rc" or "trnls -R RM-name+RM-extension-c" specified

1. This information is displayed as many times as there are resource managers executing transactions.

aa...aa

Resource manager name + resource manager extension (up to 33 characters)

bbbbb

Number of transaction branches currently being executed on the corresponding resource manager (decimal)

(5) -a and -c options both omitted

1. This information is displayed as many times as there are transactions.

aaaaaaaa

OpenTP1 system node ID (8 characters)

bbbbbbbb

Global transaction number (8 digits)

cccccccc

Transaction branch number (8 digits)

dd...dd

Transaction's first status (up to 20 characters) (for details, see (1) above)

e

Transaction's second status (1 character) (for details, see (1) above)

f

Transaction's third status (1 character) (for details, see (1) above)

gg...gg

Process ID (decimal)

hh...hh

Server name (up to 8 characters)

ii...ii

Service name (up to 32 characters) (for SUP, this item is blank)

Message ID	Description	Output destination
KFCA00970-E	Processing error occurred during trnls command execution.	Standard error output
KFCA00975-I	Help message	Standard output
KFCA00978-E	Usage of the trnls command is invalid.	Standard error output
KFCA00979-E	trnls command execution environment has not been set up.	Standard error output

As many transactions started from a CUP (Client User Program) as the maximum number of processes specified in parallel_count of the client service definition can be executed at the same time. The status of the transactions executing on these processes can be checked by the trnls command.

Executing this command displays a server name as _clttrn.