TRANSACTION resource definitions are used to define alias transactions
for CICS® Web
support. An alias transaction handles the later stages of processing for an
HTTP request, including receiving the request, executing the application's
business logic, construction of the HTTP response and code page conversion
of the HTTP response. Alias transactions can also be used for processing non-HTTP
requests.
CICS supplies
a resource definition for a default alias transaction, CWBA. You may want
to use alternative alias transaction names for the purposes of:
- Auditing, monitoring or accounting
- Resource and command checking for security
- Allocating initiation priorities
- Allocating DB2® resources
- Assigning different runaway values to different CICS application programs
- Transaction class limitation
You can set up as many alias transaction definitions as you want. You
can use the URIMAP definition or an analyzer program to specify the alias
transaction that is required for a particular request.
Important: Make
sure the priorities of the alias transactions used for application-generated
responses (like CWBA) are equal to, or higher than, the priority of the transactions
associated with Web attach tasks (like CWXN or CWXU).
The CICS Performance Guide explains
why this is important.
The CICS Resource Definition Guide has full instructions
for this type of resource definition. When you are following these instructions,
remember: