Where allowed to run:
|
Parameters Examples Error messages |
Use the Add CICS Destination Control Table (ADDCICSDCT) command to add an entry to the DCT.
Each DCT entry defines a destination to which data may be sent. In CICS systems, a destination is a transient data (TD) queue. There are four types of destination:
Create one DCT entry for each transient data queue.
Also use the DCT to define whether or not an intrapartition TD queue may be used for automatic transaction initiation (ATI).
Top |
Keyword | Description | Choices | Notes |
---|---|---|---|
LIB | Library | Communications name, *LIBL, *CURLIB | Required, Positional 1 |
GROUP | Group | Communications name | Required, Positional 2 |
DEST | Destination | Communications name | Required, Positional 3 |
TYPE | Type | *EXTERNAL, *INDIRECT, *INTERNAL, *REMOTE | Required, Positional 4 |
DESTSTS | Status | *ENABLED, *DISABLED | Optional, Positional 5 |
RECOVER | Recoverable | *NO, *YES | Optional, Positional 6 |
TRGLVL | ATI trigger level | 0-32767, 0 | Optional, Positional 7 |
TRANSID | Transaction | Character value, ' ' | Optional, Positional 8 |
DEVTYPE | CICS device indicator | *TERMINAL, *FILE | Optional, Positional 9 |
CICSDEV | CICS device | Communications name, *DEST | Optional, Positional 10 |
FILE | File | Qualified object name | Optional, Positional 11 |
Qualifier 1: File | Name | ||
Qualifier 2: Library | Name, *LIBL, *CURLIB | ||
MBR | Member | Name, *FIRST | Optional, Positional 12 |
OPENOPTION | File processing | *INPUT, *OUTPUT, *READBACK | Optional, Positional 13 |
RCDFMT | Record format | *FIXED, *VARIABLE | Optional, Positional 14 |
STGDEV | Device | *DASD, *TAPE, *DISKETTE, *PRINTER | Optional, Positional 15 |
RMTDEST | Remote destination | Communications name, *DEST | Optional, Positional 16 |
SYSID | Remote CICS system | Communications name | Optional, Positional 17 |
LENGTH | Maximum record length | 0-32767, 0 | Optional, Positional 18 |
PHYDEST | Indirect destination | Communications name | Optional, Positional 19 |
Top |
Enter the name of the OS/400 library that contains the group. Possible values are:
Top |
Enter the name of the group to which this destination control table entry is to be added.
Top |
Enter the destination identifier. This identifier will be used in EXEC CICS commands to access transient data queues. This identifier is also the name that will be used to identify this DCT entry.
Top |
Enter the type of the transient data queue.
Possible values are:
Top |
Indicates whether or not the destination identifier can be used. This parameter is not valid for internal destinations, that is when the type field contains *INTERNAL.
Possible values are:
Top |
Indicates whether or not the transient data queue associated with the destination identifier is recoverable or not recoverable. The field is valid only for an internal destination, that is when the type field contains *INTERNAL.
Note: If this DCT entry is defining CSMT, this field must be *NO.
Possible values are:
Top |
Enter the number of records to accumulate in the queue in order to start automatically the transaction to process them. This is known as automatic transaction initiation (ATI). This field is valid only for internal destinations, that is when the type field contains *INTERNAL.
The transaction identifier is specified in the transaction identifier field.
Possible values are:
Top |
Enter the name of the transaction to be started when the number of records in the queue reaches the trigger level. This field is not valid if the trigger level field contains 0.
When there is not enough space to enter the apostrophes, then enter an ampersand (&) in the first character position to get an extended field size that allows for the entry of additional characters. Blanks are accepted but, when the entry is defined to a control region, anything after the blank is ignored. For example, 'ab g' will be treated as 'ab' in the control region.
Hexadecimal characters should be enclosed in apostrophes and preceded by an uppercase X, for example X'A1A2A3A4'. Any hexadecimal value will be accepted, but, if the value is not a printable character, the entry will be rejected when it is defined to a control region.
Top |
Indicates whether or not a terminal identifier is to be associated with the ATI transaction identifier. This parameter is not valid if the trigger level field contains 0.
Possible values are:
Top |
Enter the identifier of the terminal to be used to run the ATI transaction. This field is valid only when the device type field contains *TERMINAL.
Possible values are:
Top |
Enter the name of the file that will be used by the destination identifier. This field is valid only for an extrapartition destination, that is when the type field contains *EXTERNAL.
Possible library values are:
file-name: Specify the name of the file.
Top |
Enter the name of the member that will be used by the destination identifier. This field is valid only for extrapartition destinations, that is when the type field contains *EXTERNAL.
Possible values are:
Top |
Indicates how the file is to be processed, namely:
This parameter is valid only for extrapartition destinations, that is when the type field contains *EXTERNAL.
Possible values are:
Top |
Indicates the record format of the file. This field is valid only for extrapartition destinations, that is when the type field contains *EXTERNAL.
Possible values are:
Top |
Indicates the storage medium of the file. This parameter is valid only for extrapartition destinations, that is when the type field contains *EXTERNAL.
Possible values are:
Top |
Enter the identifier by which the destination is known on the remote system. This field is valid only for remote destinations, that is when the type field contains *REMOTE.
Possible values are:
Top |
Enter the remote system identifier. The system must have an entry in the remote TCS. This field is valid only for a remote destination, that is when the type field contains *REMOTE.
Top |
Enter the maximum length in bytes of the records in the transient data queue. This value must be the same as that specified for the queue in the remote system. This field is valid only for remote queues, that is when the type field contains *REMOTE.
Possible values are:
Top |
Enter the identifier of the destination to which this DCT entry points. This identifier should have a DCT entry defining the queue as *INTERNAL, *EXTERNAL, or *REMOTE. This field is valid only for indirect destinations, that is when the type field contains *INDIRECT.
Top |
Top |
Top |