DCT - Destination Control Table

DCT - TD Destination Control Table

Each entry is used to describe a transient data (TD) destination afterwards referenced in the application. It may be either a file or a terminal.

To define an entry in this table the directive define destination is used.

define destination

Defines a destination entry in the XCICS/TS terminal table (TCT).

define destination

name=<value>,
type=<type>,
format=(fixed|variable),
size=<value>,
[reusable=(yes|no),]
[trigger=<value>,]
[transid=<value>,]
[device=(terminal|file),]
[related=<value>],
[sysid=<value],
[converter_function=<function>, converter_lib=<library>];

There are three possible types of destination:

•	Extrapartitioned

•	Intrapartitioned

•

Indirect

name

It is the symbolic name of the element (max 8 chars). If destination type is Intrapartitioned the name of the resource can be up to 4 characters long.

type

This is the type of the entry and can be :

•	External destination queue (extrapartitioned)

•	Internal destination queue (intrapartitioned)

•	Indirect destination queue (indirect)

format

Record format of the entry: fixed of variable.

size

Record length of the queue element.

reusable

This flag specifies if the resource can or cannot be reused.

trigger

This is the Trigger level counter. It is the value indicating if and when the related transaction is to be automatically started by the ATI (Asynchronous Transaction Interface) .

transid

Identifier of the transaction to be started, when trigger level limit is reached.

device

Terminal or File.

Related resource name.

converter_function

If specified, the routine is dynamically invoked by XCICS when the transaction is started on or by a mainframe system running IBM CICS/TS, to translate the commarea to and from EBCDIC. The routine must conform the XCICS dynamic conversion specs as documented in the XCICS Customization Guide.

converter_lib

specifies the name of the shared library containing the converter routine.