Overriding Communications Support at Execution Time › Execution Time Configuration › Comm Config Files › Transaction Routing

Transaction Routing

Transactions can be routed to a specified server execution environment by adding one or more TRANCODE lines to the commcfg file. Each TRANCODE line assigns a transaction code to a specific server execution environment.

• Transaction codes are specified using their full name or partial name. Partial names are designated using a trailing "*" (asterisk). A single asterisk indicates all transactions. For example:
  • ABCD is a fully qualified transaction name.
  • ABC* use a wildcard to indicate that transaction routing applies to all transaction codes that begin with the letters "ABC."
  • A* use a wildcard to indicate that transaction routing applies to all transactions codes that begin with the letter "A."

    * the wildcard that indicates transaction routing applies to all transactions.

• The arguments defining a destination for a given TRANCODE entry vary by communications type. Each communications type requires its own unique set of arguments. These arguments identify the target server execution environment. For example:
  • Host Name and Port Number for TCP/IP
  • Queue Manager and Queue Names for MQSeries

For a sample listing of the three types of commcfg files, see the appendix "Comm Config Files." The syntax that is used within each commcfg file type is followed when adding TRANCODE entries. The comments section of each sample commcfg file describes the format for each of the communication types offered and supported by the execution environments that use the given commcfg file (commcfg.ini, commcfg.properties, commcfg.txt).To determine which runtime uses which commcfg file, see Comm Config Files.

The following format of a TRANCODE line is taken from a commcfg.ini file. The use of this file is intended to illustrate the general format of the TRANCODE line. The format of the TRANCODE line for the other files can be found in their respective files that are located in the "Comm Config Files" appendix. The format of a TRANCODE line in commcfg.ini is as follows:

TRANCODE COMMTYPE arguments

where TRANCODE and COMMTYPE are required and arguments depends on the value that is specified for COMMTYPE.

The following formats designate the type TRANCODE lines that can be entered in a commcfg.ini file:

where <...> and {...} are user supplied fields such that <...> are required fields, and {...} are optional.

<TRANCODE> TCP <host> <service/port>

<TRANCODE> ITP <host> <service/port>

<TRANCODE> MQS <Queue Name> <Queue Manager> {Reply Queue Name}

<TRANCODE> MQSC <Queue Name> <Queue Manager> {Reply Queue Name}

<TRANCODE> ECI {CICS system name}

<TRANCODE> CM

<TRANCODE> EJBRMI {Initial Factory Class}{Name Manager URL}

<TRANCODE> WS <baseURL> <contextType>

<TRANCODE> NET <hostName> <portNumber> <protocolCode>

Note: ITP is a version of the CA Gen TCP/IP cooperative flow-processing product that services flows to the CA Gen IMS TCP/IP Direct Connect product.

Some TRANCODE lines that could be coded in a commcfg.ini file are as follows:

ABCD ECI CICS22A

ABC* TCP myhost2 2008

A* CM

* TCP myhost4 2050

This illustration would route an exact trancode match of ABCD to the CICS region identified as CICS22A as defined within IBM Universal Client software. Transactions using ABCD as their trancode would use ECI as its transport mechanism. Trancodes starting with ABC (but not ABCD) would be routed to myhost2, port 2008 using TCP/IP as its transport mechanism. The Client Manager processes Trancodes that begin with A (but not ABC). All others trancodes is routed to myhost4, port 2050 using TCP/IP as its transport mechanism.