DB2TRAN resource definitions

A DB2TRAN defines a transaction, or a group of transactions, associated with a DB2ENTRY, that are additional to the transactions specified in the DB2ENTRY itself.

Only one DB2TRAN definition can be installed for a specific transaction. An attempt to install a second DB2TRAN definition explicitly referring to the same transaction ID will fail.

The DB2TRAN definition allows a DB2ENTRY to have an unrestricted number of transactions associated with it, including names using wildcard characters. You can define any number of DB2TRANs to be associated with a single DB2ENTRY.

For information about installing DB2® transaction resource definitions, see Installing Db2 transaction resource definitions. For information about working with BAS, see Working with BAS Db2 transaction resource definitions.

Syntax

Attributes

DB2TRAN(name): The one to eight character name to identify this Db2® transaction definition.
Acceptable characters:
A-Z a-z 0-9 $ @ # . / - _ % & ? ! : | " = ¬ , ; < >

Valid characters are listed as they render when the code page is IBM®-037. If a different EBCDIC code page is used, be aware of variant characters, as documented in Variant characters.
DESCRIPTION(text): You can provide a description of the resource that you are defining in this field. The description text can be up to 58 characters in length. There are no restrictions on the characters that you can use. However, if you use parentheses, ensure that for each left parenthesis there is a matching right parenthesis. If you use the CREATE command, for each single apostrophe in the text, code two apostrophes.
ENTRY(db2entry): Specifies the name of the Db2 entry definition to which this Db2 transaction definition refers. It is the Db2 entry definition with which this additional transaction should be associated.
GROUP(groupname): Every resource definition must have a GROUP name. The resource definition becomes a member of the group and is installed in the CICS system when the group is installed.
Acceptable characters:
A-Z 0-9 $ @ #

Valid characters are listed as they render when the code page is IBM-037. If a different EBCDIC code page is used, be aware of variant characters, as documented in Variant characters.

Any lowercase characters that you enter are converted to uppercase.

The GROUP name can be up to eight characters in length. Lowercase characters are treated as uppercase characters.
TRANSID(transaction): Specifies the transaction id to be associated with the entry. If the TRANSID is not specified it defaults to the first four characters of the Db2 transaction definition name. The transaction id can include wildcard characters (see Wildcard characters for transaction IDs).

Wildcard characters for transaction IDs

When you define a DB2TRAN resource, you can specify a generic transaction ID using asterisk (*) and plus (+) symbols as wildcard characters.

An asterisk (*) can be added to a transaction name, or used alone, to produce the effect on any value of making it 'wild'. The transaction name specified with an asterisk at the end of the name represents 0-3 unspecified characters in the transaction ID. For example, a TRANSID of T* would represent transaction T, TA, TAB, TABE.
A plus sign (+) is allowed in any position to represent any single character.
An asterisk alone represents any transaction and can act as an alternative pool definition. It differs from a pool by having the additional attribute of the DB2ENTRY of overflowing to the pool when the thread allocation is exhausted.

The rules of matching are that the most specific match is taken. For example, transaction FRED will use DB2ENTRY(1) specifying a generic transaction ID of FRE*, rather than DB2ENTRY(2) specifying a generic transaction ID of F*. Also a '+' is more specific than a '*', eg FRE+ is more specific than FRE*.

If AUTHTYPE(TX) is specified, the actual TXID is passed to Db2 as the primary authorization ID, and not the name that used wildcard characters.

Note that if a DB2TRAN is defined using a generic transaction ID that includes a wildcard, the INQUIRE DB2TRAN command is unable to identify the individual transactions that match the generic transaction ID. For example, you can issue the command

CEMT INQUIRE DB2TRAN(*) TRANSID(ABCD)

to see details of the DB2TRAN with which transaction ABCD is associated. However, if the DB2TRAN is defined using a transaction ID ABC*, the INQUIRE DB2TRAN command is unable to match the DB2TRAN to the transaction ID ABCD, and returns a 'not found' response.