|
TRANSACTION resource definitions are used to define alias transactions for XCICS 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.
XCICS 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 XCICS 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.
| • | Your alias transaction definition must use the XCICS-supplied alias program "dfhweb" . The alias program calls the user application program that you have specified to process the request. |
| • | Your alias transaction definition must be a local transaction. |
Example
define transaction name=MWEB, program=dfhweb, twa=512, protection=1;
| 
