Transaction start EP adapter

The transaction start EP adapter extends application behavior in an event-driven way by driving a new CICS® transaction, which uses the information passed to it in the container-based event format. The CICS transaction can run on a CICS system different from the CICS system where the event occurred.

This adapter format can also be used to drive an existing CICS program, which does not need any of the event data, but can be triggered by an event occurrence.

The transaction start EP adapter is provided to call a CICS transaction on the outcome of an event. The transaction is started by the EP adapter and passes the CICS event object as input.

The transaction start EP adapter supports these emission and transactional modes. The letter x indicates a supported combination of modes.
Table 1. Transaction start EP adapter emission and transactional modes
Event processing adapter Emission mode Transactional mode Notes®
SYNC ASYNC TRANS NONTRANS
Transaction start   x x   The transaction start EP adapter does not support assured emission of events.
  x   x
Note: The transaction start EP adapter cannot emit events in a recoverable way and therefore does not support synchronous, transactional event emission.
Table 2. Transaction start EP adapter properties
Data element Description
Transaction ID The identifier for the transaction that is started. This identifier is mandatory and there is no default.
SYSID The system ID of the CICS system where the transaction is to be started. The default is to leave this field blank for the local system ID.
UserID The user ID under which the transaction is started. The default is the CICS default user ID.

The transaction start EP adapter properties apply to the transaction that is started, and not to the EP adapter itself. If you specify a user ID, the transaction runs with this user ID. If you select the option Use Context User Id, the transaction runs under the user ID that captured the event. If neither of them are specified, the transaction runs under the CICS default user ID.

If you install a transaction start EP adapter and specify a transaction user ID without selecting the option Use Context User Id, CICS checks that the installation user ID is authorized as a surrogate user of the transaction user ID. For more information, see Where surrogate user checking applies and RACF definitions for surrogate user checking.

Important: If you select a transaction start adapter for emitting a TASK threshold or TRANCLASS TASK threshold system event, and also select the option Use Context User Id, the context user ID is the CICS region user ID. In this instance, you might want to specify a specific user ID that you want the transaction to use when running.

The transaction start EP adapter calls the transaction as specified in the transaction ID, by START TRANID, passing a channel that contains the formatted data. The transaction and program must be defined to be created by the client or independent software vendors. The data is then passed, unmodified, to the transaction. The transaction start EP adapter sends the event to the started transaction in the CICS container-based event (CCE) format, where the event name values are passed in containers in a channel DFHEP.EVENT.

You specify business events and the CICS EP adapters that they use by using the CICS event binding editor. For more information about adapter properties and supported formats, see Specifying EP adapter and dispatcher information.