Persistent Transaction Definition

1.10.3 Persistent Transaction Definition - imsresource.desc

Every transaction that is defined in this file is a persistent transaction. Messages for the persistent transaction through program switch is put into /Q. You must create the /Q for every persistent transaction in corresponding queue space configured in this file with the queue name equal to the transaction name before Tuxedo ART for IMS is booted. The following table 26 list the imsresource.desc field names.

Table 1-27 Section Name: [imsresource]

Field	Type	Value	Description	Field in TRANSACT
`QSPACE`	`X(1..16)`	`Mandatory`	Qspace name
`TRANNAMES`	`X(1..1024)`	`Mandatory`	The persistent transaction names. The transaction name could be separated by comma, e.g: TRAN1, TRAN2. Every transaction name could not exceeds 8 bytes.	`N/A`

The following listing shows a script example to create queue space and queues for your reference; you can customerize the script to adapt to the real requirement. For more information, see Oracle Tuxedo /Q guides.

Listing Create Queue Space Example Script

qmadmin ${ARTIMS QSPACE_DEVICE}<<!end
crdl . . .
qspacecreate . . .
qcreate TRAN11 fifo none 2 30 80% 0 ""
qcreate TRAN12 fifo none 2 30 80% 0 ""
!end
--->
qmadmin ${ARTIMS QSPACE_DEVICE}<<!
echo
crdl ${ARTIMS QSPACE_DEVICE} 0 10000
qspacecreate
${QUEUE_SPACENAME}
22839
5000
50
1000
1000
10000
errque
y
16
qopen ${QUEUE_SPACENAME}
qcreate TRAN11 fifo none 2 30 80% 0% ""
qcreate TRAN12 fifo none 2 30 80% 0% ""
qcreate errque fifo none 2 30 80% 0% ""
q
!

For persistent transactions that issue ROLB or ROLL, the retry count for creating the transaction queue should be set to a relatively large number ( up to 2147483647).

Note:

It is suggested that you set the retry count to a number that is more than twice the number that a particular message enters a persistent transaction.

Parent topic: Configuration Files