Defining Transaction Programs

In this procedure, you define transaction programs (TPs) to the local communications server (or client connected to the communications server) so that it knows how to invoke a CICS program invoked from the mainframe.

The following TPs must be defined for inbound function shipping, transaction routing, and distributed program linking:

TP Name	CICS Transaction	Purpose
CPMI	CPMI	Function shipping mirror transaction for ANSI
CSMI	CSMI	Function shipping mirror transaction, general
x'03000000'	CSM3	Function shipping QUEUE model requests¹
CVMI	CVMI	Function shipping mirror transaction for EBCDIC
CRTE	CRTE	Transaction routing transaction
CRSR	CRSR	Internal CICS housekeeping transaction
¹You must upgrade the resource definition file, dfhdrdat, for the CSM3 transaction to be made available to the system as part of the DFHISC group. To do this, execute the caspcupg command. See the caspcupg reference topic for details.

For inbound function shipping, transaction routing, or distributed program linking, you must add the resource group DFHISC to the startup list in the SIT that contains the PCT definitions for the above transactions.

To define a transaction program:

Add a New TP and specify the transaction name. This is used to identify the transaction program to the SNA Server. This TP name should correspond to the transaction that the host system attempts to run on the local CICS region (for example, CRTE).
Setup/configure the transaction that will run on the local CICS region, specifying the region (REGIONNAME), transaction (TTPNAME) and parameters, where:
- REGIONNAME is the name of your region, for example: MSSDEMO
- TPNAME is the name of your transaction program, for example CRTE
- the name of the Local LU Alias as defined to the SNA server for the inbound request. This is the independent LU that you are going to use for your PU as defined to VTAM. The example value is: MCOLU021

Include the 'TP Name' table in the generic section.