Transaction Configuration File

3.4 Transaction Configuration File

The following table lists the transactions available to application users, with their characteristics.

The filename is transactions.desc.

Table 3-2 Transaction Parameters

Field Name	Type	Values	Description
`TRANSACTION`	`X(4)`	`Mandatory`	Name of the transaction.
`GROUP`	`X(10)`	`Mandatory`	The group notion of CICS allowing a group of related resources to be declared and instantiated or not by a CICS system when starting.
`DESCRIPTION`	`X(60)`	`Optional`	A small textual comment zone for description of the resource.
`PROGRAM`	`X(8)`	`Mandatory`	Name of the first program to be called for this transaction.
`ALIAS`	`X(4)`	`Optional`	Reserved for future use. Used to define an alias for the transaction (usually lower case).
`CMDSEC`	`X(1)`	`N\|Y`	Reserved for future use. The ESM to be called for system programming requests. The default value is `N`.
`CONFDATA`	`X(1)`	`N\|Y` `Optional`	Reserved for future use. As in confidential data: specifies whether CICS is to suppress user data from CICS trace entries when the CONFDATA system initialization parameter specifies HIDETC. If the system initialization parameter specifies `CONFDATA=SHOW`, `CONFDATA` on the transaction definition is ignored. The default value is `N`.
`PRIORITY`	`9(3)`	`1 \| nOptional`	Reserved for future use. Specifies the transaction priority. This 1-to 3-digit decimal value from 0 to 255 is used in establishing the overall transaction processing priority. (Transaction processing priority is equal to the sum of the terminal priority, transaction priority, and operator priority, not exceeding 255.) The higher the number, the higher the priority. The default value is `1`.
`RESSEC`	`X(1)`	`N\|Y`	Specifies whether resource security checking is to be used for resources accessed by this transaction. The default value is `N`.
`RESTART`	`X(1)`	`N\|Y` `Optional`	Reserved for future use. Specifies whether the transaction restart facility is to be used to restart those tasks that terminate abnormally and are subsequently backed out by the dynamic transaction back out facility. The default value is `N`.
`STATUS`	`X(10)`	`ENABLED\| DISABLED`	Specifies the transaction status. ENABLED: Allows the transaction to be executed normally. DISABLED: Prevents the transaction being executed The default value is `ENABLED`.
`TASKDATAKEY`	`X(5)`	`USER \|CICS`	Reserved for future use. The default value is `USER`.
`TPNAME`	`X(64)`	`Optional`	Reserved for future use. Specifies the name of the transaction that may be used by an APPC partner, if the 4-character length limitation of the TRANSACTION attribute is too restrictive. This name can be up to 64 characters in length.
`TRACE`	`X(1)`	`Y\|N Optional`	Reserved for future use. Specifies whether the activity of this transaction is to be traced. The default value is `Y`.
`TRANCLASS`	`X(8)`	`Optional`	Specifies the name of the transaction class to which the transaction belongs. Transactions belonging to a transaction class are subject to scheduling constraints before they are allowed to execute. See Tranclasses Configuration File for more information on the usage of this parameter on the target platform. A Transaction with no tranclass defined will have no other scheduling constraints than the number of servers offering it.
`TWASIZE`	`9(5)`	`Optional`	Specifies the size (in bytes) of the transaction work area to be acquired for this transaction. Specify a 1-to 5-digit decimal value in the range 0 through 32767. The default value is `0`.
`REMOTESYSTEM`	`X(4)`	`Optional`	Specifies the name that identifies the intercommunication link on which the transaction attach request is sent.
`UCTRAN`	`X(1)`	`N\|Y Optional`	Specify whether translate lowercase alphabetic characters to uppercase in transaction name. `Y`: translate lowercase alphabetic characters to uppercase in transaction name. `N`: do not translate lowercase alphabetic characters to uppercase in transaction name. The default value is `N`.

Each transaction is advertised as an Oracle Tuxedo service by CICS Runtime servers, for example, ARTSTRN, ARTATRN…. You can divide the transactions into different groups and assign the groups to different servers using option "–l", so that each server just advertise its own services.

Note:

It is not recommended to define all transactions to one group, as it causes every service to be advertised by every server and results in enormous consumption of Oracle Tuxedo services.

Parent topic: CICS Runtime Configuration Files