Transient data queue (TDQ) EP adapter

You can use the transient data queue (TDQ) EP adapter to emit events to any consumer that can read the event from the TD queue.

You also can use this EP adapter for the following tasks:
  • Processing event data from transient data records.
  • Developing and testing event specifications.
  • Testing whether events are captured when expected and whether they contain the expected data items.

The TDQ EP adapter puts CICS events on the transient data queue that is specified in the EP adapter specification.

The TDQ EP adapter supports the following formats:
The following table shows the emission and transactional modes that the TDQ EP adapter supports. The letter x indicates a supported combination of modes.
Table 1. TDQ EP adapter emission and transactional modes
Event processing adapter Emission mode Transactional mode Notes
SYNC ASYNC TRANS NONTRANS
TDQ x   x   For synchronous event emission, the TD queue must be a recoverable intra-partition queue for transactional events and either an unrecoverable intra-partition queue or an extra-partition queue for non-transactional events. The TDQ EP adapter can be used for testing and debugging as well as production.
x     x
  x x  
  x   x
The following table shows the properties of the TDQ EP adapter.
Table 2. Transient data queue (TDQ) EP adapter properties
Data Element Description
Queue name

The name of the TD queue to which you want the TDQ EP adapter to send events.

If the named TD queue is extra-partition, it must be defined with TYPEFILE(OUTPUT).

For synchronous event emission, the TD queue must be a recoverable intra-partition transient data queue that is defined with RECOVSTATUS(LOGICAL) or RECOVSTATUS(PHYSICAL) for transactional events.
CICS system ID | blank (default) The CICS system ID of the TD queue to which the event is to be written. The default is to leave this field blank for the local system ID.

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

The DFHECEAQ program name and CEPR default transaction are defined for you by CICS.

A logical event contains context and formatted captured data values. The logical event is written to a single transient data queue record.

The event data comes from containers each with a maximum data length of 2097152 KB. Transient data queues support 32763 bytes of data per record; events that exceed this record length are truncated. The TDQ EP adapter supports 4-byte queue names and writes 1 TD queue record per event.